September 2020 - openstack-discuss

[elections][placement][blazar] Placement PTL Non-candidacy: Stepping down
by Tetsuro Nakamura 28 Sep '20

28 Sep '20

Hello everyone, Due to my current responsibilities, I'm not able to keep up with my duties either as a Placement PTL, core reviewer, or as a Blazar core reviewer in Wallaby cycle. Thank you so much to everyone that has supported. I won't be able to checking ML or IRC, but I'll still be checking my emails. Please ping me via email if you need help. Thanks. - Tetsuro -- Tetsuro Nakamura <tetsuro.nakamura.bc(a)hco.ntt.co.jp> NTT Network Service Systems Laboratories TEL:0422 59 6914(National)/+81 422 59 6914(International) 3-9-11, Midori-Cho Musashino-Shi, Tokyo 180-8585 Japan

4 3

[Kuryr] Proposing Roman Dobosz for kuryr-kubernetes core
by Michał Dulko 28 Sep '20

28 Sep '20

Hello, I'd like to propose Roman for the core reviewer role in kuryr- kubernetes. Roman was leading several successful development activities during Train and Ussuri cycles: * Switch to use openstacksdk as our OpenStack API client. * Support for IPv6. * Moving VIF data from pod annotations to a KuryrPort CR. He also demonstrated code reviewing skills of an experienced Python developer. In the absence of objections, I'll proceed with adding Roman to the core team next week. Thanks, Michał

5 5

Re: [openstack-ansible] OpenStack Ansible deployment fails, due to lxc containers not having network connection
by Oliver Wenz 28 Sep '20

28 Sep '20

> I would recommend always building an All-In-One deployment in a virtual > machine > so that you have a reference to compare against when moving away from > the 'stock config'. > Documentation for the AIO can be found here > https://docs.openstack.org/openstack-ansible/ussuri/user/aio/quickstart.html I gradually decreased the complexity of my test system towards the 'stock config' to find out what caused the error but it kept showing up. Finally, it vanished when I rebooted the server and my original configuration also completed successfully afterwards. 🤦‍♂️ Thank you for your help and the insights to OSA! Kind regards, Oliver

1 0

[ptl][election][mistral] PTL candidacy
by Renat Akhmerov 28 Sep '20

28 Sep '20

Hi, I'm Renat Akhmerov. I'd like to announce my PTL candidacy for Mistral in Wallaby cycle. In Victoria, we made a huge change related to how we manage actions in Mistral. Previously, all actions were stored in the database and when any Mistral subsystem needed to get info about an action (action definition) it sent a query to DB. So, there wasn't any abstraction responsible for action management. This approach is not flexible and makes refactoring incredibly hard. It also means that it's nearly impossible to deliver actions to the system or alter them in runtime w/o having to reboot a cluster node. In Victoria we introduced the new abstraction called Action Provider. Action providers are fully responsible for delivering actions to Mistral. It is possible to. register many providers in the entry point "mistral.action.providers" in setup.cfg of any Python project (installed within the same Python env as Mistral) and Mistral will be using them all to find actions. So action management is now decoupled from the rest of the system and it's now possible to move away from storing action definitions only in the DB. It's fully up to a particular action provider implentation. Actions can even be dynamically generated, for example, as wrappers around a subset of operating system commands. Another option is. requesting info about actions via some communication protocols like HTTP, AMQP etc. There's still work to polish this all and document properly but the main infrastructure is already available and everyone can implement their own action providers. For W cycle I'd like to proceed with improving Mistral usability (toolset for developing Mistral actions, docs etc.) and address several known scalability issues. As always, anyone is very welcome to join our project. It's a lot of fun to work on it. The best way to get in touch with us is IRC channel #openstack-mistral or the openstack-discuss mailing list (with [mistral] tag in email subject). [1] https://review.opendev.org/#/c/754646/ Cheers Renat Akhmerov @Nokia

1 0

[tripleo][ci] proposing Yatin as tripleo-ci core
by Wesley Hayutin 28 Sep '20

28 Sep '20

Greetings, I really thought someone else had already sent this out. However I don't see it so here we go. I'd like to propose Yatin Karel as tripleo-ci core. You know you want to say +2 :)

19 18

[adjutant][election] PTL candidacy for Wallaby
by Adrian Turjak 28 Sep '20

28 Sep '20

Hello All, I'm submitting myself as the PTL for Adjutant during the W cycle. The focus is as always to continue maintaining the project to ensure it is operating as expected and as bug free as possible. Wallaby will mostly be about cleaning up some internal systems, and minor features to help with custom plugin support. The hope is to also clean up policy/role in this release, and include some elements of that into the plugin layer, and to start working on more useful user management features. Depending on time and resources, we may start work on async worker support to allow some parts of tasks to be processed asynchronously. Cheers, Adrian Turjak

1 0

[all][elections][ptl][tc] Combined PTL/TC Nominations ending soon
by Jeremy Stanley 28 Sep '20

28 Sep '20

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Sep 29, 2020 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. Election statistics[2]: Nominations started @ 2020-09-22 23:45:00 UTC Nominations end @ 2020-09-29 23:45:00 UTC Nominations duration : 7 days, 0:00:00 Nominations remaining : 1 day, 23:12:19 Nominations progress : 71.90% --------------------------------------------------- Projects[1] : 55 Projects with candidates : 18 ( 32.73%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 37 (Adjutant Barbican Blazar Cinder Cloudkitty Cyborg Designate Ec2_Api Freezer Horizon Ironic Karbor Magnum Manila Masakari Mistral Monasca Murano Octavia OpenStack_Charms OpenStack_Helm Oslo Packaging_Rpm Placement Qinling Quality_Assurance Rally Requirements Searchlight Senlin Solum Storlets Tacker Telemetry Trove Watcher Zun) =================================================== Stats gathered @ 2020-09-28 00:32:41 UTC This means that with approximately 2 days left, 37 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.openstack.org/#/q/is:open+project:openstack/election have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for… -- Jeremy Stanley on behalf of the OpenStack Technical Election Officials

1 1

[election][tacker] PTL candidacy for Wallaby
by Yasufumi Ogawa 27 Sep '20

27 Sep '20

Hi, I'd like to propose my candidacy for Tacker PTL in Wallaby cycle. In Victoria release, we have released great features required for the latest ETSI NFV standard and made several improvements for Tacker as and as planed in the last vPTG. We also fix issues for migrating to python3 and Ubuntu focal. As a PTL, I've led the team by proposing not only new features, but also things for driving the team such as documentation or bug tracking. It was something hard, but is running well. In Wallaby cycle, I would like to continue to make Tacker be more useful product from not only telco, but also all users interested in NFV. I believe Tacker will be a good reference implementation for NFV standard. We have planed to make Tacker more feasible not only for VM environment, but also container to meet requirements from industries. - Introduce the latest container technology with ETSI NFV standard. - Reinforce test environment for keeping the quality of the product, not only unit tests and functional tests, but also introduce more sophisticated scheme such as robot framework. - Revise wiki and documentation for covering users more. Regards, Yasufumi Ogawa

1 0

[election][heat] PTL candidacy for Wallaby
by Rico Lin 27 Sep '20

27 Sep '20

Hi all, I would like to announce my candidacy for Heat PTL for Wallaby cycle. Over the past couple of cycles, we running Heat dynamically according to requirements. We never stop encouraging people to join us and provide consistent reviews or fixes as much as we can based on priorities. And if those priorities not working for you, that means you must join the community to help. I believe the goals for the next cycle should be community CI stability, cross-project/community scenario tests to ensure what we deliver to users will get higher quality, also to get rid of legacy mode and move everything to convergence mode, and finally container-native support to make sure we provide usable Orchestration services for the container environment. I believe in new features, so we will try to encourage more features and review them as many as possible, but will not plan for team feature goals unless we can trigger more discussion and hands-on.Thank you for taking my self-nomination into consideration. -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

API short reponse time between the S version and the U version
by Zhi CZ Chang 27 Sep '20

27 Sep '20

1 0