[openstack-dev] [nova] Notification update week 4

Balázs Gibizer balazs.gibizer at ericsson.com
Mon Jan 22 12:20:31 UTC 2018


Here is the status update / focus settings mail for w4.

[High] https://bugs.launchpad.net/nova/+bug/1742962 nova functional
test does not triggered on notification sample only changes
During the zuul v3 migration the project-config generated based on the
zuul v2 jobs. It contained a proper definition of when nova wants to
trigger the functional job. Unfortunately this job definition does not
override the openstack-tox-functional job definition from the
openstack-zuul-jobs repo. This caused that the openstack-tox-functional
(and functional-py35) jobs were not triggered for certain commits. The
fix is to create a nova specific tox-functional job in tree. Patches
has been proposed:
* https://review.openstack.org/#/c/533210/ Make sure that functional
test triggered on sample changes
* https://review.openstack.org/#/c/533608/ Moving nova functional test
def to in tree
In general we have to review all nova jobs in the project-config and
move those in-tree that try to override parameters of the job
definitions in openstack-zuul-jobs repo.

[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
Patch has been proposed: https://review.openstack.org/#/c/529194/
Dan left feedback on it and I accept his comment that this is mostly
papering over a problem that we don't fully understand how can happen
in the first place. In the other hand I don't know how can we figure
out what happend. So if somebody has an idea then don't hesistate to
tell me. This bug is still stuck.

[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
Thanks for Takashi we have multiple patches needing only a second +2:
* https://review.openstack.org/#/c/482148 Transform instance-evacuate 
* https://review.openstack.org/#/c/465081 Transform 
instance.resize_prep notification
* https://review.openstack.org/#/c/482557 Transform 
instance.resize_confirm notification

Also there are patches ready for cores to review:
* https://review.openstack.org/#/c/403660 Transform instance.exists
* https://review.openstack.org/#/c/410297 Transform missing delete
* https://review.openstack.org/#/c/476459 Send soft_delete from context

Introduce instance.lock and instance.unlock notifications
A specless bp has been proposed to the Rocky cycle
Some preliminary discussion happened in an earlier patch

Add the user id and project id of the user initiated the instance
action to the notification
A new bp has been proposed
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
We have to be carefull to approve these type of commits until the
solution for https://bugs.launchpad.net/nova/+bug/1742962 merged as
functional tests could be broken silently.

Weekly meeting
The next meeting will be held on 23th of January on #openstack-meeting-4


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180122/9d5ad3db/attachment.html>

More information about the OpenStack-dev mailing list