Re: [openstack-dev] [goals][upgrade-checkers] Oslo library status
Ok. Thx for info Matt. My patch is now marked as WIP and I will wait for release of this lib then. > Wiadomość napisana przez Matt Riedemann w dniu > 08.10.2018, o godz. 18:08: > > On 10/7/2018 4:10 AM, Slawomir Kaplonski wrote: >> I start working on „neutron-status upgrade check” tool with noop operation >> for now. Patch is in [1] >> I started using this new oslo_upgradecheck library in version 0.0.1.dev15 >> which is available on pypi.org but I see that in master there are some >> changes already (like shorted names of base classes). >> So my question here is: should I just wait a bit more for kind of „stable” >> version of this lib and then push neutron patch to review (do You have any >> eta for that?), or maybe we shouldn’t rely on this oslo library in this >> release and implement all on our own, like it is done currently in nova? >> [1]https://review.openstack.org/#/c/608444/ > > I would wait. I think there are just a couple of changes we need to get into > the library (one of which changes the interface) and then we can do a > release. Sean McGinnis is waiting on the release for Cinder as well. > > -- > > 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 — Slawek Kaplonski Senior software engineer Red Hat __ 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
Re: [openstack-dev] [goals][upgrade-checkers] Oslo library status
On 10/7/2018 4:10 AM, Slawomir Kaplonski wrote: I start working on „neutron-status upgrade check” tool with noop operation for now. Patch is in [1] I started using this new oslo_upgradecheck library in version 0.0.1.dev15 which is available on pypi.org but I see that in master there are some changes already (like shorted names of base classes). So my question here is: should I just wait a bit more for kind of „stable” version of this lib and then push neutron patch to review (do You have any eta for that?), or maybe we shouldn’t rely on this oslo library in this release and implement all on our own, like it is done currently in nova? [1]https://review.openstack.org/#/c/608444/ I would wait. I think there are just a couple of changes we need to get into the library (one of which changes the interface) and then we can do a release. Sean McGinnis is waiting on the release for Cinder as well. -- 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
[openstack-dev] [goals][upgrade-checkers] Oslo library status
Hi, I start working on „neutron-status upgrade check” tool with noop operation for now. Patch is in [1] I started using this new oslo_upgradecheck library in version 0.0.1.dev15 which is available on pypi.org but I see that in master there are some changes already (like shorted names of base classes). So my question here is: should I just wait a bit more for kind of „stable” version of this lib and then push neutron patch to review (do You have any eta for that?), or maybe we shouldn’t rely on this oslo library in this release and implement all on our own, like it is done currently in nova? [1] https://review.openstack.org/#/c/608444/ — Slawek Kaplonski Senior software engineer Red Hat __ 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
