yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

I'm going to close this as wishlist and track it under this blueprint:

https://blueprints.launchpad.net/openstack/?searchtext=add-notification-
for-server-groups

** Changed in: nova
   Importance: Undecided => Wishlist

** Changed in: nova
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1637635

Title:
  security_groups not present in server notifications

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  This is a follow-up to https://bugs.launchpad.net/nova/+bug/1637634
  which has some more background; this bug report is one of several
  noting some discrepancies between nova's server API and create/update
  notifications.

  An example API response to retrieve a server's information is at
  http://paste.openstack.org/show/xbv2CwtHnhhl1nLLiJeN/

  An example compute.create.end notification is at
  http://paste.openstack.org/show/zG5aJeUpC3LAGr0J0P2T/

  An example compute.update.end notification is at
  http://paste.openstack.org/show/uwh1izVsaW5eg7zDrgFm/

  'security_groups' is listed by the API but not by notifications (and
  in addition, adding/removing security groups from an instance results
  only in notifications related to the neutron port attached to the
  instance).

  If it's undesirable to add security_groups to notificaitons (which
  would be understandable given they're maintained by a separate
  service) we need to decide whether to remove them from Searchlight's
  representation of a server.

  Also related and useful to us:
  https://bugs.launchpad.net/nova/+bug/1438338

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