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

2018-04-16 Thread Balázs Gibizer

Hi,

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

Bugs


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.

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
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
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
-
https://review.openstack.org/#/q/topic:bp/versioned-notification-transformation-rocky+status:open

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
-
https://blueprints.launchpad.net/nova/+spec/trigger-notifications-when-lock-unlock-instances
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
-
https://blueprints.launchpad.net/nova/+spec/add-action-initiator-to-instance-action-notifications
Implementation patch exists but still needs work 
https://review.openstack.org/#/c/536243/



Add request_id to the InstanceAction versioned notifications

https://blueprints.launchpad.net/nova/+spec/add-request-id-to-instance-action-notifications
Implemenation needs a rebase and review 
https://review.openstack.org/#/c/553288/



Sending full traceback in versioned notifications
-
https://blueprints.launchpad.net/nova/+spec/add-full-traceback-to-error-notifications
I have to propose the implementation.

Add versioned notifications for removing a member from a server group
-
The specless bp
https://blueprints.launchpad.net/nova/+spec/add-server-group-remove-member-notifications
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
-
https://review.openstack.org/#/q/topic:refactor-notification-samples+status:open
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
https://www.timeanddate.com/worldclock/fixedtime.html?iso=20180417T17

Cheers,
gibi




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [nova] notification update week 16

2017-04-24 Thread Balazs Gibizer

Hi,

Here is the status update / focus setting mail about notification work
for week 16.

Bugs

[Medium] https://bugs.launchpad.net/nova/+bug/1657428 The instance
notifications are sent with inconsistent timestamp format. We need to
iterate more on the solution I updated last week.
https://review.openstack.org/#/c/421981


Versioned notification transformation
-
The volume_attach and detach notifications are still in focus to support
Searchlight switching to the versioned notifications. Both are ready for
core review:
* https://review.openstack.org/#/c/401992/ Transform
instance.volume_attach notification
* https://review.openstack.org/#/c/408676/ Transform
instance.volume_detach notification
* https://review.openstack.org/#/c/455801/ Transform 
instance.volume_attach.error notification



Searchlight integration
---
changing Searchlight to use versioned notifications
~~~
https://blueprints.launchpad.net/searchlight/+spec/nova-versioned-notifications
bp is a hard dependency for the integration work.

The path on Searchlight side https://review.openstack.org/#/c/453352/
evolves gradually. That code gives feedback about the usability of the 
versioned interface from consumer perspective. Current versioning 
schema that use separate versions per even_type and separate 
independent ve
rsions per subobjects in the payloads makes the interface flexible but 
harder to consume. See some of my comments in PS5 on the above patch 
for details. Also Searchlight code still need to do some transformation

between notification fields and API fields to match them up.


bp additional-notification-fields-for-searchlight
~
Besides volume_attach and volume_detach we need the following patches to
help Searchlight integration:
https://review.openstack.org/#/q/status:open+topic:bp/additional-notification-fields-for-searchlight

The debate about adding the tags to the instance payload now seems to
moving to the direction of adding the tags only to instance.create and
instance.update. This means that the related patch needs to be reworked.

Patches only needs a second +2:
https://review.openstack.org/#/c/419185/ Adding auto_disk_config field 
to InstancePayload
https://review.openstack.org/#/c/407228/ add tags field to 
instance.update notification


The keypairs patch also up to date and ready for review:
https://review.openstack.org/#/c/419730/
We still need to work on the https://review.openstack.org/#/c/448779/
(Add BDM to InstancePayload) path from testing point of view.


Weekly meeting
--
The notification subteam holds it's weekly meeting on Tuesday 17:00 UTC
on openstack-meeting-4 so the next meeting will be held on 25th of
April.
https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170425T17

Cheers,
gibi



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev