February 2022 - openstack-discuss

Fwd: DPDK+OVS with OpenStack
by Mark Wittling 23 Apr '25

23 Apr '25

Looking for someone who knows OpenStack with OpenVSwitch, and in addition to that, DPDK with OpenStack and OVS.I am using OpenStack Queens, with OpenVSwitch. The architecture I am using is documented here: https://docs.openstack.org/neutron/queens/admin/deploy-ovs-provider.htmlThe OVS I am using on the Compute Node, is compiled with DPDK, and I have enabled the datapath to netdev (DPDK) on br-prv (provider network bridge), and br-tun (tunneling bridge). But these two bridges, br-tun and br-prv, are patched into another OpenStack bridge, called br-int. I wasn’t actually sure about whether to tinker with this bridge, and wondered what datapath it was using.Then, I realized there is a parameter in the openvswitch_agent.ini file, which I will list here: # OVS datapath to use. 'system' is the default value and corresponds to the # kernel datapath. To enable the userspace datapath set this value to 'netdev'. # (string value) # Possible values: # system - <No description provided> # netdev - <No description provided> #datapath_type = system datapath_type = netdev So in tinkering with this, what I realized, is that when you set this datapath_type to system or netdev, it will adjust the br-int bridge to that datapath type.So here is my question. How can I launch a non-DPDK VM, if all of the bridges are using the netdev datapath type?Here is another question. What if one of the flavors don’t have the largepages property set on them? I assumed OpenStack would revert to a system datapath and not use DPDK for those VM interfaces. Well, I found out in testing, that is not the case. If you set all your bridges up for netdev, and you don’t set the property on the Flavor of the VM (largepages), the VM will launch, but it simply won’t work.Is there no way, on a specific Compute Host, to support both DPDK (netdev datapaths) and non-DPDK (system datapaths)?Either on a VM interface level (VM has one interface that is netdev DPDK and another that is system datapath non-DPDK)?Or on a VM by VM basis (VM 1 has 1 or more netdev datapath interfaces and VM 2 has 1 or more system datapath interfaces)?Am I right here? Once you set up a Compute Host for DPDK, it’s DPDK or nothing on that Compute Host? (edited)

3 2

How to config DPDK compute in OVN
by dangerzone ar 22 Apr '25

22 Apr '25

Hi....as far I understand ovs does support dpdk compute to be deployed. I'm referring to the guideline ' *https://docs.openstack.org/networking-ovn/queens/admin/dpdk.html <https://docs.openstack.org/networking-ovn/queens/admin/dpdk.html>* ' ... It's too brief.. May I know how to config dpdk compute in OVN networking openstack? Hope someone could help what is the config to be done.... Currently compute is run without dpdk over openstack train ovn based. Please need some info on how I can proceed. Thank you

2 1

Live migration fails
by Szabo, Istvan (Agoda) 06 Aug '24

06 Aug '24

Hi, I have couple of compute nodes where the live migration fails with existing vms. When I quickly spawn a vm and try live migration it works so I assume shouldn't be a big problem with the compute node. However I have many existing vms where it fails with a servername not found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 ERROR nova.conductor.tasks.migrate [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Unable to find record for source node servername on servername: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Failed to compute_task_migrate_server: Compute host servername could not be found.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Setting instance to ACTIVE state.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.672 227612 ERROR oslo_messaging.rpc.server [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Exception during message handling: ComputeHostNotFound: Compute host am-osfecn-4025 Tried with this command: nova live-migration --block-migrate id. Any idea? Thank you. ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.

5 16

[all] Dynamic Zuul results table in Gerrit 3
by Radosław Piliszek 04 Aug '22

04 Aug '22

Hello Fellow OpenStack and OpenDev Folks! TL;DR click on [3] and enjoy. I am starting this thread to not hijack the discussion happening on [1]. First of all, I would like to thank gibi (Balazs Gibizer) for hacking a way to get the place to render the table in the first place (pun intended). I have been a long-time-now user of [2]. I have improved and customised it for myself but never really got to share back the changes I made. The new Gerrit obviously broke the whole script so it was of no use to share at that particular state. However, inspired by gibi's work, I decided to finally sit down and fix it to work with Gerrit 3 and here it comes: [3]. Works well on Chrome with Tampermonkey. Not tested others. I hope you will enjoy this little helper (I do). I know the script looks super fugly but it generally boils down to a mix of styles of 3 people and Gerrit having funky UI rendering. Finally, I'd also like to thank hrw (Marcin Juszkiewicz) for linking me to the original Michel's script in 2019. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-November/019051… [2] https://opendev.org/x/coats/src/commit/444c95738677593dcfed0cfd9667d4c4f0d5… [3] https://gist.github.com/yoctozepto/7ea1271c299d143388b7c1b1802ee75e Kind regards, -yoctozepto

5 7

[all] PyCharm Licenses Renewed till July 2021
by Swapnil Kulkarni 13 Jul '22

13 Jul '22

Hello, Happy to inform you the open source developer license for Pycharm has been renewed for 1 additional year till July 2021. Best Regards, Swapnil Kulkarni coolsvap at gmail dot com

8 13

Nova not updating to new size of an extended in-use / attached cinder volume (Ceph RBD) to guest
by Christian Rohmann 28 Jun '22

28 Jun '22

Hello Openstack-Discuss, after some digging I found out that cinder learned to resize attached (in-use) volumes quite a while ago with the introduction of the initial "extend 'in-use' volume" feature: https://review.opendev.org/c/openstack/cinder/+/454287/ The support was then extended to also cover Ceph RBD backed volumes with: https://review.opendev.org/c/openstack/nova/+/613039/ Since this is only about the cinder part, I was wondering if nova would ever find out and would actively rescan the device / volume and quintessentially present an increased new size to the guest. Apparently this is where a certain volume-extended event comes into play: https://review.opendev.org/c/openstack/nova/+/454322/ that is to be emitted by cinder when a volume had been extened. I then went head and tried this with the openstack cli (as Horizon does not seem to support / offer to resize in-use volumes. I run Openstack Train with Ceph RBD as storage. First I ran into an issue with the openstack cli (https://bugs.launchpad.net/cinder/+bug/1871759/comments/2 <https://bugs.launchpad.net/cinder/+bug/1871759/comments/2>) but using cinder extend $volumeid $newsize I was able to resize in-use volumes just fine. The only thing missing was the propagation to the guest. I played around with SCSI rescans, but that did not work, reboots also failed to do anyting in this regards. Stopping and starting the VM did work, but why having the capability to online-resize an attached volume when not being able to resize the guest volume as well? Apparently there seems to be an old and somewhat similar observation / bug with https://bugs.launchpad.net/nova/+bug/1369465 So I was simply wondering if this is expected to be working? Are there any special settings / options I need to set to enable this feature? Thanks and with kind regards Christian

4 9

[oslo] Propose to EOL stable/queens, stable/rocky on all the oslo scope
by Herve Beraud 24 Jun '22

24 Jun '22

Hi, On our last meeting of the oslo team we discussed the problem with broken stable branches (rocky and older) in oslo's projects [1]. Indeed, almost all these branches are broken. Előd Illés kindly generated a list of periodic-stable errors on Oslo's stable branches [2]. Given the lack of active maintainers on Oslo and given the current status of the CI in those branches, I propose to make them End Of Life. I will wait until the end of month for anyone who would like to maybe step up as maintainer of those branches and who would at least try to fix CI of them. If no one will volunteer for that, I'll EOLing those branches for all the projects under the oslo umbrella. Let us know your thoughts. Thank you for your attention. [1] https://meetings.opendev.org/meetings/oslo/2021/oslo.2021-10-04-15.00.log.t… [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023939.html -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

5 5

[api=sig][i18n][infra][tc] Cleaning up more defunct mailing lists
by Jeremy Stanley 04 May '22

04 May '22

A quick audit of the mailing lists we host at lists.openstack.org turned up the following 11 which have had no new posts for at least three years now: * openstack-api-consumers * openstack-de * openstack-el * openstack-i18n-fr * openstack-ir * openstack-personas * openstack-ru * openstack-sos * openstack-tw * openstack-vi * third-party-announce I'd like to clean them up by removing their list configurations, but leaving any public archives intact. Are there any objections? Should any of the above have future messages redirected to a different list (though since they haven't had any for years, that's probably unnecessary)? -- Jeremy Stanley

5 8

[neutron] Bug Deputy Report January 03 - 10
by Lucas Alvares Gomes 11 Apr '22

11 Apr '22

Hi, This is the Neutron bug report from January 3rd to 10th. Critical: * https://bugs.launchpad.net/neutron/+bug/1956344 - "Functional test test_gateway_chassis_rebalance is failing intermittently" - Assigned to: Rodolfo Alonso High: * https://bugs.launchpad.net/neutron/+bug/1956034 - "ovn load balancer health monitor cause mac address conflict" - Unassigned * https://bugs.launchpad.net/neutron/+bug/1956745 - " [ovn-octavia-provider] Load Balancer remained with ACTIVE state even with PENDING_UPDATE listener" - Assigned to: Luis Tomas Bolivar * https://bugs.launchpad.net/neutron/+bug/1956763 - "[OVN] Overlapping configuration for security group logging is not applied correctly" - Assigned to: Elvira Garcia Ruiz Medium: * 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/1956632 - "DNS integration documentation and scenario tests need update after dns_assignment calculation was changed" - Assigned to: Miguel Lavalle * https://bugs.launchpad.net/neutron/+bug/1956785 - "Duplicate validator TypeError for dict values Edit" - Assigned to: Harald Jensås Low: * https://bugs.launchpad.net/neutron/+bug/1956476 - "[OVN] Disallow multiple physnets per bridge" - Assigned to: Rodolfo Alonso * https://bugs.launchpad.net/neutron/+bug/1956770 - " keepalived no_track implemented in >= 2.0.3" - Assigned to: Rodolfo Alonso Needs further triage: * https://bugs.launchpad.net/neutron/+bug/1956435 - "OVS: support multiple segments per host" - Unassigned * https://bugs.launchpad.net/neutron/+bug/1956460 - "The VM can't get metadata from dhcp-agent" - Unassigned * https://bugs.launchpad.net/neutron/+bug/1956846 - "ha router duplicated routes" - Unassigned Cheers, Lucas

4 7

Xena and CEPH RBD backend (show_image_direct_url status )
by west, andrew 09 Apr '22

09 Apr '22

Hello experts Currently using openstack Xena and Ceph backend (Pacific 16.2.7) It seems there is a bug (since Wallaby?) where the efficient use of a CEPH Pacific RBD backend (i.e with copy-on-write-cloning) is not working . Show_image_direct_url needs to be False to create volumes (or ephemeral volumes for nova) This can of course be tremendously slow (Nova , ephemeral root disk) without copy-on-write cloning feature of Ceph. As Ceph RBD is THE most favourite backend for block storage in openstack I am wondering how others are coping (or workarounds found ?) Which combinations of Openstack and Ceph are known to work well with copy-on-write-cloning? How is the noted GRAVE Security RISK of enabling Show_image_direct_url mitigated ? (i.e I think , for CEPH RBD, it needs to be True to get cloning to work efficiently) See another report of this issue here: Re: Ceph Pacifif and Openstack Wallaby - ERROR cinder.scheduler.flows.create_volume - CEPH Filesystem Users (spinics.net)<https://www.spinics.net/lists/ceph-users/msg66016.html> Thanks for any help or pointers, Andrew West Openstack consulting CGG France ________________________________ "This e-mail and any accompanying attachments are confidential. The information is intended solely for the use of the individual to whom it is addressed. Any review, disclosure, copying, distribution, or use of the email by others is strictly prohibited. If you are not the intended recipient, you must not review, disclose, copy, distribute or use this e-mail; please delete it from your system and notify the sender immediately."

7 9

[all][tc] Zed TC-PTG Planning
by Ghanshyam Mann 01 Apr '22

01 Apr '22

Hello Everyone, As you already know that the Zed cycle virtual PTG will be held between 4th - 8th April[1]. I have started the preparation for the Technical Committee PTG sessions. Please do the following: 1. Fill the below doodle poll as per your availability. Please fill it in soon as the deadline to book the slot is March 11th. - https://doodle.com/poll/gz4dy67vmew5wmn9 2. Add the topics you would like to discuss to the below etherpad. - https://etherpad.opendev.org/p/tc-zed-ptg NOTE: this is not limited to TC members only; I would like all community members to fill the doodle poll and, add the topics you would like or want TC members to discuss in PTG. [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027051… -gmann

1 2

[TripleO] Core team cleanup
by James Slagle 30 Mar '22

30 Mar '22

Hello, I took a look at our core team, "tripleo-core" in gerrit. We have a few individuals who I feel have moved on from TripleO in their focus. I looked at the reviews from stackalytics.io for the last 180 days[1]. These individuals have less than 6 reviews, which is about 1 review a month: Bob Fournier Dan Sneddon Dmitry Tantsur Jiří Stránský Juan Antonio Osorio Robles Marius Cornea These individuals have publicly expressed that they are moving on from TripleO: Michele Baldessari wes hayutin I'd like to propose we remove these folks from our core team, while thanking them for their contributions. I'll also note that I'd still value +1/-1 from these folks with a lot of significance, and encourage them to review their areas of expertise! If anyone on the list plans to start reviewing in TripleO again, then I also think we can postpone the removal for the time being and re-evaluate later. Please let me know if that's the case. Please reply and let me know any agreements or concerns with this change. Thank you! [1] https://www.stackalytics.io/report/contribution?module=tripleo-group&projec… -- -- James Slagle --

5 6

[tc][release] Removing TC tags framework - next steps for release notes
by Radosław Piliszek 15 Mar '22

15 Mar '22

Hello Release Team, As you might have heard, the TC is removing the TC tags framework. [1] The first step has already been proposed and is being voted on. [2] The removal of certain parts seems to be affecting the release team tooling, especially with the usage of the stable:follows-policy tag to show a relevant banner. [3] The proposed change purposely avoids breaking the releases repo and awaits a "part 2" which cleans up everything TC-tags-framework-related. Thus, I am asking for your help to remove this dependency on the tags framework. I understand there might be several approaches to this and need your assistance to continue. The simplest approach is to drop the relevant code - assuming it is not actively used for release process purposes. Obviously, for anything else I need your input on what the options are. It is also possible that you would prefer to port this tag to your internal metadata. I am open to ideas and will help enact the changes. [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025554.… [2] https://review.opendev.org/c/openstack/governance/+/822900 [3] https://opendev.org/openstack/releases/src/commit/768a12e233c23999db18c807c… Kind regards, -yoctozepto

3 4

[infra] gerrit is:mergeable predicate
by Brian Rosmaita 15 Mar '22

15 Mar '22

Hello Infra team, In Gerrit 3.4, the is:mergeable predicate is disabled by default [0]. It was kind of handy to be able to screen out patches that are in merge conflict when looking for reviews. Is there an alternative way of doing this, or would you be averse to restoring the previous behavior? (I promise not to complain about gerrit performance.) cheers, brian [0] https://www.gerritcodereview.com/3.4.html#ismergeable-predicate-is-disabled…

2 3

[Neutron][Octavia][ovn-octavia-provider] proposing Luis Tomas Bolivar for ovn-octavia-provider core reviewer
by Lajos Katona 09 Mar '22

09 Mar '22

Hi I would like to propose Luis Tomas Bolivar (ltomasbo) as a core reviewer to the ovn-octavia-provider project. Luis is very active in the project (see [1] and [2]) and has experience with Kuryr side also which uses ovn-octavia-provider. As ovn-octavia-provider is a link between Neutron and Octavia I ask both Neutron and Octavia cores to vote by answering to this thread, to have a final decision. Thanks for your consideration [1]: https://review.opendev.org/q/owner:ltomasbo%2540redhat.com+branch:master [2]: https://www.stackalytics.io/report/contribution?module=neutron-group&projec… Cheers Lajos

8 8

[Triple0] Upgrade Error
by Lokendra Rathour 05 Mar '22

05 Mar '22

Hi Team, we are trying to upgrade Triple0 Train to Ussuri. Undercloud upgrade prepare is done successfully and when we are going for overcloud upgrade getting below error: * len(inspect.getargspec(type_).args) > 1)2022-02-23 16:49:50.959 187217 INFO tripleoclient.utils.utils [-] Running Ansible playbook: /usr/share/ansible/tripleo-playbooks/cli-update-params.yaml, Working directory: /tmp/tripleoj7rvp51m, Playbook directory: /usr/share/ansible/tripleo-playbooksPLAY [Update Parameters] *******************************************************2022-02-23 16:49:51.858966 | 5254007d-0040-f631-88e7-000000000008 | TASK | Check for required inputs2022-02-23 16:49:51.895961 | 5254007d-0040-f631-88e7-000000000008 | SKIPPED | Check for required inputs | localhost2022-02-23 16:49:51.897803 | 5254007d-0040-f631-88e7-000000000008 | TIMING | Check for required inputs | localhost | 0:00:00.096595 | 0.04s2022-02-23 16:49:51.901827 | 5254007d-0040-f631-88e7-000000000009 | TASK | Set parameters fact2022-02-23 16:49:51.949091 | 5254007d-0040-f631-88e7-000000000009 | OK | Set parameters fact | localhost2022-02-23 16:49:51.951583 | 5254007d-0040-f631-88e7-000000000009 | TIMING | Set parameters fact | localhost | 0:00:00.150375 | 0.05s2022-02-23 16:49:51.956146 | 5254007d-0040-f631-88e7-00000000000b | TASK | Update parameters2022-02-23 16:50:12.542028 | 5254007d-0040-f631-88e7-00000000000b | FATAL | Update parameters | localhost | error={"changed": false, "error": "Error validating environment for plan overcloud: ERROR: Property error: resources.InternalApiVirtualIP.properties: Unknown Property DnsName\n File \"/usr/lib/python3.6/site-packages/heat/common/wsgi.py\", line 891, in __call__\n request, **action_args)\n File \"/usr/lib/python3.6/site-packages/heat/common/wsgi.py\", line 964, in dispatch\n return method(*args, **kwargs)\n File \"/usr/lib/python3.6/site-packages/heat/api/openstack/v1/util.py\", line 56, in handle_stack_method\n return handler(controller, req, **kwargs)\n File \"/usr/lib/python3.6/site-packages/heat/api/openstack/v1/stacks.py\", line 633, in validate_template\n raise exc.HTTPBadRequest(result['Error'])\n", "msg": "Error updating parameters for plan overcloud: Error validating environment for plan overcloud: ERROR: Property error: resources.InternalApiVirtualIP.properties: Unknown Property DnsName\n File \"/usr/lib/python3.6/site-packages/heat/common/wsgi.py\", line 891, in __call__\n request, **action_args)\n File \"/usr/lib/python3.6/site-packages/heat/common/wsgi.py\", line 964, in dispatch\n return method(*args, **kwargs)\n File \"/usr/lib/python3.6/site-packages/heat/api/openstack/v1/util.py\", line 56, in handle_stack_method\n return handler(controller, req, **kwargs)\n File \"/usr/lib/python3.6/site-packages/heat/api/openstack/v1/stacks.py\", line 633, in validate_template\n raise exc.HTTPBadRequest(result['Error'])\n", "success": false}2022-02-23 16:50:12.544560 | 5254007d-0040-f631-88e7-00000000000b | TIMING | Update parameters | localhost | 0:00:20.743350 | 20.59s* Command used to run the overcloud upgrade prepare: *(undercloud) [stack@undercloud ~]$ cat upgrade_overcloud_prepare.shopenstack overcloud upgrade prepare --templates \ -r /home/stack/templates/roles_data.yaml \ -n /home/stack/templates/network_data.yaml \ -e /home/stack/templates/environment.yaml \ -e /home/stack/templates/environments/network-isolation.yaml \ -e /home/stack/templates/environments/network-environment.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-conductor.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-inspector.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-overcloud.yaml \ -e /home/stack/templates/ironic-config.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/docker-ha.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/podman.yaml \ -e /home/stack/templates/init-repo.yaml \ -e /home/stack/containers-prepare-parameter.yaml(undercloud) [stack@undercloud ~]$* *Document referred:*Upgrading to a Next Major Release — TripleO 3.0.0 documentation (openstack.org) <https://docs.openstack.org/project-deploy-guide/tripleo-docs/wallaby/post_d…> Any support here, please. -- ~ Lokendra skype: lokendrarathour

2 5

[tc][ptl] TC + Community Leaders interaction in Zed Virtual PTG
by Ghanshyam Mann 04 Mar '22

04 Mar '22

Hello Everyone, We had successful TC+Community leaders interaction sessions in the last PTG, and we will continue the same for Zed cycle PTG also. I have created the below etherpad with the draft agenda, If you as PTL or project representatives or SIG Chair and would like to attend this session, please add your name: - https://etherpad.opendev.org/p/tc-ptl-interaction-zed Also, I have created the doodle poll to select the best suitable time. It will be for two hours (single or two sessions) either on Monday or Tuesday. Please add your preference in the below doodle poll (including TC members): - https://doodle.com/poll/dcer6i3wk2b8eim3 -gmann

1 1

[Ironic] No suitable device was found for deployment
by 韩光宇 04 Mar '22

04 Mar '22

Dear all, I have a OpenStack Victoria environment, and tried to use ironic manage bare metal. But I got "- root device hints were not provided and all found block devices are smaller than 4294967296B." in deploy stage. 2022-02-09 17:57:56.492 3908982 ERROR ironic.drivers.modules.agent_base [-] Agent returned error for deploy step {'step': 'write_image', 'priority': 80, 'argsinfo': None, 'interface': 'deploy'} on node cc68c450-ce54-4e1c-be04-8b0a6169ef92 : No suitable device was found for deployment - root device hints were not provided and all found block devices are smaller than 4294967296B.. I used "openstack server create --flavor my-baremetal-flavor --nic net-id=$net_id --image $image testing" to deploy bare metal node. I download deploy images(ipa-centos8-master.kernel and ipa-centos8-master.initramfs) in https://tarballs.opendev.org/openstack/ironic-python-agent/dib/files/. The baremetal node info and flavor info as following: https://paste.opendev.org/show/bV7lgO6RkNQY6ZGPbT2e/ Ironic configure file as following: https://paste.opendev.org/show/bTgY9Kpn7KWqwQl73aEa/ Ironic-conductor log: https://paste.opendev.org/show/bFKZYlXmccxNxU8lEogk/ The log of ironic-python-agent in bare metal node: https://paste.opendev.org/show/btAuaMuV2IutV2Pa7YIa/ I see some old discussion about this, such as: https://bugzilla.redhat.com/show_bug.cgi?id=1312187. But those discussions took place a long time ago, not version V, and no solution was seen. Does anyone know how to solve this problem? I would appreciate any kind of guidance or help. Thank you, Han Guangyu

3 14

[Devstack][Gnocchi][Ceilometer] Not able to retrieve metrics using ceilometer and gnocchi
by Molka Gharbaoui 03 Mar '22

03 Mar '22

Hi all, I installed devstack and ceilometer by adding the following lines in the local.conf file: enable_plugin ceilometer https://opendev.org/openstack/ceilometer.git CEILOMETER_BACKEND=gnocchi Devstack (yoga) works correctly (I am able to create images, instances, etc.). The problem is that I cannot visualize the metrics. Using "gnocchi metric list" and "gnocchi resource list" commands the result is empty. When I use the "--debug" option, no errors are plotted but the body response is empty. "ceilometer-upgrade" gives the following error: DEBUG ceilometer.cmd.storage Upgrade Gnocchi resource types upgrade /opt/stack/ceilometer/ceilometer/cmd/storage.py:42 "ceilometer-polling" prints "The resource could not be found". I have a running instance. Could you help me in retrieving the metrics from openstack?

3 5

[hwsig] sushy-oem-idrac for Hardware Vendor SIG
by Jaunteva, Aija 03 Mar '22

03 Mar '22

Hi, I would like to propose moving sushy-oem-idrac [1] that is used in Ironic project to Hardware Vendor SIG. sushy-oem-idrac is iDRAC specific OEM extension of vendor-independent sushy [2] library and both use Redfish to communicate with BMCs. Any feedback welcome. Regards, Aija [1] https://opendev.org/x/sushy-oem-idrac/ [2] https://opendev.org/openstack/sushy Internal Use - Confidential

2 1

[all][tc] Technical Committee next weekly meeting on Mar 4th at 1500 UTC
by Ghanshyam Mann 02 Mar '22

02 Mar '22

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

1 2

[election][heat][ptl] PTL non-candidacy
by Rico Lin 02 Mar '22

02 Mar '22

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

4 3

[largescale-sig] Next meeting: Mar 2nd, 15utc
by Thierry Carrez 02 Mar '22

02 Mar '22

Hi everyone, 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=20220302T15 Feel free to add topics to the agenda: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[TripleO] centos9 jobs only for master, centos 8 & 9 for wallaby
by Marios Andreou 02 Mar '22

02 Mar '22

Hello TripleO o/ During the last period the tripleo-ci team has been working on getting tripleo CI jobs to run centos-9. On master branches across all TripleO repos we now run C9 exclusively (since [1]). On Wallaby branches, after the work at [2] (in particular after https://review.opendev.org/c/openstack/tripleo-ci/+/830132 merges) we will run both C8 and C9 jobs. I started an etherpad at [3] thinking this would be a PTG topic, but I think we'll want to have this conversation way before then. There is a tripleo-heat-templates example in the etherpad that shows what we can expect from the job runs (note the exact jobs that run will vary per repo and even between changes depending on the files touched - but generally there will be duplication between 8 and 9 jobs). The current proposal is that we keep a minimal subset on C8 Wallaby, with C9 wallaby having the full set of jobs. Two factors that will affect our decisions are (there may be more?) i) Upgrades requirements - are we supporting upgrading to Wallaby on 8? For example, the coming undercloud-upgrade-ffu job will be train 8 to wallaby 8. In which case we definitely need to keep at least some subset of 8 jobs (and can't entertain the removal of 8 from Wallaby completely). ii) Are we importing from Wallaby 8 or Wallaby 9? Currently it is 8 but this will soon switch. For the wallaby c8 'subset of jobs' e.g. multinode, vanilla standalone (no scenarios? some subset of them?), undercloud-ffu, minor update. This is just to start the conversation so please reply if you have thoughts or comments about any of the above. We are planning to discuss this in the coming tripleo-ci community call this coming Tuesday at 1330 UTC - meeting link at [4] so please join us if you can and would like to participate, regards, marios [1] https://review.opendev.org/q/topic:c8_teardown_master [2] https://review.opendev.org/q/topic:c9_wallaby_gates [3] https://etherpad.opendev.org/p/tripleoci-wallaby-centos-8-9 [4] https://meet.google.com/bqx-xwht-wky

4 7

[horizon][customization]
by Mathilde Hermet 02 Mar '22

02 Mar '22

Hello Openstack team, I'm currently working on customizing the Horizon (xena) dashboard to use the OVHcloud assets: logo.svg and logo-splash.svg. I've been following this documentation https://docs.openstack.org/horizon/latest/configuration/themes.html I added the ovhcloud theme in horizon/openstack_dashboard/local/local_settings.py in AVAILABLE_THEMES, I created the subdir ovhcloud in horizon/openstack_dashboard/themes and I created a ovhcloud/img with logo.svg and logo-splash.svg in it. I put a _variables.scss and a _styles.scss in /themes/ovhcloud/ Then I executed python manage.py collectstatic It put all the files in horizon-sources/horizon.../static/themes/ovhcloud But then when trying to connect with the session cookie theme="ovhcloud", I have a 500 error. i don't think it comes from images because i've been puting it in /horizon-souurces/horizon.../static/dashbaord.img and they were displayed correctly. Do you have any idea about the misconfiguration I've done ? Best regards, Mathilde Hermet

4 3

[nova][octavia][masakari][designate][oslo][requirements] oslo.context>=4.0.0 seems to need updated tests
by Matthew Thode 01 Mar '22

01 Mar '22

The update to see what's breaking is here https://review.opendev.org/829599 Feel free to make that patch depend on your fix to test (with rechecks) -- Matthew Thode

4 6

Fluentd error with Kolla ansible deployment
by A Monster 28 Feb '22

28 Feb '22

I'm getting the following error while trying to deploy openstack using kolla-ansible. I've set up a local docker registry and enabled insecure registries in daemon.json file and I even tried to pull fluentd docker image but I still get the following error TASK [common : Ensure fluentd image is present for label check] fatal: [localhost]: FAILED! => {"changed": true, "msg": "'Traceback (most recent call last):\\n File \"/usr/local/lib/python3.6/site-packages/docker/api/client.py\", line 268, in _raise_for_status\\n response.raise_for_status()\\n File \"/usr/lib/python3.6/site-packages/requests/models.py\", line 940, in raise_for_status\\n raise HTTPError(http_error_msg, response=self)\\nrequests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.41/images/create?tag=xena&fromImage=quay.io%2Fkolla%2Fcentos-source-fluentd\\n\\nDuring handling of the above exception, another exception occurred:\\n\\nTraceback (most recent call last):\\n File \"/tmp/ansible_kolla_docker_payload_xizndx9s/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 1241, in main\\n File \"/tmp/ansible_kolla_docker_payload_xizndx9s/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 1116, in ensure_image\\n File \"/tmp/ansible_kolla_docker_payload_xizndx9s/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 692, in pull_image\\n File \"/usr/local/lib/python3.6/site-packages/docker/api/image.py\", line 430, in pull\\n self._raise_for_status(response)\\n File \"/usr/local/lib/python3.6/site-packages/docker/api/client.py\", line 270, in _raise_for_status\\n raise create_api_error_from_http_exception(e)\\n File \"/usr/local/lib/python3.6/site-packages/docker/errors.py\", line 31, in create_api_error_from_http_exception\\n raise cls(e, response=response, explanation=explanation)\\ndocker.errors.APIError: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=xena&fromImage=quay.io%2Fkolla%2Fcentos-source-fluentd: Internal Server Error (\"unauthorized: access to the requested resource is not authorized\")\\n'"}

2 2

[qa][devstack] Proposing Dan Smith to devstack core
by Martin Kopec 28 Feb '22

28 Feb '22

Hi all, we would like to propose Dan Smith (IRC: dansmith) to devstack core. Dan is an experienced contributor who has been contributing to several openstack projects. We are glad Dan volunteered to help us in the Devstack project as well. You can vote/feedback in this email thread. If no objection by 17th of February, we will add Dan to the core list. Thanks, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA IM: kopecmartin

3 3

[cinder] Yoga FEATURE FREEZE in effect
by Harsha Ailani 28 Feb '22

28 Feb '22

Hello Argonauts, Having passed Milestone-3 this week (and yes, it was painful), let's evaluate where we are with cinder Yoga features: - https://blueprints.launchpad.net/cinder/yoga Note: You must apply for a Feature Freeze Exception (FFE) by 17:00 UTC on Tuesday 1 March. Features granted an FFE must be in the gate by 20:00 UTC on Monday 7 March. Being granted an FFE is not a guarantee that your feature will be included in Yoga. FFE Details: ------------------ ibm-svf-portset - https://blueprints.launchpad.net/cinder/+spec/ibm-svf-portset - https://review.opendev.org/c/openstack/cinder/+/817351 - no +2s because third-party CI isn't passing - let's face it, no one is going to review this with failing CI even if it gets an FFE - must apply for an FFE The Third-Party CI for this review is IBM Storage CI. As the storage was done last week the CI failed. But today Zuul and IBM Storage CI both passed successfully. The portset has been tested throughly and reviewed by several reviewers in the last 2 months. All the comments are addressed and tested. The review has received a +2 from Rajat and +1 from Eric and Brian. The review is ready to be merged. Thanks and Regards, Harsh Ailani

2 1

[PTLs][release] Yoga Cycle Highligts
by Előd Illés 28 Feb '22

28 Feb '22

Hi, This is a reminder, that *this week* is the week for Cycle highlights [1][2]! They need to be added to deliverable yamls so that they can be included in release marketing preparations. (See the details about how to add them at the project team guide [3].) [1] https://releases.openstack.org/yoga/schedule.html [2] https://releases.openstack.org/yoga/schedule.html#y-cycle-highlights [3] https://docs.openstack.org/project-team-guide/release-management.html#cycle… Thanks, Előd Illés irc: elodilles

2 1

[neutron] Bug deputy report for week of 21. 02. 2022
by Lajos Katona 28 Feb '22

28 Feb '22

Hi Neutron Team I was bug deputy in neutron last week. It was a very quiet week again. Needs More attention ================= * Duplicate IP address on LSPs in the same LS lead to unpredictable flow output (https://bugs.launchpad.net/neutron/+bug/1961046 ) * [ovn-octavia-provider] OVN NB DB timeouts ( https://bugs.launchpad.net/neutron/+bug/1961874 ) ** perhaps not Neutron related, but more a pkg version problem. Critical ====== * Network interface not found in namespace https://bugs.launchpad.net/neutron/+bug/1961740 ** In progress: https://review.opendev.org/c/openstack/neutron/+/830622 High ==== * Transition to SQLAlchemy 2.0 ( https://bugs.launchpad.net/neutron/+bug/1962153) * [Prefix Delegation] router add segment fails with Subnet for router interface must have a gateway IP ( https://bugs.launchpad.net/neutron/+bug/1962306 ) * [ntp] "test_network_attached_with_two_routers" randomly failing ( https://bugs.launchpad.net/neutron/+bug/1962167) ** In progress: https://review.opendev.org/c/openstack/neutron/+/830813 Low ==== * There may be a typo in the neutron document whose the title is 'Manual install & Configuration' (https://bugs.launchpad.net/neutron/+bug/1962324) Invalid ====== * generate_config_file_samples.sh fails with invalid literal for int() with base 10 (https://bugs.launchpad.net/neutron/+bug/1961906) Regards Lajos Katona (lajoskatona)

1 0

[ops][nova] How to update from N to N+3 (and manage nova services that don't start because they find too old compute nodes...)
by Massimo Sgaravatto 28 Feb '22

28 Feb '22

Dear all When we upgraded our Cloud from Rocky to Train we followed the following procedure: 1) Shutdown of all services on the controller and compute nodes 2) Update from Rocky to Stein of controller (just to do the dbsyncs) 3) Update from Stein to Train of controller 4) Update from Rocky to Train of compute nodes We are trying to do the same to update from Train to Xena, but now there is a problem because nova services on the controller node refuse to start since they find too old compute nodes (this is indeed a new feature, properly documented in the release notes). As a workaround we had to manually modify the "version" field of the compute nodes in the nova.services table. Is it ok, or is there a cleaner way to manage the issue ? Thanks, Massimo

5 10

[devstack][openstack-qa] DevStack upgrade betweem major releases
by Eduardo Santos 27 Feb '22

27 Feb '22

Hello folks, What is the procedure for upgrading a DevSack deployment from one major release to another? I didn't find any information on this in the official documentation. [1] My team maintains DevStack deployments used to provision virtual machines to developers. How can we, let's say, upgrade a stable/xena DevStack to stable/yoga, when it's released? Best regards, Eduardo Santos [1] https://docs.openstack.org/devstack/latest/

3 2

[TripleO] Gate blocker - centos-9 standalone and multinode
by Bhagyashri Shewale 27 Feb '22

27 Feb '22

Hi All, We have an issue affecting standalone and multinode centos-9 check/gate jobs due to tempest test failure. Details: https://bugs.launchpad.net/tripleo/+bug/1962298 We are currently deciding on the best course of action for unblocking this issue. We will post an update once the check/gate is clear. Until then, please hold on rechecking. Thanks and Regards Bhagyashri Shewale

2 1

[Manila] Manila Collaborative Review Session - Thursday, March 10th
by Liron Kuchlani 26 Feb '22

26 Feb '22

Hi all, We are planning a Manila collaborative review session on Thursday, March 10th, to walk through the following proposed feature: - Add S-RBAC tests for manila [1] The session will start at 14:30 UTC and continue through the first half of the weekly upstream manila community meeting as needed. We will use an etherpad [2] during the session to capture notes and discussions. Hope you can all join us, [1] https://review.opendev.org/c/openstack/manila-tempest-plugin/+/805938 [2] https://etherpad.opendev.org/p/Manila-S-RBAC-collaborative-review

3 3

[cinder] Yoga FEATURE FREEZE in effect
by Brian Rosmaita 26 Feb '22

26 Feb '22

Hello Argonauts, Having passed Milestone-3 this week (and yes, it was painful), let's evaluate where we are with cinder Yoga features: - https://blueprints.launchpad.net/cinder/yoga Note: You must apply for a Feature Freeze Exception (FFE) by 17:00 UTC on Tuesday 1 March. Features granted an FFE must be in the gate by 20:00 UTC on Monday 7 March. Being granted an FFE is not a guarantee that your feature will be included in Yoga. Note to reviewers: please concentrate on the below over the next week. 1. Complete transition to Alembic - https://blueprints.launchpad.net/cinder/+spec/complete-transition-to-alembic - this is essential technical debt elimination - has a Feature Freeze Exception 2. Reset State Robustification - https://blueprints.launchpad.net/cinder/+spec/reset-state-robustification - Tushar has been working patiently on this forever - not a destabilizing change - has a Feature Freeze Exception - let's prioritize getting the base patch reviewed and merged, and we can see how far we can work up the stack before 7 March. - https://review.opendev.org/c/openstack/cinder/+/773985/ Driver features 3. HPE Nimble driver rename - https://blueprints.launchpad.net/cinder/+spec/nimble-change-location - https://review.opendev.org/c/openstack/cinder/+/786054 - has one +2 - patch has passed third party CI configured with the old name *and* with the rename - has an FFE Hitachi VSP driver The below require this non-feature patch, which addresses followup issues - https://review.opendev.org/c/openstack/cinder/+/827259/ - has one +2 - doesn't need an FFE because it's a bugfix, but let's get it reviewed and merged! 4. Support AIX as host OS type for VSP Driver - https://blueprints.launchpad.net/cinder/+spec/hitachi-vsp-aix-os-type - https://review.opendev.org/c/openstack/cinder/+/828061 - has one +2 - has an FFE 5. Target Port Assignment for VSP Driver - https://blueprints.launchpad.net/cinder/+spec/hitachi-vsp-tgt-port-asgn - https://review.opendev.org/c/openstack/cinder/+/828060 - has one +2 - has an FFE Questionable: 1. The Return of Make Cinder Consistent and Secure RBAC Ready - https://blueprints.launchpad.net/cinder/+spec/s-rbac-ready-y - community goal - I will meet with the cinder Zed PTL to discuss what to do about this one (may give a FFE for just part) 2. Hitachi: Port Scheduler for VSP Driver - https://blueprints.launchpad.net/cinder/+spec/hitachi-vsp-port-scheduler - https://review.opendev.org/c/openstack/cinder/+/828696 - Code and tests look mostly fine, and CI is passing - some really minor issues and needs a release note - needs to be rebased on latest version of 828060 - not giving an auto-FFE because it hasn't had a +2 yet - must apply for an FFE 3. ibm-svf-portset - https://blueprints.launchpad.net/cinder/+spec/ibm-svf-portset - https://review.opendev.org/c/openstack/cinder/+/817351 - no +2s because third-party CI isn't passing - let's face it, no one is going to review this with failing CI even if it gets an FFE - must apply for an FFE

1 0

[Magnum] heat-container-agent not able to talk to keystone
by Satish Patel 25 Feb '22

25 Feb '22

Folks, I am trying to deploy k8s cluster using magnum on openstack and found cluster creation stuck during kube master heat deployment and when i look into logs i found following Feb 25 22:09:26 k8s-foo-jqpxkt2y7e46-master-0 heat-container-agent[2342]: Authorization failed: Unable to establish connection to http://192.168.75.100:5000/v3/auth/tokens Feb 25 22:09:26 k8s-foo-jqpxkt2y7e46-master-0 heat-container-agent[2342]: Source [heat] Unavailable. Feb 25 22:09:26 k8s-foo-jqpxkt2y7e46-master-0 podman[2311]: Authorization failed: Unable to establish connection to http://192.168.75.100:5000/v3/auth/tokens Feb 25 22:09:26 k8s-foo-jqpxkt2y7e46-master-0 podman[2311]: Source [heat] Unavailable. In my deployment it's a private cloud so all control plane components running on private address space and k8s cluster created their own private network which is not routable so the kube master node can't talk to keystone. I can't put my HAProxy on a public address. In that case what are the options I have? I am running OVN for networking deployed by kolla-ansible. ~S

1 0

[manila] Yoga FFE request
by Fernando Ferraz 25 Feb '22

25 Feb '22

Hi Team, I'd like to request a FFE for the following changes we have been working on for the Yoga cycle. They are all part of the effort to partially implement spec *Add spec for multiple subnet share servers* *[1]* in Manila.: 826928: Support multiple subnets per AZ https://review.opendev.org/c/openstack/python-manilaclient/+/826928 826462: Container: Multiple subnets per AZ https://review.opendev.org/c/openstack/manila/+/826462 825155: NetApp ONTAP: Add support to multiple subnets per AZ https://review.opendev.org/c/openstack/manila/+/825155 826928: Support multiple subnets per AZ https://review.opendev.org/c/openstack/python-manilaclient/+/826928 All changes were submitted in time and there has been significant progress in reviews until this point. [1] https://review.opendev.org/c/openstack/manila-specs/+/619925 Regards, Fernando

2 2

[manila] RC1 bugsquash next week, no weekly IRC meetings until 17th March 2022
by Goutham Pacha Ravi 25 Feb '22

25 Feb '22

Hello there zorillas, It's time again to gather and squash some bugs together! We're hosting a bugsquash week between 3rd March 2022 and 10th March 2022. We've a preliminary list of bugs scoped out [1]. We'd love for you to participate by claiming a bug or two to fix during the week and reviewing bug fixes. Some of these bug fixes are in-progress, and we'll be conducting collaborative reviews to merge them during the week. If you'd like to work on something, please add it to the list [1] We'll use meetpad [2] to hang out opportunistically during the week at different times to review code or brainstorm, please watch the chatter on OFTC's #openstack-manila. However, a few scheduled events: * We'll have a kick-off at 1500 UTC on 3rd March 2022 * A "almost there" check in on 8th March 2022 at 1600 UTC on 8th March 2022 * A collab-review for S-RBAC tempest tests [3] at 1430 UTC on 10th March 2022 * A wrap up for the bugsquash week at 1530 UTC on 10th March 2022 All these will occur in the meetpad room; and these times overlap with our weekly IRC meetings - so we'll skip those. If you have any topics to discuss, please call our attention on this mailing list or on OFTC's #openstack-manila. Thanks, and hope to see you there! Goutham [1] https://ethercalc.openstack.org/t727llczm00f [2] https://meetpad.opendev.org/ManilaYogaRC1Bugsquash [3] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027329…

1 0

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

25 Feb '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on 24th. 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/2022/tc.2022-02-24-15.00.log.html * Next week's meeting is on 4th March Thursday 15:00 UTC, feel free to add the topic on the agenda[1] by 3rd March. 2. What we completed this week: ========================= * Zed cycle technical election[2] * Switch Keystone back to PTL model[3] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. 2 out of 9 items are completed. Open Reviews ----------------- * Eight open reviews for ongoing activities[5]. Zed cycle Leaderless projects ---------------------------------- As elections are closed, 17 projects are missing the nomination and out of those 11 have the late nomination. 6 projects are still seeking leaders. As the next step, TC will work on the assignment of leaders if we find any other steps on these leaderless projects[6]. Zed cycle testing runtime ------------------------------ I started the Zed cycle testing runtime, please check and give any objection if there is any[7] PTG Preparation -------------------- I have started the etherpad for TC PTG[8] preparation as well as for TC+Community Leaders sessions[9]. Also, doodle poll to select the slots[10] Testing and bumping the lower bounds in requirements.txt --------------------------------------------------------------------- Brian brought this topic while there was discussion on os-bricks bumping the minimum in requirements.rst[11]. As we do not test the lower bounds, we are not sure if existing lower bounds work or not. Telling anyone to reply on those is no guarantee that they will work or not. As TC, we agreed to give more clear direction on lower bounds and that is why we will discuss this topic in Zed PTG. Meanwhile, os-brick bumping the minimum is fine. Release identification and release name ----------------------------------------------- The proposal is under review and updates [12] Dropping tags framework ------------------------------ part1 of this is merged[13], part-2 of updating release script and other tags migration is under-progress. TC position on release cadence ------------------------------------- The proposal is under review and updates [14]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[15]. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [16] 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[17]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [18] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027412… http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027411… [3] https://review.opendev.org/c/openstack/governance/+/829037 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://etherpad.opendev.org/p/zed-leaderless [7] https://review.opendev.org/c/openstack/governance/+/830454 [8] https://etherpad.opendev.org/p/tc-zed-ptg [9] https://etherpad.opendev.org/p/tc-ptl-interaction-zed [10] https://doodle.com/poll/gz4dy67vmew5wmn9 https://doodle.com/poll/dcer6i3wk2b8eim3 [11] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027343… https://review.opendev.org/c/openstack/os-brick/+/828802 [12] https://review.opendev.org/c/openstack/governance/+/829563 [13] https://review.opendev.org/c/openstack/governance/+/822900 [14] https://review.opendev.org/c/openstack/governance/+/828777 [15] https://etherpad.opendev.org/p/zuul-config-error-openstack [16] https://review.opendev.org/c/openstack/governance/+/798540 [17] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [18] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[release] Release countdown for week R-4, Feb 28 - Mar 04
by Előd Illés 25 Feb '22

25 Feb '22

Development Focus ----------------- We just passed feature freeze! Until release branches are cut, you should stop accepting featureful changes to deliverables following the cycle-with-rc release model, or to libraries. Exceptions should be discussed on separate threads on the mailing-list, and feature freeze exceptions approved by the team's PTL. Focus should be on finding and fixing release-critical bugs, so that release candidates and final versions of the Yogadeliverables can be proposed, well ahead of the final Yogarelease date. General Information ------------------- We are still finishing up processing a few release requests, but the Yogarelease requirements are now frozen. If new library releases are needed to fix release-critical bugs in Yoga, you must request a Requirements Freeze Exception (RFE) from the requirements team before we can do a new release to avoid having something released in Yoga that is not actually usable. This is done by posting to the openstack-discuss mailing list with a subject line similar to: [$PROJECT][requirements] RFE requested for $PROJECT_LIB Include justification/reasoning for why a RFE is needed for this lib. If/when the requirements team OKs the post-freeze update, we can then process a new release. A soft String freeze is now in effect, in order to let the I18N team do the translation work in good conditions. In Horizon and the various dashboard plugins, you should stop accepting changes that modify user-visible strings. Exceptions should be discussed on the mailing-list. By March 24th, 2022this will become a hard string freeze, with no changes in user-visible strings allowed. Actions ------- stable/yogabranches should be created soon for all not-already-branched libraries. You should expect 2-3 changes to be proposed for each: a .gitreview update, a reno update (skipped for projects not using reno), and a tox.ini constraints URL update. Please review those in priority so that the branch can be functional ASAP. The Prelude section of reno release notes is rendered as the top level overview for the release. Any important overall messaging for Yoga changes should be added there to make sure the consumers of your release notes see them. Finally, if you haven't proposed Yogacycle-highlights yet, you are already late to the party. Please see our email for details: http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027361… Upcoming Deadlines & Dates -------------------------- RC1 deadline: March 10th, 2022(R-3 week) Final RC deadline: March 24th, 2022(R-1 week) Final Yogarelease: March 30th, 2022 Next PTG: April 4 - 8, 2022 (virtual) ElődIllés irc: elodilles

1 0

[all][elections][tc] Technical Committee Election Results
by Ghanshyam Mann 25 Feb '22

25 Feb '22

For 5 TC open seats, there were 5 candidates so no election was required. Please join me in congratulating the 5 newly elected members of the Technical Committee (TC). Amy Marrich (spotz) Arne Wiebalck (arnewiebalck) Kristi Nikolla (knikolla) Brian Rosmaita (rosmaita) Sławek Kapłoński (slaweq) Full results: no election required. Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all of the candidates, having a good group of candidates helps engage the community in our democratic process. Thank you for another great round. -gmann, on behalf of the OpenStack Technical Election Officials

3 2

[all][elections][ptl] Project Team Lead Zed Election Conclusion and Results
by Ghanshyam Mann 24 Feb '22

24 Feb '22

Thank you to the all candidates who put their names forward for Project Team Lead (PTL) in this election. A healthy, open process breeds trust in our decision making capability. Thank you to all those who make this process possible. Now for the results of the PTL election process, please join me in extending congratulations to the following PTLs: * Barbican : Douglas Mendizábal * Blazar : Pierre Riteau * Cinder : Rajat Dhasmana * Cloudkitty : Rafael Weingartner * Cyborg : Bailin Zhang * Designate : Michael Johnson * Ec2 Api : Andrey Pavlov * Glance : Abhishek Kekane * Horizon : Vishal Manchanda * Ironic : Iury Gregory Melo Ferreira * Keystone : Douglas Mendizábal * Kolla : Michal Nasiadka * Kuryr : Maysa de Macedo Souza * Manila : Carlos Silva * Neutron : Lajos Katona * Nova : Sylvain Bauza * Octavia : Gregory Thiemonge * OpenStack Helm : Gage Hugo * OpenStackAnsible : Dmitriy Rabotyagov * OpenStackSDK : Artem Goncharov * Puppet OpenStack : Takashi Kajinami * Quality Assurance : Martin Kopec * Rally : Andrey Kurilin * Release Management : Elod Illes * Requirements : Matthew Thode * Sahara : Fossen Qiu * Storlets : Takashi Kajinami * Swift : Tim Burke * Tacker : Yasufumi Ogawa * Telemetry : Matthias Runge * Tripleo : James Slagle * Vitrage : Eyal Bar-Ilan * Winstackers : Lucian Petrut For remaining projects (without PTL candaidates), TC will work on the appointment. Elections: no election required. Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all involved in the PTL election process -gmann, on behalf of the OpenStack Technical Election Officials

1 0

[neutron] Drivers meeting agenda - 25.02.2022.
by Lajos Katona 24 Feb '22

24 Feb '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. * [RFE][L3][OVS] use controller (ovs-agent) send (packet-out) RA to (VMs) ports (https://bugs.launchpad.net/neutron/+bug/1961011 ) * [RFE][OVN] Support DNS subdomains at a network level ( https://bugs.launchpad.net/neutron/+bug/1960850 ) * Gratuitous ARPs are not sent during master transition: ( https://bugs.launchpad.net/neutron/+bug/1952907) ** For this one there are a few wip patches: ** https://review.opendev.org/c/openstack/neutron/+/821434 ** https://review.opendev.org/c/openstack/neutron/+/821433 ** https://review.opendev.org/c/openstack/neutron/+/712474 [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

No IP address in VMs instances ( neutron dhcp ) on fresh kolla-ansible deployment
by A Monster 24 Feb '22

24 Feb '22

I've deployed an all in one Openstack on Centos 8 stream using kolla-ansible following the tutorial in openstack kolla website. After the deployment, I used the int-runonce script to create networks and stuff, but after launching a cirros VM, I found that the network interfaces inside the VM didn't get IP addresses from the neutron DHCP agent, therefore that instance was not reachable from nowhere. The docker container of the dhcp agent is up and running, but VMs don't receive any data from it.

2 1

[all][tc] Technical Committee next weekly meeting on Feb 24th at 1500 UTC
by Ghanshyam Mann 23 Feb '22

23 Feb '22

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

1 1

[Oslo] Core team cleanup
by Herve Beraud 23 Feb '22

23 Feb '22

Hello, I took a look at our core team, "oslo-core" in gerrit. We have a few individuals who I feel have moved on from Oslo in their focus. I looked at the reviews from stackalytics.io for the last 180 days[2]. These individuals have no activity during the last 180 days: - Zane Bitter; - Doug Hellmann; - Sean McGinnis. These individuals have publicly expressed that they are moving on from Oslo: - Ken Guisti; - Moisés Guimarães De Medeiros. I'd like to propose we remove these folks from our core team, while thanking them for their contributions. I'll also note that I'd still value +1/-1 from these folks with a lot of significance, and encourage them to review their areas of expertise! If anyone on the list plans to start reviewing in Oslo again, then I also think we can postpone the removal for the time being and re-evaluate later. Please let me know if that's the case. Please reply and let me know any agreements or concerns with this change. Thank you! [1] https://review.opendev.org/admin/groups/106,members [2] https://www.stackalytics.io/report/contribution?module=oslo-group&project_t… <https://www.stackalytics.io/report/contribution?module=tripleo-group&projec…> -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

1 0

[all][elections][ptl][tc] Combined PTL/TC Zed cycle Election Nominations Last Days
by Ghanshyam Mann 23 Feb '22

23 Feb '22

Hello Everyone, A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Feb 15, 2022 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. Election statistics[2]: Nominations started @ 2022-02-08 23:45:00 UTC Nominations end @ 2022-02-15 23:45:00 UTC Nominations duration : 7 days, 0:00:00 Nominations remaining : 23:30:36 Nominations progress : 86.01% --------------------------------------------------- Projects[1] : 49 Projects with candidates : 19 ( 38.78%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 30 (Adjutant Cloudkitty Freezer Heat Ironic Kuryr Magnum Masakari Monasca Murano OpenStackAnsible OpenStack_Charms Openstack_Chef Rally Release_Management Requirements Sahara Senlin Skyline Solum Swift Tacker Telemetry Tripleo Trove Venus Vitrage Watcher Zaqar Zun) =================================================== Stats gathered @ 2022-02-15 00:14:24 UTC This means that with approximately 1 days left, 30 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. There are also currently 3 confirmed candidates for the 5 open Technical Committee. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.openstack.org/#/q/is:open+project:openstack/election have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for… -gmann & The OpenStack Technical Election Officials

4 7

[TripleO] Offline Installation Support
by Anirudh Gupta 23 Feb '22

23 Feb '22

Hi Team, We have successfully done POC on deploying my TripleO Train HA Setup with Baremetal Provisioning on Overcloud Node as well. We would like to thank Tripleo community members for helping us and resolving all our concerns at all times. Moving forward, we need to deploy the setup on the Lab environment for which I need some support as well. We don't have internet in Lab machines, all that we have is access to a central server (staging) which has internet access and we can download all the requirements over there. Queries: - Is there any feasible method to install Undercloud and Overcloud Machines in complete offline mode? - If yes, then 1. What are the steps to download all related stuff on the staging server? 2. What modifications would be required in undercloud/overcloud and other configuration files to support this? Regards Anirudh Gupta Regards Anirudh Gupta

3 2

[Diversity] Diversity and Inclusion Meeting -change - short notice
by Amy Marrich 23 Feb '22

23 Feb '22

Due to a conflict from another member and my decision to take PTO to play with the dogs, we are moving the March meeting to this Friday, February 25th at 16:00 UTC. The meeting will be held on video at https://meetpad.opendev.org/osf- diversity-and-inclusion as recently voted on and the agenda can be found at https://etherpad.openstack.org/p/diversity-wg-agenda. Please join us! Thanks, Amy (spotz)

1 0

SUBJECT: [ ironic][QA] Cycle With Intermediary Unreleased Deliverables
by Armstrong Foundjem 23 Feb '22

23 Feb '22

Quick reminder that we'll need a release very soon for a number of deliverables following a cycle-with-intermediary release model but which have not done *any* release yet in the Yoga cycle: ironic-prometheus-exporter ironic-python-agent-builder ironic-ui networking-baremetal networking-generic-switch patrole Those should be released ASAP, and in all cases before the March 10th deadline, so that we have a release to include in the final Yoga release. Best regards, Armstrong Foundjem irc: @armstrong

2 1

[cinder] Bug deputy report for week of 02-23-2022
by Sofia Enriquez 23 Feb '22

23 Feb '22

This is a bug report from 02-03-2022 to 02-23-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting The bug report is back! Today's meeting is on video. ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1960206 "[RBD] Amend the formula of retrieving total_capacity for a rbd pool." Fix proposed to master. Assigned to Gorka. - https://bugs.launchpad.net/os-brick/+bug/1961102 "NVMe-oF doesn't disconnect." Unassigned. Problem with request ID: - https://bugs.launchpad.net/cinder/+bug/1960329 "Wrong request ID on API middleware filters." Fix proposed to master. Assigned to Gorka. - https://bugs.launchpad.net/cinder/+bug/1960021 "Request to list REST API versions doesn't return the request id." Fix proposed to master. Assigned to Gorka. - https://bugs.launchpad.net/cinder/+bug/1960020 "Duplicated request ids in the logs." Fix proposed to master. Assigned to Gorka. - https://bugs.launchpad.net/cinder/+bug/1960019 "REST API responses have wrong request ID when using noauth." Fix proposed to master. Assigned to Gorka. Low - https://bugs.launchpad.net/cinder/+bug/1960315 "[IBM Storwize] Delete volume issue in reverse replication." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1960314 "[IBM Storwize] Resize issue in reverse replication." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1961548 "[Storwize] Fix multiple SVC CLI calls to create volume operation." Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1959178 "SolidFire: Error message logged when creating volume from image." Fix proposed to master. Have a +2! Wishlist - https://bugs.launchpad.net/cinder/+bug/1960574 "Provide back-end Qos support for spdk driver." Unassigned. Incomplete - https://bugs.launchpad.net/cinder/+bug/1959350 " [RBD] Volume status becomes available after force delete." Unassigned. Invalid - https://bugs.launchpad.net/cinder/+bug/1961685 "cinder-volume.service crashes: no module named 'wrapt'." If I'm missing bugs please let me know! 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

[infra] Gerrit email outage?
by Stephen Finucane 23 Feb '22

23 Feb '22

I haven't received any emails from Gerrit since midday (UTC) yesterday. Chatting on IRC, it seems I'm not alone. Has something changed in Gerrit or is this a simple outage? Cheers, Stephen

2 2

[kolla][rabbitmq] Trouble with RMQ 3.8 in Train
by Albert Braden 23 Feb '22

23 Feb '22

We are running kolla-ansible Train and I successfully followed the recommendations in [1] to change our RMQ settings, and our RMQ works a lot better now, but one of the recommendations is to run RMQ 3.8 and so far I haven’t been able to make it work. Our working RMQ container has these settings in the Dockerfile to force 3.7 and the appropriate erlang version: 'erlang-21.3*', 'rabbitmq-server-3.7.23*' I changed those settings to allow 3.8: 'rabbitmq-server-3.*.*el8ost*' Now my RMQ container fails to start with: {"log":"20:29:28.440 [error] Supervisor rabbit_prelaunch_sup had child prelaunch started with rabbit_prelaunch:run_prelaunch_first_phase() at undefined exit with reason no_configuration_schema_found in context start_error\r\n","stream":"stdout","time":"2022-02-22T20:29:28.441064637Z"} What am I missing? [1] https://wiki.openstack.org/wiki/Large_Scale_Configuration_Rabbit

2 1

[qa] Zed PTG planning
by Martin Kopec 23 Feb '22

23 Feb '22

Hi everyone, virtual PTG for the Zed cycle will be held between 4th - 8th April [1]. I've created a Doodle [2] to collect the best time slots for our team. Please fill it in rather sooner than later (the deadline for team signup is March 11th). I've also created an etherpad [3] to collect ideas/topics for the PTG sessions. If you have anything to discuss, please don't hesitate to write it there. [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027051… [2] https://doodle.com/poll/q5yzatzh45brt5v2 [3] https://etherpad.opendev.org/p/qa-zed-ptg Thanks, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 0

[neutron] Stale Tap Ports
by Ammad Syed 22 Feb '22

22 Feb '22

Hi, I am using neutron 19.1 and ovn 21.09. There is a strange behavior I am seeing on compute nodes that ovs logs shows below logs 2022-02-23T06:14:06.426Z|00226|bridge|WARN|could not open network device tapea0dca9a-32 (No such device) 2022-02-23T06:14:06.428Z|00227|bridge|WARN|could not open network device tapaeaa1749-b5 (No such device) 2022-02-23T06:14:06.429Z|00228|bridge|WARN|could not open network device tap53f06ea0-70 (No such device) 2022-02-23T06:14:06.431Z|00229|bridge|WARN|could not open network device tap724cf0cc-7b (No such device) 2022-02-23T06:14:06.433Z|00230|bridge|WARN|could not open network device tap18864125-6d (No such device) In the ovs-vsctl show I also see alot of ports with these status. Port tapaeaa1749-b5 Interface tapaeaa1749-b5 error: "could not open network device tapaeaa1749-b5 (No such device)" Port tap18864125-6d Interface tap18864125-6d error: "could not open network device tap18864125-6d (No such device)" Port tap54415fc0-dd Interface tap54415fc0-dd error: "could not open network device tap54415fc0-dd (No such device)" I have checked in neutron port list and there is no port found for these tap interfaces. openstack port list --long | grep -i 18864125-6d I have checked in database in ports table, there is also no ports there with these ids. mysql> select * from ports where id like '%18864125-6d%'; These ports even show on compute node even if there is no instance running on it. Are these stale ports ? If yes, is there any tool or utility to run audit and delete these ports ? Ammad

1 0

Re: [Tempest] OpenSack Powered * vs OpeStack Compatible
by yahoo yahho 22 Feb '22

22 Feb '22

Sent from Yahoo Mail on Android

1 0

[all] [requirements] Artificially inflated requirements in os-brick
by Thomas Goirand 22 Feb '22

22 Feb '22

Hi, I've been quite surprised to see $topic. Most requirements for os-brick are now to be found in Yoga only. I've asked why, and I've been told that the reason is because "we've been testing with the new versions only for the number of months". Well, the reason why someone would increase a minimum requirement *must* be only because of the need of a new feature, and should be treated with care. Otherwise, this makes upgrading very dangerous and annoying to do. As much as possible, I would strongly recommend that any dependency in Stable can be found in Stable-1 (only when a new feature is mandatory, then it's ok-ish to require that new version, though I would advocate for a possible fallback if that's not too complex to write). Now, if that's the path we're taking, all is going backward 5 years ago, and then my thinking is: we must reintroduce lower-constraints testing ASAP. Your thoughts everyone? Cheers, Thomas Goirand (zigo) P.S: Please note that this is absolutely not about os-brick, I'm not pointing my finger to any team, it's a global thinking for the whole OpenStack project.

5 10

LetsEncrypt OS Ansible Ussuri
by Marc-Antoine Godde 22 Feb '22

22 Feb '22

Hello, I have a question on how to setup LetsEncrypt with OpenStack Ansible. We are still on OpenStack Ussuri. We added the following variables to user_variables.yml. ================================================================================== haproxy_ssl_letsencrypt_enable: True haproxy_ssl_letsencrypt_install_method: "distro" haproxy_ssl_letsencrypt_setup_extra_params: "--http-01-address {{ ansible_host }} --http-01-port 8888" haproxy_ssl_letsencrypt_email: email(a)example.com haproxy_interval: 2000 user avatar user avatar haproxy_extra_services: # an internal only service for acme-challenge whose backend is certbot on the haproxy host - service: haproxy_service_name: letsencrypt haproxy_backend_nodes: - name: localhost ip_addr: {{ ansible_host }} #certbot binds to the internal IP backend_rise: 1 #quick rise and fall time for multinode deployment to succeed backend_fall: 2 haproxy_bind: - 127.0.0.1 #bind to 127.0.0.1 as the local internal address will be used by certbot haproxy_port: 8888 #certbot is configured with http-01-port to be 8888 haproxy_balance_type: http ================================================================================== Yet, Horizon config for HAproxy is already defined in the default vars (https://github.com/openstack/openstack-ansible/blob/stable/ussuri/inventory… <https://github.com/openstack/openstack-ansible/blob/stable/ussuri/inventory…>) and we don’t know where ta add the required ACL to redirect the traffic from 80 port to 8888: ==================================== haproxy_frontend_acls: #use a frontend ACL specify the backend to use for acme-challenge letsencrypt-acl: rule: "path_beg /.well-known/acme-challenge/" backend_name: letsencrypt ==================================== We know that this is fixed in OpenStack Ansible Victoria. Is it possible with Ussuri tho ? Many thanks, Best, Marc-Antoine Godde

2 5

[cinder] reminder: this week's meeting in video+IRC
by Brian Rosmaita 22 Feb '22

22 Feb '22

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

1 0

[nova] OOM Killed Processes
by Ammad Syed 22 Feb '22

22 Feb '22

Hi,, I am having trouble with my compute node that nova-compute and ovs process are being killed by OOM. I have alot memory available in system. # free -g total used free shared buff/cache available Mem: 1006 121 881 0 2 879 Swap: 7 0 7 But I am seeing process are being killed in dmesg. [Sat Feb 19 03:46:26 2022] Memory cgroup out of memory: Killed process 2080898 (ovs-vswitchd) total-vm:9474284kB, anon-rss:1076384kB, file-rss:11700kB, shmem-rss:0kB, UID:0 pgtables:2776kB oom_score_adj:0 [Sat Feb 19 03:47:01 2022] Memory cgroup out of memory: Killed process 2081218 (ovs-vswitchd) total-vm:9475332kB, anon-rss:1096988kB, file-rss:11700kB, shmem-rss:0kB, UID:0 pgtables:2780kB oom_score_adj:0 [Sat Feb 19 03:47:06 2022] Memory cgroup out of memory: Killed process 2081616 (ovs-vswitchd) total-vm:9473252kB, anon-rss:1073052kB, file-rss:11700kB, shmem-rss:0kB, UID:0 pgtables:2784kB oom_score_adj:0 [Sat Feb 19 03:47:16 2022] Memory cgroup out of memory: Killed process 2081940 (ovs-vswitchd) total-vm:9471236kB, anon-rss:1070920kB, file-rss:11700kB, shmem-rss:0kB, UID:0 pgtables:2776kB oom_score_adj:0 [Sat Feb 19 03:47:16 2022] Memory cgroup out of memory: Killed process 6098 (nova-compute) total-vm:3428356kB, anon-rss:279920kB, file-rss:9868kB, shmem-rss:0kB, UID:64060 pgtables:1020kB oom_score_adj:0 [Mon Feb 21 11:15:08 2022] Memory cgroup out of memory: Killed process 2082296 (ovs-vswitchd) total-vm:9475372kB, anon-rss:1162636kB, file-rss:11700kB, shmem-rss:0kB, UID:0 pgtables:2864kB oom_score_adj:0 Any advice on how to fix this ? Also any best practices document on configuring memory optimizations in nova compute node. Ammad

2 3

[openstacksdk][magnum] Adding get_coe_cluster_by_id() method to openstack.cloud._coe
by Florian Haas 22 Feb '22

22 Feb '22

Hi everyone, here's something I recently ran into while playing with openstacksdk against Magnum; I could use some help/feedback there if anyone's inclined. :) It looks as though openstacksdk, which presently doesn't include get_coe_cluster_by_id() in cloud._coe[1], will effectively only ever list clusters and then filter client-side, as opposed to looking up individual clusters directly. That means that it only ever hits the Magnum API's /v1/clusters URL[2], which provides only limited properties on each cluster it returns. Were it to implement get_coe_cluster_by_id(), then any Connection object that has use_direct_get set to True could hit /v1/clusters/<uuid> instead[3], which provides a much richer set of properties. I have submitted a patch for this[4], but I have a couple of open questions: (1) I'm not quite sure what's the proper way to test that get_coe_cluster() actually invokes get_coe_cluster_by_id() when passed a UUID. Normally I'd do that with unittest.mock's assert_called() method, but openstacksdk heavily wraps various mock.patch() calls so I'm sure there's a better, preferred way to do it for the openstacksdk codebase. (2) Even if implementing get_coe_cluster_by_id() is the correct approach (which I am entirely not sure of), it still strikes me as a bit unintuitive that there are additional details that could be retrieved only if use_direct_get is set on the Connection object. I think having an explicit "get me more detail" toggle on the call would be preferable, which would hit /v1/clusters first (to retrieve the cluster UUID from the name), and then hit /v1/clusters/<uuid> to retrieve the rich set of properties. Now, the docstring for search_coe_clusters() mentions a "detail" parameter[5], but that appears to be a bit of a red herring as that method doesn't actually use that param. So I'm a bit stuck and unsure what to do there. :) If anyone has thoughts on this they'd like to share, I'd be most grateful! Cheers, Florian References: [1] https://opendev.org/openstack/openstacksdk/src/branch/master/openstack/clou… [2] https://docs.openstack.org/api-ref/container-infrastructure-management/?exp… [3] https://docs.openstack.org/api-ref/container-infrastructure-management/?exp… [4] https://review.opendev.org/c/openstack/openstacksdk/+/828791 [5] https://opendev.org/openstack/openstacksdk/src/branch/master/openstack/clou…

1 1

[CloudKitty] Virtual PTG April 2022
by Rafael Weingärtner 22 Feb '22

22 Feb '22

Hello everyone, As you probably heard our next PTG will be held virtually in April. We've marked April 4, at 13:00-16:00 UTC [1]. We already have a CloudKitty meeting organized for this day. Therefore, it seems the most practical choice. However, if you guys would like some other dates and/or time, just let me know. The room we selected is called "Cactus". I've also created an etherpad [2] to collect ideas/topics for the PTG sessions. If you have anything to discuss, please don't hesitate to write it there. [1] https://ethercalc.openstack.org/7yxdas7suqnd [2] https://etherpad.opendev.org/p/cloudkitty-ptg-zed -- Rafael Weingärtner

1 0

New CI log workflow improvement
by Daniel Pawlik 22 Feb '22

22 Feb '22

Hi, tl;dr Besides sending CI logs, does someone use Logstash on Opendev to push information to the new Elasticsearch (Opensearch) service? Long version: I am currently looking into a new log workflow for OpenDev's OpenSearch that is using the logscraper tool [1], as an improvement over the current workflow [2]. I spotted a few bottlenecks that are complicating pushing logs to the new Elasticsearch service. The most important bottlenecks are: - - gearman worker - this service needs at least 10 instances to keep up with the current influx of build logs. - As a reminder, this service consumes information prepared by gearman client, downloads the logs, adds information and - pushes data to the logstash service, - - logstash service - this service is "freezing" from time to time and it requires many resources such as CPU and RAM. - As a reminder, the service receives data and by using grok filter [3] prepares information that later will be pushed - to Elasticsearch. - The new workflow would eliminate these bottlenecks by pushing data directly into Elasticsearch. This would therefore drop the following services: - gearman client - gearman worker - logstash service Before proceeding further, we need to know if these services, especially logstash, are (apart from sending logs from CI) not used anywhere, so that we don't accidentally pull the plug on any other workflows. If you are aware of these, please let me know. Dan [1] https://opendev.org/openstack/ci-log-processing [2] https://docs.opendev.org/opendev/system-config/latest/logstash.html [3] https://opendev.org/openstack/logstash-filters/src/branch/master/filters/op…

2 1

Call for Outreachy OpenStack mentors - May 2022 round
by Mahati Chamarthy 21 Feb '22

21 Feb '22

Hello! *TL;DR OpenStack is participating in Outreachy for the upcoming round! **Please submit projects.* Outreachy's goal is to support people from groups underrepresented in the technology industry. Interns will work remotely with mentors from our community. We are seeking mentors to propose projects that Outreachy interns can work on during their internship. If you or your colleagues are interested in mentoring in the next round, please submit your project proposal over here by *March 4th, 2022:* https://www.outreachy.org/communities/cfp/openstack/ Mentors should read the mentor FAQ https://www.outreachy.org/mentor/mentor-faq and find more details about the Outreachy program and timeline in https://www.outreachy.org/communities/cfp/ . If you need help crafting your project proposal or have any other queries, please contact me Mahati Chamarthy <mahati.chamarthy(a)gmail.com> or Dmitry Tantsur <divius.inside(a)gmail.com> Best, Mahati

3 3

[kolla][neutron] VM is getting the wrong IP, can't contact metadata service
by Chris DiLorenzo 21 Feb '22

21 Feb '22

Hello, I am having a weird issue. I am running openstack Victoria with OVN. Generally, everything is working. I created a VM using a fixed port with an IP of 10.210.64.6. There are no issues with this VM. When I create a new VM, I get this route info: [ 29.363664] cloud-init[564]: ci-info: ++++++++++++++++++++++++++++++++Route IPv4 info++++++++++++++++++++++++++++++++ [ 29.368568] cloud-init[564]: ci-info: +-------+-----------------+-------------+-----------------+-----------+-------+ [ 29.369945] cloud-init[564]: ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags | [ 29.372441] cloud-init[564]: ci-info: +-------+-----------------+-------------+-----------------+-----------+-------+ [ 29.376434] cloud-init[564]: ci-info: | 0 | 0.0.0.0 | 10.210.64.1 | 0.0.0.0 | ens3 | UG | [ 29.377820] cloud-init[564]: ci-info: | 1 | 10.210.64.0 | 0.0.0.0 | 255.255.255.192 | ens3 | U | [ 29.380417] cloud-init[564]: ci-info: | 2 | 169.254.169.254 | 10.210.64.6 | 255.255.255.255 | ens3 | UGH | [ 29.384448] cloud-init[564]: ci-info: +-------+-----------------+-------------+-----------------+-----------+-------+ The IP is set correctly, but you can see I am getting a gateway of 10.210.64.6 for the metadata ser. ice. This is preventing the VM from reaching the service so the SSH key is not being added preventing me from logging in. As far as I can tell, there are no error and every VM I build is getting this .6 IP for this route. Thanks, Chris

3 4

[kolla-ansible][manila]Permission denied when using cephfs nfs
by Boxiang Zhu 21 Feb '22

21 Feb '22

Hi all, I have met an issue when I use manila with cephfs nfs backend. Environment Information: - OS: ubuntu 18.04 - OpenStack Version: Train - Kolla-ansible Version: 9.3.2 I used kolla-ansible to deploy my OpenStack environment AIO. Here is the info of my globals.yml as followed: --- kolla_base_distro: "ubuntu" kolla_install_type: "source" openstack_release: "train" kolla_internal_vip_address: "172.16.150.67" network_interface: "ens3" neutron_external_interface: "ens4" enable_haproxy: "no" enable_ceph: "yes" enable_ceph_mds: "yes" enable_ceph_rgw: "yes" enable_ceph_nfs: "yes" enable_cinder: "yes" enable_manila: "yes" enable_manila_backend_cephfs_nfs: "yes" enable_ceph_rgw_keystone: "yes" ceph_osd_store_type: "filestore" I try to use cephfs nfs backend for manila. All containers are running and the services of manila is good. +----+------------------+-------------------+------+---------+-------+----------------------------+ | Id | Binary | Host | Zone | Status | State | Updated_at | +----+------------------+-------------------+------+---------+-------+----------------------------+ | 1 | manila-data | manila | nova | enabled | up | 2022-02-16T03:25:34.000000 | | 2 | manila-scheduler | manila | nova | enabled | up | 2022-02-16T03:25:35.000000 | | 3 | manila-share | manila@cephfsnfs1 | nova | enabled | up | 2022-02-16T03:25:40.000000 | +----+------------------+-------------------+------+---------+-------+----------------------------+ Here is my share type: +--------------------------------------+--------------------+------------+------------+-------------------------------------+----------------------+-------------+ | ID | Name | visibility | is_default | required_extra_specs | optional_extra_specs | Description | +--------------------------------------+--------------------+------------+------------+-------------------------------------+----------------------+-------------+ | 265a6637-0322-4c4a-9185-f30f01b96d12 | default_share_type | public | - | driver_handles_share_servers : False | | None | +--------------------------------------+--------------------+------------+------------+-------------------------------------+----------------------+-------------+ When I create a share, error information appears in manila-share.log file: 2022-02-16 09:30:04.615 20 INFO manila.share.manager [req-b57991af-5355-4202-8543-dc7ff914d919 - - - - -] Updating share status 2022-02-16 09:30:04.616 20 DEBUG manila.share.driver [req-b57991af-5355-4202-8543-dc7ff914d919 - - - - -] Updating share stats. _update_share_stats /var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/driver.py:1232 2022-02-16 09:30:54.675 20 DEBUG manila.share.drivers.cephfs.driver [req-d2c8ef2a-d3ce-483b-9e39-e5a3d857d72b eaf0e30a92694889aa46ac5a1d4b7a47 37025e7c9ae447c8975e9ef3a4e5d0ff - - -] create_share CEPHFSNFS1 name=449a52a4-f19c-4d1b-b437-7dc2443e040c size=1 share_group_id=None create_share /var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/cephfs/driver.py:262 2022-02-16 09:30:54.682 20 INFO ceph_volume_client [req-d2c8ef2a-d3ce-483b-9e39-e5a3d857d72b eaf0e30a92694889aa46ac5a1d4b7a47 37025e7c9ae447c8975e9ef3a4e5d0ff - - -] create_volume: /volumes/_nogroup/449a52a4-f19c-4d1b-b437-7dc2443e040c2022-02-16 09:30:54.927 20 ERROR manila.share.manager [req-d2c8ef2a-d3ce-483b-9e39-e5a3d857d72b eaf0e30a92694889aa46ac5a1d4b7a47 37025e7c9ae447c8975e9ef3a4e5d0ff - - -] Share instance 449a52a4-f19c-4d1b-b437-7dc2443e040c failed on creation.: cephfs.OSError: error in mkdir volumes/_nogroup/449a52a4-f19c-4d1b-b437-7dc2443e040c: Permission denied [Errno 13] 2022-02-16 09:30:54.929 20 WARNING manila.share.manager [req-d2c8ef2a-d3ce-483b-9e39-e5a3d857d72b eaf0e30a92694889aa46ac5a1d4b7a47 37025e7c9ae447c8975e9ef3a4e5d0ff - - -] Share instance information in exception can not be written to db because it contains {} and it is not a dictionary.: cephfs.OSError: error in mkdir volumes/_nogroup/449a52a4-f19c-4d1b-b437-7dc2443e040c: Permission denied [Errno 13] 2022-02-16 09:30:54.955 20 INFO manila.message.api [req-d2c8ef2a-d3ce-483b-9e39-e5a3d857d72b eaf0e30a92694889aa46ac5a1d4b7a47 37025e7c9ae447c8975e9ef3a4e5d0ff - - -] Creating message record for request_id = req-d2c8ef2a-d3ce-483b-9e39-e5a3d857d72b 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server [req-d2c8ef2a-d3ce-483b-9e39-e5a3d857d72b eaf0e30a92694889aa46ac5a1d4b7a47 37025e7c9ae447c8975e9ef3a4e5d0ff - - -] Exception during message handling: cephfs.OSError: error in mkdir volumes/_nogroup/449a52a4-f19c-4d1b-b437-7dc2443e040c: Permission denied [Errno 13] 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/ceph_volume_client.py", line 656, in _mkdir_p 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server self.fs.stat(subpath) 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server File "cephfs.pyx", line 1257, in cephfs.LibCephFS.stat 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server cephfs.ObjectNotFound: error in stat: volumes/_nogroup/449a52a4-f19c-4d1b-b437-7dc2443e040c: No such file or directory [Errno 2] 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred: 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server File "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server File "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 274, in dispatch 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server File "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 194, in _do_dispatch 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server File "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/manager.py", line 187, in wrapped 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server return f(self, *args, **kwargs) 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server File "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/utils.py", line 568, in wrapper 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server return func(self, *args, **kwargs) 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server File "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/manager.py", line 1790, in create_share_instance 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server exception=e) 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server File "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server self.force_reraise() 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server File "/var/lib/kolla/venv/lib/python3.6/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server File "/var/lib/kolla/venv/lib/python3.6/site-packages/six.py", line 693, in reraise 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server raise value 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server File "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/manager.py", line 1753, in create_share_instance 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server context, share_instance, share_server=share_server) 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server File "/var/lib/kolla/venv/lib/python3.6/site-packages/manila/share/drivers/cephfs/driver.py", line 272, in create_share 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server mode=self._cephfs_volume_mode) 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/ceph_volume_client.py", line 677, in create_volume 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server self._mkdir_p(path, mode) 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server File "/usr/lib/python3/dist-packages/ceph_volume_client.py", line 658, in _mkdir_p 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server self.fs.mkdir(subpath, mode) 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server File "cephfs.pyx", line 887, in cephfs.LibCephFS.mkdir 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server cephfs.OSError: error in mkdir volumes/_nogroup/449a52a4-f19c-4d1b-b437-7dc2443e040c: Permission denied [Errno 13] 2022-02-16 09:30:54.971 20 ERROR oslo_messaging.rpc.server

3 4

[neutron] Bug deputy - week of 14.02.2022
by Slawek Kaplonski 21 Feb '22

21 Feb '22

Hi, I was bug deputy last week. It was very quiet week in terms of bugs in Neutron. Here is the summary: ## Critical https://bugs.launchpad.net/neutron/+bug/1961112 - [ovn] overlapping security group rules break neutron-ovn-db-sync-util - fix already proposed long time ago: https://review.opendev.org/c/openstack/neutron/+/801707, ## High https://bugs.launchpad.net/neutron/+bug/1961173 - [fullstack] test_vm_is_accessible_by_local_ip fails sometimes - assigned to Oleg, fix proposed alreadh https://review.opendev.org/c/openstack/neutron/+/829659 ## Medium https://bugs.launchpad.net/neutron/+bug/1961013 - [stable][ovn] frequent OVN DB leader changes increase rate of Neutron API errors - assigned to Frode, it's about backport feature from master to stable branches, ## Low https://bugs.launchpad.net/neutron/+bug/1961184 - [OVN] Virtual ports are always DOWN - assigned to Rodolfo, ## Whishlist (RFEs) https://bugs.launchpad.net/neutron/+bug/1960850 - [RFE][OVN] Support DNS subdomains at a network level - I think it's properly described and needs to be discussed during the drivers meeting now, https://bugs.launchpad.net/neutron/+bug/1961011 - [RFE][L3][OVS] use controller (ovs-agent) send (packet-out) RA to (VMs) ports - I think it's properly described and needs to be discussed during the drivers meeting now, -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

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

18 Feb '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on 17th. 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/2022/tc.2022-02-17-15.00.log.html * Next week's meeting is on 24th Feb Thursday 15:00 UTC, feel free to add the topic on the agenda[1] by 23rd Feb. 2. What we completed this week: ========================= * Z cycle release name [2] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[3]. 2 out of 9 items are completed. Open Reviews ----------------- * Six open reviews for ongoing activities[4]. Release identification and release name ----------------------------------------------- As Zed is the last release for the current alphabet release name iteration. TC discussed the future release name ideas. Belmiro has proposed the idea of adding "<year>.<release count>" number to each release. The proposal is up for review[5] Switch Keystone back to PTL model ------------------------------------------- Keystone team proposed to move Keystone from DPL to PTL model[6] with Douglas Mendizábal as PTL. Dropping tags framework ------------------------------ yoctozepto has updated part1 of dropping the tag framework[7] which is ready for review. Elod us updating the release scripts to remove the tag ref. Z release cycle Technical Election --------------------------------------- The nomination for PTL and TC elections is closed and there is no voting required. TC Campaigning period is open until 22nd Feb[8]. We will be closing the election on 22nd Feb. There are total 17 projects that missed the nomination, I have created the etherpad to work on the leaderless projects[9]. There is already late candidacy for 8 projects and 9 projects still need leaders. Please add your name if you would like to lead those projects. TC position on release cadence ------------------------------------- No other updates from last week, Dan's proposal is under review[10]. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[11]. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [12] 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[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [14] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027242… [3] https://etherpad.opendev.org/p/tc-yoga-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://review.opendev.org/c/openstack/governance/+/829563 [6] https://review.opendev.org/c/openstack/governance/+/829037 [7] https://review.opendev.org/c/openstack/governance/+/822900 [8] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027311… [9] https://etherpad.opendev.org/p/zed-leaderless [10] https://review.opendev.org/c/openstack/governance/+/828777 [11] https://etherpad.opendev.org/p/zuul-config-error-openstack [12] https://review.opendev.org/c/openstack/governance/+/798540 [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[release] Release countdown for week R-5, Feb 21-25
by Előd Illés 18 Feb '22

18 Feb '22

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

1 0

Masquerading VM works 99%
by Derek O keeffe 17 Feb '22

17 Feb '22

Hi all, We have an openstack cluster with one controller and 4 computes (Victoria) we have set it up using vlan provider networks with linuxbridge agent, distributed routing & ml2 (I am only partly on the networking so there could be more to that which I can find out if needed) So I was tasked with creating two Instances, one (lets call it the external vm) with an external interface 10.55.9.67 and internal interface 192.168.1.2. A second instance (lets call it the internal vm) would then be placed on the 192.168.1.0 network. I configured masquerading on the "external vm" and tried to ping the outside world from the "internal" vm as per something like this https://kifarunix.com/configure-ubuntu-20-04-as-linux-router/?unapproved=49… Both VM's were instantiated on the same compute host (I've tried it with them on separate hosts as well). I can see the ping leave using tcpdumps along the way and it makes it all the way back to the internal interface on the external machine. It just fails on the last hop to the internal machine. I've tried everything in my power to find why this won't work so I would be grateful for any advice at all. I have added the below to show how I followed the ping manually and where it went and when it failed. Thank you in advance. Following the ping from source to destination and back:Generated on the private VMsent to the internal interface on the external vmsent to the external interface on the external vmsent to the tap interface on the computesent to the physical nic on the computesent to the nic on the network device out to the internet received on nic on the network devicefrom the internet received on physical nic on the computereceived on tap interface on compute received on external interface on the external vmreceived on the internal interface on the external vmNEVER gets to last step on the internal vm Regards,Derek

4 6

[cinder] festival of XS reviews 18 February 2022
by Brian Rosmaita 17 Feb '22

17 Feb '22

Hello Argonauts, Apologies for the lateness of this reminder, but hopefully everyone has already used the handy ICS file [0] to have this event on their personal calendars. The most recent edition of the Cinder Festival of XS Reviews will be held tomorrow (Friday 18 February). who: Everyone! what: The Cinder Festival of XS Reviews when: Friday 18 February 2022 from 1400-1600 UTC where: https://meetpad.opendev.org/cinder-festival-of-reviews etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews See you there! brian [0] http://eavesdrop.openstack.org/calendars/cinder-festival-of-reviews.ics

1 0

[neutron] Drivers meeting - Friday 18.2.2022 - cancelled
by Lajos Katona 17 Feb '22

17 Feb '22

Hi Neutron Drivers! As Friday is recharge day for RedHat, and most probably we will not have a quorum for the voting, let's cancel tomorrow's meeting. See You at the meeting next week. Lajos Katona (lajoskatona)

1 0

[TripleO] Gate blocker - ansible version
by Rafael Castillo 17 Feb '22

17 Feb '22

Hi All, We have an issue affecting multiple centos stream 8 gate jobs related to an ansible version conflict. Details: https://bugs.launchpad.net/tripleo/+bug/1961035 We are currently deciding on the best course of action for unblocking this issue. We will post an update once the gate is clear. Until then, please hold on rechecking. Thank you!

1 1

[TripleO] Sergii Golovatiuk for TripleO core reviewer (upgrades-related)
by Jose Luis Franco Arza 17 Feb '22

17 Feb '22

Hello folks, I would like to propose Sergii Golovatiuk [1][2][3] as a core reviewer on the TripleO repositories related to the upgrades workflow (openstack/tripleo-heat-templates, openstack/tripleo-ansible, openstack/python-tripleoclient, openstack/tripleo-ci, openstack/tripleo-quickstart, openstack/tripleo-quickstart-extras). Sergii has been working in OpenStack for the last 10 years, he is already core-reviewer of the tripleo-upgrade <https://github.com/openstack/tripleo-upgrade>repository in which he is providing with very valuable feedback, as well as helping getting relevant patches merged. His deep knowledge of the different OpenStack projects, as well as his involvement in the upgrades/updates workflows for the last 9 OpenStack releases makes him a great code reviewer, being able to catch several issues during the code review process. I will monitor the thread for a week and if no objections are exposed I will add him to the tripleo-core group. PD: Here comes the +1 from my side. Thanks. Cheers, José Luis [1]: https://review.opendev.org/q/owner:sgolovat%2540redhat.com [2]: https://www.stackalytics.io/?project_type=all&metric=commits&user_id=sgolov… [3]: Position #25 in the most active TripleO contributors list <https://www.stackalytics.io/report/contribution?module=tripleo-group&projec…>

13 13

[Tripleo] Issue in Baremetal Provisioning from Overcloud
by Anirudh Gupta 16 Feb '22

16 Feb '22

Hi Team I am trying to Provision Bare Metal Node from my tripleo Overcloud. For this, while deploying the overcloud, I have followed the *"default flat" *network approach specified in the below link https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15… Just to highlight the changes, I have defined the *ironic-config.yaml* parameter_defaults: ... ... IronicIPXEEnabled: true IronicInspectorSubnets: - ip_range: *172.23.3.100,172.23.3.150* IronicInspectorInterface: 'br-baremetal' Also modified the file *~/templates/network-environment.yaml* parameter_defaults: NeutronBridgeMappings: datacentre:br-ex,baremetal:br-baremetal NeutronFlatNetworks: datacentre,baremetal With this I have Followed all the steps of creating br-baremetal bridge on controller, given in the link below: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15… - type: ovs_bridge name: br-baremetal use_dhcp: false members: - type: interface name: nic3 Post Deployment, I have also create a flat network on "datacentre" physical network and subnet having the range *172.23.3.200,172.23.3.240 *(as suggested subnet is same as of inspector and range is different) and the router Also created a baremetal node and ran *"openstack baremetal node manage bm1", *the state of which was a success. Observation: On executing "openstack baremetal node *provide* bm1", the machine gets power on and ideally it should take an IP from ironic inspector range and PXE Boot. But nothing of this sort happens and we see an IP from neutron range " *172.23.3.239*" (attached the screenshot) [image: image.png] I have checked overcloud ironic inspector podman logs alongwith the tcpdump. In tcpdump, I can only see dhcp discover request on br-baremetal and nothing happens after that. I have tried to explain my issue in detail, but I would be happy to share more details in case still required. Can someone please help in resolving my issue. Regards Anirudh Gupta

5 20

[all][tc] Technical Committee next weekly meeting on Feb 17th at 1500 UTC
by Ghanshyam Mann 16 Feb '22

16 Feb '22

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

1 1

[kolla-ansible][nova]Problem with distribution of instance on servers
by Franck VEDEL 16 Feb '22

16 Feb '22

Hello, I seem to have a problem that I hadn't seen. I have 3 servers for my openstack, built with Kolla-ansible, I'm in Victoria version. I had simply put the 3 servers in the [compute] part of the multinode file, at first it worked, but for some time all the VMs are placed on server 1. The 3 servers are operational, identical. here are 3 screenshots to show it. (on the images, the instances on servers 2 and 3 are present because it worked correctly, but no more instances are created on these servers now) I tried to understand how the instances are distributed on the servers, but in my case, I don't understand why none are assigned to the 2nd and 3rd server. How to find the problem? It should be nova-scheduler . Do you have to do anything special? Go see if a parameter has a bad value? Thanks in advance if you can help me. Franck VEDEL

4 10

[manila][cinder][glance][nova][devstack][qa] Add fmount to devstack-plugin-ceph core
by Goutham Pacha Ravi 16 Feb '22

16 Feb '22

Hello, As you're aware, we're looking to adopt cephadm within devstack-plugin-ceph to align with the ceph community's recommendations on day0-day2 handling of ceph [1] in devstack. Francesco Pantano has worked a ton on the integration of ceph with tripleo. He has been our go-to person for deploying and using the new nfs daemon with manila. In light of this, to make reviews more productive, I would like to propose fpantano(a)redhat.com (fmount on launchpad and oftc) to the devstack-plugin-ceph-core group [2]. He's aware of our review policies, and will take care not to break existing testing. Any objections? Thank you, Goutham Pacha Ravi [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026778.… [2] https://review.opendev.org/admin/groups/8e51d8f39e33d932a40f03060b861db57a3…

5 5

[keystone] anyone using OpenID with Keystone?
by Francois 16 Feb '22

16 Feb '22

Hi Keystone users! I am wondering if anyone has experience with keystone openid integration. Initially I was using Keystone LDAP backend (using tripleo KeystoneLDAPDomainEnable and KeystoneLDAPBackendConfigs parameters) and it works! Users are able to log in through Horizon or through the cli, roles can be given per LDAP group, and you can click in Horizon and download a working openrc or clouds.yaml file (minus the root CA that has to be added) to authenticate with the cli (and your password ends as an OS_PASSWORD variable in your environment). I am now trying the Keystone Openid backend (using the enable-federation-openidc.yaml provided by tripleo - https://github.com/openstack/tripleo-heat-templates/blob/master/environment…) with a mapping like this: [{"local":[{"user":{"name":"{0}"},"group":{"domain":{"name":"Default"},"name":"federated_users"}}],"remote":[{"type":"HTTP_OIDC_EMAIL"}]}] The SSO works superb with Horizon, however - logging with the cli seems impractical. I see some doc here: https://docs.ukcloud.com/articles/openstack/ostack-how-use-api-sso.html where you need to provide a secret, I am skeptical I want to do that. The openrc file downloaded from Horizon is not usable as is and needs some tuning. And there is no SSO, and the password still ends up in the environment... - I don't see how I can grant roles to groups anymore. It seems I need an extra mechanism to grant permissions (as I used to do that using LDAP groups). I am wondering if anyone is willing to share their experience dealing with Keystone and OpenID. Thanks! Francois (frigo)

5 5

Openstack HPC Infiniband question
by Satish Patel 16 Feb '22

16 Feb '22

Hi all, I am playing with HPC on openstack cloud deployment and I have a Mellanox infiniband nic card. I have a couple of deployment questions regarding the infiniband network. I am new to ib so excuse me if i ask noob questions. I have configured Mellanox for sriov and created a flavor with the property pci_passthrough:alias='mlx5-sriov-ib:1' to expose VF to my instance. so far so good and i am able to see the ib interface inside my vm and its active. (I am running SM inside infiniband HW switch) root@ib-vm:~# ethtool -i ibs5 driver: mlx5_core[ib_ipoib] version: 5.5-1.0.3 firmware-version: 20.28.1002 (MT_0000000222) expansion-rom-version: bus-info: 0000:00:05.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes I didn't configure any ipaddr on the ibs5 interface etc. For testing purposes I have compiled mpirun hello world program to POC my infiniband network between two instances and I am able to successfully run the mpi sample program. Somewhere i read about neutron-mellanox agent to setup IPoIB for segmentation etc but not very sure that how complex it and what are the advantage here over just using simple passthru of SR-IOV Is this the correct way to set up an HPC cluster using openstack or is there a better way to design HPC on openstack?

2 2

[all][elections][tc] TC Election Campaigning Kickoff
by Ghanshyam Mann 16 Feb '22

16 Feb '22

Community Members, The TC Election Campaigning Period has now started [1]. During the next couple days, you are all encouraged to ask the candidates questions about their platforms [2], opinions on OpenStack, community governance, and anything else that will help you to better determine how you will vote. This is the time to raise any issues you wish the future TC to consider, and to evaluate the opinions of the nominees prior to their election. Candidates, Each of you has posted a platform [2], and announced your nomination to the developers. From this point, you are encouraged to ask each other questions about the posted platforms, and begin discussion of any points that you feel are particularly important during the next cycle. Even though there are no runoffs, still it is good to have campaigning discussion. [1] https://governance.openstack.org/election/ [2] https://governance.openstack.org/election/#z-tc-candidates -gmann & The OpenStack Technical Election Officials

1 0

[all][elections][ptl][tc] Combined PTL/TC Zed cycle Election Nominations End
by Ghanshyam Mann 15 Feb '22

15 Feb '22

Hello Everyone, The PTL and TC Nomination period is now over. The official candidate lists for PTLs [0] and TC seats [1] are available on the election website. -- PTL Election Details -- There are 17 projects without candidates, so according to this resolution[2], the TC will have to decide how the following projects will proceed: Adjutant, Freezer, Heat, Magnum, Masakari, Monasca, Murano, OpenStack_Charms, Openstack_Chef, Senlin, Skyline, Solum, Trove, Venus, Watcher, Zaqar, Zun There are 0 projects that will have elections. -- TC Election Details -- The 5 seats were filled and no runoff is required. Now begins the campaigning period where candidates and electorate may debate their statements. Thank you, [0] https://governance.openstack.org/election/#z-ptl-candidates [1] https://governance.openstack.org/election/#z-tc-candidates [2] https://governance.openstack.org/resolutions/20141128-elections-process-for… -gmann & The OpenStack Technical Election Officials

1 0

Create Image in queue State in XENA Version
by Adivya Singh 15 Feb '22

15 Feb '22

Hi Team, We have lately upgraded to Xena , but when users trying to upload any image, it is always in queue state, i did not see any error regarding any issue with glance configuration file. Any thoughts on this Regards Adivya Singh

2 1

[tooz] [mistral] Tenacity >= 8.0.1 issues (in Debian)
by Thomas Goirand 15 Feb '22

15 Feb '22

Hi, It seems Tenacity has some incompatible changes leading to this: https://bugs.debian.org/1005636 (tooz) https://bugs.debian.org/1005467 (mistral) Note that both Manila and Heat were fixed already for this last version of Tenacity, so these would likely be the only remaining blockers to upgrade to 8.0.1. As Tenacity 8.0.1 is already in Debian Unstable, I'd prefer if we fixed these rather than pinning to a lower version. Can anyone help? Cheers, Thomas Goirand (zigo)

2 2

[cinder] final reviews needed for os-brick yoga release
by Brian Rosmaita 15 Feb '22

15 Feb '22

Hello Argonauts, We are now aiming to release on Tuesday 15 Feb at 20:00 UTC. The list of patches needing review and some comments on their status is here: https://etherpad.opendev.org/p/os-brick-yoga-release We're in mostly good shape, just need a final sprint to close this out. reviewers: please review! patch authors: please keep an eye on your patches and respond quickly and make sure your CI has responded with success thanks, brian

1 1

[election][Requirements] PTL candidacy for Zed
by Matthew Thode 15 Feb '22

15 Feb '22

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

1 0

[election][swift] PTL candidacy for Zed
by Timothy Burke 15 Feb '22

15 Feb '22

I intend to continue serving as Swift PTL for the Zed cycle. We have seen Swift scale in spectacular ways. Hard drives have grown from 2-4 terabytes when Swift was started to 10-20T. The idea of a "large cluster" has gone from dozens of petabytes across hundreds of nodes to hundreds of petabytes across thousands of nodes. We will continue to see (and address) new challenges in scaling Swift. We anticipate hitting the bounds of our current ring format. We see operators struggle to balance the prioritization of cluster expansion and data durability. We see the need to improve sharding, so that clients are less impacted by what's going on in the backend. All of these have seen progress in the last cycle, and will continue to be advanced in the next. Just as important as scaling the core storage platform, however, is building up the ecosystem of ancillary services that users have come to expect out of their object storage. When a container grows to have billions of objects, it is impractical to perform thousands of listing requests to analyze its contents; instead, users expect a periodic inventory that's easy to pull into their existing data pipelines. Users should be able to examine their own access logs rather than needing to involve operators. Users want to manage their data movement and retention en masse rather than object-by-object. I look forward to seeing the balance we strike between enhancing the core storage platform and building out the data services surrounding it over the coming years. Tim Burke

1 0

[election][Release_Management] PTL candidacy for Z cycle
by Előd Illés 15 Feb '22

15 Feb '22

Hello OpenStack Community, I would like to announce my candidacy for the PTL role of the Release Management team for the Z cycle. I am core member in the Release Management team since Wallaby, but I followed the team's work even before that, and I also have been the PTL of the team for Yoga cycle for some months now. (Though, from release management perspective this is not a long period, since the most laborous part will only start in the coming weeks ;)) Furthermore, as in the past, beside release management duties, my focus is still on stable maintenance as well, since I am stable-maint-core member, too. The next cycle's challenges will be to prepare our tooling to alphabet roll-over after the Z cycle and to adjust to any other changes in our processes. And of course, parallel to this, to release OpenStack Z :) Thanks for your consideration, Előd Illés (elodilles)

1 0

[nova][placement] Implementation review day on Thursday Fev 17
by Sylvain Bauza 15 Feb '22

15 Feb '22

Hey folks, Last minute item, but we agreed during today's meeting to run a feature review day on Thursday February the 17th. If you're one of the owners of the blueprints that are marked in [1], you're eligible to ensure that this etherpad is up to date based on your last efforts and that you're somehow around either on IRC or asynchronously through Gerrit on that day to answer comments and questions about your patches. Cores, I'd appreciate if you can dedicate this Thursday to feature reviews as we still have a large set of blueprints that aren't merged yet. Thanks, -Sylvain [1] https://etherpad.opendev.org/p/nova-yoga-blueprint-status

1 0

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

15 Feb '22

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

4 6

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

15 Feb '22

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

1 0

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

15 Feb '22

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

1 0

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

15 Feb '22

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

1 0

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

15 Feb '22

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

1 0

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

15 Feb '22

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

1 0

oslo.messaging integration development
by liyang 15 Feb '22

15 Feb '22

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

5 9

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

15 Feb '22

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

1 0

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

15 Feb '22

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

4 3

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

15 Feb '22

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

1 0