yahoo-eng-team team mailing list archive

[Steve McLellan <1637634@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

This is a follow up from some summit discussions between the searchlight
and nova teams to note discrepancies between the nova API and
notification payloads. The reason this causes us some issues is that at
scale it becomes far simpler to treat notifications as a complete record
of a servers's state rather than updating individual fields. At the
present time we contact nova's API for some notification events to get
that complete record.

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/

I'll break these into multiple bug reports since some of the fields pose
more difficulties. The fields missing from both create and update
notifications that I think will be easier to add are:

 * tags
 * description
 * key_name
 * locked
 * OS-DCF:diskConfig (some extensions are mapped to alternate field names, but this one and possibly some others are not)


I'm running devstack with it and all services from master as of Oct 28 2016, API microversion 2.35.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: searchlight

-- 
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/1637634

Title:
  Missing fields in compute.end and compute.update notifications

Status in OpenStack Compute (nova):
  New

Bug description:
  This is a follow up from some summit discussions between the
  searchlight and nova teams to note discrepancies between the nova API
  and notification payloads. The reason this causes us some issues is
  that at scale it becomes far simpler to treat notifications as a
  complete record of a servers's state rather than updating individual
  fields. At the present time we contact nova's API for some
  notification events to get that complete record.

  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/

  I'll break these into multiple bug reports since some of the fields
  pose more difficulties. The fields missing from both create and update
  notifications that I think will be easier to add are:

   * tags
   * description
   * key_name
   * locked
   * OS-DCF:diskConfig (some extensions are mapped to alternate field names, but this one and possibly some others are not)

  
  I'm running devstack with it and all services from master as of Oct 28 2016, API microversion 2.35.

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