- openstack-discuss - lists.openstack.org

[all][elections][ptl][tc] Combined PTL/TC Nominations ending in less than 24 hours
by Amy Marrich 24 Aug '21

24 Aug '21

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Aug 24, 2021 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 @ 2021-08-17 23:45:00 UTC Nominations end @ 2021-08-24 23:45:00 UTC Nominations duration : 7 days, 0:00:00 Nominations remaining : 1 day, 7:37:12 Nominations progress : 81.18% --------------------------------------------------- Projects[1] : 47 Projects with candidates : 28 ( 52.00%) Projects with election : 1 ( 2.00%) --------------------------------------------------- Need election : 1 (Cyborg) Need appointment : 19 (Adjutant Cinder Cloudkitty Designate Heat Ironic Magnum Manila Monasca OpenStack_Charms Openstack_Chef Puppet_OpenStack Release_Management Requirements Sahara Storlets Swift Tripleo Zun) =================================================== Stats gathered @ 2021-08-23 16:07:48 UTC This means that with approximately 2 days left, 23 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. There are also currently 4 confirmed candidates for the 4 open Technical Committee. Thank you, Amy (spotz) On behalf of all the Election Officials [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…

2 1

[cinder] reminder: this week's meeting in video+IRC
by Brian Rosmaita 24 Aug '21

24 Aug '21

Quick reminder that this week's Cinder team meeting on Wednesday 25 August, being the final meeting of the month, will be held in both videoconference and IRC at the regularly scheduled time of 1400 UTC. These are the video meeting rules we've agreed to: * Everyone will keep IRC open during the meeting. * We'll take notes in IRC to leave a record similar to what we have for our regular IRC meetings. * Some people are more comfortable communicating in written English. So at any point, any attendee may request that the discussion of the current topic be conducted entirely in IRC. * The meeting will be recorded. connection info: https://bluejeans.com/3228528973 meeting agenda: https://etherpad.opendev.org/p/cinder-xena-meetings cheers, brian

1 0

[election][Release_Management] PTL candidacy for Yoga
by Előd Illés 24 Aug '21

24 Aug '21

Hello OpenStack Community, I would like to announce my candidacy for PTL of the Release Management team for the Yoga cycle. I became core member in the Release Management team during Wallaby cycle to help the work of the team with release patch reviews, but I was involved in the release process for some time already as my focus has been Stable Maintenance (especially around the introduction of the Extended Maintenance process) as being member of the stable-maint-core group. Thanks to the great work of the former PTLs and team members of the Release Management team, now the process is fairly automated and should be straightforward to follow. During the Yoga cycle I'm planning to get familiar with all the aspects of the release management (with the help of the more experienced team members) and continue the work that my predecessors started and keep things maintained. Thanks for your consideration, Előd Illés (elodilles)

1 0

[election][cinder] PTL Candidacy for Yoga
by Brian Rosmaita 24 Aug '21

24 Aug '21

Hello everyone, I'd like to announce my candidacy for Cinder PTL for the Yoga cycle. The primary challenge we face in the Cinder community continues to be that our reviewing bandwidth has declined at the same time third-party driver contributions have not decreased. As I see it, the problem is that many vendors who maintain third-party drivers do not appear to be clear on the concept of community participation. (For what it's worth, I think this is more a manager problem than a developer problem, but the effect on Cinder is the same, namely, lots of request for reviews and not much doing of reviews. The Cinder documentation has information about how to review, how you don't need to be a core to do valuable reviews, etc., but it's not clear that many people have actually read them.) The Cinder community has tried to address this participation deficit in Xena by providing more upstream activities for contributors (for example, the monthly Festival of XS reviews [0] and the weekly Bug Squad meetings [1]), and these have had decent participation. In Yoga, I'd like to explore having some kind of Review Squad meeting to give people a chance to get "live" feedback on features under development. Some people do use the weekly Cinder meeting for this, but not everyone takes advantage of that, plus weekly meeting time is limited. I hate to propose yet another team meeting, but on the other hand, the bug squad and festival of reviews meetings are extremely productive, so I don't mind proposing another *productive* meeting. (We'll simply cancel it if it turns out that people don't take advantage. Also, I'm open to other ideas ... the key issue is providing faster feedback and more visibility for people developing cinder features, and allowing cinder cores to use their review time productively. So two key issues.) On the positive side, we did add a new cinder core during Xena and there's another person right on the verge of being proposed as a core. So that will help address review bandwidth, though I want to stress that non-core reviews are extremely important to the project as well. Our core reviewers also develop features and fix bugs--they are not full-time code reviewers. And the way to become a cinder core is to review widely in the project and demonstrate a good breadth of knowledge of the software. (As always, anyone currently working on cinder project who's interested becoming a cinder core, please contact me (or any of the current cores) to discuss what the expectations are.) Also on the good side is that we've done quite a bit of work on the Cinder CI this cycle. (I'm not going to tempt fate by saying anything more about that.) With respect to the details of Cinder development in Yoga, I expect those to emerge from our virtual PTG discussions in October. You can help set the agenda here: https://etherpad.opendev.org/p/yoga-ptg-cinder-planning To summarize, I would like to continue working on improving the review throughput of the Cinder team and find additional ways to get people more thoroughly involved in the project. Thanks for reading this far, and thank you for your consideration. Brian Rosmaita (rosmaita) [0] http://eavesdrop.openstack.org/#Cinder_Festival_of_XS_Reviews [1] http://eavesdrop.openstack.org/#Cinder_Bug_Squad_Meeting

1 0

[election][requirements][ptl] PTL Candidacy for Yoga
by Matthew Thode 24 Aug '21

24 Aug '21

I would like to announce my candidacy for PTL of the Requirements project for the Yoga cycle. The following will be my goals for the cycle, in order of importance: 1. The primary goal is to keep a tight rein on global-requirements and upper-constraints updates. (Keep things working well) 2. Un-cap requirements where possible (stuff like prettytable). 3. Fix some automation of generate contstraints (pkg-resources being added and setuptools being dropped) 4. Audit global-requirements and upper-constraints for redundancies. One of the rules we have for new entrants to global-requirements and/or upper-constraints is that they be non-redundant. Keeping that rule in mind, audit the list of requirements for possible redundancies and if possible, reduce the number of requirements we manage. I look forward to continue working with you in this cycle, as your PTL or not. IRC: prometheanfire -- Matthew Thode

1 0

[election][manila][ptl] PTL Candidacy for Yoga
by Goutham Pacha Ravi 24 Aug '21

24 Aug '21

Hello fellow zorillas and other interested stackers, I'm expressing interest to continue serving as PTL for the OpenStack Manila team through the Yoga cycle. I've used my great privilege in this role to affect the community in many small and significant ways over the past four cycles. It has been a smooth ride because of stellar contributors who're beyond motivated and enthusiastic to develop and maintain impactful software while having fun. The enthusiasm is bolstered by grit to be a team with a difference. We jump at the opportunity to help a user or mentor and welcome new contributors or back each other up and help get stuff done, regardless of the "barriers" of affiliation. I enjoy being the occasional enabler to this camaraderie. During the Xena cycle, we mentored two Outreachy interns and on-boarded several new contributors. We added sub team core maintainers in the manila-tempest-plugin project and a new core maintainer across the manila repos. We drove down bug backlogs through bug squash weeks, swarmed to work on the OpenStackClient with a hack-a-thon and crushed the goal to drive down tech debt. We kept the momentum on several multi-cycle efforts such as OpenStackSDK integration, Secure RBAC, Active/Active HA. The Yoga cycle will be critical in our efforts to drive some of these multi-cycle efforts to closure. So, if you will have me, I wish to serve you through the Yoga cycle and get things done. I would tell you it's going to be the best release ever; but I would hold out the distinction for the Zorilla cycle - yes that's what we'll name it, what other cool name will we have anyway :) Thank you for your support, Goutham Pacha Ravi <gouthampravi(a)gmail.com> IRC: gouthamr

3 2

[infra][devstack][CI] pmlogger service fails to start
by Balazs Gibizer 24 Aug '21

24 Aug '21

Hi, Is there any work ongoing to figure out why devstack fails with? Job for pmlogger.service failed because a timeout was exceeded. We have 120 hits in the last 7 days. Recent example [1], logstash signature [2]. cheers, gibi [1] https://zuul.opendev.org/t/openstack/build/a36289ff4fc34b18af70b5b29d38bdf4… [2] http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3…

1 0

[storlets] Transition stable/stein and older branches to EOL
by Takashi Kajinami 24 Aug '21

24 Aug '21

Hi all, I recently noticed that our project still has many old stable branches, from Newton (!!). Because I've never seen any interests to backporting changes to very old branches, I'll propose transitioning stable/stein and older stable branches to EOL. If you have any concerns with that transition please let me know in the following gerrit review. https://review.opendev.org/c/openstack/releases/+/804562 Note that Newton and Ocata will be anywary marked as EOL now since these branches are globally marked as EOL, IIUC. Thank you, Takashi

1 0

[ironic] Not running for PTL this cycle
by Julia Kreger 24 Aug '21

24 Aug '21

Greetings everyone, I know I've repeatedly stated over the last few PTGs and midcycle sessions that I wouldn't be running this cycle, but I also realized this morning I had not sent an email. I've served as Ironic's PTL for 7 cycles, and after three and a half years, it is far past time to step down for at least a cycle. Serving the community has been a privilege and an honor, and I'm not planning on going anywhere, but a single person can only take on and handle so much stress. Changes in leadership are also a good thing as it can bring fresh perspective and voices into a project. I encourage Ironic contributors to consider if they would like to serve as the PTL, and to go ahead and submit their candidacy to the elections repository. The only thing I ask is we remain mindful of the needs of the community. I'll be there to help, to guide, and resolve conflicts if necessary. Much as Dmitry, Jim, and Aeva did before me. -Julia

8 7

[election][storlets] PTL Candidacy for Yoga
by Takashi Kajinami 23 Aug '21

23 Aug '21

Hi All, I'd like to announce my candidacy to continue the PTL role for Storlets project in the Yoga cycle. After inactive recent cycles, we fortunately got some interest around the project again. So I'll propose the items below as our focus during the next cycle. - Keep compatibility with Swift. This is always top-priority - Merge some patches still open to achieve easier operation and improve resource efficiency Thank you for your consideration. Thank you, Takashi

1 0

[horizon][dev] Auto-Refresh Feature Proposal
by Santos, Gustavo Faganello 23 Aug '21

23 Aug '21

Hello, everyone. I'm here to find out what you think about the addition of a feature in OpenStack Horizon. As you may know, Horizon requires the user to manually update the page in order to get the most recent data in the system, e.g. if an instance is created, deleted or renamed before the page is reloaded, the user has to hit the refresh button in their browser to see those changes in the page. This applies to the majority of Horizon's pages, including, but not limited to, Instances, Volumes, Users and so on. With that in mind, our team has implemented and tested a prototype of an auto-refresh feature for Horizon. We've been using it for a while now and have received positive feedback from our clients. It automatically updates the information in tables, pie charts (such as the Compute Overview page graphs) and details pages every five seconds, without the need for manually refreshing the page. The information displayed on the page will be replaced by the most recent data without any action from the user or any page reloading. It essentially works by requesting, in the background, the opened page again and again every few seconds through AJAX, and then replacing the old information with the new one if they differ. The feature affects every element in Horizon, except AngularJS ones - the tables in the Compute Images, Key Pairs and Server Groups pages are AngularJS elements and will not be affected by auto-refresh, for example. We are open to looking into this issue in the future, though. Could you please let us know if you would be open to adding such a feature to Horizon? If so, we'd be willing to do the upstream implementation in OpenStack, and we think it would be a great addition to the end users. Kind regards. Gustavo Santos

5 5

[election][ironic] PTL Candidacy for Yoga
by Iury Gregory 23 Aug '21

23 Aug '21

Hello Stackers, I would like to nominate myself to serve as Ironic PTL for the Yoga cycle. I've been working with OpenStack since 2015 and contributing to ironic since Oct 2018 (Stein release). I hope that we as a community can continue to achieve goals together, let's not forget that our main objective is to take over the world and make operator's life easier! We should also aim to grow our contributor base and continue to spread the word about Ironic (blog posts, social media, etc). Features that I think we should aim for during the next cycle: Virtual Media visibility, Security Interface using Keylime. Best regards, -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

2 1

No meeting tomorrow
by Gage Hugo 23 Aug '21

23 Aug '21

Hey team, Since there are no agenda items [0] for the IRC meeting tomorrow, the meeting is cancelled. Our next meeting will be Aug 31st. Thanks [0] https://etherpad.opendev.org/p/openstack-helm-weekly-meeting

1 0

[election][kuryr] PTL Candidacy for Yoga
by Maysa De Macedo Souza 23 Aug '21

23 Aug '21

Hello OpenStack community, I would like to continue serving as Kuryr PTL for the Yoga cycle. I have started serving as Kuryr PTL in the Wallaby cycle. It has been a great opportunity to contribute back to the community as PTL and I would like to continue doing that. In the Xena cycle we achieved the following goals: * CI improvements: started moving gates to use OVN by default while still having a few supporting OVS. * Dev env improvements: Support for Kubeadm for DevStack installations. * Extended features in Kuryr: Support to reconcile Load Balancer with respective Kubernetes Service, improvement on the Kuryr logs. * Increased diversity of contributors with great addition of contributors from the Outreachy program. For the next cycle, I propose the following goals for Kuryr: * Improve CI: we already did great improvements, but we must continuously work on it to provide better and quicker feedback during the development process. * Migrate CNI code from pyroute2.IPDB to NDB; Add support to reconciliation of other Kubernetes resources; Reduce OpenStack resource usage; Provide better debugging by relying on Kubernetes events. Thank you for your consideration. Kind regards, Maysa Macedo

1 0

OpenInfra Live - August 26, 2021 at 9am CT
by Ashlee Ferguson 23 Aug '21

23 Aug '21

Hi everyone, This week’s OpenInfra Live episode is brought to you by the OpenStack community. When we talk about Large Scale, it usually refers to scaling out to hundreds of thousands of commodity nodes. But there is another dimension to Large Scale OpenStack: using OpenStack to build supercomputers to use in research and HPC. In this episode, operators of OpenStack supercomputers and HPC centers will discuss the unique challenges this use case brings. Episode: Large Scale OpenStack: Discussing software-defined supercomputers Date and time: August 26, 2021 at 9am CT (1400 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=fOJTHanmOFg <https://www.youtube.com/watch?v=fOJTHanmOFg> LinkedIn: https://www.linkedin.com/feed/update/urn:li:ugcPost:6834150009706037248/ <https://www.linkedin.com/feed/update/urn:li:ugcPost:6834150009706037248/> Facebook: https://www.facebook.com/104139126308032/posts/4256168904438346/ <https://www.facebook.com/104139126308032/posts/4256168904438346/> WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Stig Telfer, StackHPC Sadaf Alam, Swiss National Supercomputer Centre Jonathan Mills, NASA Goddard Space Flight Center Steve Quenette, Monash e-Research Centre Happy Sithole, Center for High Performance Computing in South Africa Have an idea for a future episode? Share it now at ideas.openinfra.live <https://openinfrafoundation.formstack.com/forms/openinfralive>. Thanks! Ashlee

1 0

[election][Designate] PTL candidacy for Yoga
by Michael Johnson 23 Aug '21

23 Aug '21

Hello OpenStack community, I would like to announce my candidacy for PTL of Designate for the Yoga cycle. I would like to continue to support the Designate team for the Yoga release. We have made good progress improving the Designate tempest tests and documentation, but we have more work to do. I am also excited to see progresson new features. Thank you for your support and your consideration for Yoga, Michael Johnson (johnsom)

1 0

[election][Octavia] PTL candidacy for Yoga
by Gregory Thiemonge 23 Aug '21

23 Aug '21

Hi everyone, I would like to nominate myself for Octavia PTL for the Yoga release. I am the current PTL for the Xena release and I would like to continue to serve our team for the next release. I have been an Octavia contributor for more than 2 years, and a core reviewer for 3 releases. My focus will be to continue the tasks that we have worked on during Xena: completing the Amphorav2 driver feature, supporting multiple subnets on a Load Balancer VIP, improving our CI coverage, ... Thanks for your consideration, Gregory

1 0

[election][tc]Jay Bryant candidacy for Technical Committee ...
by Jay Bryant 23 Aug '21

23 Aug '21

Hello OpenStack Community! I would like to announce my candidacy for another term on the Technical Committee. First of all, I have appreciated the opportunity to serve on the TC for the last two years. I have endeavored to use this time to get to know the broader community better and have also tried to better understand the role and activities of the TC. With this experience under my belt I would like to continue to work with the TC in the coming year to address some of the challenges that currently face the community. Most importantly the challenge of getting more new companies and contributors to engage with the OpenStack community. I also would like to continue to work with the TC to innovate and improve OpenStack's processes given the always changing landscape of the community. I appreciate you all taking the time to read/consider my candidacy! Sincerely, Jay Bryant (jungleboyj)

1 0

[election][tc]Jay Bryant candidacy for Technical Committee ...
by Jay Bryant 23 Aug '21

23 Aug '21

Hello OpenStack Community! I would like to announce my candidacy for another term on the Technical Committee. First of all, I have appreciated the opportunity to serve on the TC for the last two years. I have endeavored to use this time to get to know the broader community better and have also tried to better understand the role and activities of the TC. With this experience under my belt I would like to continue to work with the TC in the coming year to address some of the challenges that currently face the community. Most importantly the challenge of getting more new companies and contributors to engage with the OpenStack community. I also would like to continue to work with the TC to innovate and improve OpenStack's processes given the always changing landscape of the community. I appreciate you all taking the time to read/consider my candidacy! Sincerely, Jay Bryant (jungleboyj)

1 0

[CLOUDKITTY] Missed CloudKitty meeting today (23 August 2021)
by Rafael Weingärtner 23 Aug '21

23 Aug '21

Hello guys, I would like to apologize for missing the CloudKitty meeting today. I had an accident with my laptop last thursday, and just now I managed to get my hands on a replacement. If you need something, just let me know. Sorry for the inconvenience; see you guys at our next meeting. -- Rafael Weingärtner

1 0

about deploy method
by Tommy Sway 23 Aug '21

23 Aug '21

Hi: For the four deployment schemes given in the official document, I have the following questions: First, is the charms deployment scheme only applicable to Ubuntu system? Second, what is the difference between kallo and Openstack-Ansible deployment? Thanks !

3 5

[nova][placement] PTL nomination open
by Balazs Gibizer 23 Aug '21

23 Aug '21

Hi! As per [1] Nova (including Placement) PTL nomination period is open. As I noted in my Xena nomination[2] I'm not intended to run for a 4th cycle. If you have any question about being a nova PTL then feel free to contact me publicly or privately. Cheers, gibi [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024191.h… [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-March/020834.ht…

3 2

Is there a new version of FUEL available now?
by Tommy Sway 23 Aug '21

23 Aug '21

And there to download it if exists ? Thanks.

2 2

[neutron] Bug deputy report - week of Aug 16th
by Slawek Kaplonski 23 Aug '21

23 Aug '21

Hi, I was Neutron bug deputy last week. Here is summary of it: **Critical** https://bugs.launchpad.net/neutron/+bug/1940243 - Neutron-tempest-plugin scenario tests - oom-killer is killing mysql process - gate failure, fix proposed https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/ 805057 **High** https://bugs.launchpad.net/neutron/+bug/1940541 - [ovn] metadata readiness check is looking for wrong uuid in chassis - Issue in stable branches only, in progress https://bugs.launchpad.net/neutron/+bug/1940071 - Neutron VPNaaS - growing memory consumption - needs investigation, https://bugs.launchpad.net/neutron/+bug/1940425 - test_live_migration_with_trunk tempest test fails due to port remains in down state - gate failure, needs assignment, **Medium** https://bugs.launchpad.net/neutron/+bug/1940074 - Neutron port bulk creation procedure ignores binding:vnic_type parameter - not assigned yet, seems like low-hanging-fruit https://bugs.launchpad.net/neutron/+bug/1940073 - "Unable to create the network. No available network found in maximum allowed attempts." during rally stress test - Unassigned, seems a bit as low-hanging-fruit for me https://bugs.launchpad.net/neutron/+bug/1940312 - Ussuri-only: Network segments are not tried out for allocation - Assigned, patch proposed already. It's stable only bug, fixed in master https://bugs.launchpad.net/neutron/+bug/1940311 - Quota engine should not retry DB operation when releasing reservation - fix proposed https:// review.opendev.org/c/openstack/neutron/+/805031 https://bugs.launchpad.net/neutron/+bug/1940617 - [ovn] metadata agent needlessly connects to ovsdb cluster leader - In progress, patch proposed https://review.opendev.org/c/openstack/neutron/+/805335 **Low** https://bugs.launchpad.net/neutron/+bug/1940086 - [api-ref] doc does not list resource_request as a field of the response of port bulk create - Needs assignment https://bugs.launchpad.net/neutron/+bug/1940790 - oslo.cache options are missing from neutron.conf generated by "tox -e genconfig" - In progress, patch proposed: https://review.opendev.org/c/openstack/neutron/+/805547 **Whishlist** https://bugs.launchpad.net/neutron/+bug/1940084 - neutron-agent causes 10m delay on start-up - assigned to slaweq https://bugs.launchpad.net/neutron/+bug/1940518 - Add network_ip_availability pagging support - assigned to ralonsoh -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[masakari] Deprecating process monitor - querying the community in this thread
by Radosław Piliszek 23 Aug '21

23 Aug '21

Hello users of Masakari, As the Masakari core team, we have discussed the deprecation/retirement of one of the monitors - the process monitor. The reason is simple - we consider its mission is better handled by other software such as Kubernetes, Docker, or systemd, depending on how you deploy your OpenStack cluster. I believe the process monitor might have made sense in the pre-containerisation, pre-systemd world but it does not seem to any longer. Please let us know, by replying to this mail, if you have a use case for the process monitor that cannot be handled by the aforementioned software. -yoctozepto

1 1

[election][nova][placement] PTL candidacy for Yoga
by Sylvain Bauza 22 Aug '21

22 Aug '21

Hello Nova (and Placement) fellows, That's been some time I started to work on OpenStack and Nova in particular (I leave you guessing it [1]) but I feel this is time for me to run for the Nova PTL election and ask you to accept me for this hot seat (which is not a Yoga mat). First and foremost, I'd like to thank gibi for the hard work he did on the previous cycles, especially during this (hopefully) transient situation we currently face which challenges us in terms of teamwork. Running our team gatherings virtually twice is awfully exhausting and I also thank you all for supporting this situation. Hopefully our next PTG will be the last virtual one but who knows. I personally feel Nova now entered a period of quiet but productive pace. We accepted a solid amount of blueprints over the past cycles but we also delivered a decent ratio of them. That said, many challenges occur as of now which as a PTL I have the intention to continue to stress on and engage discussions between us how to solve them : - CI stability : We recently faced a couple of bugs that prevented us to merge code and I have the feeling that some of them are intertwined. I'd like us to identify all the stressing bits so we could prioritize any kind of tech debt fix that would help to gain better stability and not treat them as just standard bugs that we only look after our feature delivery duties. - Upgrades : I'm very happy to say we solved the long-running problem of version-to-next upgrades which are now painless. We have a couple of tools for helping operators to gain confidence before upgrades and we also have CI jobs that prove their stability. That said, I personally feel we now have another dimension of upgrades we barely scratched to define and I would like us to think about them. Placement reshapes and fast-forward-upgrades are for example two new features that Nova supports but I'd like us to take a second and identify all the improvements we could make for those (and prioritize efforts accordingly) - Contributors diversity : I don't think there is any surprise if I say that our Nova community is smaller than before. I don't think it's a problem and as I already said, we're productive. No, the concern that I have is that I'd love to have a way to help contributors that are maybe not having time to develop on Nova as a primary day-to-day job. We started to discuss on ways to define review priorities and I would like to pursue this direction by wondering what and how we could do for those contributors. Either way, I truly respect the ideal of Open Design. Whatever Nova becomes or evolves in the future, every single contributor is part of it and my role will be to make sure we have a consensus. Thanks, -Sylvain [1] 0x7DD

2 1

how to update existing vm instances 'availability_zone' field in nova database 'instances' table
by hai wu 20 Aug '21

20 Aug '21

Hi, How to update existing vm instances 'availability_zone' field in nova database 'instances' table? It turns out there are many VMs with default 'nova' availability zone, while the hypervisors are with another different target aggregate/availability zone name, thus live migration for these VMs are failing. The strange thing is that the 'OS-EXT-AZ:availability_zone' output from 'openstack server show VM_NAME' is showing these VMs are already with the target availibity_zone name. No idea why we have this inconsistency. Would it be ok to just update database table entry directly to set 'availility_zone' to different value for these VMs? Or there might be better alternatives I am not aware of? Thanks, Hai

2 4

[all][tc] What's happening in Technical Committee: summary 20th Aug, 21: Reading: 5 min
by Ghanshyam Mann 20 Aug '21

20 Aug '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * TC held this week's IRC meeting on Aug 19th Thursday. * I am summarizing the meeting activities in the below sections (Completed or in-progress activities section). To know more details, you can check the full log @ - https://meetings.opendev.org/meetings/tc/2021/tc.2021-08-19-15.00.log.html * We will have next week's meeting on Aug 26th, Thursday 15:00 UTC[1] feel free the topic in agenda by Aug 25th. 2. What we completed this week: ========================= * Discussion on Murano project retirement[2] ** We discussed this in the TC meeting and as Rong Zhu (current PTL) confirmed to continue maintaining it we decided to drop the retirement process. 3. Activities In progress: ================== TC Tracker for Xena cycle ------------------------------ TC is using the etherpad[3] for Xena cycle working item. We will be checking and updating the status biweekly in the same etherpad. Open Reviews ----------------- * Four open reviews for ongoing activities[4]. Combined PTL/TC Election Season for Yoga ---------------------------------------------------- * The nomination period for PTL and TC elections are open, please add your nomination before the deadline[5] * Also encourage people to run for election especially for TC seats. New project application: 'Venus' -------------------------------------- * There is a new project application called 'Venus': Log management service[6]. * Governance patch is also up with all the details[7] and discussion going on. If you have any queries on this, this is the right time to ask on the ML thread or on Gerrit. Moving TC meetings to video/voice calls ------------------------------------------------ * In TC we are thinking of moving the meeting to video/voice calls. Brian also posted Cinder's monthly video call experience which was helpful, feel free to share your experience too if any. * In this week TC meeting, we agreed to try monthly video call (1st weekly meeting of every month) and based on the experience we will discuss it in PTG to make it more formal or so. * We will continue the discussion on which tool to use etc in next week's TC meeting also. Project updates ------------------- * Retiring js-openstack-lib [8] * Retire puppet-monasca[9] Yoga release community-wide goal ----------------------------------------- * Please add the possible candidates in this etherpad [10]. * Current status: Proposed "Secure RBAC" to select for Yoga cycle[11]. PTG planning ---------------- * We are collecting the PTG topics in etherpad[12], feel free to add any topic you would like to discuss. Test support for TLS default: ---------------------------------- * Rico has started a separate email thread over testing with tls-proxy enabled[13], we encourage projects to participate in that testing and help to enable the tls-proxy in gate testing. 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[14]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [15] 3. Office hours: The Technical Committee offers a weekly office hour every Tuesday at 0100 UTC [16] 4. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024263.h… [3] https://etherpad.opendev.org/p/tc-xena-tracker [4] https://review.opendev.org/q/project:openstack/governance+status:open [5] http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024191.h… [6] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019748.… [7] https://review.opendev.org/c/openstack/governance/+/804824 [8] https://review.opendev.org/c/openstack/governance/+/798540 [9] https://review.opendev.org/c/openstack/governance/+/805105 [10] https://etherpad.opendev.org/p/y-series-goals [11] https://review.opendev.org/c/openstack/governance/+/803783 [12] https://etherpad.opendev.org/p/tc-yoga-ptg [13] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023000.html [14] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [15] http://eavesdrop.openstack.org/#Technical_Committee_Meeting [16] http://eavesdrop.openstack.org/#Technical_Committee_Office_hours -gmann

1 0

[neutron][ovn] Error when listing agents
by Marc 'risson' Schmitt 20 Aug '21

20 Aug '21

Hi, After ugprading to Wallaby, I get the following error when listing my agents: ``` 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource [req-148cc4ed-c2b1-4e33-9e0c-1a5573652e6a b867d59eb3f34e2eab684b74e2ba7e87 28d6433dd9db4e7298c84b1058ea825a - default default] index failed: No details.: AttributeError: 'Chassis_Private' object has no attribute 'hostname' 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource Traceback (most recent call last): 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/neutron/api/v2/resource.py", line 98, in resource 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource result = method(request=request, **args) 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/neutron_lib/db/api.py", line 139, in wrapped 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource setattr(e, '_RETRY_EXCEEDED', True) 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource self.force_reraise() 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource raise self.value 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/neutron_lib/db/api.py", line 135, in wrapped 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource return f(*args, **kwargs) 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_db/api.py", line 154, in wrapper 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource ectxt.value = e.inner_exc 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource self.force_reraise() 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource raise self.value 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_db/api.py", line 142, in wrapper 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource return f(*args, **kwargs) 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/neutron_lib/db/api.py", line 183, in wrapped 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource LOG.debug("Retry wrapper got retriable exception: %s", e) 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource self.force_reraise() 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource raise self.value 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/neutron_lib/db/api.py", line 179, in wrapped 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource return f(*dup_args, **dup_kwargs) 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/neutron/api/v2/base.py", line 369, in index 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource return self._items(request, True, parent_id) 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/neutron/api/v2/base.py", line 304, in _items 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource obj_list = obj_getter(request.context, **kwargs) 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py", line 1159, in fn 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource return op(results, new_method(*args, _driver=self, **kwargs)) 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py", line 1223, in get_agents 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource agent_dict = agent.as_dict() 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource File "/var/lib/kolla/venv/lib/python3.8/site-packages/neutron/plugins/ml2/drivers/ovn/agent/neutron_agent.py", line 55, in as_dict 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource 'host': self.chassis.hostname, 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource AttributeError: 'Chassis_Private' object has no attribute 'hostname' 2021-08-20 23:42:33.466 24 ERROR neutron.api.v2.resource ``` (pasted here: https://bin.lama-corp.space/o8Q7xYtrGtp0jSKdR8qF1) Should I open a bug report or is it something I'm doing wrong? Lookiing at the code, I see recent changes were made, which maybe introduced a bug, in which case I'd be happy to help. About the setup: neutron with OVN agents, version 18.1.1.dev7, deployed with kolla-ansible, nothing especially fancy. Thanks in advance, -- Marc 'risson' Schmitt CRI - EPITA

1 0

[manila] Collab review
by Carlos Silva 20 Aug '21

20 Aug '21

Hello, Zorillas! Next Wednesday and Thursday (Aug 25th and 26th), we'll have a Manila collaborative review session, where we'll go through the code and review the following proposed features: August 25th: - Share server migration enhancements [1] - [NetApp] Share server migration through SVM Migrate [2] August 26th: - [NetApp] Add Flexgroup volume support [3] Each session is meant to take one hour, starting at 16:00PM UTC. Meeting notes and videoconference links to the share server migration enhancements meeting will be available here [4]. Meeting notes and videoconference links to the flexgroup volumes support meeting will be available here [5]. [1] https://review.opendev.org/c/openstack/manila/+/803623 [2] https://review.opendev.org/c/openstack/manila/+/803624 [3] https://review.opendev.org/c/openstack/manila/+/803622 [4] https://etherpad.opendev.org/p/server-migration-enhancements-collab-review [5] https://etherpad.opendev.org/p/flexgroups-support-collab-review Feel free to attend if you are interested and available. Hoping to see you there! Regards, Carlos Silva irc: carloss

1 0

[election][tc] TC Candidacy
by Ghanshyam Mann 20 Aug '21

20 Aug '21

Hello Everyone, I would like to announce my candidacy for another term on the Technical Committee. First of all, thanks for giving me the opportunity as the Technical Committee member in the previous terms. Apart from TC activities, I am currently a core developer in QA projects and Nova. Also, helping project-config, OpenStack zuul-jobs, Tempest plugins for bug fixes/ Tempest compatibility and in the policy-popup team to make Openstack API policy more consistent and secure. And helping with community-wide goals; because we did not have any community-wide goals for the Xena cycle, I worked on finishing the previous cycles' pending goals. I am serving as TC chair in Xena cycle. TC directions have always been valuable and help to maintain the common standards in OpenStack. In my next term, I would like to continue doing cross-project teams work to solve OpenStack's common problems. Helping secure RBAC with Lance is one of my priority targets for the Yoga cycle, and we are also proposing that as a community-wide goal. Another area I would like to focus on improving TC interaction with community leaders and Board. Apart from that, I will continue working on the activities I am currently doing as TC and help the community grow. Thank you for reading and considering my candidacy. - Ghanshyam Mann (gmann)

1 0

[tripleo] Changing TripleO's release model
by Wesley Hayutin 20 Aug '21

20 Aug '21

Greetings TripleO community! At the most recent TripleO community meetings we have discussed formally changing the OpenStack release model for TripleO [1]. The previous released projects can be found here [2]. TripleO has previously released with release-type[‘trailing’, ‘cycle-with-intermediary’]. To quote the release model doc: ‘Trailing deliverables trail the release, so they cannot, by definition, be independent. They need to pick between cycle-with-rc <https://releases.openstack.org/reference/release_models.html#cycle-with-rc> or cycle-with-intermediary <https://releases.openstack.org/reference/release_models.html#cycle-with-int…> models.’ We are proposing to update the release-model to ‘independent’. This would give the TripleO community more flexibility in when we choose to cut a release. In turn this would mean less backporting, less upstream and 3rd party resources used by potentially some future releases. To quote the release model doc: ‘Some projects opt to completely bypass the 6-month cycle and release independently. For example, that is the case of projects that support the development infrastructure. The “independent” model describes such projects.’ The discussion here is to merely inform the greater community with regards to the proposal and conversations regarding the release model. This thread is NOT meant to discuss previous releases or their supported status, merely changing the release model here [3] [0] https://etherpad.opendev.org/p/tripleo-meeting-items [1] https://releases.openstack.org/reference/release_models.html [2] https://releases.openstack.org/teams/tripleo.html [3] https://opendev.org/openstack/releases/src/branch/master/deliverables/xena

9 17

[release] Release countdown for week R-6, Aug 23 - Aug 27
by Herve Beraud 20 Aug '21

20 Aug '21

In last week's email we erroneously announced that this week (August 19) would be the deadline for all non-client libraries, while only Oslo libraries were concerned. See this email for updated dates. Development Focus ----------------- Work on libraries should be wrapping up, in preparation for the various library-related deadlines coming up. Now is a good time to make decisions on deferring feature work to the next development cycle in order to be able to focus on finishing already-started feature work. General Information ------------------- We are now getting close to the end of the cycle, and will be gradually freezing feature work on the various deliverables that make up the OpenStack release. This coming week is the deadline for general libraries (except client libraries): their last feature release needs to happen before "Non-client library freeze" on August 26. Only bugfixes releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/xena branching request with the review (as an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… In the next weeks we will have deadlines for: * Client libraries (think python-*client libraries), which need to have their last feature release before "Client library freeze" (Sept 2nd) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, September 2nd. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. As we are getting to the point of creating stable/xena branches, this would be a good point for teams to review membership in their xena-stable-maint groups. Once the stable/xena branches are cut for a repo, the ability to approve any necessary backports into those branches for xena will be limited to the members of that stable team. If there are any questions about stable policy or stable team membership, please reach out in the #openstack-stable channel. Upcoming Deadlines & Dates -------------------------- Non-client library freeze: August 26 (R-6 week) Client library freeze: September 2nd (R-5 week) Xena-3 milestone: September 2nd (R-5 week) Cycle Highlights Due: September 2nd (R-5 week) Xena final release: October 6th Yeti PTG: October 18-22 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

1 0

[sahara] Sahara maintenance - PTL vacancy and call for contributions
by Jeremy Freudberg 20 Aug '21

20 Aug '21

Hi, I've worked on Sahara for a long time, especially since the Mirantis folks left. I implemented many features and fixes from 2017 through 2019 but barely anything more recently. Now it is time for me to actually move on. I don't plan to be PTL in the upcoming cycle. Sahara is not in especially good shape, given the situation with the vendors and other neglect. Help is needed, in order for Sahara to continue as a useful project. As of now I am not aware of anyone to fill the PTL role or generally contribute to the project. If you use Sahara and have interest in maintaining it, please reach out. Thanks, Jeremy

1 0

[Interop][Refstack] Today's meeting is cancelled
by Arkady Kanevsky 20 Aug '21

20 Aug '21

Please, see progress on https://etherpad.opendev.org/p/interop <https://www.google.com/url?q=https://etherpad.opendev.org/p/interop&sa=D&so…> . -- Arkady Kanevsky, Ph.D. Phone: 972 707-6456 Corporate Phone: 919 729-5744 ext. 8176456

1 0

[Ironic] No upstream meeting on Aug 23
by Iury Gregory 20 Aug '21

20 Aug '21

Hello Ironicers, I forgot to send this email earlier. Since next week is our midcycle, we won't have the upstream meeting. -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 0

[Ironic] Xena Midcycle next week!
by Iury Gregory 20 Aug '21

20 Aug '21

Hello Ironicers! Our schedule for the Midcycle is available in the etherpad[1]. See you next week! [1] https://etherpad.opendev.org/p/ironic-xena-midcycle -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 1

Active and standby controller nodes
by Midhunlal Nb 20 Aug '21

20 Aug '21

Hi team, I have a rocky installed openstack environment and it is working fine.In my set up I have; 1 controller node,2 compute nodes and 1 storage node. Now we are planning to add 1 more controller node as standby.Is it possible to add 1 more controller node in existing set up? if it is possible ,anyone please share the procedure. Thanks & Regards Midhunlal N B +918921245637

3 3

Wallaby Magnum Issue
by Karera Tony 19 Aug '21

19 Aug '21

Hello Team, I deployed Openstack Wallby on Ubuntu20 and enabled Magum, however when I create a cluster I get the error below. *Status ReasonERROR: Property error: : resources.api_lb.properties: : Property allowed_cidrs not assigned* Can someone advise on where I could be wrong. Btw, I disabled load balancer while creating the cluster. Regards Tony Karera

3 6

[blazar] PTL on holiday next week
by Pierre Riteau 19 Aug '21

19 Aug '21

Hello, I will be on holiday next week and will be back on August 30. The bi-weekly IRC meeting of August 26 is cancelled. Cheers, Pierre Riteau (priteau)

1 0

[election][blazar] PTL candidacy for Yoga
by Pierre Riteau 19 Aug '21

19 Aug '21

Hi, I would like to self-nominate for the role of PTL of Blazar for the Yoga release cycle. I have been PTL since the Stein cycle and I am willing to continue in this role. During the Xena cycle, an existing contributor became a core reviewer and we also welcomed changes from new contributors. I will keep working with the community to maintain the Blazar software for their use cases and encourage the addition of new functionalities, such as providing a calendar view in the dashboard or supporting preemptible instances. Thank you for your support, Pierre Riteau (priteau)

1 0

It's time to submit your OpenStack User Survey
by Allison Price 19 Aug '21

19 Aug '21

Hi everyone, Here’s my annual email requesting you complete the OpenStack User Survey [1] and share with your local communities / community friends who are operating OpenStack. Anonymous reposes and aggregated data from the User Survey are shared with the OPenStack PTLs and overall community to help understand operator software requirements. If you have never taken it before, please do! We welcome your feedback and I am happy to answer any questions you may have. If you are one of the many who have, all of your previous information should be stored, so you will just need to provide updates where relevant and re-save. Thank you all! Cheers, Allison [1] https://www.openstack.org/user-survey/survey-2021 <https://www.openstack.org/user-survey/survey-2021> Allison Price Director of Marketing & Community OpenInfra Foundation e: allison(a)openstack.org <mailto:allison@openstack.org>

1 1

Configuration of OvS running on SmartNIC using OpenStack
by Hrishikesh Karanjikar 19 Aug '21

19 Aug '21

Dear All, I am looking forward to configuration/management of OvS running on SmartNIC using Openstack. Any pointers that can help are appreciated. -- Thanks and Regards, Hrishikesh Karanjikar

2 1

[all][tc] Technical Committee next weekly meeting on Aug 19th at 1500 UTC
by Ghanshyam Mann 19 Aug '21

19 Aug '21

Hello Everyone, Technical Committee's next weekly meeting is scheduled for Aug 19th at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, Aug 18th, at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

3 5

[tacker][elections] PTL candidacy for Yoga
by Yasufumi Ogawa 19 Aug '21

19 Aug '21

Hi, I'd like to propose my candidacy for Tacker PTL in Yoga cycle. I've contributed to Tacker to introduce ETSI-NVF standard compliant features from Victoria cycle as a PTL. It's still midway of roadmap of our development plan and I'll continue to lead the development in the next cycle. - Implement the latest container technology with ETSI NFV standard. - Support multi API versions which is a mechanism for operators enable to deploy mixed environment of multi-vendor products in which some products provide a stable version APIs while other products adopt move advanced ones. - Proceed to design and implement test framework under development in ETSI NFV TST to improve the quality of the product, not only unit tests and functional tests, but also introduce more sophisticated scheme such as robot framework. - And also new requirements will be proposed in the next PTG! Thanks, Yasufumi

1 0

[murano][tc] Project Retirement
by Mohammed Naser 19 Aug '21

19 Aug '21

Hi folks, Today, at the TC weekly meeting, it was brought up that Murano was not very active over the past few years and most likely has had a major amount of bitrot. The community is not able to reach the current PTL of the project either. Personally, I think that at this point, Murano is a bit past it's time. We've got a lot more developments in application deployment nowadays, OpenStack offers things like Magnum to get a Kubernetes cluster which you can run workloads on via Helm, or projects like Zun offer serverlerss containers directly, making a lot of what Murano used to do not so helpful in the current landscape. I'm sending this email to discuss/propose the idea of retiring the project. Regards, Mohammed -- Mohammed Naser VEXXHOST, Inc.

5 6

[nova][qa][infra] Adding no_timer_check to the kernel command line of our CI images
by Lee Yarwood 19 Aug '21

19 Aug '21

Hello all, For a while now we've been attempting to track down some infrequent but annoying Tempest test cleanup failures in CI when detaching volumes from an instance. Finally after rewriting part of the Tempest logic controlling the cleanup we've been able to confirm that this is being caused by a kernel panic within the instance at boot time as documented in the following bug: Failure to detach volume during Tempest test cleanup due to APIC related kernel panic within the guest OS https://bugs.launchpad.net/nova/+bug/1939108 This had been previously found in 2014 but at the time a fix was only proposed to Nova that would solve this when using a supplied kernel image: cirros 0.3.1 fails to boot https://bugs.launchpad.net/cirros/+bug/1312199 Use no_timer_check with soft-qemu https://review.opendev.org/c/openstack/nova/+/96090 Most (all?) of our CI currently running with [libvirt]virt_type=qemu uses the full Cirros 0.5.2 image. Does anyone have any suggestions on the best way of modifying the image(s) we use in CI to use the no_timer_check kernel command line arg? Thanks in advance, -- Lee Yarwood A5D1 9385 88CB 7E5F BE64 6618 BCA6 6E33 F672 2D76

4 5

[kolla][wallaby]bug 1815989
by Ignazio Cassano 19 Aug '21

19 Aug '21

Hello All, I just updated my kolla wallaby installation, and seems the bug 1815989 has not solved yet. I lost packages during live migration. Is there any prediction for the solution of this problem? Many thanks Ignazio

1 0

[puppet] Propose retiring puppet-monasca
by Takashi Kajinami 19 Aug '21

19 Aug '21

Hello, tl;dr If nobody is interested in fixing bug 1930553, then I'll propose retiring puppet-monasca during this cycle. A few months ago, I found an issue[1] with puppet-monasca and it turned out that the module is not compatible with the recent puppet-python. The module still relies on python::virtualenv which was removed in puppet-python 6.0. Currently the gate was unblocked by pinning puppet-python to an older version but we should remove that pin at some point. [1] https://bugs.launchpad.net/puppet-monasca/+bug/1930553 However, fixing the problem requires relatively large refactoring, and I'm afraid we(at least, I) don't have enough resources for that. The main challenge is that we have no functional tests in our CI jobs now to validate the fix in puppet-monasca. I checked the commit history of this module but I don't see any meaningful change made for several years. If nobody is interested in maintaining the module and fixing the problem then I'd propose retiring the module. I'll wait for any feedback for a week, then decide whether I'll submit actual patches to retire the repo. Thank you, Takashi

1 1

[masakari][elections] Self-nomination for PTL in Yoga
by Radosław Piliszek 19 Aug '21

19 Aug '21

Dears, I have been making sure Masakari is alive and well during the last 2 cycles (Wallaby and Xena). I have also ensured Masakari's smooth release at the end of its Victoria cycle before that. I also contribute to the Kolla project which is able to deploy Masakari with its monitors and the required Pacemaker stack. I plan to continue my work around the project, focusing on improving the reliability of and community confidence in Masakari by ensuring we align with the rest of the OpenStack, run meetings, have complete, healthy and robust gating, triage bugs, handle the mailing list, and improve our docs and contribution transparency. -yoctozepto

1 0