yahoo-eng-team team mailing list archive

[Michal Dulko <michal.dulko@xxxxxxxxx>]

Public bug reported:

We have a use case to tag all Neutron resources created by Kuryr-
Kubernetes, as Kubernetes clusters that Kuryr serves may come and go and
it should be possible to easily identify all the leftovers for garbage
collection purpose. As adding a tag is a distinct API call that should
be done after initial POST, it's a bit painful, but in most cases
manageable.

We, however, also use bulk port creation to create and keep some ports
ready in what we call "port pools". In case of bulk creation we need 1+n
calls to Neutron API to create and tag n ports. This is ridiculously
inefficient.

Allowing bulk-tagging, either when doing bulk request itself, or by a
distinct call that accepts list of ID's would be very useful for us.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: rfe

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

Title:
  [RFE] Allow bulk-tagging of resources

Status in neutron:
  New

Bug description:
  We have a use case to tag all Neutron resources created by Kuryr-
  Kubernetes, as Kubernetes clusters that Kuryr serves may come and go
  and it should be possible to easily identify all the leftovers for
  garbage collection purpose. As adding a tag is a distinct API call
  that should be done after initial POST, it's a bit painful, but in
  most cases manageable.

  We, however, also use bulk port creation to create and keep some ports
  ready in what we call "port pools". In case of bulk creation we need
  1+n calls to Neutron API to create and tag n ports. This is
  ridiculously inefficient.

  Allowing bulk-tagging, either when doing bulk request itself, or by a
  distinct call that accepts list of ID's would be very useful for us.

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