Open Stack

On Mon, Jul 17, 2017 at 9:32 PM, Matt Riedemann <mriedemos at gmail.com> 
wrote:
> On 7/17/2017 2:36 AM, Balazs Gibizer wrote:
> > Hi,
> >
> > Here is the status update / focus setting mail about notification 
> work
> > for week 29.
> >
> > Bugs
> > ----
> > [Undecided] https://bugs.launchpad.net/nova/+bug/1684860 Versioned
> > server notifications don't include updated_at
> > The fix https://review.openstack.org/#/c/475276/ is in focus but
> > comments needs to be addressed.
> >
> > [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 needs review:  https://review.openstack.org/#/c/476538/
> >
> > [Undecided] https://bugs.launchpad.net/nova/+bug/1702667 
> publisher_id of
> > the versioned instance.update notification is not consistent with 
> other
> > notifications
> > The inconsistency of publisher_ids was revealed by #1696152. Patch 
> needs
> > review: https://review.openstack.org/#/c/480984
> >
> > [Undecided] https://bugs.launchpad.net/nova/+bug/1699115 api.fault
> > notification is never emitted
> > Still no response on the ML thread about the way forward.
> > 
> http://lists.openstack.org/pipermail/openstack-dev/2017-June/118639.html
> >
> > [Undecide] https://bugs.launchpad.net/nova/+bug/1700496 
> Notifications
> > are emitted per-cell instead of globally
> > Fix is to configure a global MQ endpoint for the notifications in 
> cells
> > v2. Patch looks good from notification perspective but affects other
> > part of the system as well: https://review.openstack.org/#/c/477556/
> >
> >
> > Versioned notification transformation
> > -------------------------------------
> > The last week's merge conflicts are mostly cleaned up and there is 
> 11
> > patches that are waiting for core revew:
> > 
> 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:Verified%253C0+AND+NOT+label:Code-Review%253C0
> >
> >
> > If you are affraid of the long list then here is a short list of 
> live
> > migration related transformations to look at:
> > * https://review.openstack.org/#/c/480214/
> > * https://review.openstack.org/#/c/420453/
> > * https://review.openstack.org/#/c/480119/
> > * https://review.openstack.org/#/c/469784/
> >
> >
> > Searchlight integration
> > -----------------------
> > bp additional-notification-fields-for-searchlight
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > The BDM addition has been merged.
> >
> > As a last piece of the bp we are still missing the Add tags to
> > instance.create Notification 
> https://review.openstack.org/#/c/459493/
> > patch but that depends on supporting tags and instance boot
> > https://review.openstack.org/#/c/394321/ which is getting closer to 
> be
> > merged. Focus is on these patches.
> >
> > There are a set of follow up patches for the BDM addition to 
> optimize
> > the payload generation but these are not mandatory for the 
> functionality
> > https://review.openstack.org/#/c/483324/
> >
> >
> > Instability of the notification sample tests
> > --------------------------------------------
> > Multiple instability of the sample test was detected last week. The 
> nova
> > functional test fails intermittenly at least for two distinct 
> reasons:
> > * https://bugs.launchpad.net/nova/+bug/1704423 _test_unshelve_server
> > intermittently fails in functional versioned notification tests
> > Possible solution found, fix proposed and it only needs a second +2:
> > https://review.openstack.org/#/c/483986/
> > * https://bugs.launchpad.net/nova/+bug/1704392
> > TestInstanceNotificationSample.test_volume_swap_server fails with
> > "testtools.matchers._impl.MismatchError: 7 != 6"
> > Patch that improves logging of the failure has been merged
> > https://review.openstack.org/#/c/483939/ and detailed log now 
> available
> > to look at
> > 
> http://logs.openstack.org/82/482382/4/check/gate-nova-tox-functional-ubuntu-xenial/38a4cb4/console.html#_2017-07-16_01_14_36_313757
> >
> >
> >
> > 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 18th of 
> July.
> > 
> https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170718T170000
> >
> > Cheers,
> > gibi
> >
> >
> >
> >
> > 
> __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: 
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> What do you want to do with this blueprint?
> 
> https://blueprints.launchpad.net/nova/+spec/json-schema-for-versioned-notifications
> 
> I don't know if all of the dependencies are done, and it looks like 
> the
> Nova changes are pretty stale. Should we just defer this to Queens?

Unfortunately the assignee left OpenStack during Pike so that BP did 
not progress. We definitely cannot make this to Pike. However I don't 
even know if there is somebody who will have time to work with it in 
Queens. Can we move this to the backlog somehow?

Cheers,
gibi

> 
> 
> --
> 
> Thanks,
> 
> Matt
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev