--fix-network doesn't pass to bay at all

[Eli Qiao]

 55 magnum baymodel-create --name swarmmodel --image-id $image_name \
 56 --keypair-id $KEYPAIR \
 57 --external-network-id $NIC_ID \
 58 --dns-nameserver 10.248.2.5 \
 59 --flavor-id m1.small --docker-volume-size 5 \
 60 --coe swarm --fixed-network 192.168.0.0/24 \
 61 --http-proxy http://10.239.4.160:911/ \
 62 --https-proxy https://10.239.4.160:911/ \
 63 --no-proxy 192.168.0.1,192.168.0.2,192.168.0.3,192.168.0.4,192.168.0.5,192.168.0.6,192.168.0.7 \
 64 --network-driver flannel

the bay created is still use default network in the template file

taget@taget-ThinkStation-P300:~/devstack$ heat stack-show swarmbay-jwvj7j4ecnaj | grep fixed
| | "fixed_network_cidr": "10.0.0.0/24",

Check the commit cb211c165e52867a29d8f6ca705a6017d56f8600 ,we can see that it's revert fixed_network and remove it from template.

[Eli Qiao (taget-9)]

there is a patch working on, but no update for long time. https://review.openstack.org/#/c/252222/

[Ton Ngo (ton-i)]

The option --fixed-subnet does not work either. The template creates a new subnet for the bay and does not reuse the existing subnet.

[Spyros Trigazis (strigazi)]

Could someone who has confirmed this bug provide steps to reproduce?
What is the desired behavior and what is the current behavior?

[Spyros Trigazis (strigazi)]

Marking it as incomplete until more information is provided.

[Spyros Trigazis (strigazi)]

fixed-subnet and fixed-network are used for ironic

[Spyros Trigazis (strigazi)]

Definately fixed-subnet [1], I'll have to check for fixed-network.

[1] https://github.com/openstack/magnum/blob/master/magnum/tests/functional/k8s_ironic/test_k8s_python_client.py#L22

[rajiv (rajiv-kumar)]

If fixed-subnet and fixed-subnet is used only for ironic then it must be validated for others.

[Ton Ngo (ton-i)]

The option fixed-network and fixed-subnet are basically not implemented.
Their meaning:
--fixed-network = an existing Neutron network id or name
--fixed-subnet = an existing Neutron subnet id or name that belongs to the fixed-network

Currently for non-ironic cluster, Magnum will always create a new private network and subnet and ignore these options.
The Heat template needs to be updated to handle this case, probably by switching environments.
The cluster nodes will be attached to the network specified, with IP from the subnet specified.

For simplicity, we can require that these two options are specified together; in other words, the user would manage the networking completely.

[Spyros Trigazis (strigazi)]

There is work in progress to allow passing the fixed-network and fixed-subnet in all drivers.

https://blueprints.launchpad.net/magnum/+spec/decouple-private-network

[Spyros Trigazis (strigazi)]

Now it's possible to pass create a cluster in a predefined network.

NOTE: At the moment you need to pass a subnet too.