- openstack-discuss - lists.openstack.org

[charms] PTL Non-Candidacy
by Frode Nordahl 08 Mar '19

08 Mar '19

Hello all, The Stein cycle is coming to a end and the contributors to the Charms project has done great progress in the key areas we set afoot at the beginning of the cycle. We have also had good participation from the broader community and I hope to see that flourish further in the coming cycle. I believe rotating leadership for open source projects is a good thing and I am happy to pass on the relay baton for the Train cycle. -- Frode Nordahl

1 0

[ptl][kolla][election] Mark Goddard PTL candidacy
by Mark Goddard 08 Mar '19

08 Mar '19

Hi, I'd like to nominate myself to serve as the Kolla PTL for the Train cycle. I've been a user and developer of Kolla and Kolla Ansible since 2016 - initially while at Cray, but my upstream contribution really started in earnest when I joined StackHPC two years ago. I became core in May last year. I am passionate about this particularly operator-driven and community-led project, and started the Kayobe [1] project that allows deployment of an OpenStack control plane to bare metal using Kolla, Kolla Ansible and Bifrost. The flip side of being an operator-driven project is that contributors come and go, and even regular contributors don't always have as much time as they might like. That said, the project is very much alive in terms of code and review contributions. I'd like to help those on the periphery of the project to get more involved. Kolla is also a very global project, with many contributors in Asia particularly. This is really healthy, and I'd like to try out a more APAC-friendly IRC meeting time and a virtual PTG to keep everyone involved. I'm lucky enough to also be an Ironic core (I don't intend for that to change if elected Kolla PTL), and it's been interesting to compare how these two quite different projects operate. The Ironic team does a great job of planning and tracking their work, making use of a whiteboard [2]. I'd like to try adopting a lightweight version of some of these practices in Kolla. As the project matures, stability becomes increasingly important. This is particularly true for the images, which are used by multiple projects. We've been working on improving our CI testing this cycle, but still have a way to go. I want to make sure that work continues, to ensure we can continue to make changes with confidence, whatever the hype cycle throws at us. Thanks for reading, Mark Goddard (mgoddard) [1] https://kayobe.readthedocs.io [2] https://etherpad.openstack.org/p/IronicWhiteBoard

1 0

[networking-odl] check/gate job fail
by Elõd Illés 08 Mar '19

08 Mar '19

Hi, I would appreciate some review / help with openstack/networking-odl: Currently networking-odl check/gate fails (networking-odl-functional-oxygen job) due to Oxygen version of ODL snapshotting was stopped some days ago and now ODL Oxygen is only available on ODL's release page but not on the snapshot page [1]. I've created a small patch that changes to use Oxygen latest release instead of latest snapshot [2]. It solves the issue so just needs some review from networking-odl cores :) [1] http://logs.openstack.org/95/636395/2/check/networking-odl-functional-oxyge… [2] https://review.openstack.org/#/c/641088/ Thanks in advance, Előd

1 0

[all][elections] 'Train' Technical Committee Election Results
by Kendall Nelson 08 Mar '19

08 Mar '19

Hello Everyone! Please join me in congratulating the 7 newly elected members of the Technical Committe (TC). Alexandra Settle (asettle) Graham Hayes (mugsie) Jim Rollenhagen (jroll) Mohammed Naser (mnaser) Rico Lin (ricolin) Thierry Carrez (ttx) Zane Bitter (zaneb) Full results: https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_6c71f84caff2b37c Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all of the candidates, having a good group of candidates helps engage the community in our democratic process. Thank you to all who voted and who encouraged others to vote. We need to ensure your voice is heard. Thank you for another great round! -Kendall (diablo_rojo)

8 7

Re: Using Trove with Rocky
by Darek Król 08 Mar '19

08 Mar '19

Hello Ankit, could you share more details regarding your configuration? How did you create the qcow image ? What do you mean by "the status shows building but the instance is up and running" ? Do you mean Trove service or vm instance with the built image ? What do you see when you run $ openstack server show <vm_name> $ openstack database instance show <vm_name> ? Best, Darek > Message-ID: <CAHSrjzBV3V86YzQtRx3FxMXMOTM68Qk61iqmPDWnkpv36+gEBQ(a)mail.gmail.com> >Content-Type: text/plain; charset="utf-8" >I am trying to use Trove with Rocky. i am able to make a qcow image using >the scripts provided in trove [ disk builder ] . Unfortunately, when i >start trove, the status shows building but the instance is up and running. >I feel that the problem is regarding the improper setup of the trove image. >Can someone guide me with the steps to create a trove image and launch it >using kolla ansible >*With Regards,* >*Ankit Awal*

2 1

[FYI] Inspur's recruiting openstack experts and opendaylight experts
by Yi Yang (杨�D)-云服务集团 08 Mar '19

08 Mar '19

Hi, all Inspur's recruiting openstack experts and opendaylight experts, please contact me at WeChat yang_y_yi0408 or yangyi01(a)inspur.com <mailto:yangyi01@inspur.com> , we can offer very competitive salary in industries.

2 1

[tc] Revamping the Help Needed List
by Lance Bragstad 08 Mar '19

08 Mar '19

The idea of reworking the Help Needed List [0] to better describe the business value of an initiative has cropped up several times recently. I attempted to try and write up what I thought that might look like, but for unified limits and not an existing item on the list [1]. Based on the feedback in that review, it sounds useful to keep doing. As such, I've _attempted_ to do the same for all existing items on the list [2-6]. I'll be completely transparent and apologize if I missed key points in what the original authors were trying to relay. But, that's what we have review for. The patch for reworking the Goal Champions item actually includes an introduction on the intended audiences for the document. Matt suggested this in review and I was having a tough time transitioning between writing for developers and writing for people with resources to delegate, since it felt like most of the original items were written with developers in mind. Based on the feedback from Alan in Vancouver, it seems like we need to be more direct in targeting particular decision makers. Ultimately, making it as clear as possible what each initiative brings, value-wise, to a potential sponsor. At this point, I think we're good to continue in review? But, I at least wanted to describe the reason behind the changes and my perspective in case folks have been focused on other things and need context about these new changes. Thanks, Lance [0] https://governance.openstack.org/tc/reference/help-most-needed.html [1] https://review.openstack.org/#/c/637025/ [2] https://review.openstack.org/#/c/641750/ [3] https://review.openstack.org/#/c/641790/ [4] https://review.openstack.org/#/c/641784/ [5] https://review.openstack.org/#/c/641890/ [6] https://review.openstack.org/#/c/641773/

1 0

[all][tc] Which py3 unit tests to run in Stein
by Zane Bitter 08 Mar '19

08 Mar '19

tl;dr * Continue with the goal to add py36 tests * Add py37 tests if you can * Integration tests are being migrated from Xenial to Bionic before the Stein release. Once that migration happens we will drop py35 tests, but please don't do it yet The TC held a special meeting today to determine which versions of Python 3 to test in the Stein and Train releases. Minutes are here: http://eavesdrop.openstack.org/meetings/tc_python3/2019/tc_python3.2019-03-… The choice of versions for Train is already well-defined under a formula previously agreed by the TC: https://governance.openstack.org/tc/resolutions/20181024-python-update-proc… For Train, we will unit test py27, py36, and py37. We'll capture this in a Zuul template (https://review.openstack.org/641878) and set a project-wide goal for everyone to switch to it *after* Train development opens. In practice this will likely mean that a goal champion will auto-propose self-testing patches to all repos, and projects will be able to test and merge when ready during Train. For Stein we already have a project-wide goal for all projects that support Python3 to unit test on py36: https://governance.openstack.org/tc/goals/stein/python3-first.html#python-3… - please complete that if you haven't already done so! Python3.7 testing is obviously coming up in Train, so if you can add py37 jobs now, please do. Some distros are already shipping on py37 and they would appreciate it. However, this is not _required_. The intention is to switch all integration tests from Xenial to Bionic. For non-legacy Zuul jobs this switch was already planned for next week. The intention now is to switch the bulk of legacy jobs as well - caveats apply, so stay tuned for a separate email from gmann with more details and the schedule. Completing this migration before the end of Stein allows us to drop py35 testing in Train. We *will* eventually drop py35 support in Stein (we don't want it to run on stable/stein), but *not yet*. You can drop py35 once *all* of the integration tests (not just the ones for that project) have migrated to Bionic. thanks, Zane.

1 0

[requirements][FFE] os-brick 2.8.0 ...
by Jay Bryant 08 Mar '19

08 Mar '19

All, os-brick's release got missed last week. We have now corrected that with a patch for os-brick 2.8.0 [1]. It has changes that should go into Stein so we would like to request a Feature Freeze Exception. Thanks! Jay [1] https://review.openstack.org/#/c/641863/

2 1

[ptl][loci][election]
by Chris Hoge 08 Mar '19

08 Mar '19

I am announcing my candidacy for Loci PTL. I stepped in as interim PTL during the previous cycle and was a member of the founding core team. Loci is a project for packaging OpenStack projects into lightweight Docker images. It's currently being used in OpenStack-Helm and StarlingX. We have a small team, a stable project, and low velocity, but still have a number of objectives to work towards in the next cycle. My agenda as PTL will include: * Adopting stable branches. There are enough recent dependency changes that require us to reevaulate our stance on stable branching. * Improving testing. Currently the only thing Loci tests are builds without any functional or integration testing. We will look at ways to run project tests and Tempest integrated tests against a small single node deployment[1] of OpenStack with Loci. I will also continue to encourage adoption of Loci and support use cases in container-based OpenStack deployments. Thank you for support, and if elected I look forward to representing the Loci team and the OpenStack community in the coming months. -Chris Hoge (hogepodge) [1] this, for example https://github.com/hogepodge/locistack

1 0