- openstack-discuss - lists.openstack.org

[ptl][neutron][election] PTL Candidacy
by Miguel Lavalle 12 Mar '19

12 Mar '19

Hello OpenStackers, I write this to submit my candidacy for Neutron PTL during the Train cycle. I have had a blast being the project's PTL for the past three cycles. After everything is said and done, the most rewarding part of this job is to get to work with an amazing group of top notch software engineers from around the World. I will be grateful forever for everything that you all have taught me. So I humbly ask for another chance to be trained during Train. We had a successful Stein cycle, delivering on most of the goals we set for ourselves in Denver: * Delivered most of the implementation of bandwidth based scheduling, that enables Neutron and Nova to guarantee network bandwidth to instances based on QoS policies. * To better serve edge computing use cases, we partnered with the StarlingX team to implement management of network segments ranges dynamically through a new API extension. * Extended Neutron QoS to support L3 router gateway IPs. * Improved the performance of port creation in bulk to better support containers use cases. * Improved the security groups implementation by optimizing the performance of rules creation and making security groups shareable with the RBAC mechanism. * We created the os-ken project, OpenStack community fork of the Ryu library, which will not be supported by its original implementor anymore. os-ken is now maintained by the Neutron project team. * We continued our efforts of de-coupling common functionality from the Neutron repository and moving it to neutron-lib. * We worked hard on past and present community goals, so at the end of Stein Neutron will be completely caught up. * We implemented a successful mentoring program for prospective core reviewers. This enabled us to add three new members to the Neutron team: Nate Johnston, Hongbin Lu and Liu Yulong. We also added Bernard Cafarelli, Ryan Tidwell and Manuel Buil as stable branches, BGP Dynamic Routing and networking-sfc core reviewers, respectively. Moving forward, these are some of the goals that I propose for the team during the Train cycle: * Improve the usability of routed networks by allowing more that one segment per network per compute host. This will enable the scaling up of deployments without being constrained by subnet IP address ranges. * Add the capabillity to tag ports during bulk creation, to better support containers use cases. * Actively continue our collaboration with the StarlingX team to identify and implement better support for edge computing use cases. * Continue the implementation of smart NICs support. * During Stein, we formed a performance sub-team with the aim of improving Neutron's scalability. We will bring this effort to fruition by identifying and implementing areas of improvement based on the characterization work we are doing with osprofiler and the EnOS (Experimental eNvironment for OpenStack) team. * We will continue our efforts of de-coupling common functionality from the Neutron repository and moving it to neutron-lib. * I see myself, with the support of my current employer, actively involved in the project and the community for many cycles in the future. I think, though, that we are getting to a point where it is healthy to pass the baton to a new leader. To that end, I will actively encourage team members to step up to the plate in the next cycle. I will support and help propective candidates every step of the way. Thank you for your consideration and for taking the time to read this Miguel Lavalle (mlavalle)

1 0

[all][ptl]tc] Only 24 hours remaining for PTL nominations
by Jeremy Stanley 12 Mar '19

12 Mar '19

A quick reminder that we are in the last hours for PTL candidate nominations. If you want to stand for PTL, 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. The following projects are still lacking any PTL candidate at this time: Adjutant Congress Glance Heat I18n Magnum Monasca Neutron Octavia OpenStack Helm PowerVMStackers Puppet OpenStack Tacker Telemetry Tripleo Vitrage Zaqar This means that with approximately 1 day left, these 17 projects may be deemed leaderless. In this case the TC will oversee PTL selection as described by [2]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] https://governance.openstack.org/resolutions/20141128-elections-process-for… -- Jeremy Stanley

1 0

[ptl][ironic][election] PTL Candidacy
by Julia Kreger 12 Mar '19

12 Mar '19

Greetings fellow carbon based lifeforms and sentient software programs, I would like announce my candidacy to serve as the Ironic project team leader for the Train cycle, if you will have me. Passion is a funny thing. It drives us and motivates us, but it does not tell us when we are done. And I can say for certain that I am not done. Last cycle we turned the dial to eleven and this cycle we've reached twelve. I suspect we need to re-calibrate the dial and begin a new standard for audio volume measurement. We achieved more than I could have imagined for this past cycle, but not quite what we planned. Our wants, desires, purpose, and meaning are fluid. It is clear to me we evolved because the needs of those we support have changed while keeping a single central theme. To make it easier to deploy and manage bare metal. To continue on this journey, I think we must embrace and extend our operator community. Just as with our use cases and hardware support. We must no longer think of ourselves as only a service with-in the confines of OpenStack. We must view beyond our OpenStack roots while continuing to strengthen them. We can only do this by growing our community. Together, I am sure we can further make bare metal rock. And perhaps, somewhere along the way, we may take over the world. Julia Kreger (TheJulia)

1 0

[ptl][tacker][election] Only one more day to submit your candidacy for Tacker PTL
by Trinh Nguyen 12 Mar '19

12 Mar '19

Hi team, Just so you know that we have only 1 more day left [1] to submit your candidacy for Tacker PTL. Please do it asap. Bests, [1] https://governance.openstack.org/election/ -- *Trinh Nguyen* *www.edlab.xyz <https://www.edlab.xyz>*

1 0

[edge][all] Edge hacking days
by Ildiko Vancsa 12 Mar '19

12 Mar '19

Hi, A few of us in the Edge WG are working on to organize hacking days[1] to ensure we can have some dedicated time to progress with work items as well as speed up the learning phase in areas like identity or image management or bootstrap testing activities. Our thinking is to organize these as virtual events through Google Hangouts or any other tool we prefer to use to keep in contact. We can also leverage conferences to try and organize in person occasions even if not for a full day. Would you be interested in participating? If yes what is the topic/task you would like to work on? Thanks and Best Regards, Ildikó [1] http://lists.openstack.org/pipermail/edge-computing/2019-March/000555.html

1 1

[ptl][cinder][election] PTL Candidacy ...
by Jay Bryant 12 Mar '19

12 Mar '19

All, This letter is to indicate my interest in continuing to serve as the Cinder PTL for the Train release. This would be my fourth release as PTL and am happy to continue leading the Cinder project. Over the last three releases, for which I have been PTL, I have seen Cinder transition from focussing on merging new functionality to focussing on fixing bugs and improving Cinder's stability. This is a natural progression for a project of this type and, I feel, requires the team to take a new approach to how we go forward. During the Train release I think that the team should continue to look at the bugs filed against Cinder and work to address them. We started reducing the number of bugs during Stein and I hope that we can continue that momentum in Train. I also feel that we need to be better about monitoring 3rd Party CI runs and ensure that they are testing what they should be testing. With the move to Python3 ensuring it is being tested and that each driver works with Python3 is going to be essential. Other goals I have during Train include: * Continuing to address how cinderlib fits with Cinder * Continuing to reach out to our users seeking their input for improvement * Continued improvement of core reviewer participation * Increasing the breadth of testing against Cinder I look forward to the continued opportunity to lead the Cinder project. Sincerely, Jay Bryant (jungleboyj)

1 0

[all][ptl][tc] Missing PTL nominations for 31 more teams
by Jeremy Stanley 12 Mar '19

12 Mar '19

A quick reminder that we're still missing "Train" cycle PTL candidate nominations for nearly half our official teams: Adjutant Blazar Chef OpenStack Cinder Congress Designate Glance Heat Horizon I18n Ironic Magnum Manila Mistral Monasca Neutron Octavia OpenStack Helm PowerVMStackers Puppet OpenStack Qinling Rally Storlets Tacker Telemetry Tricircle Tripleo Trove Vitrage Zaqar Zun This means that with approximately 2 days left, 31 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [1]. (Any open reviews[2] have not been factored into these stats.) If you want to stand for PTL, don't delay, follow the instructions at [3] 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. Thank you, [1] https://governance.openstack.org/resolutions/20141128-elections-process-for… [2] https://review.openstack.org/#/q/is:open+project:openstack/election [3] https://governance.openstack.org/election/#how-to-submit-a-candidacy -- Jeremy Stanley

3 3

[tripleo] Nova HWMachineType settings
by Wesley Hayutin 12 Mar '19

12 Mar '19

Greetings, As we started to bootstrap f28 standalone jobs we noticed basic tempest tests were failing because the libvirt on f28 did not support the default "x86_64=pc-i440fx-rhel7.6.0" [5] Kashyap recommend switch to q35 [1]. So we can change to q35 maybe globally in puppet [2] if Juan, Alex and Emilien approve. Alternatively we can isolate the deployment in question w/ [3],[4] I should restart this thread in openstack-dev[tripleo] for greater transparency. Thanks Any comments on how to proceed? We need to enable f28 jobs in the next few days, so [2] may need to be the short term answer until we get feedback. [1] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8-be… [2] https://review.openstack.org/#/c/642443/ [3] https://review.openstack.org/#/c/642517/ switch to "pc" [4] https://review.openstack.org/#/c/642547 switch to "q35" [5] http://logs.rdoproject.org/openstack-periodic/git.openstack.org/openstack-i…

1 0

[tc][all][sdk] Devs and feedback needed for 'Project Resource Cleanup' goal for Train cycle
by Adrian Turjak 12 Mar '19

12 Mar '19

Hello OpenStackers! As has been mentioned a few times on the mailing list, one of the current community goal proposals is a new library/tool for cleaning up all the resources for a given project in an OpenStack cloud. For a long time we've lacked something like this, and it has made cleaning up a project and deleting it a pain, specifically because of the various dependencies around resources. The goal is now up for review: https://review.openstack.org/#/c/639010 The discussion right now is around the version originally proposed and discussed at the last Summit, a plugin based solution with a central library. We are also looking at an alternative which would be a single library like the SDK, or potentially even including the deletion login in the SDK itself, and the CLI part in the OpenStackClient. In all likelihood the single library approach will end up chosen, and I'll have a new written version of the goal up soon for that. If you have feedback against that you should voice it now! Are there any arguments for or against a plugin based solution we haven't heard yet? Additionally we would like feedback (specifically from the SDK team) if they think we should keep this as a standalone library that uses the SDK, or make it part of the SDK. We also need additional developers willing to contribute their time to this goal. Ideally we want every service to have some say in the code to clean up their resources, so I would highly suggest each new PTL works with their team to see who wants to help us make sure they are represented in this goal. Let's actually make this goal a reality! Put your hand up for wanting to contribute review time, and code! Cheers, Adrian

3 2

[tc] weekly update
by Mohammed Naser 12 Mar '19

12 Mar '19

Hi everyone: Just wanted to keep everyone up to date on what's going on in the TC over the past week briefly, this is meant to be a quick digested update that can (and should!) spark up some conversation, so please feel free to ask questions or bring in ideas # Python 3 The TC met and discussed last week about finalizing everything regarding Python 3. This happened over an ad-hoc meeting which you can follow the minutes here alongside the action items that came out of it - http://eavesdrop.openstack.org/meetings/tc_python3/2019/tc_python3.2019-03-… # Cycle goals There has also been work done from Lance and Jean-Philippe regarding the cycle goals, input from projects would be really useful, please have a look at them here: - https://review.openstack.org/#/c/639376/ Add Move legacy client CLIs to OSC goal to Train - https://review.openstack.org/#/c/639010/ Add Project Deletion goal for Train # Business value of help most needed Lance has put in a lot of work and effort in terms of moving our help most needed document to something that explains business value, reviews are up: - https://review.openstack.org/#/c/641790/ Elaborate on the business value of Designate - https://review.openstack.org/#/c/641773/ Elaborate on the business value of goal champions - https://review.openstack.org/#/c/641750/ Elaborate on the business value of documentation owners - https://review.openstack.org/#/c/641890/ Elaborate on the business value of infra admins - https://review.openstack.org/#/c/641784/ Elaborate on the business value of Glance # Goal closure updates Matt has pushed up a change discussing what to be done "at the end of a goal" which is currently up for discussion: - https://review.openstack.org/#/c/641507/ Document goal closure # Other Thanks to Doug once again for serving as chair for the past few cycles. The PTG is coming up and we're excited to see all the community again to build Train, without the train background noise :) Thanks, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 0