Jump to: navigation, search

Difference between revisions of "Nova/VersionedNotificationTransformation"

(Tasks)
(How to do it)
Line 10: Line 10:
 
** Make sure that you create a new sample file under doc/notificaiton_samples/
 
** Make sure that you create a new sample file under doc/notificaiton_samples/
 
** Make sure that you add a notification sample test under nova/tests/functional/notification_sample_test/
 
** Make sure that you add a notification sample test under nova/tests/functional/notification_sample_test/
* If you got stuck you can ask questions from rlrossit and gibi on IRC or join the weekly notification subteam meeting https://wiki.openstack.org/wiki/Meetings/NovaNotification
+
* If you got stuck you can ask questions from gibi on IRC or join the weekly notification subteam meeting https://wiki.openstack.org/wiki/Meetings/NovaNotification
  
 
== Tasks ==
 
== Tasks ==

Revision as of 13:37, 13 November 2017

Goal

Transform every legacy notification to the new versioned notification framework.

How to do it

Tasks

The master is now open for Ocata so work can continue.

Please use the https://review.openstack.org/#/q/topic:bp/versioned-notification-transformation-ocata topic for the transformation commits


The burndown chart is updated hourly from gerrit. You can see what to transform and what to review there.


There are three types of transformations:

  • category: instance-payload: The easy ones that uses the same payload as instance.delete
  • category: extended-instance-payload: The complex instance.<action> notifications that needs payload extension.
  • category: specific-payload: The rest that needs specific payload


If something doesn't show up on the burndown then please ping gibi on IRC.


Follow up tasks