August 2022 - openstack-discuss - lists.openstack.org

[release] Release countdown for week R-5, Aug 29 - Sep 02
by Előd Illés 26 Aug '22

26 Aug '22

Development Focus ----------------- We are getting close to the end of the Zed cycle! Next week on September 1st, 2022 is the Zed-3 milestone, also known as feature freeze. It's time to wrap up feature work in the services and their client libraries, and defer features that won't make it to the 2023.1 Antelope cycle. General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on September 1st, 2022. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/zed branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… September 1st, 2022 is also the deadline for feature work in all OpenStack deliverables following the cycle-with-rc model. To help those projects produce a first release candidate in time, only bugfixes should be allowed in the master branch beyond this point. Any feature work past that deadline has to be raised as a Feature Freeze Exception (FFE) and approved by the team PTL. Finally, feature freeze is also the deadline for submitting a first version of your cycle-highlights. Cycle highlights are the raw data that helps shape what is communicated in press releases and other release activity at the end of the cycle, avoiding direct contacts from marketing folks. See https://docs.openstack.org/project-team-guide/release-management.html#cycle… for more details. Upcoming Deadlines & Dates -------------------------- Zed-3 milestone (feature freeze): September 1st, 2022 (R-5 week) RC1 deadline: September 15th, 2022 (R-3 week) Final RC deadline: September 29th, 2022 (R-1 week) Final Zed release: October 5th, 2022 Next PTG: October 17-21, 2022 (virtual PTG!!!) Előd Illés irc: elodilles

1 0

[Nova] Can't Attach An Encrypted NFS (luksv1) Volume
by Sofia Enriquez 26 Aug '22

26 Aug '22

Hello Nova Team, eharney and I are working on NFS encrypted volume support [1] and [2]. I'm trying to attach an encrypted volume to a nova instance. However, this fails with "libvirt.libvirtError: internal error: unable to execute QEMU command 'blockdev-add': Image is not in qcow2 format" error. I'm using a Devstack environment (nova/cinder master branch). Last week I opened a bug report [3] and I'd like to raise some attention to it. I've proposed a WIP patch [4] with a possible solution that I'd like to get some feedback on or know if should follow a different approach. The problem is that is_luks() returns false for the NFS case, because NFS is using LUKS inside of qcow2 and not regular LUKS. Let me know what you think Thank you Sofia [1] https://review.opendev.org/c/openstack/cinder/+/597148 [2] https://review.opendev.org/c/openstack/cinder/+/749155 [3] https://bugs.launchpad.net/nova/+bug/1987311 [4] https://review.opendev.org/c/openstack/nova/+/854030 -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[charms][elections] PTL candidacy for Antelope cycle
by Alex Kavanagh 26 Aug '22

26 Aug '22

Hi All I would like to put myself forward for another cycle for the Charms PTL for the Antelope cycle. I've been a contributor to OpenStack and Charms since 2016 and a core member since mid 2016. I've also been the PTL for the last 2 cycles. Why do I want to be PTL again? The team has again achieved a huge amount, testing and supporting the charms and packages across multiple Ubuntu LTS releases (bionic, focal and now, jammy) with Charms and OpenStack support back to queens. We've (almost) transitioned to the new Charmhub ( charmhub.io) and will continue to support Queens through to the upcoming Zed release, and onto Antelope. I'd like to continue to support the team as we march forward with the responsibilities of the PTL to smooth the processes. Thanks Alex (tinwood) -- Alex Kavanagh - Software Engineer OpenStack Engineering - Data Centre Development - Canonical Ltd

1 0

[Glance] PTL non-candidacy
by Abhishek Kekane 26 Aug '22

26 Aug '22

Hi all, I'm writing this email to let you know that I'm not going to run for Glance PTL for the Antelope dev cycle, I think it's time for some new ideas and new approaches so it's a good idea to hand over the hat of PTL to a new member of the team. I've been serving Glance PTL since Ussuri, tried my best to keep Glance stable, lots of changes have been made since then, my initial focus was to improve glance-tempest coverage which we managed to do in past cycles. I would like to thank all the members of the Glance team and others for supporting me during this period. My plan is to stick around, attend to my duties as a glance core contributor, and support my successor in whatever way I can to make for a smooth transition. Thank you once again! Cheers, Abhishek Kekane

4 3

[kuryr][elections] PTL candidacy for Antelope cycle
by Roman Dobosz 26 Aug '22

26 Aug '22

Hello, I would like to announce my candidacy to be the Kuryr PTL for the next Antelope cycle. I've been Kuryr contributor since the Ussuri release and became core reviewers member at the end of Victoria cycle. In the upcoming Antelope cycle, I'd like to focus on Kuryr stability and compatibility with upcoming Kubernetes release. Another thing which I'd like to move forward is to eliminate Kuryr services restarts. Thanks, Roman Dobosz (gryf)

1 0

[election][heat][ptl] PTL non-candidacy
by Rico Lin 25 Aug '22

25 Aug '22

Hi all, As the PTL election will soon start, I would like to share my statement on not planning to run another term of Heat PTL. And instead, I encourage anyone (core reviewer or not) who is interested to put their name on. I will definitely still stay around and help with reviews and patches. *Rico Lin*

2 1

Regarding Designate Installation in ansible Playbook
by Adivya Singh 25 Aug '22

25 Aug '22

hi Team, I have made under conf.d a designate. yml file, and rerunning the setup of Openstack-setuphost but still it is not installing a Designate Container in OpenStack. Is there any Reason for this, Something i am doing right Regards Adivya Singh

2 1

[OPS] Participation Poll for OPS Meetup at the PTG
by Amy Marrich 25 Aug '22

25 Aug '22

Hey all, Just putting this on the list for more visibility. On Monday we posted a poll from the OPS Meetup Twitter account for how Operators would prefer to interact with the Developers[0]. The poll closes on Monday but if you don't have twitter please reply here with your preference. We also have a poll for preferred times[1] Thanks, Amy 0 - https://twitter.com/osopsmeetup/status/1561708280455593984 1 - https://doodle.com/meeting/participate/id/bD9kR2yd

1 0

[neutron] Drivers meeting agenda - 26.08.2022.
by Lajos Katona 25 Aug '22

25 Aug '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. We have the following RFEs to discuss tomorrow: * [RFE] Add a port extension to set/define the switchdev capabilities (#link https://bugs.launchpad.net/neutron/+bug/1987093 ) * [RFE] Add DSCP mark 44 (#link https://bugs.launchpad.net/neutron/+bug/1987378 ) And we have a topic for the On Demand agenda: * (amorin): Add new novaplug mechanism driver ** https://bugs.launchpad.net/neutron/+bug/1986969 ** https://review.opendev.org/c/openstack/neutron/+/854553 [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

DCN and DVR in Openstack wallaby | tripleo
by Swogat Pradhan 24 Aug '22

24 Aug '22

Hi, I have a site1 and a site2. Site1 contains the controller nodes with some compute and storage and in site2 i have compute nodes maybe hci solution for it. site1 has a different network pool and site2 has a different network pool and these cannot be extended to one another. What I want to know is how I am going to configure network to be used by the compute nodes in site2. If i use DVR then i can just create a normal external network which will only be used for site2 and then the traffic doesn't have to go through the network node. Is it the right solution? And is DVR enabled by default or do I have to use the neutron-ovn-dvr.yaml template? And if i use DVR do i have to set the following parameter?: ComputeParameters: NeutronBridgeMappings: "" Is DCN with DVR the correct approach? With regards, Swogat Pradhan

1 0