make fip toplogy check configurable
Bug #1815032 reported by
Edward Hope-Morley
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard Charm |
Fix Released
|
Medium
|
Edward Hope-Morley |
Bug Description
We have seen cases in the field where, instead of having the common topology of one router per project, some users are prefering to have a single router owned by an admin project, connected to the external network and then have non-admin projects use that router for external networking i.e. floating ips. By default Horizon performs a network topology check [1] that prevent projects from associating a floating ip with an instance if the router is not owned by that same project. The proposal here is to make this configurable to enable both use cases.
[1] https:/
Changed in charm-openstack-dashboard: | |
importance: | Undecided → Medium |
Changed in charm-openstack-dashboard: | |
status: | New → In Progress |
Changed in charm-openstack-dashboard: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Patch: https:/ /review. openstack. org/#/c/ 635489/