yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #42452
[Bug 1515506] Re: There is no facility to name LBaaS v2 Members and Health Monitors
** Changed in: neutron
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1515506
Title:
There is no facility to name LBaaS v2 Members and Health Monitors
Status in neutron:
Fix Released
Status in python-neutronclient:
In Progress
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 :321da8f6263d46bf059163bcf7fd005cf68601bd
Environment:
Ubuntu 14.04, with Devstack All In One, FWaaS , LBaaSv2 and Octavia enabled.
Perceived Severity: Medium
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1515506/+subscriptions
References