Public bug reported:
When launching a Heat stack through Horizon, a user should be able to
choose an existing floating IP address from a drop-down if the user has
specified the custom constraint 'neutron.floating_ip'. If
'neutron.floating_ip' is specified, the appropriate field data is pulled
from neutron regarding the floating IP addresses that exist and are
accessible by this tenant.
* The proposed change would add a custom choice in
dashboards/project/stacks/forms.py
* A corresponding change would be made to retrieve/assemble the field
data in dashboards/project/instances/utils.py
* No changes would be necessary to openstack_dashboard/api/neutron.py
since it already has methods to retrieve this data from the neutron
client.
As I understand it, this would mean that a custom constraint validation
would need to be added to the Heat project, to ensure the floating IP
address is validated as such.
** Affects: horizon
Importance: Undecided
Assignee: Paul Breaux (p-breaux)
Status: New
** Changed in: horizon
Assignee: (unassigned) => Paul Breaux (p-breaux)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1539691
Title:
Horizon should support a 'neutron.floatingip' custom choice when
launching a Heat stack
Status in OpenStack Dashboard (Horizon):
New
Bug description:
When launching a Heat stack through Horizon, a user should be able to
choose an existing floating IP address from a drop-down if the user
has specified the custom constraint 'neutron.floating_ip'. If
'neutron.floating_ip' is specified, the appropriate field data is
pulled from neutron regarding the floating IP addresses that exist and
are accessible by this tenant.
* The proposed change would add a custom choice in
dashboards/project/stacks/forms.py
* A corresponding change would be made to retrieve/assemble the field
data in dashboards/project/instances/utils.py
* No changes would be necessary to openstack_dashboard/api/neutron.py
since it already has methods to retrieve this data from the neutron
client.
As I understand it, this would mean that a custom constraint
validation would need to be added to the Heat project, to ensure the
floating IP address is validated as such.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1539691/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
