lbaas multiple instance interface
Bug #1241709 reported by
Kevin Fox
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Won't Fix
|
Undecided
|
George Peristerakis |
Bug Description
If you have an instance with multiple ip's, there is no way to select which one to use when adding it as a member of a load balancer via horizon.
Changed in horizon: | |
assignee: | nobody → George Peristerakis (george-peristerakis) |
status: | Confirmed → In Progress |
Changed in horizon: | |
milestone: | icehouse-1 → icehouse-2 |
Changed in horizon: | |
milestone: | icehouse-2 → icehouse-3 |
Changed in horizon: | |
milestone: | icehouse-3 → icehouse-rc1 |
Changed in horizon: | |
milestone: | icehouse-rc1 → next |
tags: | removed: lbaas |
Changed in horizon: | |
milestone: | next → none |
To post a comment you must log in.
According to LBaaS API spec, members should belong to a pool subnet_id.
Horizon LBaaS member creation form needs to be improved from the following points:
- Member candidates should be listed per port instead of per instance (as the bug report describes)
- Member candidates is better to be listed dynamically based on a selected pool.
- Check selected members belong to a subnet_id of a selected pool.