openstack: allow only bootstrap node to get floating-ip

[David Britton]

In one typical openstack environment deployment, access to the private ip range is limited. In order to get to the instance a floating ip needs to be allocated. With recent advancements in juju including juju ssh jumping through the bootstrap node, only user visialbe services need this floating IP. It would be nice if it could be allocated in a new manner

If you specify 'floating-ip: only-on-bootstrap' in your environments, or "floating-ip-only-for-bootstrap: true", then only the bootstrap node would get a floating ip, other nodes would only be usable as "backend services".

Perhaps if you ran "juju expose" it would associate the floating ip at that point.

Just to be clear, I think the current behavior is great, this would be just another option that some orgs may want.

[Curtis Hovey (sinzui)]

This issues has been reported before bug I cannot find it. Maybe it was wrongly closed. This issue might be fixed by bug 1287662 which asks that juju support assigning and removing floating-ip. If juju could
    juju add-floating-ip 0
then we don't need another config setting.

[Andreas Hasenack (ahasenack)]

I think bootstrap wouldn't finish without a floating ip in this scenario, so it's not possible to call juju add-floating-ip 0 after the fact.

[Anastasia (anastasia-macmood)]

Re-targeting for Juju 2.x

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

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