openstack: allow only bootstrap node to get floating-ip
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
juju-core |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
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-
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.
tags: | added: openstack-provider |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → next-stable |
tags: | added: hp-cloud |
Changed in juju-core: | |
status: | Triaged → In Progress |
assignee: | nobody → Dimiter Naydenov (dimitern) |
Changed in juju-core: | |
status: | In Progress → Triaged |
Changed in juju-core: | |
milestone: | 1.21 → 1.22 |
Changed in juju-core: | |
milestone: | 1.22-alpha1 → 1.23 |
Changed in juju-core: | |
assignee: | Dimiter Naydenov (dimitern) → nobody |
milestone: | 1.23 → none |
importance: | High → Medium |
tags: | removed: hp-cloud |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 2.1.0 |
Changed in juju: | |
milestone: | 2.1-rc2 → none |
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.