- openstack-discuss - lists.openstack.org

[kolla] Proposing Michal Nasiadka to kolla core team
by Eduardo Gonzalez 22 Mar '19

22 Mar '19

Hi, Is been some weeks since Michal was added to kolla-ansible core team. he's been working hard in kolla too. I think is time for him to be part of the kolla-core group too. Please give a vote before 21 of March. Consider this email my +1 vote. Regards

8 8

manila 8.0.0.0rc1 (stein)
by no-reply＠openstack.org 22 Mar '19

22 Mar '19

Hello everyone, A new release candidate for manila for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/manila/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/manila/log/?h=stable/stein Release notes for manila can be found at: https://docs.openstack.org/releasenotes/manila/

1 0

[kolla] Train summit & virtual PTG planning
by Mark Goddard 22 Mar '19

22 Mar '19

Hi, The Train summit is fast approaching. I've created etherpads for planning this and the proposed kolla virtual PTG. [Summit] Please add your name to the summit etherpad [1] if you plan to attend. There are a number of summit sessions related to kolla. We also have 3 forum sessions: * Tues 12:05 - 12:25: Kolla project update * Tues 13:40 - 14:20: Kolla project onboarding * Weds 11:40 - 12:20: Kolla user feedback I'm signed up to present the first two and moderate the last. If anyone is available to help present the update or onboarding it would be much appreciated. There is an etherpad [2] for the user feedback session, please populate with topics that you'd like to discuss. [Virtual PTG] Please add your name to the virtual PTG etherpad [3] if you are interested in attending a kolla virtual PTG. It will be held some time after the summit, at a time and date to be agreed. I'd expect it to be a full days worth of topics, possibly split over two half days. I've started filling out some topic proposals. Please add your own, then we can vote on which to discuss. I've included a few 'process' things here like bug review, user feedback review & documentation review. Cheers, Mark [1] https://etherpad.openstack.org/p/kolla-train-summit [2] http://etherpad.openstack.org/p/DEN-train-kolla-feedback [3] https://etherpad.openstack.org/p/kolla-train-ptg

1 0

[placement] update 19-11
by Chris Dent 22 Mar '19

22 Mar '19

HTML: https://anticdent.org/placement-update-19-11.html Placement update 19-11! Our little friend has come so far: a `stable/stein` branch was cut this week. # Most Important Soon after RC1 was created, we discovered an issue in the PlacementFixture, used by nova. This was fixed and backported so there will be an RC2, toward the end of next week. In the meantime we should be trying to find release critical bugs and looking for feedback from others. There are (thus far) two PTG related etherpads where you may want to leave some placement-planning-related thoughts: * [Placement](https://etherpad.openstack.org/p/placement-ptg-train) * [Nova and Placement](https://etherpad.openstack.org/p/ptg-train-xproj-nova-placement) # What's Changed * There's been an [initial stein release](https://docs.openstack.org/releasenotes/placement/stein.html). * That release included [install from PyPI](https://docs.openstack.org/placement/latest/install/from-pypi.html) and [Upgrading from Nova](https://docs.openstack.org/placement/latest/upgrade/to-stein.html) instructions. Both of which probably need to be validated by people who are not close to the details. Note that the state of the distro-related docs remains undefined. # House Ordering * The Monday nova scheduler meeting has been renamed to placement. I'll be taking over from Eric as the usual chair as he's busy with other things. While we are still establishing ourselves as a new project, the meeting seems like a good idea, but we should decide if/how we want to phase it out (or into office hours). Feel free to respond with your thoughts (on this or anything else in the post). * I sent out [a message](http://lists.openstack.org/pipermail/openstack-discuss/2019-March/… earlier in the week asking Nova cores to confirm if they'd like to stay on as Placement core. I'll give it a few more days and then remove nova-cores as an included member. * In-tree specs are going to happen (see next section). * A [message was sent](http://lists.openstack.org/pipermail/openstack-discuss/2019-March/004… asking for volunteers for cross project liaisons. # Specs/Blueprint/Features A review is in progress for [in-tree specs](https://review.openstack.org/#/c/645195/), also mentioned in [an email](http://lists.openstack.org/pipermail/openstack-discuss/2019-March/00…. As mentioned there, some specs need to be re-proposed for Train. # Bugs We've got a StoryBoard [project group](https://storyboard.openstack.org/#!/project_group/placement) now. I've started using it. Tagging bugs with `bug` and also making use of `cleanup` and `rfe` tags to indicate things that needs to be cleaned up or feature requests. Please be prepared for these structures to evolve as we gain some understanding of how StoryBoard works. There are still bugs in launchpad and we need to continue to watch there: * Placement related [bugs not yet in progress](https://goo.gl/TgiPXb):14. +1 * [In progress placement bugs](https://goo.gl/vzGGDQ) 6. -1. # osc-placement osc-placement is currently behind by 13 microversions. Pending changes: * [support for 1.19](https://review.openstack.org/#/c/641094/) * [support for 1.21](https://review.openstack.org/#/c/641123/) * [aggregate allocation ratio tool](https://review.openstack.org/#/c/640898/) # Prepping the RC Everything listed last week has been done except for: * Ensuring the install docs are sane and complete. [I have asked](http://lists.openstack.org/pipermail/openstack-discuss/2019-March/00… packaging-related people for their input, as they're the ones who know how their packages are (or will be) set up. # Main Themes Be thinking about what you'd like the main themes to be. Put them on the [PTG etherpad](https://etherpad.openstack.org/p/placement-ptg-train). With regard to the PTG, because we will have limited time, we should do as much of the discussion in email prior to the PTG so that when we get to the PTG we are resolving the difficult problems, not discovering what they are. # Other Placement * <https://review.openstack.org/#/q/topic:cd/gabbi-tempest-job> Gabbi-based integration tests of placement. These recently found a bug that none of the functional, grenade, nor tempest tests did. Not release related, but useful testing. * <https://review.openstack.org/#/q/topic:bp/negative-aggregate-membership> Negative member of aggregate filtering resource providers and allocation candidates. Work on this can go ahead now that `stable/stein` has been cut. * <https://review.openstack.org/#/c/645255/> This is a start at unit tests for the PlacementFixture. It is proving a bit "fun" to get right, as there are many layers involved. Making sure seemingly unrelated changes in placement don't break the nova gate is important. Besides these unit tests, there's discussion on the PTG etherpad of running the nova functional tests, or a subset thereof, in placement's check run. On the one hand this is a pain and messy, but on the other consider what we're enabling: Functional tests that use the real functionality of an external service (real data, real web requests), not stubs or fakes. # Other Service Users We'll hold off here until the final RC is cut. In the future if you stick "placement" somewhere in your commit message I'll probably eventually find your in-progress placement-related changes. A quick scan indicates there's quite a lot of interesting work in progress. # End 🍺🐦 -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

1 0

[cyborg][mistral][powervmstackers][storlets][telemetry][trove] Processing RC1 releases
by Sean McGinnis 22 Mar '19

22 Mar '19

There has been great progress on the RC1 releases at this point, with ~11 hours left until the end of the deadline. There have been a few where the PTL's or release liaisons have indicated they are trying to get the last few patches through before they update the hash in the proposed patches. There are a few projects where we have not had a +1 indicating to go ahead or a -1 to let us know to wait for an update. For these, we will be approving the release patches tomorrow morning (March 22) since they will then be past the RC1 deadline. The list of releases without a response are: Cyborg - cyborg Mistral - mistral - mistral-dashboard - mistral-extra PowerVMStackers - ceilometer-powervm - networking-powervm - nova-powervm Storlets - storlets Telemetry - aodh - panko Trove - trove - trove-dashboard If any owners of these know that things are ready to go, a +1 would be appreciated to let us know to go ahead. Otherwise, this is just a notification that RC1 and a stable/stein branch will be created for these once we are past the deadline. Just let us know if there are any questions, either here or in the #openstack-releases channel. Thanks! Sean

2 1

nova 19.0.0.0rc1 (stein)
by no-reply＠openstack.org 22 Mar '19

22 Mar '19

Hello everyone, A new release candidate for nova for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/nova/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/nova/log/?h=stable/stein Release notes for nova can be found at: https://docs.openstack.org/releasenotes/nova/

1 0

openstack-cyborg 2.0.0.0rc1 (stein)
by no-reply＠openstack.org 22 Mar '19

22 Mar '19

Hello everyone, A new release candidate for openstack-cyborg for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/cyborg/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/openstack-cyborg/log/?h=stable/ste… Release notes for openstack-cyborg can be found at: https://docs.openstack.org/releasenotes/openstack-cyborg/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/openstack-cyborg and tag it *stein-rc-potential* to bring it to the openstack-cyborg release crew's attention.

1 0

neutron-lbaas 14.0.0.0rc1 (stein)
by no-reply＠openstack.org 22 Mar '19

22 Mar '19

Hello everyone, A new release candidate for neutron-lbaas for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/neutron-lbaas/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/neutron-lbaas/log/?h=stable/stein Release notes for neutron-lbaas can be found at: https://docs.openstack.org/releasenotes/neutron-lbaas/

1 0

openstack-congress 9.0.0.0rc1 (stein)
by no-reply＠openstack.org 22 Mar '19

22 Mar '19

Hello everyone, A new release candidate for openstack-congress for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/congress/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/openstack-congress/log/?h=stable/s… Release notes for openstack-congress can be found at: https://docs.openstack.org/releasenotes/openstack-congress/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/congress and tag it *stein-rc-potential* to bring it to the openstack-congress release crew's attention.

1 0

neutron-fwaas 14.0.0.0rc1 (stein)
by no-reply＠openstack.org 22 Mar '19

22 Mar '19

Hello everyone, A new release candidate for neutron-fwaas for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/neutron-fwaas/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/neutron-fwaas/log/?h=stable/stein Release notes for neutron-fwaas can be found at: https://docs.openstack.org/releasenotes/neutron-fwaas/

1 0