February 2022 - openstack-discuss

[all][tc] OpenStack next release name is final- "OpenStack Zed"
by Ghanshyam Mann 16 Feb '22

16 Feb '22

Hello Everyone, We have the final name selected for the OpenStack next release name. Its "OpenStack Zed". As per the release name criteria[1], selection of release name has gone through three steps: Step1: Name nomination from community members[2]. Step2: TC voted on the nominated names[3]. Step3: Trademark checks by Foundation on winners from TC votes. In trademark check, “Zed” is finalized as the best bet for this release. Thanks community members for participating in name nomination, TC to vote and Foundation for performing the trademark checks. [1] https://governance.openstack.org/tc/reference/release-naming.html#release-n… [2] https://wiki.openstack.org/wiki/Release_Naming/Z_Proposals [3] https://civs1.civs.us/cgi-bin/results.pl?id=E_693bd8bbe63ca52f -gmann

4 6

[election][Kuryr] PTL candidacy for the Z cycle
by Maysa De Macedo Souza 16 Feb '22

16 Feb '22

Hello OpenStack community, I would like to announce my candidacy for the Z cycle. I have been serving as Kuryr PTL since the Wallaby and I would like to continue doing that. In the Yoga cycle we have achieved the following: * Extended features and improvements: addition of events to Kubernetes resources, reduction on the workload Kuryr puts on Neutron, limiting the number of Neutron Ports creation happening in parallel, continuation on the load-balancer resources reconciliation with k8s Services, and many more. * CI improvements: Made Devstack installations to use CRI-O and improved some tempest tests. For the next cycle, I propose the following goals to Kuryr: * Continue improvements for Kuryr scalability with Neutron, OpenStack resources reconciliation with Kubernetes and Kuryr controller health checks. Thanks for your consideration. Best regards, Maysa Macedo. IRC: maysams

1 0

[election][tc] TC candidacy for Z release
by Slawek Kaplonski 16 Feb '22

16 Feb '22

Hi, I want to propose my candidacy for the Technical Committee. I have been an OpenStack contributor since around 2015. For most of that time I have contributed to the Neutron project where I am core reviewer and member of the Neutron drivers team, which is the subset of the Neutron core team for steering the Neutron project. I also served as the Neutron PTL for 4 cycles. Currently I work for Red Hat as software engineer and OpenStack Neutron developer and I would like to bring that developer’s perspective to the TC. Before I joined Red Hat, I worked in the OVH which is a Public Cloud provider. That gave me experience as an OpenStack operator as well. I have experience with the Neutron CI and I would like to expand it wider, for OpenStack as a whole. In the past I cooperated with TC members to reduce CI resources usage by the Neutron project and we made great improvements there. I understand that this new role will require a lot of learning and I will be very happy to have that opportunity. I’m willing to learn and contribute to the TC as much as possible. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[election][tc] TC candidacy for Z release
by Arne Wiebalck 16 Feb '22

16 Feb '22

Hello Everyone! I would like to declare my candidacy for the Technical Committee. I joined the CERN OpenStack team in 2014, initially to help with the operations of the storage components (Cinder, later Manila), and since 2016 I am looking after the overall operations of our cloud infrastructure service here at CERN. As part of this operational role, I have contributed upstream to several projects [1], recently mostly to Ironic which I help as a core member since about three years. I chair the Bare Metal SIG [2] since its inception, and together with other community members I am trying to establish it as a forum to promote the use of OpenStack for bare metal use cases [3] and to help new users to get started. Presentations at several summits [4] and regular blog posts [5] are examples of how I share the operational challenges and the solutions we apply in our cloud, in the hope these are helpful to other deployers in the same way we profit from them sharing their experiences. The combination of running an in-production OpenStack deployment downstream while interacting with core developers and the overall community upstream is something that I've enjoyed _a lot_ since several years now. I see how real-life input can be essential for upstream projects to move forward, set priorities, or maintain momentum. Equally, interaction with a responsive community where feedback is turned into tangible improvements is a valuable asset for any deployment. This positive experience of being an operator/developer hybrid in the OpenStack community is something I would like to bring to the TC, assisting with the ongoing (but continuous) effort to engage operators and help when global technical issues need to be sorted. I am sure being a member of the TC and helping with its work comes with a learning curve, but I'd be happy to contribute where I can. Thanks for reading and your consideration! Arne Wiebalck IRC (OFTC): arne_wiebalck [1] https://www.stackalytics.io/?metric=commits&release=all&user_id=arne-wiebal… [2] https://etherpad.opendev.org/p/bare-metal-sig [3] https://www.youtube.com/playlist?list=PLKqaoAnDyfgoBFAjUvZGjKXQjogWZBLL_ [4] https://www.openstack.org/videos/search?search=wiebalck [5] https://techblog.web.cern.ch/techblog/

1 0

OpenInfra Live - February 17 at 1500 UTC
by Allison Price 16 Feb '22

16 Feb '22

Hi everyone, This week’s OpenInfra Live episode is brought to you by the OpenInfra Foundation. Organizations like AT&T, CERN, China Mobile, China Telecom, Verizon, Vodafone, and Yahoo have adopted the OpenInfra Standard and run it in production today. Similar to how LAMP stack became the standard for deploying web applications, LOKI helps operators identify successful patterns and combinations of technologies to build production infrastructure. This OpenInfra Live episode will discuss this emerging standard and why organizations have adopted these open source technologies together. Episode: Linux OpenStack Kubernetes Infrastructure: The OpenInfra Standard Date and time: Thursday, February 17 at 9am CT (1500 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=pnYB7eYYiPg <https://www.youtube.com/watch?v=pnYB7eYYiPg> LinkedIn: https://www.linkedin.com/video/event/urn:li:ugcPost:6899060799814418432/ <https://www.linkedin.com/video/event/urn:li:ugcPost:6899060799814418432/> Facebook: https://www.facebook.com/104139126308032/posts/4852599164795314/ <https://www.facebook.com/104139126308032/posts/4852599164795314/> WeChat: recording will be posted on OpenStack WeChat after the live stream Participants: Host: Mark Collier, COO at the OpenInfra Foundation Maria Bracho, Manager Product Management at Red Hat Philip Williams, Product Leader at Canonical Have an idea for a future episode? Share it now at ideas.openinfra.live <https://openinfrafoundation.formstack.com/forms/openinfralive>. Thanks, Allison

1 0

[glance] Zed PTG Planning
by Abhishek Kekane 15 Feb '22

15 Feb '22

Hello Everyone!!! As you are already aware that Zed virtual PTG will be held between April 4th to 8th [1]. Please use below etherpad to add the topics you would like to discuss during PTG. https://etherpad.opendev.org/p/zed-ptg-glance-planning <https://etherpad.opendev.org/p/yoga-ptg-glance-planning> [1] https://openinfra-ptg.eventbrite.com/ Thanks & Best Regards, Abhishek Kekane

1 0

oslo.messaging integration development
by liyang 15 Feb '22

15 Feb '22

Hi everyone, I find Apache Pulsar is very popular in MQ area, especially in clound native area. Is there any body integrate this MQ to oslo.messaging? Said to the truth. RabbitMQ developed in Erlang has very little source code level material, Qpid has very little operation practice in the internet. Kafka only support notification in oslo.messaging. I think the Apache Pulsar is clound native based. It may enforece the big scale in extension about Openstack deployment.

5 9

[election][tc] TC candidacy for Z
by Brian Rosmaita 15 Feb '22

15 Feb '22

Hello Everyone, I am declaring my candidacy for the Technical Committee. I've been involved in OpenStack for a while now (my first commit was into Folsom). I've been a very active member of the community as a core member of the Glance, Cinder, and Searchlight teams. I've attended many PTGs and presented at many Summits. I've also served as PTL for Glance (Ocata through Queens) and Cinder (Ussuri through Yoga). You may have seen my clever irc nick, 'rosmaita', mostly in #openstack-cinder and #openstack-glance, but occasionally making a pest of myself in other channels. The TC is tasked with providing technical leadership for OpenStack as a whole and enforcing the OpenStack ideals (the Four Opens [0], the Guiding Principles [1]). While the TC's primary mission is to provide technical leadership, promoting the ideals calls for a broader membership than just technical people actively developing OpenStack. So I think it's appropriate that TC membership includes operators, distributors, and cultural members of the OpenStack community. But it's also important that the TC include highly technical people who contribute to the projects it oversees [2]. I believe that I'm well-suited to represent that constituency. I don't have an agenda other than to represent active contributors and participate in the TC in a manner consistent with its charter [3]. If you ask people who've worked with me, you'll find that I'm good about making sure discussions are done in the open, and that all parties concerned are listened to. I'll bring these qualities to the TC. Finally, I should probably mention who pays my bills. I'm a Principal Software Engineer at Red Hat. As you're hopefully aware, Red Hat has an "upstream first" philosophy [4], which is pretty evident when you look at code contributions to OpenStack, but which also extends to the company encouraging us, when participating in an open source community, to make decisions based on the needs and goals of the community rather than those of Red Hat. (That sounds very noble, but the idea is that a strong community benefits Red Hat in the long run. My key point here, though, is that I'm empowered to represent the OpenStack community's interest, not Red Hat's, if I'm elected to the TC.) Thanks for reading this far, and thank you for considering my candidacy for the OpenStack Technical Committee. - Brian Rosmaita (rosmaita) [0] https://governance.openstack.org/tc/reference/opens.html [1] https://governance.openstack.org/tc/reference/principles.html [2] I appropriated this line from Dan Smith. [3] https://governance.openstack.org/tc/reference/charter.html [4] https://opensource.com/article/16/12/why-red-hat-takes-upstream-first-appro…

1 0

[manila][election][ptl] PTL Candidacy for Z
by Carlos Silva 15 Feb '22

15 Feb '22

Hello, Zorillas and dear stackers, I would like to submit my candidacy to be the PTL of Manila for the Z cycle. I have been a contributor to OpenStack since the Stein release. It has been an awesome experience. During these years, I had the opportunity to contribute with new features, fixes, reviews and other exciting enhancements for Manila. I can tell you that I've faced thrilling challenges, and I learned a lot with the community that made this journey enjoyable day after day. I'm tremendously happy to see the state Manila is at. I'd like to keep the momentum for the project by continuing to focus in some areas we have been focusing, but also start tackling other issues: - Continue increasing the number of contributors and active reviewers through mentoring and engaging them in the community, teaching the OpenStack way and making it collaboratively as we did in the past cycles, promoting hackatons, bug squashes and collaborative review sessions. - Encouraging the involvement of Manila contributors in important programs/events such as GHC, Outreachy and the other opportunities we've been able to contribute in the past. - Pursue the completion of the Manila implementation on the openstackclient/openstacksdk; - Continue pushing Manila to cover the tech debt areas we identified over the past cycles; - Enforcing maintainers to collaboratively cover the lack of documentation we have on third party CI setups for Manila, helping potential new vendors to quickly setup up their CI systems; - Continue discussing with community and making the necessary enhancements for HA and Edge; Thank you for your consideration! Carlos da Silva IRC: carloss

4 3

[election][cloudkitty] PTL candidacy for Zed
by Rafael Weingärtner 15 Feb '22

15 Feb '22

Hello guys, I would like to self-nominate for the role of PTL of CloudKitty for the Zed release cycle. I am the current PTL for the Xena cycle and I am willing to continue in this role. I will keep working with existing contributors to maintain CloudKitty for their use cases and encourage the addition of new functionalities. Thank you for your support, -- Rafael Weingärtner

1 0