Hi,
Here is the status update / focus settings mail for w36.
Bugs
----
[Medium] https://bugs.launchpad.net/nova/+bug/1699115 api.fault
notification is never emitted
We still have to figure out what is the expected behavior here based on:
http://lists.openstack.org/pipermail/openstack-dev/2017-June/118639.html
[High] https://bugs.launchpad.net/nova/+bug/1706563
TestRPC.test_cleanup_notifier_null fails with timeout
[High] https://bugs.launchpad.net/nova/+bug/1685333 Fatal Python error:
Cannot recover from stack overflow. - in py35 unit test job
The first bug is just a duplicate of the second. It seems the TetRPC
test suite has a way to end up in an infinite recusion.
I don't know about a way to reproduce it localy or to change the gate
env so that python prints out the full stack trace to see where the
problematic call is. Also adding extra log messages won't help as a
timed out test doesn't have the log messages printed to the logs. So
this bug is pretty stuck.
Versioned notification transformation
-------------------------------------
Review backlog is piling up behind
https://blueprints.launchpad.net/nova/+spec/versioned-notification-transformation-queens
Searchlight integration
-----------------------
I opened a follow up bp for Queens:
https://blueprints.launchpad.net/nova/+spec/additional-notification-fields-for-searchlight-queens
I left it in drafting state as I expect the Searchlight team to come
back with some feedback and / or extra needs. I pinged the Searchlight
folks on IRC to get some feedback on this BP.
I think we can still wait for feedback. No reason to rush here.
Small improvements
------------------
* 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.
I will rebase the series and resolve the merge conflicts then I will
ask for feedback about the validity of the current direction.
Weekly meeting
--------------
This week I cannot chair the meeting. Next week most of us will be in
Denver. So the next meeting is expected to be held on 19th of September.
Cheers,
gibi