On 4/18/2017 3:55 AM, Balazs Gibizer wrote:
Hi,

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

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


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.

Cool, this is a pleasant surprise.



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.

An update from the notifications meeting today, we agreed to just put instance.tags on the instance.update notifications for now. Kevin Zheng has a blueprint to tag an instance during create, and we'll add instance.tags to the instance.create notification as part of that change (including creating a new payload for the instance.create notifications). gibi is going to take over the patch to put instance.tags into the instance.update patch.


The auto_disk_config patch only needs a second +2
https://review.openstack.org/#/c/419185/

I left some comments on this one today, but my concern is mostly the same old story now about putting more fields in the base instance action payload that means it has to go into every instance action payload, but it's really only used in a few operations from what I can tell (create, resize, rebuild, and maybe a couple of others like rescue and unshelve - I suppose migrations too). I'm less concerned about that one though since it does not require lazy-loading fields on the instance object (like we had to do with instance.tags).


The author of the keypairs patch
https://review.openstack.org/#/c/419730/ Anusha told me that she was
moved away from OpenStack so we need somebody to pick this patch up and
rebase it.

I've asked Kevin Zheng to see if he can take over this one or any others in this blueprint series that need help now.


We still need to work on the https://review.openstack.org/#/c/448779/
(Add BDM to InstancePayload) path from testing point of view.


Other items
-----------
No progress from last week, so see the last maill
http://lists.openstack.org/pipermail/openstack-dev/2017-April/115179.html for
details.

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 18th of
April.
https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170418T170000

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


--

Thanks,

Matt

__________________________________________________________________________
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

Reply via email to