Hi, Here is the status update / focus settings mail for w6. Bugs ---- No new bugs and the below bug status is the same as last week. [High] https://bugs.launchpad.net/nova/+bug/1737201 TypeError when sending notification during attach_interface Fix merged to master. Backports have been proposed: * Pike: https://review.openstack.org/#/c/531745/ * Queens: https://review.openstack.org/#/c/531746/ [High] https://bugs.launchpad.net/nova/+bug/1739325 Server operations fail to complete with versioned notifications if payload contains unset non-nullable fields We need to understand first how this can happen. Based on the comments from the bug it seems it happens after upgrading an old deployment. So it might be some problem with the online data migration that moves the flavor into the instance. [Low] https://bugs.launchpad.net/nova/+bug/1487038 nova.exception._cleanse_dict should use oslo_utils.strutils._SANITIZE_KEYS 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 ------------------------------------- The rocky bp has been created https://blueprints.launchpad.net/nova/+spec/versioned-notification-transformation-rocky Every open patch needs to be reproposed to this bp as soon as master opens for Rocky. Introduce instance.lock and instance.unlock notifications --------------------------------------------------------- A specless bp has been proposed to the Rocky cycle https://blueprints.launchpad.net/nova/+spec/trigger-notifications-when-lock-unlock-instances Some preliminary discussion happened in an earlier patch https://review.openstack.org/#/c/526251/ Add the user id and project id of the user initiated the instance action to the notification ----------------------------------------------------------------- A new bp has been proposed https://blueprints.launchpad.net/nova/+spec/add-action-initiator-to-instance-action-notifications As the user who initiates the instance action (e.g. reboot) could be different from the user owning the instance it would make sense to include the user_id and project_id of the action initiatior to the versioned instance action notifications as well. Factor out duplicated notification sample ----------------------------------------- https://review.openstack.org/#/q/topic:refactor-notification-samples+status:open No open patches. We can expect some as soon as master opens for Rocky. Weekly meeting -------------- The next meeting will be held on 6th of February on #openstack-meeting-4 https://www.timeanddate.com/worldclock/fixedtime.html?iso=20180206T170000 Cheers, gibi