yahoo-eng-team team mailing list archive

[Gal Sagie <gal.sagie@xxxxxxxxxx>]

Public bug reported:

In most popular REST API interfaces, objects in the domain model can be
"tagged" with zero or more simple strings. These strings may then be used
to group and categorize objects in the domain model.

Neutron resources in current DB model do not contain any tags, and
dont have a generic consistent way to add tags or/and any other data
by the user.
Adding tags to resources can be useful for management and
orchestration in OpenStack, if its done in the API level
and IS NOT backend specific data.

The following use cases refer to adding tags to networks, but the same
can be applicable to any other Neutron resource (core resource and router):

1) Ability to map different networks in different OpenStack locations
   to one logically same network (for Multi site OpenStack)

2) Ability to map Id's from different management/orchestration systems to
   OpenStack networks in mixed environments, for example for project Kuryr,
    map docker network id to neutron network id

3) Leverage tags by deployment tools

spec : https://review.openstack.org/#/c/216021/

** Affects: neutron
     Importance: Undecided
     Assignee: Gal Sagie (gal-sagie)
         Status: New


** Tags: rfe

** Changed in: neutron
     Assignee: (unassigned) => Gal Sagie (gal-sagie)

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

Title:
  Add tags to neutron resources

Status in neutron:
  New

Bug description:
  In most popular REST API interfaces, objects in the domain model can be
  "tagged" with zero or more simple strings. These strings may then be used
  to group and categorize objects in the domain model.

  Neutron resources in current DB model do not contain any tags, and
  dont have a generic consistent way to add tags or/and any other data
  by the user.
  Adding tags to resources can be useful for management and
  orchestration in OpenStack, if its done in the API level
  and IS NOT backend specific data.

  The following use cases refer to adding tags to networks, but the same
  can be applicable to any other Neutron resource (core resource and router):

  1) Ability to map different networks in different OpenStack locations
     to one logically same network (for Multi site OpenStack)

  2) Ability to map Id's from different management/orchestration systems to
     OpenStack networks in mixed environments, for example for project Kuryr,
      map docker network id to neutron network id

  3) Leverage tags by deployment tools

  spec : https://review.openstack.org/#/c/216021/

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