After the long silence here is the current notification status info.


New bugs

[Low] https://bugs.launchpad.net/nova/+bug/1757407 Notification sending sometimes hits the keystone API to get glance endpoints As the versioned notifications does not use the glance endpoints info we can avoid hitting the keystone API if notification_format is set to 'versioned'

[Medium] https://bugs.launchpad.net/nova/+bug/1763051 Need to audit when notifications are sent during live migration We need to go throught the live migration codepath and make sure that the different live migartion notifications sent at a proper time.

[Low] https://bugs.launchpad.net/nova/+bug/1761405 impossible to disable notifications The way to turn off emitting notification from nova is to set the oslo_messaging_notifications.driver config option to 'noop'. We need to document this better in the notification devref and in the notification_format config option.

There are two follow up bugs opened based on the Matt's review comments in https://review.openstack.org/#/c/403660:

[Low] https://bugs.launchpad.net/nova/+bug/1764390 Replace passing system_metadata to notification functions with instance.system_metadata usage

[Low] https://bugs.launchpad.net/nova/+bug/1764392 Avoid bandwidth usage db query in notifications when the virt driver does not support collecting such data

Old bugs

[High] https://bugs.launchpad.net/nova/+bug/1737201 TypeError when
sending notification during attach_interface
Fix merged to most of the stable branches. The backport for ocata is still open but has +2 from Tony.

[High] https://bugs.launchpad.net/nova/+bug/1739325 Server operations
fail to complete with versioned notifications if payload contains unset
non-nullable fields
No progress. We still need to understand how this problem happens to
find the proper solution.

[Low] https://bugs.launchpad.net/nova/+bug/1487038
nova.exception._cleanse_dict should use
Old abandoned patches exist but need somebody to pick them up:
* https://review.openstack.org/#/c/215308/
* https://review.openstack.org/#/c/388345/

Versioned notification transformation

There are some patches that only needs a second +2:
* https://review.openstack.org/#/c/460625 Transform aggregate.update_metadata notification * https://review.openstack.org/#/c/403660 Transform instance.exists notification

Introduce instance.lock and instance.unlock notifications
Implementation proposed but needs some work: https://review.openstack.org/#/c/526251/

Add the user id and project id of the user initiated the instance
action to the notification
Implementation patch exists but still needs work https://review.openstack.org/#/c/536243/

Add request_id to the InstanceAction versioned notifications
Implemenation needs a rebase and review https://review.openstack.org/#/c/553288/

Sending full traceback in versioned notifications
I have to propose the implementation.

Add versioned notifications for removing a member from a server group
The specless bp
is pending approval as we would like to see the POC code first. Takashi has been proposed the POC code https://review.openstack.org/#/c/559076/ so we have to look at it.

Factor out duplicated notification sample
Kevin proposed a lot of patches. \o/ Now I have to go and review them.

Weekly meeting
The next meeting will be held on 17th of April on #openstack-meeting-4


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to