- openstack-discuss - lists.openstack.org

[all][Neutron][devstack] Deprecate lib/neutron
by Lajos Katona 06 Jan '22

06 Jan '22

Hi, In devstack we have two more or less overlapping lib for deploying Neutron: lib/neutron and lib/neutron-legacy. lib/neutron-legacy was recently "undeprecated" (see [0]), and Openstack CI mostly (fully?) uses it. To avoid double maintenance, and confusion in settings we would like to deprecate lib/neutron, for recent discussions see [1] and [2]. The plan is to keep lib/neutron for 2 cycles (that will be AA or the release after Z) and delete lib/neutron then, and rename lib/neutron-legacy to lib/neutron. As You can see from the discussions below there are questions like how to name the processes, log-files etc..., as lib/neutron-legacy uses q-* and lib/neutron uses neutron-* names. The best would be to keep both in the long term (we love q-* as historical tradition, but neutron-* looks like so fresh and modern;)) If you have any thoughts suggestions or questions please answer to this mail or comment on the deprecation patch: [3] [0]: https://review.opendev.org/c/openstack/devstack/+/704829 [1]: https://meetings.opendev.org/meetings/networking/2022/networking.2022-01-04… [2]: https://meetings.opendev.org/irclogs/%23openstack-qa/%23openstack-qa.2022-0… [3]: https://review.opendev.org/c/openstack/devstack/+/823653

1 0

[neutron] Dadfailed of ipv6 metadata IP in qdhcp namespace and disappearing dhcp namespaces
by Kamil Madáč 06 Jan '22

06 Jan '22

Hello, In our small cloud environment, we started to see weird behavior during last 2 months. Dhcp namespaces started to disappear randomly, which caused that VMs losed connectivity once dhcp lease expired. After the investigation I found out following issue/bug: 1. ipv6 metadata address of tap interface in some qdhcp-xxxx namespaces are stucked in "dadfailed tentative" state (i do not know why yet) 2. 3. root@cloud01:~# ip netns exec qdhcp-3094b264-829b-4381-9ca2-59b3a3fc1ea1 ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2585: tap1797d9b1-e1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether fa:16:3e:77:64:0d brd ff:ff:ff:ff:ff:ff inet 169.254.169.254/32 brd 169.254.169.254 scope global tap1797d9b1-e1 valid_lft forever preferred_lft forever inet 192.168.0.2/24 brd 192.168.0.255 scope global tap1797d9b1-e1 valid_lft forever preferred_lft forever inet6 fe80::a9fe:a9fe/64 scope link dadfailed tentative valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fe77:640d/64 scope link valid_lft forever preferred_lft forever 4. 5. This blocked dhcp agent to finish sync_state function, and NetworkCache was not updated with subnets of such neutron network 6. During creation of VM assigned to such network, agent does not detect any subnets (see point 2), so he thinks (reload_allocations()) there is no dhcp needed and deletes qdhcp-xxxx namespace, so no DHCP and no Metadata are working on such network since that moment, and after 24h we see connectivity issues. 7. Restart of DHCP agent recreates missing qdhcp-xxxx namespaces, but NetworkCache in dhcp agent is again empty, so creation of VM deletes the qdhcp-xxxx namespace again 🙁 Workaround is to remove dhcp agent from that network and add it again. Interestingly, sometimes I need to do it multiple times, because in few cases tap interface in new qdhcp finishes again in dadfailed tentative state. After year in production we have 20 networks out of 60 in such state. We are using kolla-ansible deployment on Ubuntu 20.04, kernel 5.4.0-65-generic. Openstack version Victoria and neutron is in version 17.2.2.dev70. Is that bug in neutron, or is it misconfiguration of OS on our side? I'm locally testing patch which disables ipv6 dad in qdhcp-xxxx namespace (net.ipv6.conf.default.accept_dad = 1), but I'm not sure it is good solution when it comes to other neutron features? Kamil Madáč Slovensko IT a.s.

3 3

[horizon] Bump XStatic-Angular-FileUpload to 12.2.13
by Thomas Goirand 06 Jan '22

06 Jan '22

Hi, After someone unrelated to OpenStack maintenance uploaded libjs-angular-file-upload 12.2.13, I tested it, and it didn't break Horizon (at least, when I manually uploaded a file, it worked...). So IMO, it would be fine to just bump to that version. Cheers, Thomas Goirand (zigo)

1 0

[keystone][requirements] keystone holding back pysaml2-7.1.x update
by Matthew Thode 05 Jan '22

05 Jan '22

Hi again, pysaml2===7.1.0 has been breaking updates for a while now. https://review.opendev.org/818612 -- Matthew Thode

1 0

[horizon][requirements] falling behind on requirements updates
by Matthew Thode 05 Jan '22

05 Jan '22

Hi, The following requirements updates have been stalled. XStatic-Angular===1.8.2.1 Has been held back for at least 7 months, but I think closer to a year now. Some review history is here: https://review.opendev.org/794258 django-compressor===2.4.1 rcssmin===1.1.0 rjsmin===1.1.0 These come as a group and have been holding things back for about a month. I'm not sure what's holding things back here on the horizon side. Review bundled with XStatic-Angular here: https://review.opendev.org/823449 -- Matthew Thode

1 0

[all][tc] Technical Committee next weekly meeting on Jan 6th at 1500 UTC
by Ghanshyam Mann 05 Jan '22

05 Jan '22

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

1 1

[infra] Missing releases from opendev.org/opendev/git-review/tags
by Pete Zaitcev 05 Jan '22

05 Jan '22

Greetings: I noticed that the list of tags for git-review in the website does not include the 2.2.x tags, which exist in git: [zaitcev@niphredil git-review-0]$ grep url .git/config url = https://opendev.org/opendev/git-review.git [zaitcev@niphredil git-review-0]$ git tag -l --format='%(objectname) %(objecttype) %(refname)'| grep 2\\.2 bb81051c2481d4ac983ec0b28bd62b590d361141 tag refs/tags/2.2.0 [zaitcev@niphredil git-review-0]$ git show bb81051c2481d4ac983ec0b28bd62b590d361141 | head -5 tag 2.2.0 Tagger: Jeremy Stanley <fungi(a)yuggoth.org> Date: Wed Nov 24 02:20:05 2021 +0000 Release 2.2.0 [zaitcev@niphredil git-review-0]$ The 2.2.0 is missing from https://opendev.org/opendev/git-review/tags Coincidentally, it is also missing from https://tarballs.opendev.org/openstack/git-review/ Is this something that the infrastructure team did on purpose? Or is this just a bug to be reported? -- Pete

3 7

RE: [nova][dev] Revisiting qemu emulation where guest arch != host arch
by Race, Jonathan 05 Jan '22

05 Jan '22

That makes sense which is the best method I saw as well. For your example "use HW_ARCH_X86 to idenfiy the host as being x86 and COMPUTE_ARCH_X86 for emulated", I actually implemented a new field called hw_emulation_architecture as to not conflict with any existing nova operations and to eliminate confusion. This allows for setting this specific value as an image meta property in glance, and if it is set then it will execute emulation via qemu for the designated architecture. If it is not set then operations will occur as normal. https://review.opendev.org/c/openstack/nova/+/822053 is really just an initial response for the bug, that was submitted. And our long-term goal is to collab on this existing blueprint https://blueprints.launchpad.net/nova/+spec/pick-guest-arch-based-on-host-a… for a more full set of capabilities. Jonathan Race Cyber Range Engineer | Georgia Cyber Range GEORGIA CYBER CENTER On Wed, 2020-07-15 at 14:17 +0000, Apsey, Christopher wrote: > All, > > A few years ago I asked a question[1] about why nova, when given a hw_architecture property from glance for an image, would not end up using the correct qemu-system-xx binary when starting the guest process on a compute node if that compute nodes architecture did not match the proposed guest architecture. As an example, if we had all x86 hosts, but wanted to run an emulated ppc guest, we should be able to do that given that at least one compute node had qemu-system-ppc already installed and libvirt was successfully reporting that as a supported architecture to nova. It seemed like a heavy lift at the time, so it was put on the back burner. > > I am now in a position to fund a contract developer to make this happen, so the question is: would this be a useful blueprint that would potentially be accepted? > yes, i cant really speak to how much use it would get or how useful it woudl be to the majoriy fo user but i would be supportive of adding this capablity. We have to be a little carful to get the design wright for example we might want to differnciate between the native architecture and emulated architectures e.g. use HW_ARCH_X86 to idenfiy the host as being x86 and COMPUTE_ARCH_X86 for emulated with the new "in" suppot being added to placment we can use required=in:HW_ARCH_X86,COMPUTE_ARCH_X86 in cases where you dont care and by default if you wanted native only you could use the HW_ARCH_* traits in the image and we can have a prefileter add the both triats by default if the architrue is set in the iamge and there is not arch trait in the flavor or image. i will certenly review a spec if you proporse one but you might now have time to get it approved this cycle the spec deadlien woudl have been thursday btu it has been moved to next week. > Most of the time when people want to run an emulated guest they would just nest it inside of an already running guest of the native architecture, but that severely limits observability and the task of managing any more than a handful of instances in this manner quickly becomes a tangled nightmare of networking, etc. I see real benefit in allowing this scenario to run natively so all of the tooling that exists for fleet management 'just works'. This would also be a significant differentiator for OpenStack as a whole. > > Thoughts? > > [1] > http://lists.openstack.org/pipermail/openstack-operators/2018-August/015653…<https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.open…> > > Chris Apsey > Director | Georgia Cyber Range > GEORGIA CYBER CENTER > > 100 Grace Hopper Lane | Augusta, Georgia | 30901 > https://www.gacybercenter.org<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.gacyb…> >

1 0

[largescale-sig] Next meeting: Jan 5th, 15utc
by Thierry Carrez 05 Jan '22

05 Jan '22

Hi everyone, and happy new year! To kick off 2022, the Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. You can doublecheck how that time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220105T15 We will be discussing our upcoming activities and our next OpenInfra Live episode, as well as any topic you may add to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[nova][dev] Revisiting qemu emulation where guest arch != host arch
by Apsey, Christopher 05 Jan '22

05 Jan '22

All, A few years ago I asked a question[1] about why nova, when given a hw_architecture property from glance for an image, would not end up using the correct qemu-system-xx binary when starting the guest process on a compute node if that compute nodes architecture did not match the proposed guest architecture. As an example, if we had all x86 hosts, but wanted to run an emulated ppc guest, we should be able to do that given that at least one compute node had qemu-system-ppc already installed and libvirt was successfully reporting that as a supported architecture to nova. It seemed like a heavy lift at the time, so it was put on the back burner. I am now in a position to fund a contract developer to make this happen, so the question is: would this be a useful blueprint that would potentially be accepted? Most of the time when people want to run an emulated guest they would just nest it inside of an already running guest of the native architecture, but that severely limits observability and the task of managing any more than a handful of instances in this manner quickly becomes a tangled nightmare of networking, etc. I see real benefit in allowing this scenario to run natively so all of the tooling that exists for fleet management 'just works'. This would also be a significant differentiator for OpenStack as a whole. Thoughts? [1] http://lists.openstack.org/pipermail/openstack-operators/2018-August/015653… Chris Apsey Director | Georgia Cyber Range GEORGIA CYBER CENTER 100 Grace Hopper Lane | Augusta, Georgia | 30901 https://www.gacybercenter.org

2 2

openstack-kolla with GlusterFS integration
by Satish Patel 05 Jan '22

05 Jan '22

Folks, Recently I have started playing with the Openstack Kolla Project because of some requirements. I want to integrate kolla with GlusterFS for nova vm backend storage. I have functional Glsuter storage and want to mount on compute node to use for vm backend but not sure how do i do that because i am new to containers I can see kolla use following to bind volume with nova_compute container { "Type": "volume", "Name": "nova_compute", "Source": "/var/lib/docker/volumes/nova_compute/_data", "Destination": "/var/lib/nova", "Driver": "local", "Mode": "rw", "RW": true, "Propagation": "" } If I can mount GlusterFS in /mnt directory then how do I tell docker to use /mnt to create volume for nova_compute?

2 6

Logical Volume migration to a New Openstack environment
by KK CHN 05 Jan '22

05 Jan '22

List, I am in need to migrate a Virtual machine ( running in an old OpenStack environment with only one controller). This VM has its own disk file + a logical volume attached to it with application data on it. Only Cinder backend( No rbd/ceph backend configured ) for this environment. Now I am migrating this Virtual machine to another OpenStack(ussuri with three controllers, three compute nodes and three storage nodes) environment with ceph/rbd backend. I am able to export the VM with its disk file and import it to the other openstack environment and able to boot the machine. But How to export the attached logical volume from the old VM and attach to the VM in the other environment ? what is the methodology to follow to export this logical volume in the old openstack VM and import to the new VM running in the other openstack environment ? kindly share your suggestions/expertise to perform this Thanks in advance for your valuable guidance. Krish

3 2

[cinder] Bug deputy report for week of 01-05-2022
by Sofia Enriquez 05 Jan '22

05 Jan '22

No meeting today. This is a bug report from 12-29-2021 to 01-05-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- No bugs in this period :P Cheers, -- 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

[nova][placement] Spec approval freeze punted to Jan13st
by Sylvain Bauza 05 Jan '22

05 Jan '22

Hi folks, As agreed on yesterday's nova meeting [1], we accepted to punt the spec approval freeze for one week, ie. at January 13st. That said, we won't accept any exception for a spec approval after this day as we will only have 6 weeks after Jan 13st until FeatureFreeze. Thanks (and happy new 2022 by the way), -Sylvain [1] https://meetings.opendev.org/meetings/nova/2022/nova.2022-01-04-16.00.log.h…

1 0

OpenInfra Live - January 6 at 9am CT
by Allison Price 04 Jan '22

04 Jan '22

Hi everyone, This week, I will be hosting the first OpenInfra Live <http://openinfra.live/> episode of 2022, brought to you by the OpenStack, Kata Containers, Zuul, and StarlingX communities! It's been one year since the formation of the OpenInfra Foundation and the global community has produced more software, more production use cases, more collaboration than ever before. Join us as we look back at 2021, the software milestones, production growth, and momentum across the OpenInfra landscape. Episode: A Year in Review: OpenInfra Highlights from 2021 Date and time: Thursday, January 6 at 9am CT (1500 UTC) You can watch us live on: YouTube <https://www.youtube.com/watch?v=MhAK2efrl9I> LinkedIn <https://www.linkedin.com/video/event/urn:li:ugcPost:6884201840976764928/> Facebook <https://www.facebook.com/104139126308032/posts/4704702346251664/> WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Ghanshyam Mann, OpenStack TC Chair Tao Peng, Kata Containers Architecture Committee Member James Blair, Zuul Maintainer Greg Waines, StarlingX Technical Steering Committee Member Have an idea for a future episode? Share it now at ideas.openinfra.live <https://openinfrafoundation.formstack.com/forms/openinfralive>. Have you heard that the OpenInfra Summit is going back to Berlin, June 7-9? Registration and sponsorship opportunities are now available here: https://openinfra.dev/summit/ <https://openinfra.dev/summit/>. Thanks, Allison

1 0

[charms] nominate Hemanth Nakkina for charms-core
by Edward Hope-Morley 04 Jan '22

04 Jan '22

I would like propose Hemanth Nakkina for charms-core. Hemanth has really stepped up his efforts to provide invaluable contributions both in code and reviews and I beleive he is in a good position to be considered for core where he will be able to provide additional value to the project. Hemanth has demonstrated rigour for quality through his contributions and is always keen to help others with his deep knowledge of the charms and Openstack. Here is a list of all his contributions: patches: https://review.opendev.org/q/owner:hemanth.nakkina%2540canonical.com reviews: https://review.opendev.org/q/reviewedby:hemanth.nakkina%2540canonical.com I hope you will join me in voting for Hemanth. - Ed

6 5

Subject: [kolla] Updating libvirt container images without VM downtime
by CHALANSONNET Stéphane (Acoss) 04 Jan '22

04 Jan '22

Hello, When you update or restart libvirt container , the instances aren't restart . The qemu process /usr/libexec/qemu-kvm is executed outside the container. However for the lastest functionality you need to restart your instances later Regards, stephane.chalansonnet(a)acoss.fr -----Message d'origine----- De : openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> Envoyé : mardi 4 janvier 2022 20:18 À : openstack-discuss(a)lists.openstack.org Objet : openstack-discuss Digest, Vol 39, Issue 11 Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss or, via email, send a message with subject or body 'help' to openstack-discuss-request(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. Re: [charms] nominate Hemanth Nakkina for charms-core (Frode Nordahl) 2. Re: [TripleO] Douglas Viroel for tripleo-ci core (Jason Poulin) 3. Re: [TripleO] Douglas Viroel for tripleo-ci core (Ade Lee) 4. Re: [TripleO] Douglas Viroel for tripleo-ci core (Jeremy Stanley) 5. [kolla] Updating libvirt container images without VM downtime (J-P Methot) ---------------------------------------------------------------------- Message: 1 Date: Tue, 4 Jan 2022 17:33:34 +0100 From: Frode Nordahl <frode.nordahl(a)canonical.com> To: Billy Olsen <billy.olsen(a)canonical.com> Cc: Alex Kavanagh <alex.kavanagh(a)canonical.com>, openstack-discuss(a)lists.openstack.org Subject: Re: [charms] nominate Hemanth Nakkina for charms-core Message-ID: <CAKpbOATbKOH1116UUxAWjQoyRiE-9u8CiHjTcTashb6tcvQ1yg(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" On Fri, Dec 10, 2021 at 6:12 PM Billy Olsen <billy.olsen(a)canonical.com> wrote: > > > > On Fri, Dec 10, 2021 at 7:08 AM Alex Kavanagh <alex.kavanagh(a)canonical.com> wrote: >> >> >> >> On Fri, Dec 10, 2021 at 1:24 PM Edward Hope-Morley <opentastic(a)gmail.com> wrote: >>> >>> I would like propose Hemanth Nakkina for charms-core. Hemanth has >>> really stepped up his efforts to provide invaluable contributions >>> both in code and reviews and I beleive he is in a good position to >>> be considered for core where he will be able to provide additional value to the project. >>> Hemanth has demonstrated rigour for quality through his >>> contributions and is always keen to help others with his deep >>> knowledge of the charms and Openstack. Here is a list of all his contributions: >>> >>> patches: >>> https://review.opendev.org/q/owner:hemanth.nakkina%2540canonical.com >>> reviews: >>> https://review.opendev.org/q/reviewedby:hemanth.nakkina%2540canonica >>> l.com >>> >>> I hope you will join me in voting for Hemanth. >> >> >> +1 from me; Hemanth has submitted good patches and thoughtful reviews in my experience. He would be a good member of charms-core. >> >> Cheers >> Alex. >> > > I concur with Alex here. +1 from me as well. I concur with Alex and Billy here. I would like to add that it has been a pleasure to work with Hemanth to resolve some really hard problems and I look forward to what he can bring to the team and project in the capacity of being a charms core. -- Frode Nordahl > - Billy > >>> >>> >>> - Ed >>> >>> >> >> >> -- >> Alex Kavanagh - Software Engineer >> OpenStack Engineering - Data Centre Development - Canonical Ltd ------------------------------ Message: 2 Date: Tue, 4 Jan 2022 12:00:53 -0500 From: Jason Poulin <corellianimports(a)aol.com> To: Ronelle Landy <rlandy(a)redhat.com> Cc: Amol Kahat <akahat(a)redhat.com>, Marios Andreou <marios(a)redhat.com>, openstack-discuss <openstack-discuss(a)lists.openstack.org> Subject: Re: [TripleO] Douglas Viroel for tripleo-ci core Message-ID: <C5A32FC3-0DB1-4190-9A10-6D8288B95F88(a)aol.com> Content-Type: text/plain; charset="utf-8" Can someone take me off this list. I don?t know why I?m on it. Please. > On Jan 4, 2022, at 11:32 AM, Ronelle Landy <rlandy(a)redhat.com> wrote: > > ? > +1 absolutely > >> On Tue, Jan 4, 2022 at 11:25 AM Amol Kahat <akahat(a)redhat.com> wrote: >> +1 >> >>> On Tue, Jan 4, 2022 at 6:40 PM Marios Andreou <marios(a)redhat.com> wrote: >>> Hello TripleO ( & happy new year :) \o/ ) >>> >>> I'd like to propose Douglas Viroel [1] for core on the tripleo-ci >>> repos (openstack/tripleo-ci, openstack/tripleo-quickstart-extras, >>> openstack/tripleo-quickstart, openstack/tripleo-repos). >>> >>> Doug joined the team last year and besides his code contributions he >>> has also been consistently providing many very useful and thoughtful >>> code reviews. I think he will be an excellent addition to the ci >>> core team. >>> >>> As is customary, let's leave this thread open for a week and if >>> there are no objections or other concerns then we add Doug to the >>> core group next week. >>> >>> thanks, marios >>> >>> [1] https://review.opendev.org/q/owner:viroel%2540gmail.com >>> >>> >> >> >> -- >> Amol Kahat >> Software Engineer >> Red Hat India Pvt. Ltd. Pune, India. >> akahat(a)redhat.com >> B764 E6F8 F4C1 A1AF 816C 6840 FDD3 BA6C 832D 7715

1 0

[neutron] Bug deputy December 27
by Rodolfo Alonso Hernandez 04 Jan '22

04 Jan '22

Hello: These are the bugs opened during the last week: https://bugs.launchpad.net/neutron/+bug/1956034: "ovn load balancer health monitor cause mac address conflict". Unassigned. https://bugs.launchpad.net/neutron/+bug/1956035: "ovn load balancer member failover not working when accessed from floating ip". Unassigned. https://bugs.launchpad.net/neutron/+bug/1955799: "Not changing floatingip status while deleting instance that had floatingip assocciate (Showing ACTIVE)". Patch: https://review.opendev.org/c/openstack/neutron/+/822091 Regards.

1 0

[neutron] CI meeting agenda - 4.01.2022
by Slawek Kaplonski 04 Jan '22

04 Jan '22

Hi, It's just reminder that we will today have Neutron CI meeting. It will be at 3pm UTC time. Meeting will be on the #openstack-neutron channel and on jiitsi: https://meetpad.opendev.org/neutron-ci-meetings Agenda is in the etherpad https://etherpad.opendev.org/p/neutron-ci-meetings See You there :) -- Slawek Kaplonski Principal Software Engineer Red Hat

2 1

[nova] Getting away from cdrkit / genisoimage
by Thomas Goirand 04 Jan '22

04 Jan '22

Hi, Please see: https://bugs.debian.org/982241 It looks like cdrkit / genisoimage wont be available in the next Debian 12 (and therefore probably it will also be dropped in Ubuntu). As per the bug report: "I'm told xorriso and libburnia are alternatives and are alive and doing well." Would it be possible to switch to that? Cheers, Thomas Goirand (zigo)

2 1

cpu pinning
by open infra 04 Jan '22

04 Jan '22

3 7

[all][qa][triplo] Help need to maintain OpenStack health dashboard
by Ghanshyam Mann 04 Jan '22

04 Jan '22

Hello Everyone, In the QA meeting[1], we discussed the help needed to maintain the OpenStack health dashboard which is broken currently and the QA team does not have the JS developer and bandwidth to fix it. While discussing it meeting, we found that the TripleO team might be working on a similar dashboard for their CI results. If that is the case, can we collaborate on maintaining the existing dashboard? OpenStack health dashboard: https://opendev.org/openstack/openstack-health Repo: http://status.openstack.org/openstack-health/#/ [1] https://meetings.opendev.org/meetings/qa/2021/qa.2021-11-16-15.00.log.html#… -gmann

5 7

[tempest] Extending tempest for mixed-architecture stacks
by James LaBarre 03 Jan '22

03 Jan '22

Recently I had been running Tempest on my setup testing a mixed-architecture deployment (x86_64 ans ppc64le compute nodes at the same time). It seems that some of the migration and affinity tests will check if there's more than one Compute node before they run. However, it would seem that's as far as they check, without checking if they are in fact compatible or even of the same architecture. (my test cluster is very small, and normally includes two ppc64le Compute nodes, and sometimes one x86_64 Compute node. Currently one ppc64le machine is down for repair). Because the two compute nodes are different architectures, I am getting failures in various migration and affinity tests, maybe more if I tested a larger subset. Now granted my particular setup is a special case, but it does bring to mind some extensions that may be needed for Tempest in the future. I could see it being possible to have x86_64 and ARM mixed together in one stack, maybe even tossing in RISC-v someday. I'm thinking we need to start adding in extra test images, flavors, etc into the Tempest configurations (as in defining multiple options so that each architecture can have test images, etc assigned to it, rather than the current primary and alt image for just one architecture) Additionally, there should be testcases taking into account the architectures involved (such as seeing that an instance on one arch cannot be migrated to the other, as an example). I know this involves a bit of refactoring, I didn't know if it had even been considered yet. -- James LaBarre Software Engineer, OpenStack MultiArch Red Hat <https://www.redhat.com> jlabarre(a)redhat.com <mailto:jlabarre@redhat.com> <https://www.redhat.com>

3 2

[tc][all] Follow up pain point discussion
by Rico Lin 03 Jan '22

03 Jan '22

Dear all The pain point collection etherpad [1] seems to get good attention from teams. We plan to host a one-hour video meeting to keep the discussion going. Please fill in the doodle to select your preferred time if you can join us: https://doodle.com/poll/kur2mfywceerqcvh?utm_source=poll&utm_medium=link The discussion will be hosted in video format. Here are some items (but not limited to) I expect we will discuss and hopefully put some actions/efforts on. - General Pain point: RabbitMQ - General Pain point: OpenStackClient support - General project pain point discussion: How to encourage teams to work/reply on pain points. Meanwhile, we encourage all to check the etherpad and provide your feedback. Also if teams can help to answer questions/concerns on etherpad (like Nova team does) will be greatly appreciated. [1] https://etherpad.opendev.org/p/pain-point-elimination *Rico Lin*

7 11

[octavia] Management Network Issue
by Ammad Syed 03 Jan '22

03 Jan '22

Hi, I am using octavia 9.0. I have created a neutron vlan based management network of octavia. I am creating a loadbalancer with a subnet in the tenant network, its getting created successfully. Then added a listener and created a pool, both created successfully. Now a weird situation is happening. Now when I add a member in the pool, the management network interface get detached automatically from the AMPHORA instance and amphora keeps in PENDING_UPDATE state. I have created a dedicated service-project for octavia and management network and subnet resides there. Any advise how to fix it ? Ammad

2 2

[Diversity] D&I WG Meeting Cancellation and Poll Reminder
by Amy Marrich 02 Jan '22

02 Jan '22

Just a reminder that tomorrow's meeting is canceled and to participate in the Meeting Time and IRC vs Video Poll! https://doodle.com/poll/mnzxkauzwf2isssm?utm_source=poll&utm_medium=link Thanks, Amy (spotz)

1 0

[release] Release countdown for week R-12, Jan 03-07
by Előd Illés 31 Dec '21

31 Dec '21

Development Focus ----------------- Happy new year! The Yoga-2 milestone is next week, on January6th, 2022. Yoga-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/ <https://releases.openstack.org/yoga/schedule.html>yoga <https://releases.openstack.org/yoga/schedule.html>/schedule.html <https://releases.openstack.org/yoga/schedule.html>for details. General Information ------------------- Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library that has not been otherwise released since milestone 1. PTL's and release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well. A +1 would be appreciated, but if we do not hear anything at all by the end of the week, we will assume things are OK to proceed. Remember that non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. Next week is also the deadline to freeze the contents of the final release. All new 'Yoga' deliverables need to have a deliverable file in https://opendev.org/openstack/releases/src/branch/master/deliverables <https://opendev.org/openstack/releases/src/branch/master/deliverables> and need to have done a release by milestone-2. Changes proposing missingdeliverables for inclusion in Yogahave been posted, so if you have one in your project team please update them with an actual release request before the milestone-2 deadline if you plan on including that deliverable in Yoga, or -1 if you need one more cycle to be ready. Upcoming Deadlines & Dates -------------------------- Yoga-2 Milestone:January6th, 2022 Előd Illés irc: elodilles

1 0

[cinder] proposing Simon Dodsley for cinder-specs-core
by Brian Rosmaita 31 Dec '21

31 Dec '21

As everyone is painfully aware, we have review bandwidth issues in the Cinder project. I propose to address this issue with respect to cinder specs, at least, by adding a contributor who is not currently a cinder-core as a member of the cinder-specs-core team. (Right now, the only members of cinder-specs-core are the cinder-core team.) Simon Dodsley (simondodsley on IRC) has been a cinder contributor for a long time, and has been especially active in PTGs and midcycle meetings over the past few cycles. He's done quality reviews, especially of specs, this cycle. As a vendor representative, he brings a useful perspective to reviews that affect drivers, as well as general deployment and usability issues. Additionally, given that the current core team has reviewing responsibilities spread over multiple repositories, having a person focused primarily on specs should help us to get more timely feedback for specs proposers. Finally, don't forget that it is thanks to Simon that the Cinder mascot finally has a name ("Argo"), which in turn has given the Cinder team the really cool name "The Argonauts". In the absence of objections, I'll add Simon to the cinder-specs-core team shortly after 1500 UTC on Friday 31 December. Please communicate any concerns to me before that time. cheers, brian

4 4

PTR records in Designate
by Albert Braden 30 Dec '21

30 Dec '21

We have hacked Designate to add PTR records and it is a mess. Every upgrade turns into a bug hunt. I'd like to advocate for going back to vanilla kolla-ansible but then we wouldn't have PTR records. How are other Designate users dealing with the PTR issue?

2 2

[neutron] Do I need to replace NetworkManager with network.service in centos8?
by 韩光宇 29 Dec '21

29 Dec '21

Dear all, I am deploing OpenStack Victoria. I want to ask a question. Do I need to replace NetworkManager with network-scripts in centos8? I saw that "OpenStack Networking does not work on systems that have the Network Manager service enabled" in past redhat documentation and some other places. But I don't see this in latest documentation of OpenStack community（ https://docs.openstack.org/install-guide/environment-packages-rdo.html）. And If NetworkManager is confit will OpenStack network, Do anyone know where I can see the reason of confit. I would appreciate any kind of guidance. Thanks, Han Guangyu. Past redhat documentation: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11…

2 1

[cinder] Bug deputy report for week of 12-29-2021
by Sofia Enriquez 29 Dec '21

29 Dec '21

No meeting today. This is a bug report from 12-22-2021 to 12-29-2021. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1955670 "Unable to delete a group volume after transfer". Unassigned. Cheers, -- 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

[TripleO] Unable to deploy Overcloud Machines
by Anirudh Gupta 28 Dec '21

28 Dec '21

Hi Team, I am trying to deploy TripleO Train with 3 controller and 1 Compute. For overcloud images, I have a registry server at undercloud only. I executed the following command to deploy overcloud openstack overcloud deploy --templates \ -r /home/stack/templates/roles_data.yaml \ -e /home/stack/templates/node-info.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/podman.yaml \ -e /home/stack/containers-prepare-parameter.yaml The command ran for around 1.5 hrs and initially stack got successfully created and after that for 45 mins, ansible tasks were getting executed. It then gave following error in overcloud-controller-0 2021-12-27 11:12:27,507 p=181 u=mistral n=ansible | 2021-12-27 11:12:27.506838 | 525400b1-b522-2a06-ea9d-00000000356f | OK | Debug output for task: Start containers for step 2 | overcloud-novacompute-0 | result={ "changed": false, "failed_when_result": false, "start_containers_outputs.stdout_lines | default([]) | union(start_containers_outputs.stderr_lines | default([]))": [ "f206c31a781641313aa4a0499c62475efc335de6faea785cd4e855dc32ebb571", "", "Info: Loading facts", "Notice: Compiled catalog for overcloud-novacompute-0.localdomain in environment production in 0.05 seconds", "Info: Applying configuration version '1640604309'", "Notice: /Stage[main]/Tripleo::Profile::Base::Neutron::Ovn_metadata_agent_wrappers/Tripleo::Profile::Base::Neutron::Wrappers::Haproxy[ovn_metadata_haproxy_process_wrapper]/File[/var/lib/neutron/ovn_metadata_haproxy_wrapper]/ensure: defined content as '{md5}5bb050ca70c01981975efad9d8f81f2d'", "Info: Tripleo::Profile::Base::Neutron::Wrappers::Haproxy[ovn_metadata_haproxy_process_wrapper]: Unscheduling all events on Tripleo::Profile::Base::Neutron::Wrappers::Haproxy[ovn_metadata_haproxy_process_wrapper]", "Info: Creating state file /var/lib/puppet/state/state.yaml", "Notice: Applied catalog in 0.01 seconds", "Changes:", " Total: 1", "Events:", " Success: 1", "Resources:", " Changed: 1", " Out of sync: 1", " Skipped: 7", " Total: 8", "Time:", " File: 0.00", " Transaction evaluation: 0.01", " Catalog application: 0.01", " Config retrieval: 0.09", " Last run: 1640604309", " Total: 0.01", "Version:", " Config: 1640604309", " Puppet: 5.5.10", * "Error executing ['podman', 'container', 'exists', 'nova_compute_init_log']: returned 1", "Did not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=nova_compute_init_log', '--filter', 'label=config_id=tripleo_step2', '--format', '{{.Names}}']\" - retrying without config_id", "Did not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=nova_compute_init_log', '--format', '{{.Names}}']\"", "Error executing ['podman', 'container', 'exists', 'create_haproxy_wrapper']: returned 1", "Did not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=create_haproxy_wrapper', '--filter', 'label=config_id=tripleo_step2', '--format', '{{.Names}}']\" - retrying without config_id", "Did not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=create_haproxy_wrapper', '--format', '{{.Names}}']\""* ] } I am also attaching ansible.log file for more information. Note: On Centos 8, there is no docker, so I didn't pass docker-ha.yml Can someone please help in resolving my issue Regards Anirudh Gupta

2 9

[neutron] bug deputy report of week 2021-12-20
by Bence Romsics 27 Dec '21

27 Dec '21

Hi Team, We only had a few new bugs last week, here they are: High: * https://bugs.launchpad.net/neutron/+bug/1955478 Scenario test failed due to metadata service not available slaweq investigated this gate failure, but did not find enough information in the logs. * https://bugs.launchpad.net/neutron/+bug/1955546 [stable only] Logging service plugin expects wrong arguments in the callback function fixes mostly merged: https://review.opendev.org/q/I0003bd566dc769436ad1342351ad058394bd52da * https://bugs.launchpad.net/neutron/+bug/1955578 OVN transaction could not be completed due to a race condition proposed fix: https://review.opendev.org/c/openstack/neutron/+/821401 * https://bugs.launchpad.net/neutron/+bug/1955775 Error when l3-agent get filter id for ip proposed fix: https://review.opendev.org/c/openstack/neutron/+/822987 Medium: * https://bugs.launchpad.net/neutron/+bug/1955639 Performance of mariadb's neutron.agents table unassigned Incomplete: * https://bugs.launchpad.net/neutron/+bug/1955503 [ovn] OVN agents showing as dead until neutron services restarted If ovn folks have an intuition what may go wrong with agent caching, then please look at it, but we don't have reproduction steps, so marked as Incomplete. Other: * https://bugs.launchpad.net/neutron/+bug/1955765 Devstack - Can no longer enable qos with neutron-qos Now that we un-deprecated the legacy plugin what do we want to do with the new plugin? Possible discussion point for the next meeting. Cheers, Bence

1 0

[cloudkitty] No weekly meeting today
by Rafael Weingärtner 27 Dec '21

27 Dec '21

Hello guys, As agreed in the previous meeting, we will skip IRC meeting this week and be on 10th Jan next year. I hope you all had a merry Christmans, and happy holidays! -- Rafael Weingärtner

1 0

[kolla] No IRC meeting this week
by Michał Nasiadka 26 Dec '21

26 Dec '21

Hello Koalas, As agreed in the previous meeting, we will skip IRC meeting this week (planned for 29th Dec) and meet on 5th Jan. Happy new year! Michal -- Michał Nasiadka mnasiadka(a)gmail.com

1 0

[tacker] No weekly meeting until 2022
by Yasufumi Ogawa 26 Dec '21

26 Dec '21

Hi, As agreed in the previous meeting, we will skip IRC meeting this week and be on 11th Jan next year. Happy holidays! Cheers, yasufumi

1 0

No network access for Openstack instances
by A Monster 26 Dec '21

26 Dec '21

I have used kolla ansible to deploy openstack on two machine servers, but after setting up the images and the virtual networks, the vm instances don't get the ip address that neutron provides for them, so I had to manually set the addresses inside the vm's, but even with that I can't seem to connect vm's to neither internet nor any other network. I'm on centos 7 and trying to deploy openstack train using kolla ansible 9.3.1 Ansible 2.9.25 And neutron open vSwitch.

3 2

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

24 Dec '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had a quick meeting yesterday. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2021/tc.2021-12-23-15.00.log.html * Next week's meeting on 30th Dec is canceled. We will continue our weekly meeting from Jan 6th, Thursday 15:00 UTC, feel free the topic on the agenda[1] by 5th Jan. 2. What we completed this week: ========================= * Nothing much in this week. 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[2]. Open Reviews ----------------- * 4 open reviews for ongoing activities[3]. SIG i18n status check -------------------------- Ian (SIG chair) responded on ML thread and will look into the things after he is back from leave next month[4]. OpenStack Pain points discussion ---------------------------------------- No updates in this week. Stay tuned on the ML thread[5] and Rico will inform you about the next meeting details. TC position on release cadence ------------------------------------- No updates on this. Discussion is in-progress in ML thread[6]. No other updates from TC on this and we will set up a separate call to continue the discussion sometime in Jan (after the Christmas holidays). Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[7]. Skyline as official projects ------------------------------ We accepted the Skyline as an official project last week and next work on project renaming etc are also started. Adjutant need maintainers and PTLs ------------------------------------------- We are still waiting to hear from Braden, Albert on permission to work on this project[8]. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [9] 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[10]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [11] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. Marry Chirsmas and Happy new year to everyone and stay safe! [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://etherpad.opendev.org/p/tc-yoga-tracker [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026441… [5] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245… [6] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684… [7] https://etherpad.opendev.org/p/zuul-config-error-openstack [8] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [9] https://review.opendev.org/c/openstack/governance/+/798540 [10] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [11] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[gate][tempest][plugins][stable] Stable/train tempest plugins jobs are broken
by Ghanshyam Mann 23 Dec '21

23 Dec '21

Hello Everyone, gthiemonge reported the issue for tempest plugin stable/train jobs are broken. I have explained the issue in https://bugs.launchpad.net/tempest/+bug/1955418 and fix is up (it is under testing). This is applicable for any tempest plugin job on stable/train. Please hold the recheck until the below fix is merged: https://review.opendev.org/c/openstack/tempest/+/822339 -gmann

1 1

[tc][sig][i18n] What's the status for Xena translation?
by Akihiro Motoki 23 Dec '21

23 Dec '21

Hi, # I include TC and SIG tags to get broader attractions to this topic. # Also Cc'ed to Ian (i18n SIG char) and Andreas. I would like to ask the status of Xena translation in translate.openstack.org (Zanata). In past releases, stable-XXX branches were created on Zanata, but a branch for Xena translation has not been created yet. Ajaeger usually prepared these branches as a volunteer (I am really appreciated) but AFAIK he no longer works on OpenStack actively. Who takes care of the translatio preparation around the release now? I hope the i18n SIG is not dead. Thanks, Akihiro Motoki (amotoki)

3 2

Re: [kolla-ansible][cinder] MPIO - how to set "storage_interface" when using two NICs for storage connection
by Adam Tomas 23 Dec '21

23 Dec '21

Hi again, I found some informations about MPIO here (https://docs.oracle.com/cd/E78305_01/E78304/html/setup-cinder.html) : "By default, the Cinder block storage service uses the iSCSI protocol to connect instances to volumes. The iscsid container runs on compute nodes and handles the iSCSI session using an iSCSI initiator name that is generated when you deploy Nova compute services. The Nova compute service supports iSCSI multipath for failover purposes and increased performance. Multipath is enabled by default (configured with the enable_multipathd property). When multipath is enabled, the iSCSI initiator (the Compute node) is able to obtain a list of addresses from the storage node that the initiator can use as multiple paths to the iSCSI LUN." But still - how should I set storage_interface, if I have two NICs for storage connection (let’s say eth4 and eth5)? storage_interface=eth4,eth5 ? Best regards Adam Tomas > Hi, > I’d like to use MPIO in connection to storage array, so I have two physical NIC’s in different VLANS on each node and also 4 NIC’s in the storage array (2 in each storage VLAN) so it should result in 4 MPIO paths from every node (2 paths in each VLAN). But how to set it in kolla-ansible? Can I point to more than one interface using storage_interface variable? Or maybe I should configure it in different way?

2 4

Networks for different availability zones in Horizon
by hai wu 23 Dec '21

23 Dec '21

In Horizon "Launch Instance" workflow, in its 4th step of selecting networks for the new instance, it would always show all the available networks from all availability zones, regardless of which "Availability Zone" got picked in 1st step of "Details". I tried to update some DB field for availability zone hint for the relevant network, and that did not help. Any way to ensure in Horizon "Launch Instance" GUI workflow, after a user picking one availability zone in step 1, it would only show the related networks in that availability zone as available networks in step 4?

6 10

[all][tc] Technical Committee next weekly meeting on Dec 23rd at 1500 UTC
by Ghanshyam Mann 22 Dec '21

22 Dec '21

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

1 1

[adjutant][requirements] Adjutant Django version
by Dmitriy Rabotyagov 22 Dec '21

22 Dec '21

2 1

[requirements][OpenStackClients][rally][tempest][watcher][nova][glance] Use prettytable in requirements
by Dmitriy Rabotyagov 22 Dec '21

22 Dec '21

2 2

[cinder] Bug deputy report for week of 12-22-2021
by Sofia Enriquez 22 Dec '21

22 Dec '21

No meeting today. This is a bug report from 12-15-2021 to 12-22-2021. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/os-brick/+bug/1955020 "multipath -l <device_name> is failing". Assigned to Rajat Dhasmana. Low - https://bugs.launchpad.net/cinder/+bug/1955057 "NetApp driver fails to compare ONTAP version". Assigned to Nahim Alves de Souza. Wishlist - https://bugs.launchpad.net/cinder/+bug/1955360 "Cannot clone a volume from the image within the same ceph cluster". Assigned to Eric Xie. Cheers -- 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

[tripleo][ussuri] Log4j add protection to haproxy {even it is not impacted
by Ruslanas Gžibovskis LPIC 22 Dec '21

22 Dec '21

3 2

[kolla-ansible][cinder]
by Adam Tomas 22 Dec '21

22 Dec '21

Hi, I’d like to use MPIO in connection to storage array, so I have two physical NIC’s in different VLANS on each node and also 4 NIC’s in the storage array (2 in each storage VLAN) so it should result in 4 MPIO paths from every node (2 paths in each VLAN). But how to set it in kolla-ansible? Can I point to more than one interface using storage_interface variable? Or maybe I should configure it in different way? Best regards Adam Tomas

1 0

[neutron] CI meeting 28.12.2021 cancelled
by Slawek Kaplonski 21 Dec '21

21 Dec '21

Hi, Next week Neutron CI meeting is cancelled. Happy holidays for all of You and see You on the meetings in 2022! We will start with CI meeting 4.01.2022 :) -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[cinder] weekly meetings for the remainder of december
by Brian Rosmaita 21 Dec '21

21 Dec '21

As agreed at last week's cinder meeting, our meetings for the remainder of 2021 will be: * Wednesday, December 22: no meeting * Wednesday, December 29: no meeting The next weekly cinder meeting will be Wednesday, January 5 at the usual time (1400 UTC) in the usual place (#openstack-meeting-alt on OFTC). The meeting agenda is here: https://etherpad.opendev.org/p/cinder-yoga-meetings cheers, brian

1 0