Reviewed: https://review.openstack.org/246077 Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=b77985562983e41a2260f21169d8a6275a8c7dc5 Submitter: Jenkins Branch: master
commit b77985562983e41a2260f21169d8a6275a8c7dc5 Author: Reedip Banerjee <[email protected]> Date: Tue Nov 17 07:11:22 2015 +0530 Support for Name field in Members and HMs This patch adds support to enable naming LBaasV2 Members and Health Monitors(HMs) in python-neutronclient. Closes-Bug: #1515506 Change-Id: I27ac48953bb09841234fce6d852f062e2030284e ** Changed in: python-neutronclient Status: In Progress => 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: Fix Released 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
