RFE: allow the operator to control which floating ip pool is selected by default when allocating a new floating ip

Bug #1807527 reported by Lars Kellogg-Stedman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
In Progress
Wishlist
Lars Kellogg-Stedman

Bug Description

There may exist multiple floating ip pools in an OpenStack environment. The operator may prefer that users allocate from a specific pool by default. While this can be partially addresses by documentation, people are terrible at reading things and it would be nice if the operator could control which floating ip network is pre-selected in the "allocate floating ip" dialog.

Ideally this would be something that could be controlled via metadata associated with the network, such as the tagging mechanism.

Changed in horizon:
assignee: nobody → Lars Kellogg-Stedman (larsks)
status: New → In Progress
Revision history for this message
Lars Kellogg-Stedman (larsks) wrote :

Implementation proposed in https://review.openstack.org/#/c/623582/

Revision history for this message
Akihiro Motoki (amotoki) wrote :

It sounds reasonable that some floating IP pool is preferred when a deployment has multiple floating IP pools. From my operator experiences, there are cases where some floating IP pool is a preferred route and other pools are optional. In such cases, it sounds reasonable that the preferred pool is pre-selected.

Changed in horizon:
importance: Undecided → Wishlist
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on horizon (master)

Change abandoned by Lars Kellogg-Stedman (<email address hidden>) on branch: master
Review: https://review.openstack.org/623582

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.