yahoo-eng-team team mailing list archive

[wuhao <wuhao@xxxxxxxxxxxxxxx>]

Public bug reported:

I'm using liberty to get notifications from nova. And I found a problem
with 'notify_on_state_change'.

In the configuration doc, 'notify_on_state_change' means that "If set,
send compute.instance.update notifications on instance state changes."
Valid values are None, 'vm_state' and 'vm_and_task_state'. However, in
current implementation,  if it's set to 'vm_state',
compute.instance.update notifications will be sent for all the state
changes and it will be a special state change notification when the vm
state changes. So as to 'vm_and_task_state'.

** Affects: nova
     Importance: Undecided
     Assignee: wuhao (wuhao)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => wuhao (wuhao)

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

Title:
  illustration of 'notify_on_state_change' are different from
  implementation

Status in OpenStack Compute (nova):
  New

Bug description:
  I'm using liberty to get notifications from nova. And I found a
  problem with 'notify_on_state_change'.

  In the configuration doc, 'notify_on_state_change' means that "If set,
  send compute.instance.update notifications on instance state changes."
  Valid values are None, 'vm_state' and 'vm_and_task_state'. However, in
  current implementation,  if it's set to 'vm_state',
  compute.instance.update notifications will be sent for all the state
  changes and it will be a special state change notification when the vm
  state changes. So as to 'vm_and_task_state'.

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