RFE There is no facility to name LBaaS v2 Members and Health Monitors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Wishlist
|
Unassigned | ||
python-neutronclient |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
High Level Requirement:
Currently there is no facility to name LBaaS v2 Members and Health Monitors.
Although optional, having the NAME field allows the users to remember specific objects( in this case Health Monitors and Members) , so that any task related to these objects can be done easily , instead of retrieving the IDs of these objects everytime.
The following issue is raised to allow a new parameter 'name' to be added to LBaaS Tables Health Monitors and Members, just like other LBaaS tables ( listener, loadbalancer, pool) have.
Pre-Conditions:
LBaaS v2 is enabled in the system.
Version:
Git ID :321da8f6263d46
Environment:
Ubuntu 14.04, with Devstack All In One, FWaaS , LBaaSv2 and Octavia enabled.
Perceived Severity: Medium
affects: | python-neutronclient → neutron |
summary: |
- There is no facility to name LBaaS v2 members and Health Monitors + There is no facility to name LBaaS v2 Members and Health Monitors |
Changed in neutron: | |
assignee: | nobody → Reedip (reedip-banerjee) |
Changed in python-neutronclient: | |
assignee: | nobody → Reedip (reedip-banerjee) |
Changed in neutron: | |
milestone: | none → mitaka-1 |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in python-neutronclient: | |
milestone: | none → 4.0.0 |
summary: |
- There is no facility to name LBaaS v2 Members and Health Monitors + RFE There is no facility to name LBaaS v2 Members and Health Monitors |
This would also require extension changes to expose this in the API