yahoo-eng-team team mailing list archive

[Matthew Gilliard <matthew.gilliard@xxxxxx>]

Public bug reported:

Currently there is inconsistency in what fields are present in some
instance-lifecycle notifications.  `compute.instance.update` includes
fields `audit_period_beginning` and `audit_period_end` but
`compute.instance.{create,delete}.{start,end}` event types do not, and
we are forced to assume that the the audit period can be inferred from
the timestamp of the notification.

This causes billing teams problems because of:
  - inconsistency between nova events
  - inconsistency between nova and other OS components

I propose adding the audit_period_{beginning,end} fields to those
messages as a fix.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  compute.instance.{create,delete}.{start,end} messages do not include
  audit_period_{beginning,end} fields

Status in OpenStack Compute (Nova):
  New

Bug description:
  Currently there is inconsistency in what fields are present in some
  instance-lifecycle notifications.  `compute.instance.update` includes
  fields `audit_period_beginning` and `audit_period_end` but
  `compute.instance.{create,delete}.{start,end}` event types do not, and
  we are forced to assume that the the audit period can be inferred from
  the timestamp of the notification.

  This causes billing teams problems because of:
    - inconsistency between nova events
    - inconsistency between nova and other OS components

  I propose adding the audit_period_{beginning,end} fields to those
  messages as a fix.

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