Support bootstraping openstack provider controllers with multiple networks

[Alvaro Uria]

I'm filing this bug to keep track of its resolution as it seems it is being worked out for the 20.04 release (per [1]).

When Juju is backed by the openstack provider, a single tenant network (and optionally, an external network associated as floating IP) can be defined. There are cases where the controller can access internet via a tenant network, but needs to be attached to a different one to reach the OpenStack API endpoints.

Two things happen now:
1) If only attached to the network with access to the API endpoints: bootstrap will hang because "apt" can't be run (firewall dropping such access)

2) If only attached to the tenant network with internet access: bootstrap will reach its last step, gathering details of the nova instance where the controller has been bootstrapped. This step will fail because the nova API is not reachable.

Using "--primary-network" (mandatory), "--external-network" (optional) and "--network" (optional and specified multiple times) would help associate an external network to a primary tenant network, and also specify as many secondary networks as wanted. The default route should be via the primary network.

1. https://discourse.jujucharms.com/t/bootstrap-controller-patched-to-2-networks-openstack-provider/2322

[Pen Gale (pengale)]

This did not make it into the work for 20.04, and it is a feature, rather than a bug.

Removing it from the rc-1 milestone.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.