# fuel --fuel-version
api: '1.0'
astute_sha: 6db5f5031b74e67b92fcac1f7998eaa296d68025
build_id: 2014-08-14_19-52-36
build_number: '170'
fuellib_sha: a31dbac8fff9cf6bc4cd0d23459670e34b27a9ab
fuelmain_sha: fd58828f404e4298ed338e8f44c6a326cebd31de
mirantis: 'yes'
nailgun_sha: af3d1922bfc21345f81be3454115ab6139675c35
ostf_sha: 09b6bccf7d476771ac859bb3c76c9ebec9da9e1f
production: docker
release: 5.0.1
Through Web-UI, I create an environment, set networks and settings and add 3 nodes (1 controller, 2 computes/osd).
Before deploy changes, through Fuel CLI, I download network settings to modify IP ranges for management and storage networks.
I don't want the starting addresses Fuel determine.
# fuel --debug --env 1 network -d
GET http://127.0.0.1:8000/api/v1/clusters/1/
GET http://127.0.0.1:8000/api/v1/clusters/1/network_configuration/nova_network
Network configuration for environment with id=1 downloaded to /root/network_1.yaml
# vi network_1.yaml
Changes starting addresses in ip_ranges for mgmt and storage networks
# fuel --debug --env 1 network -u
GET http://127.0.0.1:8000/api/v1/clusters/1/
PUT http://127.0.0.1:8000/api/v1/clusters/1/network_configuration/nova_network data={"networking_parameters": {"fixed_network_size": 32, "fixed_networks_cidr": "192.168.78.32/27", "dns_nameservers": ["134.214.100.6", "134.214.100.9"], "floating_ranges": [["192.168.78.200", "192.168.78.254"]], "net_manager": "VlanManager", "fixed_networks_vlan_start": 1363, "fixed_networks_amount": 1}, "networks": [{"name": "public", "ip_ranges": [["192.168.78.131", "192.168.78.199"]], "gateway": "192.168.78.129", "meta": {"name": "public", "notation": "ip_ranges", "render_type": null, "assign_vip": true, "map_priority": 1, "ip_range": ["172.16.0.2", "172.16.0.127"], "vlan_start": null, "render_addr_mask": "public", "cidr": "172.16.0.0/24", "configurable": true, "gateway": "172.16.0.1", "use_gateway": true}, "cluster_id": 1, "vlan_start": 1369, "cidr": "192.168.78.128/25", "id": 2}, {"name": "management", "ip_ranges": [["192.168.77.131", "192.168.77.254"]], "gateway": null, "meta": {"name": "management", "notation": "cidr", "render_type": "cidr", "assign_vip": true, "map_priority": 2, "use_gateway": false, "vlan_start": 101, "render_addr_mask": "internal", "cidr": "192.168.0.0/24", "configurable": true}, "cluster_id": 1, "vlan_start": 1368, "cidr": "192.168.77.128/25", "id": 3}, {"name": "storage", "ip_ranges": [["192.168.77.3", "192.168.77.126"]], "gateway": null, "meta": {"name": "storage", "notation": "cidr", "render_type": "cidr", "assign_vip": false, "map_priority": 2, "use_gateway": false, "vlan_start": 102, "render_addr_mask": "storage", "cidr": "192.168.1.0/24", "configurable": true}, "cluster_id": 1, "vlan_start": 1367, "cidr": "192.168.77.0/25", "id": 4}, {"name": "fixed", "ip_ranges": [], "gateway": null, "meta": {"ext_net_data": ["fixed_networks_vlan_start", "fixed_networks_amount"], "name": "fixed", "notation": null, "render_type": null, "assign_vip": false, "map_priority": 2, "use_gateway": false, "vlan_start": null, "render_addr_mask": null, "configurable": false}, "cluster_id": 1, "vlan_start": null, "cidr": null, "id": 5}, {"name": "fuelweb_admin", "ip_ranges": [["192.168.73.5", "192.168.73.16"]], "gateway": null, "meta": {"notation": "cidr", "render_type": null, "assign_vip": false, "map_priority": 0, "unmovable": true, "use_gateway": false, "render_addr_mask": null, "configurable": false}, "cluster_id": null, "vlan_start": null, "cidr": "192.168.73.0/27", "id": 1}]}
JSON data are the wanted one, with new starting addresses (192.168.77.131 and 192.168.77.3)
When I download again network settings, starting addresses are still the original ones (192.168.77.130 and 192.168.77.2).
When I deploy the environment, the original starting addresses are used.
Fuel API supports ip_ranges setup for public and floating networks only. For all other networks ip_ranges is calculated from CIDR.
You can only change IPs on every node as a workaround:
# fuel --env 1 deployment default
Change nodes' IPs in yaml files.
# fuel --env 1 deployment upload
This will be fixed within https:/