yahoo-eng-team team mailing list archive

[Doug Wiegley <dougwig@xxxxxxxxxxx>]

This was discussed at the summit, and the impetus for tags was to pass
meta from the api layer to the drivers, which is explicitly against its
listed use cases, because it leaks implementation details to end users.

The alternative discussed was finishing the flavors framework, which has
a notion of passing metadata to drivers, in an end user agnostic manner
(very much vendor not agnostic for the operator, but they can configure
their cloud however they want.)

Closing after that discussion, please re-open if you have another use
case in mind.

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

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

Title:
  [RFE]Add tag extension to Neutron-Lbaas Resources

Status in neutron:
  Won't Fix

Bug description:
  [Use-cases]
  - Supporting tag functionality as part of LBaaSv2
  Implement tag extension support for LBaaSv2 objects such as Listener, Pool and PoolMember objects.

  [Limitations]
  In the Mitaka release Neutron was introduced with the tag extension but unfortunately tags are limited to Neutron project. From the documentation and and comments in the implementation code it is clear that the intent is to extend tags to other Neutron modeled objects.

  [Enhancement]
  
- Add tag support to LBaaSv2 Objects
  Extend the tag supported resources of Neutron to LBaaSv2 objects such as Listener, Pool and PoolMember.

  - Extend existing API

  Add the support for tags to the Neutron-Lbaas objects API.

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