yahoo-eng-team team mailing list archive

[Doug Wiegley <dougwig@xxxxxxxxxxx>]

You're right, but the ship has sailed, and backwards compat is king.  If
you can come up with a way of supporting the old way and a new
consistent way at the same time, please re-open as an RFE.

** Changed in: neutron
       Status: New => Won't Fix

** Tags added: lbaas

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1571900

Title:
  Neutron-LBaaS v2:  "Add member to pool" and "Create new health
  monitor" should be consistent

Status in neutron:
  Won't Fix

Bug description:
  Since health monitors and members are sub-resources of pools, they
  should both be created/retrieved/updated/deleted the same way.

  See: 
  https://wiki.openstack.org/wiki/Neutron/LBaaS/API_2.0#Create_a_Health_Monitor
  vs.
  https://wiki.openstack.org/wiki/Neutron/LBaaS/API_2.0#Add_a_New_Member_to_a_Pool

  
  Result: In members, the pool_id is part of the URI.  However, in health_monitors, it becomes an attribute of the health_monitor object.

  Expected:  CRUD should be similar for health monitors and members.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1571900/+subscriptions