- openstack-discuss - lists.openstack.org

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

[Triple0] Unable to pxeBoot overcloud Nodes via ipv6
by Lokendra Rathour 20 Dec '21

20 Dec '21

Hi Team, we have installed Undercloud with Train release on Centos8 using ipv6 as loca_ip in undercloud.conf file. Undercloud seems to be installed successfully and we are able to see IPv6 endpoints as well. Also, the OpenStack overcloud images are uploaded and well visible on http://<ipv6>:8088 tftp link. Problem Statement: During introspection start, we see that ipv6 is allocated to the node, further no action is being performed. Please refer the screen attached. [image: image.png] As we can see ipv6 bbbb:bbbb:bbbb::9 is allocated to the desired machine. Furthermore, we see that the link is shown as down for the same mac, which also becomes up as can be seen but the configuring on that NIC eventually fails for some reason. Any idea/inputs on this please? -- ~ Lokendra

1 0

[TripleO] Tomorrow's (Dec 21) meeting cancelled, next meeting Jan 3
by James Slagle 20 Dec '21

20 Dec '21

As we have no items on the agenda[1] for tomorrow's meeting, let's cancel it and hold our next meeting on Tuesday, January 3rd. Thanks! [1] https://etherpad.opendev.org/p/tripleo-meeting-items -- -- James Slagle --

1 0

[kolla] The impact of CentOS Linux 8 EOL and OpenDev's drop of the respective image
by Radosław Piliszek 20 Dec '21

20 Dec '21

Dears, As you may recall, the CentOS Linux 8 (as opposed to CentOS Stream 8) is reaching its EOL (End Of Life) Dec 31st, 2021 (that is, in eleven days). [1] Due to that, the OpenDev team (that hosts kolla's repos and the CI/CD that we rely on) has decided to drop the EOLed images January 14th, 2022. [2] This impacts both Kolla and Kolla Ansible in subtle ways - both operator-wise and contributor-wise. The EM (Extended Maintenance) branches, Train and Ussuri, in both projects, rely solely on CentOS Linux 8, the Stream variant is *not* supported there. This means that in 2022 we are forced to cease to test these branches against CentOS Linux 8 (we will still test the two other distros - Ubuntu and Debian). Operators are advised to upgrade to Victoria or (preferably) later (psst, go Xena). Furthermore, CentOS Linux 8 is currently supported in Victoria but this support will also end naturally with 2022 on the horizon. Operators are advised to migrate to CentOS Stream 8 and images based on it. [1] https://www.centos.org/centos-linux-eol/ [2] http://lists.opendev.org/pipermail/service-announce/2021-December/000029.ht… Kind regards, -yoctozepto

1 0

[kolla] Dropping support for vmtp in Yoga
by Radosław Piliszek 20 Dec '21

20 Dec '21

Dear Users of Kolla! The Kolla project, so far, provided vmtp [1] image and ansible role. However, the status of those has been unknown (the ansible role looks pretty stale, still referencing ubuntu 16.04!) and now the vmtp image is failing to build so we are forced to disable it. [2] The project itself [1] looks rather unmaintained and it's outside of the openstack namespace so our plan is to drop support for it entirely in this cycle (Yoga). Please reply to this mail if you are using vmtp with Kolla in some recent release and are willing to contribute to let us keep supporting it. [1] https://opendev.org/x/vmtp [2] https://review.opendev.org/c/openstack/kolla/+/820043 Kind regards, -yoctozepto

1 1

[Glance] No weekly meeting until New Year
by Abhishek Kekane 20 Dec '21

20 Dec '21

Hello All, Christmas and New year holidays are approaching and most of the glance team is on vacation so we are canceling our next two weekly meetings. Next meeting will be on 06th January, 2022. Merry Christmas and Happy New year in advance!!! Cheers, Abhishek Kekane

1 0

[nova][placement] PTL on PTO until Jan 3rd
by Sylvain Bauza 20 Dec '21

20 Dec '21

Hi folks, I'll be off the keyboard from tonight and only be back on Monday January the 3rd. Have good holidays if you have them and good rest. For others, thanks for continuing to help Nova and see you again in 2022 ! -Sylvain

1 0

[qa] Cancelling office hour on Dec 28th due to holidays
by Martin Kopec 20 Dec '21

20 Dec '21

Hi all, we'll have the last office hour in 2021 tomorrow (Dec. 21st). Our first office hour in 2022 will be held on Dec. 4th. Merry Christmas and Happy New Year! Regards, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA

2 2

[nova] random unauthorized errors
by Ammad Syed 20 Dec '21

20 Dec '21

Hi, I am using nova 23.0.0 and I am randomly facing unauthorized error sometime when nova uses neutron or cinder phython3 client during listing of server and creation of server. When I list server again, it works fine. I have found below logs in nova-api. 2021-12-20 09:10:24.920 2689471 DEBUG nova.api.openstack.wsgi [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Calling method '<bound method ServersController.detail of <nova.api.openstack.compute.servers.ServersController object at 0x7f840b6c5070>>' _process_stack /usr/lib/python3/dist-packages/nova/api/openstack/wsgi.py:513 2021-12-20 09:10:24.925 2689471 DEBUG nova.compute.api [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Searching by: {'project_id': '890eb2b7d1b8488aa88de7c34d08817a', 'deleted': False} get_all /usr/lib/python3/dist-packages/nova/compute/api.py:2857 2021-12-20 09:10:24.930 2689471 DEBUG oslo_concurrency.lockutils [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Lock "00000000-0000-0000-0000-000000000000" acquired by "nova.context.set_target_cell.<locals>.get_or_set_cached_cell_and_set_connections" :: waited 0.000s inner /usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py:355 2021-12-20 09:10:24.931 2689471 DEBUG oslo_concurrency.lockutils [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default def2021-12-20 09:10:24.548 2689471 INFO nova.osapi_compute.wsgi.server [req-c5da1a3c-3c99-46c2-84e9-b504ccc5d156 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] 172.16.30.56 "GET /v2.1/ HTTP/1.1" status: 200 len: 800 time: 0.0048089 2021-12-20 09:10:24.697 2689471 DEBUG nova.osapi_compute.wsgi.server [req-572eca81-8d3b-4524-89e5-e4e1124a7ac5 - - - - -] (2689471) accepted ('172.16.30.56', 52016) server /usr/lib/pytho n3/dist-packages/eventlet/wsgi.py:992 2021-12-20 09:10:24.920 2689471 DEBUG nova.api.openstack.wsgi [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default defaul t] Calling method '<bound method ServersController.detail of <nova.api.openstack.compute.servers.ServersController object at 0x7f840b6c5070>>' _process_stack /usr/lib/python3/dist-packag es/nova/api/openstack/wsgi.py:513 2021-12-20 09:10:24.925 2689471 DEBUG nova.compute.api [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Sear ching by: {'project_id': '890eb2b7d1b8488aa88de7c34d08817a', 'deleted': False} get_all /usr/lib/python3/dist-packages/nova/compute/api.py:2857 2021-12-20 09:10:24.930 2689471 DEBUG oslo_concurrency.lockutils [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default def ault] Lock "00000000-0000-0000-0000-000000000000" acquired by "nova.context.set_target_cell.<locals>.get_or_set_cached_cell_and_set_connections" :: waited 0.000s inner /usr/lib/python3/d ist-packages/oslo_concurrency/lockutils.py:355 2021-12-20 09:10:24.931 2689471 DEBUG oslo_concurrency.lockutils [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default def ault] Lock "00000000-0000-0000-0000-000000000000" released by "nova.context.set_target_cell.<locals>.get_or_set_cached_cell_and_set_connections" :: held 0.001s inner /usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py:367 2021-12-20 09:10:24.933 2689471 DEBUG oslo_concurrency.lockutils [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Lock "fc805771-7891-4095-8162-491cf824b02f" acquired by "nova.context.set_target_cell.<locals>.get_or_set_cached_cell_and_set_connections" :: waited 0.000s inner /usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py:355 2021-12-20 09:10:24.934 2689471 DEBUG oslo_concurrency.lockutils [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Lock "fc805771-7891-4095-8162-491cf824b02f" released by "nova.context.set_target_cell.<locals>.get_or_set_cached_cell_and_set_connections" :: held 0.001s inner /usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py:367 2021-12-20 09:10:25.019 2689471 DEBUG nova.compute.multi_cell_list [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Listed batch of 13 results from cell out of 21 limit. Returned 13 total so far. do_query /usr/lib/python3/dist-packages/nova/compute/multi_cell_list.py:371 2021-12-20 09:10:25.093 2689471 DEBUG oslo_concurrency.lockutils [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Lock "fc805771-7891-4095-8162-491cf824b02f" acquired by "nova.context.set_target_cell.<locals>.get_or_set_cached_cell_and_set_connections" :: waited 0.000s inner /usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py:355 2021-12-20 09:10:25.094 2689471 DEBUG oslo_concurrency.lockutils [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Lock "fc805771-7891-4095-8162-491cf824b02f" released by "nova.context.set_target_cell.<locals>.get_or_set_cached_cell_and_set_connections" :: held 0.000s inner /usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py:367 *2021-12-20 09:10:25.393 2689471 DEBUG neutronclient.v2_0.client [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Error message: {"error": {"code": 401, "title": "Unauthorized", "message": "The request you have made requires authentication."}} _handle_fault_response /usr/lib/python3/dist-packages/neutronclient/v2_0/client.py:258* 2021-12-20 09:10:25.394 2689471 ERROR nova.network.neutron [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Neutron client was not able to generate a valid admin token, please verify Neutron admin credential located in nova.conf: neutronclient.common.exceptions.Unauthorized: 401-{'error': {'code': 401, 'title': 'Unauthorized', 'message': 'The request you have made requires authentication.'}} 2021-12-20 09:10:25.395 2689471 INFO nova.api.openstack.wsgi [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] HTTP exception thrown: Networking client is experiencing an unauthorized exception. 2021-12-20 09:10:25.396 2689471 DEBUG nova.api.openstack.wsgi [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Returning 400 to user: Networking client is experiencing an unauthorized exception. __call__ /usr/lib/python3/dist-packages/nova/api/openstack/wsgi.py:927 2021-12-20 09:10:25.398 2689471 INFO nova.osapi_compute.wsgi.server [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] 172.16.30.56 "GET /v2.1/890eb2b7d1b8488aa88de7c34d08817a/servers/detail?limit=21&project_id=890eb2b7d1b8488aa88de7c34d08817a&sort_dir=desc&sort_dir=desc&sort_dir=desc&sort_key=created_at&sort_key=display_name&sort_key=uuid HTTP/1.1" status: 400 len: 529 time: 0.7002470 Is there anything that I need to change ? -- Regards, Syed Ammad Ali

1 0

[octavia] cancelling weekly meetings until 2022
by Gregory Thiemonge 20 Dec '21

20 Dec '21

Hi, As discussed during our last weekly meeting, the next 2 meetings (Dec 22nd and 29th) are cancelled. Our next meeting will be on January 5th, Greg

1 0

[neutron] PTL on PTO
by Lajos Katona 19 Dec '21

19 Dec '21

Hi, I will be on PTO, back in Tuesday, 04. 01. 2022. Don't hesitate to write, I will be reachable. Regards Lajos Katona (lajoskatona)

3 3

Inquiry on FWaaS Deprecation
by 권다진 19 Dec '21

19 Dec '21

1 0

[neutron] bug deputy report December 13th to 19th
by Miguel Lavalle 19 Dec '21

19 Dec '21

Hi, Here's this week's bugs deputy report: High ==== https://bugs.launchpad.net/neutron/+bug/1954666 "LoggingPlugin._clean_logs_by_target_id" failing in stable releases. Assigned to Rodolfo Alonso. Fixes: https://review.opendev.org/c/openstack/neutron/+/821563, https://review.opendev.org/c/openstack/neutron/+/821564, https://review.opendev.org/c/openstack/neutron/+/821565 Medium ====== https://bugs.launchpad.net/neutron/+bug/1954763 Creating ports in bulks can be very slow due to many IPAM module conflicts. Assigned to Slawek Kaplonski. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/821727 https://bugs.launchpad.net/neutron/+bug/1954785 Session semantic violated when sending FloatingIP disassociation update during port deletion. Assigned to Szymon Wróblewski https://bugs.launchpad.net/neutron/+bug/1954942 [fullstack] Failure of "test_reschedule_network_on_new_agent". Needs owner https://bugs.launchpad.net/neutron/+bug/1955008 [functional] Failure of "test_floatingip_mac_bindings". Needs owner https://bugs.launchpad.net/neutron/+bug/1955010 [stable] py27 is not supported in "python-lazy-object-proxy" release 1.7.0. Assigned to Rodolfo Alonso Low ==== https://bugs.launchpad.net/neutron/+bug/1954903 [OVN] Add floating IP pools L3 extension to OVN L3 service. Assigned to Rodolfo Alonso. Proposed fix https://review.opendev.org/c/openstack/neutron/+/821818 https://bugs.launchpad.net/neutron/+bug/1955121 Update subnet with same gateway_ip as is already used should be allowed. Assigned to Slawek Kaplonski. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/822098 Waiting for response from submitter =========================== https://bugs.launchpad.net/neutron/+bug/1954771 [OVN]MAC of lrp has not been updated in MAC_Binding when it re-associated. https://bugs.launchpad.net/neutron/+bug/1954777 setting same static route with subnet already exists as direct connected network Cheers Miguel

1 0

[horizon] Networks for different availability zones in Horizon
by hai wu 18 Dec '21

18 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?

1 0

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

17 Dec '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * 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-16-15.00.log.html * Next week's meeting is on IRC on 23rd Dec (it is scheduled as of now but i will confirm it on Monday), Thursday 15:00 UTC, feel free the topic on the agenda[1] by 22nd Dec. 2. What we completed this week: ========================= * Skyline is accepted as an official project [2] * Updated Yoga testing runtime and job templates[3] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. Open Reviews ----------------- * 3 open reviews for ongoing activities[5]. SIG i18n status check -------------------------- As you might have seen in the email from Amotoki on missing Xena translation[6] or ID translation bug[7], we checked this SIG status in the TC meeting. We did not get any concrete answer about the status of this SIG, but I have an action item to reach out to the current chair of this SIG (Ian). If anyone would like to help or know who can help especially those who need the translation, please reply to this thread or thread started by Amotoki[6]. OpenStack Pain points discussion ---------------------------------------- No updates in this week. Stay tuned on the ML thread[8] and Rico will inform you about the next meeting details. TC position on release cadence ------------------------------------- Discussion is in-progress in ML thread[9]. 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 -------------------------- There is some progress by projects but still, we need to fix a lot of config errors. If your project is listed in zuul config error, please start planning to fix those[10] Community-wide goal updates ------------------------------------ You might have seen my email[11] about goal status and planning the work, below is the current status: * Selected (active) goals[12]: ** Migrate from oslo.rootwrap to oslo.privsep ** Consistent and Secure Default RBAC * Goal proposal under review: ** FIPS compatibility and compliance [13]. Adjutant need maintainers and PTLs ------------------------------------------- We are still waiting to hear from Braden, Albert on permission to work on this project[14]. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [15] 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[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [17] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/814037 [3] https://review.opendev.org/c/openstack/governance/+/820195 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026244… [7] https://review.opendev.org/c/openstack/contributor-guide/+/821371 [8] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245… [9] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684… [10] https://etherpad.opendev.org/p/zuul-config-error-openstack [11] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026218… [12] https://governance.openstack.org/tc/goals/selected/index.html [13] https://review.opendev.org/c/openstack/governance/+/816587 [14] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [15] https://review.opendev.org/c/openstack/governance/+/798540 [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

No network access for openstack instances
by A Monster 17 Dec '21

17 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.

2 2

[neutron] Routing fake "floating IPs" of VMs running inside VMs of an OpenStack
by Thomas Goirand 17 Dec '21

17 Dec '21

Hi, I've been designing a CI for OCI [1] to make it more robust and easier to contribute. After a week and a half, I've been able to make OCI deploy itself in an OpenStack itself. OCI itself pops with a public IP I can reach from the outside, and it setups OpenStack inside OpenStack VMs on a flat, private subnet (currently 192.168.100.0/24). This works pretty well, I have a fully working setup, and the deployment is completely automated. This even works without admin credentials, so all one needs, is a non-privileged account in any OpenStack. However, at this point, I'd like to setup the network for VMs inside the VMs. And that's where it becomes tricky. The VM that runs tempest will need to reach the floating IPs of the VMs inside the VMs that are running nova-compute, in order to do ssh tests. How can I do that? Is this even possible? Cheers, Thomas Goirand (zigo) [1] https://salsa.debian.org/openstack-team/debian/openstack-cluster-installer

2 1

[neutron][ovn] VLAN Ranges
by Ammad Syed 17 Dec '21

17 Dec '21

Hi, I am using neutron xena release with OVN. I have currently defined the vlan range "network_vlan_ranges = vlannet1:3500:3600" in ml2_conf.ini. I have set bridge mapping via ovs with the below command. ovs-vsctl set open . external-ids:ovn-bridge-mappings=vlannet1:br-vlan Now I have to add a new vlan range. Can anyone confirm the syntax of ml2_conf.ini and bridge mapping. network_vlan_ranges = vlannet1:3500:3600,vlannet2:300:400 ovs-vsctl set open . external-ids:ovn-bridge-mappings=vlannet1:br-vlan,vlannet2:br-vlan Need to confirm the correct way to add new vlan range if the server is currently live ? Can we use the same bridge with two different mapping i.e vlannet1 and vlannet2 ? Ammad

2 3

[blazar] Next IRC meeting cancelled
by Pierre Riteau 17 Dec '21

17 Dec '21

Hello, As decided during yesterday's meeting, we are cancelling the Blazar IRC meeting scheduled for December 30. The next meeting will be on January 13. Merry Christmas and Happy New Year! Best wishes, Pierre Riteau (priteau)

1 0

[horizon] Cancelling next two weekly meetings
by vishal manchanda 17 Dec '21

17 Dec '21

Hello Team, As agreed, during the last weekly meeting, we are canceling our weekly meeting on 22nd and 29th December. The next weekly meeting will be on 5th December. Happy holidays and happy new year in advance! Thanks & Regards, Vishal Manchanda

1 0

[charms] review abandonment policy
by James Page 17 Dec '21

17 Dec '21

Hi Charms Contributors As part of this cycles work to put in more proactive general maintenance of the Gerrit review queue for the OpenStack Charms projects we have introduced an abandonment policy for reviews: https://docs.openstack.org/charm-guide/latest/community/rotas.html#abandonm… Pruning the set of open reviews on a regular basis against this policy will help reviewers focus on active reviews. We'll start doing this in January - you can follow the blocked/failing links in the charm-guide policy section to see which reviews will be abandoned at any given point in time. Cheers James

1 0