| 2021-09-16 19:13:11 |
Felipe Reyes |
description |
When using the openstack provider and spaces there is a limitation of using a single network with multiple subnets (see bug 1940334), now when there is an environment like that one there is configuration option to bootstrap juju in a specific subnet, juju will pick up the first subnet listed by openstack.
This limitation can become a more problematic issue when that first subnet is a subnet meant to non management connectivity or simply doesn't even have a dhcp service configured.
When using maas provider it's expected the operator will take advantage of juju-mgmt-space config option to bootstrap in a specific space/subnet/vlan, but when using the openstack provider there are no spaces defined before the bootstrap process. |
When using the openstack provider and spaces there is a limitation of using a single network with multiple subnets (see bug 1940334), now when there is an environment like that one there is no configuration option to bootstrap juju in a specific subnet, juju will pick up the first subnet listed by openstack.
This limitation can become a more problematic issue when that first subnet is a subnet meant to non management connectivity or simply doesn't even have a dhcp service configured.
When using maas provider it's expected the operator will take advantage of juju-mgmt-space config option to bootstrap in a specific space/subnet/vlan, but when using the openstack provider there are no spaces defined before the bootstrap process. |
|
