RFE There is no facility to name LBaaS v2 Members and Health Monitors

Bug #1515506 reported by Reedip
10
This bug affects 2 people
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 :321da8f6263d46bf059163bcf7fd005cf68601bd

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)
Revision history for this message
Brandon Logan (brandon-logan) wrote :

This would also require extension changes to expose this in the API

tags: added: rfe
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron-lbaas (master)

Fix proposed to branch: master
Review: https://review.openstack.org/245664

Changed in neutron:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-neutronclient (master)

Fix proposed to branch: master
Review: https://review.openstack.org/246077

Changed in python-neutronclient:
status: New → In Progress
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote : Re: There is no facility to name LBaaS v2 Members and Health Monitors

Sounds trivial enough. I wonder if this was just overlooked, or there was some rationale behind the lack of names for such LB properties.

Changed in neutron:
importance: Undecided → Wishlist
Changed in python-neutronclient:
importance: Undecided → Wishlist
tags: added: rfe-approved
removed: rfe
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This nearly borderline for not being an RFE to be honest. If the lack of the name field is a genuine mistake, I don't see why we would even track this as RFE, this is so trivial that should be treated as a plain bug report.

Changed in neutron:
milestone: none → mitaka-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron-lbaas (master)

Reviewed: https://review.openstack.org/245664
Committed: https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=cb3ae497c0a6349dfea0a41788b962a4cd3ef3eb
Submitter: Jenkins
Branch: master

commit cb3ae497c0a6349dfea0a41788b962a4cd3ef3eb
Author: Reedip Banerjee <email address hidden>
Date: Fri Nov 13 12:32:27 2015 +0530

    Support for Name field in Members and HMs

    This patch adds support to enable naming LBaasV2 Members and Health
    Monitors(HMs).

    DocImpact

    Closes-Bug: #1515506
    Change-Id: Ieb66386fac3a5a4dace0112838fe9afde212f055

Changed in neutron:
status: In Progress → Fix Committed
Revision history for this message
Thierry Carrez (ttx) wrote : Fix included in openstack/neutron-lbaas 8.0.0.0b1

This issue was fixed in the openstack/neutron-lbaas 8.0.0.0b1 development milestone.

Changed in neutron:
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-neutronclient (master)

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 address hidden>
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
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/python-neutronclient 4.0.0

This issue was fixed in the openstack/python-neutronclient 4.0.0 release.

Akihiro Motoki (amotoki)
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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.