Hi,
Here is the status update / focus setting mail about notification work
for week 26.
Bugs
----
[Undecided] https://bugs.launchpad.net/nova/+bug/1684860 Versioned
server notifications don't include updated_at
Takashi proposed the fix https://review.openstack.org/#/c/475276/ that
only needs a second +2.
[Low] https://bugs.launchpad.net/nova/+bug/1696152 nova notifications
use nova-api as binary name instead of nova-osapi_compute
Agreed not to change the binary name in the notifications. Instead we
make an enum for that name to show that the name is intentional.
Patch has been proposed: https://review.openstack.org/#/c/476538/
[Undecided] https://bugs.launchpad.net/nova/+bug/1699115 api.fault
notification is never emitted
It seems that the legacy api.fault notification is never emited from
nova. More details and the question about the way forward is in a
separate ML thread
http://lists.openstack.org/pipermail/openstack-dev/2017-June/118639.html
[Undecided] https://bugs.launchpad.net/nova/+bug/1698779 aggregate
related notification samples are missing from the notification dev-ref
It is a doc generation bug. Fix and improvement on doc generation has
been proposed https://review.openstack.org/#/c/475349/
[Undecide] https://bugs.launchpad.net/nova/+bug/1700496 Notifications
are emitted per-cell instead of globally
Vitrage tempest test was broken due to missing notifications from
nova-compute caused by the cells devstack change
https://review.openstack.org/#/c/436094/. Revert is on the way
https://review.openstack.org/#/c/477436/. The final solution is to
configure a separate and non cell local transport_url for
notifications. This is already possible with current oslo.messaging
https://docs.openstack.org/developer/oslo.messaging/opts.html#oslo_messaging_notifications.transport_url
Versioned notification transformation
-------------------------------------
Patches needs only a second +2:
* https://review.openstack.org/#/c/402124/ Transform
instance.live_migration_rollback notification
Patches that looks good from the subteam perspective:
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/versioned-notification-transformation-pike+label:Code-Review%253E%253D%252B1+label:Verified%253E%253D1+AND+NOT+label:Code-Review%253C0
Searchlight integration
-----------------------
bp additional-notification-fields-for-searchlight
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
https://review.openstack.org/#/q/topic:bp/additional-notification-fields-for-searchlight+status:open
The next two patches in the series needs just a second +2. The last
patch needs a rebase due to conflict
Small improvements
~~~~~~~~~~~~~~~~~~
* https://review.openstack.org/#/c/428199/ Improve assertJsonEqual
error reporting
* https://review.openstack.org/#/q/topic:refactor-notification-samples
Factor out duplicated notification sample data
This is a start of a longer patch series to deduplicate notification
sample data. The third patch already shows how much sample data can be
deleted from nova tree. We added a minimal hand rolled json ref
implementation to notification sample test as the existing python json
ref implementations are not well maintained.
Weekly meeting
--------------
The notification subteam holds it's weekly meeting on Tuesday 17:00 UTC
on openstack-meeting-4. The next meeting will be held on 27th of June.
https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170627T170000
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
