- openstack-discuss - lists.openstack.org

[TripleO] gate blocker centos-9 please hold rechecks
by Marios Andreou 27 Jan '22

27 Jan '22

o/ Hi folks please hold rechecks especially if you see failing centos9 jobs (should be all of master tripleo repos now) we have a gate blocker there https://bugs.launchpad.net/tripleo/+bug/1959181 thank you, marios (on behalf of tripleo-ci team - #oooq and #tripleo channels)

1 1

Neutron issue || Remote error: TimeoutError QueuePool limit of size 5 overflow 50 reached
by Md. Hejbul Tawhid MUNNA 27 Jan '22

27 Jan '22

Hi, Suddenly we have observed few VM down . then we have found some agent are getting down (XXX) , agents are getting UP and down randomly. Please check the attachment. //////////////////////////////////////////////////////////////////////////////////////////////////// /sqlalchemy/pool.py", line 788, in _checkout\n fairy = _ConnectionRecord.checkout(pool)\n', u' File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 532, in checkout\n rec = pool._do_get()\n', u' File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 1186, in _do_get\n (self.size(), self.overflow(), self._timeout), code="3o7r")\n', u'TimeoutError: QueuePool limit of size 5 overflow 50 reached, connection timed out, timeout 30 (Background on this error at: http://sqlalche.me/e/3o7r)\n']. 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent Traceback (most recent call last): 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/neutron/agent/l3/agent.py", line 837, in _report_state 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent True) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/neutron/agent/rpc.py", line 97, in report_state 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent return method(context, 'report_state', **kwargs) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/client.py", line 179, in call 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent retry=self.retry) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/oslo_messaging/transport.py", line 133, in _send 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent retry=retry) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 645, in send 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent call_monitor_timeout, retry=retry) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 636, in _send 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent raise result 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent RemoteError: Remote error: TimeoutError QueuePool limit of size 5 overflow 50 reached, connection timed out, timeout 30 (Background on this error at: http://sqlalche.me/e/3o7r) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 163, in _process_incoming\n res = self.dispatcher.dispatch(message)\n', u' File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 265, in dispatch\n return self._do_dispatch(endpoint, method, ctxt, args)\n', u' File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 194, in _do_dispatch\n ///////////////////////////////////////////////////////////////////////////////// Is there anything related with the following default configuration. /etc/neutron/neutron.conf #max_pool_size = 5 #max_overflow = 50 regards, Munna

4 7

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

26 Jan '22

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

1 1

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

26 Jan '22

This is a bug report from 01-19-2022 to 01-26-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- The cinder bug meeting will return on Feb 16th. If you have an urgent bug, please bring it to the main cinder meeting! Medium - https://bugs.launchpad.net/cinderlib/+bug/1958159 "stable/ussuri: cinderlib-lvm-functional job is failing." Fix proposed to stable/ussuri and master. Assigned to Takashi Kajinami. - https://bugs.launchpad.net/cinder/+bug/1958632 "SVC storwize regression after fixing 1913363." Unassigned. Incompleted - https://bugs.launchpad.net/cinder/+bug/1958845 "Rbd: possibility of data loss during revert-to-snap." Fix proposed to master. 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

[swift] Dropping support for py27
by Timothy Burke 26 Jan '22

26 Jan '22

The Swift team plans for the coming Yoga release to be the final Swift release to support Python 2.7. This is long overdue; it is now two years since the official Python 2.7 end-of-life. We were relatively late in adding Python 3 support, however, and wanted to ensure a long-enough period to root out Python 3 bugs and transition existing Python 2 clusters. We've used that time effectively; now it's time to move forward. We'll do what we can to ensure subsequent releases are *not* considered for installation on unsupported versions of Python. Notably, we'll ensure wheels are no longer flagged as universal, and `python_requires` will be set. If you have a continued interest in running latest Swift on Python 2.7, please get in touch with us, either here on the mailing list or in #openstack-swift on OFTC. Tim Burke Swift PTL

1 0

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

26 Jan '22

This is a bug report from 01-12-2022 to 01-19-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1957804 "RBD deferred deletion causes undeletable RBD snapshots." In Progress. Assigned to Eric. - https://bugs.launchpad.net/cinder/+bug/1958122 "HPE 3PAR: In multi host env, multi-detach works partially if volume is attached to instances from separate hosts." In Progress. Assigned to Raghavendra Tilay. Low - https://bugs.launchpad.net/cinder/+bug/1958023 "Solidfire: there are some references to the removed parameters left." In Progress. Assigned to kajinamit. - https://bugs.launchpad.net/cinder/+bug/1958245 "NetApp ONTAP driver shows type error exception when replicating FlexGroups." Unassigned. Cheers, -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

2 2

[heat][interop] StackBuildErrorException on a master job
by Martin Kopec 26 Jan '22

26 Jan '22

Hi there, our interop master job (jobs for older OpenStack releases are fine) is constantly failing on 2 heat tests: heat_tempest_plugin.tests.functional.test_software_config.ParallelDeploymentsTest.test_deployments_metadata heat_tempest_plugin.tests.functional.test_software_config.ParallelDeploymentsTest.test_deployments_timeout_failed Full log at: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/… Patch where you can see all the jobs - master one failing and the rest passing: https://review.opendev.org/c/openinfra/refstack-client/+/819918 We can't figure out what's going on there. Maybe additional configuration of the deployment is required? New requirements? Any ideas what the job is missing? Thank you, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA

2 3

2021 OpenInfra Foundation Annual Report Now Available
by Kendall Nelson 26 Jan '22

26 Jan '22

Hello Everyone! The 2021 OpenInfra Annual Report is live! It includes sections on all OpenInfra projects, Foundation updates, open infrastructure growth, SIG and WG updates, and more. You can find the 2021 OpenInfra Annual Report here: https://openinfra.dev/annual-report/2021 Thanks! Kendall (diablo_rojo)

1 0

[release][infra] SSH host key issue - RedFlag stop approving
by Előd Illés 26 Jan '22

26 Jan '22

Hi, tag-release jobs started to fail today and what i see is mostly that ECDSA host key for IP address X not in list of known hosts [1][2][3] Please don't approve release patches until we haven't figure out what is the problem. [1] https://zuul.opendev.org/t/openstack/build/a490703c83514eb7ba9d0ff6307f7371… [2] https://zuul.opendev.org/t/openstack/build/00d3f765ea6847a3bf7ea53294cf2a88… [3] https://zuul.opendev.org/t/openstack/build/d8aaeff52dac442e89fd3e253596e0c2… Thanks, Előd irc:elodilles @ #openstack-release

2 4

[monasca] [Release-job-failures] Release of openstack/monasca-agent for ref refs/tags/4.0.1 failed
by Előd Illés 26 Jan '22

26 Jan '22

Hi Monasca team, The forwarded mail contains a release job failure, specifically the publish-monasca-agent-docker-images job failed [1] with a missing package during docker image build. Can you please have a look at the issue? [1] https://zuul.opendev.org/t/openstack/build/2ebcbfec634c4c068e9f7625473ea726 Thanks in advance, Előd irc:elodilles @ #openstack-release -------- Forwarded Message -------- Subject: [Release-job-failures] Release of openstack/monasca-agent for ref refs/tags/4.0.1 failed Date: Wed, 26 Jan 2022 11:57:09 +0000 From: zuul(a)openstack.org Reply-To: openstack-discuss(a)lists.openstack.org To: release-job-failures(a)lists.openstack.org Build failed. - openstack-upload-github-mirror https://zuul.opendev.org/t/openstack/build/bba91d0025a2496087a29803451a314f : SUCCESS in 45s - release-openstack-python https://zuul.opendev.org/t/openstack/build/a749eb25de1d426e845740cae1876afe : SUCCESS in 3m 50s - announce-release https://zuul.opendev.org/t/openstack/build/551dd5bd118347908b7113a5e2fa5c5e : SUCCESS in 5m 37s - propose-update-constraints https://zuul.opendev.org/t/openstack/build/e95a5bee9817491d84c89f89758872d6 : SUCCESS in 4m 18s - publish-monasca-agent-docker-images https://zuul.opendev.org/t/openstack/build/2ebcbfec634c4c068e9f7625473ea726 : POST_FAILURE in 7m 08s _______________________________________________ Release-job-failures mailing list Release-job-failures(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures

2 1

Z Release Naming ...
by Jay Bryant 26 Jan '22

26 Jan '22

All, As in the past, I would like the community's input on the 'Z' release name [1] . I have narrowed the list down to my top 4 choices. Please take a few minutes to vote. The poll closes around 14:30 UTC on 1/28/22. Thanks for your input! Jay (jungleboyj) [1] https://twitter.com/jungleboyj/status/1486344910693441541

1 0

[horizon] Cancelling Today's weekly meeting
by vishal manchanda 26 Jan '22

26 Jan '22

Hello Team, Since there are no agenda items [1] to discuss for today's horizon weekly meeting. Also, Today is a holiday for me. So let's cancel today's weekly meeting. The next weekly meeting will be on 2nd February. Thanks & Regards, Vishal Manchanda [1] https://etherpad.opendev.org/p/horizon-release-priorities

1 0

[TripleO] Proposing Juan Badia Payno for TripleO core reviewer.
by Carlos Camacho Gonzalez 26 Jan '22

26 Jan '22

Hi everyone! I'd like to propose Juan Badia Paino [1][2][3] as a core reviewer on the TripleO repositories that are or might be related to the backup and restore efforts (openstack/tripleo-ci, openstack/tripleo-ansible, openstack/python-tripleoclient, openstack/tripleo-quickstart-extras, openstack/tripleo-quickstart). Juan has been around since 2016 making useful contributions and code reviews to the community and I believe adding him to our core reviewer group will help us improve the review and coding speed for the backup and restore codebase. As usual, consider this email as an initial +1 from my side, I will keep an eye on this thread for a week, and based on your feedback and if there are no objections I will add him as a core reviewer in two weeks. [1]: https://review.opendev.org/q/owner:jbadiapa%2540redhat.com [2]: https://www.stackalytics.io/?project_type=all&metric=commits&user_id=jbadia… [3]: https://www.stackalytics.io/report/contribution?module=tripleo-group&projec… Cheers, Carlos.

9 9

Re: Re: [ops] [kolla] RabbitMQ High Availability
by Albert Braden 25 Jan '22

25 Jan '22

Replying from my home email because I've been asked to not email the list from my work email anymore, until I get permission from upper management. I'm not sure I follow. I was planning to add 2 lines to etc/kolla/config/global.conf: [oslo_messaging_rabbit] amqp_durable_queues = False Is that not sufficient? What is involved in configuring dedicated control exchanges for each service? What would that look like in the config? From: Herve Beraud <hberaud(a)redhat.com> Sent: Thursday, December 9, 2021 2:45 AM To: Bogdan Dobrelya <bdobreli(a)redhat.com> Cc: openstack-discuss(a)lists.openstack.org Subject: [EXTERNAL] Re: [ops] [kolla] RabbitMQ High Availability Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Le mer. 8 déc. 2021 à 11:48, Bogdan Dobrelya <bdobreli(a)redhat.com> a écrit : Please see inline >> I read this with great interest because we are seeing this issue. Questions: >> >> 1. We are running kola-ansible Train, and our RMQ version is 3.7.23. Should we be upgrading our Train clusters to use 3.8.x? >> 2. Document [2] recommends policy '^(?!(amq\.)|(.*_fanout_)|(reply_)).*'. I don't see this in our ansible playbooks, nor in any of the config files in the RMQ container. What would this look like in Ansible, and what should the resulting container config look like? >> 3. It appears that we are not setting "amqp_durable_queues = True". What does this setting look like in Ansible, and what file does it go into? > > Note that even having rabbit HA policies adjusted like that and its HA > replication factor [0] decreased (e.g. to a 2), there still might be > high churn caused by a large enough number of replicated durable RPC > topic queues. And that might cripple the cloud down with the incurred > I/O overhead because a durable queue requires all messages in it to be > persisted to a disk (for all the messaging cluster replicas) before they > are ack'ed by the broker. > > Given that said, Oslo messaging would likely require a more granular > control for topic exchanges and the durable queues flag - to tell it to > declare as durable only the most critical paths of a service. A single > config setting and a single control exchange per a service might be not > enough. Also note that therefore, amqp_durable_queue=True requires dedicated control exchanges configured for each service. Those that use 'openstack' as a default cannot turn the feature ON. Changing it to a service specific might also cause upgrade impact, as described in the topic [3]. The same is true for `amqp_auto_delete=True`. That requires dedicated control exchanges else it won't work if each service defines its own policy on a shared control exchange (e.g `openstack`) and if policies differ from each other. [3] https://review.opendev.org/q/topic:scope-config-opts > > There are also race conditions with durable queues enabled, like [1]. A > solution could be where each service declare its own dedicated control > exchange with its own configuration. > > Finally, openstack components should add perhaps a *.next CI job to test > it with durable queues, like [2] > > [0] https://www.rabbitmq.com/ha.html#replication-factor > > [1] > https://zuul.opendev.org/t/openstack/build/aa514dd788f34cc1be3800e6d7dba0e8… > > [2] https://review.opendev.org/c/openstack/nova/+/820523 > >> >> Does anyone have a sample set of RMQ config files that they can share? >> >> It looks like my Outlook has ruined the link; reposting: >> [2] https://wiki.openstack.org/wiki/Large_Scale_Configuration_Rabbit > > > -- > Best regards, > Bogdan Dobrelya, > Irc #bogdando -- Best regards, Bogdan Dobrelya, Irc #bogdando -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

6 16

Compute Node Not Getting PXE boot During Scale-In/Out Activity
by Pradeep Antil 25 Jan '22

25 Jan '22

Hello Folks, Hope you are doing well ! I have a compute node (SRIOV) in my RedHat Openstack 13 Lab. I have a task to remove the sriov compute and add it back as a dpdk compute node. After removing this node as scale-in activity via overcloud stack when I tried to add it again, introspection for this node is failing. After looking into the logs in undercloud , it appears like it is not getting the ip address from pxe. # cat /var/log/messages|grep -i "0c:42:a1:45:03:10" --color [image: image.png] [root@director ~]# tcpdump -n -i br-ctlplane -e | grep -i "0c:42:a1:45:03:10" --color tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on br-ctlplane, link-type EN10MB (Ethernet), capture size 262144 bytes 23:54:08.653057 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 436: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 394 23:54:12.669877 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 436: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 394 23:54:20.744605 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 436: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 394 23:54:36.839226 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 436: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 394 23:56:48.967623 0c:42:a1:45:03:10 > 33:33:00:00:00:16, ethertype IPv6 (0x86dd), length 90: :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 23:56:49.044752 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 300 23:56:49.269645 0c:42:a1:45:03:10 > 33:33:ff:45:03:10, ethertype IPv6 (0x86dd), length 86: :: > ff02::1:ff45:310: ICMP6, neighbor solicitation, who has fe80::e42:a1ff:fe45:310, length 32 23:56:49.781577 0c:42:a1:45:03:10 > 33:33:00:00:00:16, ethertype IPv6 (0x86dd), length 90: :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 23:56:50.271663 0c:42:a1:45:03:10 > 33:33:00:00:00:16, ethertype IPv6 (0x86dd), length 90: fe80::e42:a1ff:fe45:310 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 23:56:50.271922 0c:42:a1:45:03:10 > 33:33:00:00:00:02, ethertype IPv6 (0x86dd), length 70: fe80::e42:a1ff:fe45:310 > ff02::2: ICMP6, router solicitation, length 16 23:56:50.368576 0c:42:a1:45:03:10 > 33:33:00:00:00:16, ethertype IPv6 (0x86dd), length 90: fe80::e42:a1ff:fe45:310 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 23:56:54.274049 0c:42:a1:45:03:10 > 33:33:00:00:00:02, ethertype IPv6 (0x86dd), length 70: fe80::e42:a1ff:fe45:310 > ff02::2: ICMP6, router solicitation, length 16 23:56:54.675024 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 300 23:56:58.282332 0c:42:a1:45:03:10 > 33:33:00:00:00:02, ethertype IPv6 (0x86dd), length 70: fe80::e42:a1ff:fe45:310 > ff02::2: ICMP6, router solicitation, length 16 23:57:07.638252 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 300 23:57:10.053205 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 300 23:57:18.720085 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 300 23:57:32.817306 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 300 Physical connectivity of this node is intact. Any idea and suggestions ? how this issue can be fixed. -- Best Regards Pradeep Kumar

1 0

[neutron] Bug Deputy Report Jan 17 - 23
by Oleg Bondarev 25 Jan '22

25 Jan '22

Hi everyone, Please find Bug Deputy report for the week Jan 17 - 23rd below. 1 Critical bug (with a related logs-improving patch from Slawek) looks for volunteers. A couple of Medium bugs: an l3-bgp bug to be verified by bgp team - 1958627, and an ipv6+ovs firewall bug - 1958643. Also several OVN bug needs some triage from OVN folks + assignees. Details: Critical -------- - https://bugs.launchpad.net/neutron/+bug/1958363 - Notifications to nova disabled causing tests failures - Confirmed - Related patch: https://review.opendev.org/c/openstack/neutron/+/825513 - Unassigned! Medium ---------- - https://bugs.launchpad.net/neutron/+bug/1958627 - Incomplete ARP entries on L3 gw namespace - Opinion - Unassigned! - https://bugs.launchpad.net/neutron/+bug/1958149 - ha backup router ipv6 accept_ra broken - In progress: https://review.opendev.org/c/openstack/neutron/+/824947 - Assigned to Maximilian Stinsky - https://bugs.launchpad.net/neutron/+bug/1958364 - [ovn]Set NB/SB connection inactivity_probe does not work for cluster - In progress: https://review.opendev.org/c/openstack/neutron/+/825269 - Assigned to ZhouHeng - https://bugs.launchpad.net/neutron/+bug/1958225 - [ovn]chassis available zone changed, not reschedule router gateway_chassis - In progress: https://review.opendev.org/c/openstack/neutron/+/825073 - Assigned to ZhouHeng - https://bugs.launchpad.net/neutron/+bug/1958353 - [ovn]Gateway port is down after gateway chassis changed - In progress: https://review.opendev.org/c/openstack/neutron/+/825041 - Assigned to ZhouHeng - https://bugs.launchpad.net/neutron/+bug/1958501 - [ovn]Refusing to bind port to dead agent - In progress: https://review.opendev.org/c/openstack/neutron/+/825428 - Assigned to ZhouHeng - https://bugs.launchpad.net/neutron/+bug/1958643 - Unicast RA messages for a VM are filtered out by ovs rules - Confirmed - Unassigned! Low ----- - https://bugs.launchpad.net/neutron/+bug/1958513 - [test]The unit test file ovn_l3.test_plugin cannot be run alone - In progress: https://review.opendev.org/c/openstack/neutron/+/825478 - Assigned to ZhouHeng Undecided ------------- - https://bugs.launchpad.net/neutron/+bug/1958355 - Undecided - Unassigned! - https://bugs.launchpad.net/neutron/+bug/1958561 - [ovn-octavia-provider] Listner/Pool Stuck in PENDING_CREATE Using Fully Populated LB API - Undecided - Unassigned! - https://bugs.launchpad.net/neutron/+bug/1958593 - [ovn]neutron-server allow more efficient reconnections when connecting to clustered OVSDB servers - Undecided - Unassigned! Invalid -------- - https://bugs.launchpad.net/neutron/+bug/1958128 - Neutron l3 agent keeps restarting (Ubuntu) Expired --------- - https://bugs.launchpad.net/neutron/+bug/1939680 - Neutron - set "dns_domain" for existing network is passively failing when Designate DNS extension is not enabled for Neutron - Undecided - Unassigned Thanks, Oleg --- Advanced Software Technology Lab Huawei

1 0

[Oslo] First IRC meeting of the year.
by Daniel Mats Niklas Bengtsson 25 Jan '22

25 Jan '22

Hi there, Yesterday we had the first oslo IRC meeting. You can find the log[1] on the meeting. Sorry I forget the ping and I confused the hour, but I will do better job next time. [1] https://meetings.opendev.org/meetings/oslo/2022/

1 0

Openstack+Magnum for edge
by Vikarna Tathe 24 Jan '22

24 Jan '22

Hello All, Is there a solution available for OpenStack controllers at a central location and computes at the edge (far from central)? If not what's the alternative? Any help would be appreciated. Thanks, Vikarna

1 0

[openstack-helm] No meeting tomorrow
by Gage Hugo 24 Jan '22

24 Jan '22

Hey team, Since there's nothing on the agenda for tomorrow's meeting, it has been cancelled. We will meet again next week.

1 0

答复: [cyborg] Proposing core reviewers
by Brin Zhang(张百林) 24 Jan '22

24 Jan '22

> ��: Brin Zhang(�Ű��) > ��ʱ��: 2022��1��17�� 9:13 > �ռ��: 'openstack-discuss(a)lists.openstack.org' <openstack-discuss(a)lists.openstack.org> > ��: 'xin-ran.wang(a)intel.com' <xin-ran.wang(a)intel.com>; Alex Song (��ƽ) <songwenping(a)inspur.com>; 'huangzhipeng(a)huawei.com' <huangzhipeng(a)huawei.com>; 'liliueecg(a)gmail.com' <liliueecg(a)gmail.com>; 'shogo.saito.ac(a)hco.ntt.co.jp' <shogo.saito.ac(a)hco.ntt.co.jp>; 'sundar.nadathur(a)intel.com' <sundar.nadathur(a)intel.com>; 'yumeng_bao(a)yahoo.com' <yumeng_bao(a)yahoo.com>; 'chen.ke14(a)zte.com.cn' <chen.ke14(a)zte.com.cn>; '419546439(a)qq.com' <419546439(a)qq.com>; 'shaohe.feng(a)intel.com' <shaohe.feng(a)intel.com>; 'wangzhengh(a)chinatelecom.cn' <wangzhengh(a)chinatelecom.cn>; 'zhuli2317(a)gmail.com' <zhuli2317(a)gmail.com> >��: [cyborg] Proposing core reviewers > Hello all, > Eric xie has been actively contributing to Cyborg in various areas, adding new features, improving quality, reviewing patches. Despite the relatively short time, he has been one of the most prolific contributors, > and brings an enthusiastic and active mindset. I would like to thank and acknowledge him for his steady valuable contributions, and propose him as a core reviewer for Cyborg. fwiw, saw no negative votes, so added Eric to cyborg-core group. Welcome Eric on board and thanks for helping the community ! > Some of the currently listed core reviewers have not been participating for a lengthy period of time. It is proposed that those who have had no contributions for the past 18 months > �C i.e. no participation in meetings, no code contributions, not participating in Cyborg open source activities and no reviews �C be removed from the list of core reviewers. > -- The Cyborg team recognizes everyone's contributions, but we need to ensure the activity of the core-reviewer list. If you are interested in rejoining the cyborg team, feel free to ping us to restore the core reviewer for you. > If no objections are made known by January 24, I will make the changes proposed above.. > Regards, > Brin Zhang

1 0

[PTG] April 2022 Virtual PTG Dates & Registration
by Kendall Nelson 24 Jan '22

24 Jan '22

Hello Everyone! We're happy to announce the next virtual PTG[1] will take place April 4-8, 2022! Registration is now open[2]. The virtual PTG is free to attend, but make sure to register so you receive important communications like schedules, passwords, and other relevant updates. Next week, keep an eye out for info regarding team sign-ups. Can't wait to see you all there! -Kendall (diablo_rojo) [1] https://www.openstack.org/ptg/ [2] https://openinfra-ptg.eventbrite.com/

1 0

[sdk] R1 branch merged into master
by Artem Goncharov 24 Jan '22

24 Jan '22

Hi everybody, Just wanted to give a hint that feature/r1 branch of the OpenStackSDK is now merged into the master. While most of the challenging things are now completed the work is not finished yet, but will soon be. Most important: most of the work is backward compatible, but few things were not. I took care on keeping things working and testing, but there might be side effects that I have not expected. Please let me know if jobs in your projects start failing. Regards, Artem

2 2

[ops][nova][victoria] Power State = Suspended?
by DHilsbos＠performair.com 24 Jan '22

24 Jan '22

All; I had something unusual happen this morning; one of my VMs was showing "Suspended" under the Power State in the Horizon dashboard. I've never seen that. What does it mean? Any search that I do points me to a bunch of resources for Status Suspended. Thank you, Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

4 8

[TripleO] Horizon login failed with Something went wrong error in IPv6
by Anirudh Gupta 23 Jan '22

23 Jan '22

Hi Team, We are trying to deploy the Tripleo Train with IPv6. All the overcloud control plane networks - internal, management etc are also on the IPv6 subnet. Upon successful completion of overcloud, when I am trying to open the page, it does open. But when I enter the correct login credentials, it says something went wrong. [image: image.png] Upon looking into error logs, I found 2022-01-21 12:33:34.825 324 WARNING keystone.server.flask.application [req-0660e62c-dff7-4609-89fe-225e177a84f8 f908417368a24cc685818bb5fc54fe12 - - default -] *Authorization failed. The request you have made requires authentication. from fd00:fd00:fd00:2000::359: keystone.exception.Unauthorized: The request you have made requires authentication.* where *fd00:fd00:fd00:2000::359 is my internal IP address which is reachable.* Regards Anirudh Gupta

3 2

[xena][nova] Libvirt Live Migration Lock
by Ammad Syed 23 Jan '22

23 Jan '22

Hi, I have a weird error while performing live migration of trove instances. The instance has a root disk residing on a local compute node and a second a second disk is attached from shared storage via cinder. There are two networks attached with the instance, one is vlan backed and other one is geneve. When I try to perform its live migration, it fails. I see below errors in libvirt logs and the same in nova-compute logs. Jan 19 15:56:54 host03.cloud.com libvirtd[731030]: Cannot start job (query, none, none) for domain instance-00000819; current job is (none, none, migration in) owned by (0 <null>, 0 <null>, 0 remoteDispatchDomainMigratePrepare3Params (flags=0x9b)) for (0s, 0s, 61s) Jan 19 15:56:54 host03.cloud.com libvirtd[731030]: Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainMigratePrepare3Params) Jan 19 15:36:30 host03.cloud.com libvirtd[731030]: migration successfully aborted Any advise how to fix it ? I am using below libvirt version. libvirt 6.0 qemu-kvm 4.2 kernel 5.4 nova 24.0 Ammad

1 1

[neutron] Welcome Oleg Bondarev in the drivers team
by Lajos Katona 23 Jan '22

23 Jan '22

Hi, Oleg is one of the most active and experienced developers around Neutron, and long served to be a member of the Drivers team (see: [0]). We all agreed that Oleg deserves to be part of the team and he will be a great member (see [1]), so I just added him to the neutron-drivers group. Welcome to the team Oleg! [0]: https://review.opendev.org/admin/groups/5b063c96511f090638652067cf0939da1cb… [1]: http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026690.… Lajos Katona (lajoskatona)

3 2

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

21 Jan '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week meeting yesterday. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-01-20-15.00.log.html * Next week's meeting is on 27th Jan Thursday 15:00 UTC, feel free add the topic on the agenda[1] by 26th Jan. 2. What we completed this week: ========================= * [masakari] Transfer PTL role to suzhengwei[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 ----------------- * 4 open reviews for ongoing activities[4]. Z release cycle name ------------------------- Z release cycle naming process schedule is merged[5]. Follow the ML thread for updates[6]. Z release cycle Technical Election --------------------------------------- Its time for Z release Technical Election, I have proposed the election dates (combined PTL + TC) [7], please review and add your feedback. Remove the tags framework --------------------------------- yoctozepto has proposed the WIP patch to remove the tag framework, feel free to review and provide early feedback[8]. OpenStack Pain points discussion ---------------------------------------- No updates in this week. Stay tuned on the ML thread[9] and Rico will inform you about the next meeting details. TC position on release cadence ------------------------------------- No updates on this. Discussion is in-progress in ML thread[10]. No other updates from TC on this and we will set up a separate call to continue the discussion. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[11]. Adjutant need maintainers and PTLs ------------------------------------------- We are still waiting to hear from Braden, Albert on permission to work on this project[12], we discussed it in this week TC meeting and there is blocker for Yoga release. We will leave this item from monitoring now and check the situation at the time of Z release election. I hope till that time, we will have more maintainer/leaders to lead this project. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [13] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[14]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [15] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. Welcome back from the holidays and stay safe! [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/824509 [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/+/824201 [6] http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026810.… [7] https://review.opendev.org/c/openstack/election/+/825017 [8] https://review.opendev.org/c/openstack/governance/+/822900 [9] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245… [10] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684… [11] https://etherpad.opendev.org/p/zuul-config-error-openstack [12] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [13] https://review.opendev.org/c/openstack/governance/+/798540 [14] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [15] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[all] Nomination open for OpenStack "Z" Release Naming
by Ghanshyam Mann 21 Jan '22

21 Jan '22

Hello Everyone, We are now starting the process for the OpenStack 'Z' release name. We are a little late to start it, sorry for that. I have proposed to close the nomination on 24th Jan[1]. I am hoping that is enough time to collect the names, If not please reply to this thread or in gerrit review[1]. Once the governance patch is merged I will update the final dates of nomination close and polls here, meanwhile in parallel please start proposing the name on the wiki page. Criteria: ====== - Refer to the below governance page for the naming criteria: https://governance.openstack.org/tc/reference/release-naming.html#release-n… - Any community members can propose the name to the below wiki page: https://wiki.openstack.org/wiki/Release_Naming/Z_Proposals We encourage all community members to participate in this process. [1] https://review.opendev.org/c/openstack/governance/+/824201 -gmann

1 2

Bug Fix - openstack-archive/syntribos
by Abdullah Zaman Babar 21 Jan '22

21 Jan '22

Dear Sir/Madam, I hope this email finds you well. Recently I was working with syntribos and I found a bug in the code which I wanted to report but the repository is archived and I'm unable to generate a pull request. Could you please guide me to contribute to the repository? It will be my first ever contribution to open-source. Regards Abdullah Zaman Babar

3 2

[gate][nova][qa] tempest-*-centos-8-stream job failing consistently since yesterday
by Ghanshyam Mann 21 Jan '22

21 Jan '22

Hello Everyone, You might have noticed that 'tempest-integrated-compute-centos-8-stream' and 'tempest tempest-full-py3-centos-8-stream' job started failing the below two tests consistently since yesterday (~7 PM CST) - https://169dddc67bd535a0361f-0632fd6194b48b475d9eb0d8f7720c6c.ssl.cf2.rackc… I have filed the bug and to unblock the gate (nova & tempest), I have pushed patch to make these job non voting until bug is fixed. - https://review.opendev.org/c/openstack/tempest/+/824740 Please hold the recheck on nova or tempest (or any other effected project). ralonsoh mentioned that this is not the same issue which is raised in - http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026682.… or may be triggered due to same root cause? -gmann

4 6

[magnum][tc] Proposing Jake Yip for core-reviewer
by Spyros Trigazis 21 Jan '22

21 Jan '22

Dear all, I would like to nominate Jake Yip for core reviewer in the magnum project. Jake has been doing code reviews for the past years in magnum at a steady rate and is running magnum as well in their organization. With very good knowledge of the magnum codebase, I am confident that Jake will help increase the pace of development in the project. Cheers, Spyros

4 3

[outreachy] Stepping down as Outreachy co-organizer
by Samuel de Medeiros Queiroz 21 Jan '22

21 Jan '22

Hi all, Outreachy is a wonderful program that promotes diversity in open source communities by giving opportunities to people in underrepresented groups. This was a hard decision to make, but I have not been committing the time this project deserves. For that reason, I would like to give visibility that I am stepping down as an Outreachy organizer. It was a great honor to serve as co-organizer since late 2018, and we had 19 internships since then. I also had the pleasure to serve twice (2016 and 2017) as a mentor. Mahati, it was a great pleasure co-organizing Outreachy in this community with you. Thanks! Samuel Queiroz

5 4

[Infra]CentOS Stream 8 based jobs are hitting RETRY or RETRY_LIMIT
by Chandan Kumar 20 Jan '22

20 Jan '22

Hello, Currently CentOS Stream 8 based jobs are hitting RETRY or RETRY_LIMIT. https://zuul.opendev.org/t/openstack/builds?result=RETRY&result=RETRY_LIMIT… Based on the logs, all are hitting with : ``` rrors during downloading metadata for repository 'appstream': 2022-01-20 09:34:18.119377 | primary | - Status code: 404 for https://mirror-int.iad.rax.opendev.org/centos/8-stream/AppStream/x86_64/os/… (IP: 10.208.224.52) 2022-01-20 09:34:18.119443 | primary | - Status code: 404 for https://mirror-int.iad.rax.opendev.org/centos/8-stream/AppStream/x86_64/os/… (IP: 10.208.224.52) ``` While taking a look at https://opendev.org/opendev/system-config/src/branch/master/playbooks/roles… ``` 404 for http://mirror.dal10.us.leaseweb.net/centos/8-stream/AppStream/x86_64/os/re podata/09255ba7c10e01afeb0d343667190f9c3e42d0a6099f887619abcb92ea0378db-filelists.xml.gz (IP: 209.58.153.1) ``` It seems the centos mirror have issues. https://review.opendev.org/c/opendev/system-config/+/825446 make the switch to facebook mirror. It might fix the issue. Thanks Alfredo for debugging it. Thanks, Chandan Kumar

2 3

[all][infra][kayobe][kolla] ping not permitted on latest centos-8-stream images
by Pierre Riteau 20 Jan '22

20 Jan '22

Hello, Late yesterday, I noticed many Kayobe CI jobs started failing with "ping: socket: Operation not permitted". I investigated the issue with clarkb on #openstack-infra, with help from #centos-devel as well (on Libera). This happens on the latest CentOS Stream 8 images and is caused by iputils 20180629-8.el8 removing capabilities on the ping binary [1]. This should have been shipped with a sysctl configuration allowing any group to access unprivileged ICMP echo sockets [2], but this is not in the systemd package yet. As a result, using ping without root privileges fails. TripleO is also impacted. They have fixed it in their CI jobs [3]. It is possible other projects are affected. There are multiple places within Kayobe and Kolla where we would need to set this sysctl to fix our CI, including backports to all supported branches. I was wondering if infra could instead customise their stream image or apply the sysctl in one of the common roles from zuul/zuul-jobs that are run at the beginning of each job? Many thanks. Best wishes, Pierre Riteau (priteau) [1] https://git.centos.org/rpms/iputils/c/efa64b5e05ccb2c1332304ad493acc874b61e… [2] https://github.com/redhat-plumbers/systemd-rhel8/pull/246 [3] https://review.opendev.org/c/openstack/tripleo-ci/+/824635

4 8

[Diversity] Diversity and Inclusion WG new meeting time
by Amy Marrich 20 Jan '22

20 Jan '22

Thank you to those who responded to the Doodle for our meeting time. The day and time selected was Friday at 15:00 UTC so we will move to that in February with our first meeting being on 2/4. As usual, should we need to cancel the first Friday of the month we have the backup date of the third week. Should we end up having to do that too frequently ,as Fridays are popular for holidays and vacations, we'll readdress the meeting time again. Also chosen was to switch to a video platform and we will work on choosing one before the meeting reminder goes out Thanks, Amy (spotz)

1 0

[neutron] Drivers meeting - Friday 21.01.2022 - cancelled
by Lajos Katona 20 Jan '22

20 Jan '22

Hi Neutron Drivers! Due to the lack of agenda, let's cancel tomorrow's drivers meeting. See You on the meeting next week. [0]: https://meetings.opendev.org/meetings/neutron_drivers/2021/neutron_drivers.…

1 0

Tesla V100 32G GPU with openstack
by Satish Patel 20 Jan '22

20 Jan '22

Folk, We have Tesla V100 32G GPU and I’m trying to configure with openstack wallaby. This is first time dealing with GPU so I have couple of question. 1. What is the difference between passthrough vs vGPU? I did google but not very clear yet. 2. If I configure it passthrough then does it only work with single VM ? ( I meant whole GPU will get allocate to single VM correct? 3. Also some document saying Tesla v100 support vGPU but some folks saying you need license. I have no idea where to get that license. What is the deal here? 3. What are the config difference between configure this card with passthrough vs vGPU? Currently I configure it with passthrough based one one article and I am able to spun up with and I can see nvidia card exposed to vm. (I used iommu and vfio based driver) so if this card support vGPU then do I need iommu and vfio or some other driver to make it virtualize ? Sent from my iPhone

4 11

[nova] [placement] Proposing Sean Mooney as nova-core
by Sylvain Bauza 20 Jan '22

20 Jan '22

Hi all, I would like to propose Sean as an addition to the nova-core team (which includes placement merge rights as nova-core is implicitly a subgroup). As we know, he's around for a long time, is already a nova-specs-core and has proven solid experience in reviews. Cores, please vote (-1, 0, +1) before next Wednesday Jan 19th 1600UTC. Cheers, -Sylvain

6 6

Cannot ssh/ping instance
by Celinio Fernandes 20 Jan '22

20 Jan '22

Hi, I am running Ubuntu Server 20.04 LTS on Virtualbox. I installed OpenStack (Xena release) through Devstack. Here is the content of my /opt/stack/devstack/local.conf file : [[local|localrc]] ADMIN_PASSWORD=secret DATABASE_PASSWORD=$ADMIN_PASSWORD RABBIT_PASSWORD=$ADMIN_PASSWORD SERVICE_PASSWORD=$ADMIN_PASSWORD HOST_IP=10.0.2.15 I created an instance through Horizon. The security group contains the 2 rules needed (one to be able to ping and one to be able to ssh the instance). I also allocated and associated a floating IP address. And a ssh key pair. Here is the configuration : openstack server list ---------------------------------+--------------------------+---------+ | ID | Name | Status | Networks | Image | Flavor | ---------------------------------+--------------------------+---------+ | f5f0fdd5-298b-4fa3-9ee9-e6e4288f4327 | InstanceJanvier | ACTIVE | shared=172.24.4.133, 192.168.233.165 | cirros-0.5.2-x86_64-disk | m1.nano | ------------------------------------------------------+ openstack network list : ------------------------------------------------------+ | ID | Name | Subnets | ------------------------------------------------------+ | 96a04799-7fc7-4525-b05c-ad57261aed38 | public | 07ce42db-6f3f-4135-ace7-2fc104ea62a0, 6dba13fc-b10c-48b1-b1b4-e1f1afe25b53 | | c42638dc-fa56-4644-ad34-295fce4811d2 | shared | a4e2d8cc-02b2-42e2-a525-e0eebbb08980 | | ffb8a527-266e-4e96-ad60-f7e9aba8f0c1 | private | 42e36677-cf3c-4df4-88a1-8cf79b9d6060, e507e6dd-132a-4249-96b1-83761562dd73 | ------------------------------------------------------+ openstack router list : +--------------------------------------+----------------+--------+------ | ID | Name | Status | State | Project | +--------------------------------------+----------------+--------+------ | b9a15051-a532-4c93-95ad-53c057720c62 | Virtual_router | ACTIVE | UP | 6556c02dd88f4c45b535c2dbb8ba1a04 | +--------------------------------------+----------------+--------+------ I cannot ping/ssh neither the fixed IP address or the floating IP address : ping -c 3 172.24.4.133 PING 172.24.4.133 (172.24.4.133) 56(84) bytes of data. --- 172.24.4.133 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2035ms ping -c 3 192.168.233.165 PING 192.168.233.165 (192.168.233.165) 56(84) bytes of data. --- 192.168.233.165 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2035ms Maybe that has something to do with the network namespaces configuration on Ubuntu. Does anyone know what could go wrong or what is missing ? Thanks for helping.

2 6

[cinder] review priorities for the next 2 days
by Brian Rosmaita 20 Jan '22

20 Jan '22

Not surprisingly, the review priority for the next 2 days is to review new driver patches. The merge deadline is tomorrow (21 January) at 20:00 UTC. To be more specific: We have 2 new drivers that depend on the following patches that generalize the hitachi driver: - https://review.opendev.org/c/openstack/cinder/+/786873 - https://review.opendev.org/c/openstack/cinder/+/815461 Then there are the 2 drivers that depend on the above; they are small patches and each of their third-party CIs is running: - https://review.opendev.org/c/openstack/cinder/+/815582 - https://review.opendev.org/c/openstack/cinder/+/815614 So those should be fairly quick reviews. The teams have been quick to respond to comments. There is also the Lightbits driver; it has both cinder and os-brick patches: - https://review.opendev.org/c/openstack/cinder/+/821602 - https://review.opendev.org/c/openstack/os-brick/+/821603 Their third-party CI is running and they have been very responsive to reviews. So really, only 3 new drivers to review! Other drivers: - TOYOU NetStor - merged! \o/ - Pure NVMe-RoCE - vendor is now aiming to merge in Z - Dell EMC PowerStore NFS - vendor is now aiming to merge in Z - YADRO Tatlin - initial commit posted today; has not yet passed Zuul. (Look at it if you have spare time, but please prioritize the patches listed above.)

1 0

[nova][libvirt] Secure boot with SMM support
by Imran Hussain 20 Jan '22

20 Jan '22

Hi, I posted yesterday about my issue http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026796.… but having looked in to it I think it's a Nova problem and should be solved by Nova Compute. I've pushed up a quick patch I wrote https://review.opendev.org/c/openstack/nova/+/825496 that's running on my systems. Thoughts? Thanks, Imran

1 0

[charms] Welcome Hemanth Nakkina to the charms core
by Alex Kavanagh 20 Jan '22

20 Jan '22

Hello Just a quick note to let you know that Hemanth has joined the core charms team, so a huge welcome to him! Thanks for joining the team. Hemanth has been a trusted and helpful reviewer and contributor to the charms, and received many +1s and comments on his proposal. All the best Alex. -- Alex Kavanagh - Software Engineer OpenStack Engineering - Data Centre Development - Canonical Ltd

1 0

[cyborg] Proposing core reviewers
by Brin Zhang(张百林) 19 Jan '22

19 Jan '22

Hello all, Eric xie has been actively contributing to Cyborg in various areas, adding new features, improving quality, reviewing patches. Despite the relatively short time, he has been one of the most prolific contributors, and brings an enthusiastic and active mindset. I would like to thank and acknowledge him for his steady valuable contributions, and propose him as a core reviewer for Cyborg. Some of the currently listed core reviewers have not been participating for a lengthy period of time. It is proposed that those who have had no contributions for the past 18 months �C i.e. no participation in meetings, no code contributions, not participating in Cyborg open source activities and no reviews �C be removed from the list of core reviewers. -- The Cyborg team recognizes everyone's contributions, but we need to ensure the activity of the core-reviewer list. If you are interested in rejoining the cyborg team, feel free to ping us to restore the core reviewer for you. If no objections are made known by January 24, I will make the changes proposed above.. Regards, Brin Zhang

4 4

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

19 Jan '22

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

1 1

[Neutron][drivers] Proposing Oleg Bondarev (obondarev) to the Drivers team
by Lajos Katona 19 Jan '22

19 Jan '22

Hi Neutron Drivers, I would like to propose Oleg Bondarev to be a member of the Neutron Drivers team. He has long experience with Neutron, he has been always around to help with advice and reviews, and enthusiastically participated in the Drivers meeting (big +1 as it is on Friday 1400UTC, quite late afternoon in his timezone :-)). Neutron drivers, please vote before the next Drivers meeting (next Friday, 21. January). Best Regards Lajos Katona (lajoskatona)

7 6

[kolla-anbsible][centos-stream][novnc]
by Franck VEDEL 19 Jan '22

19 Jan '22

Hello, what is the solution to adjust the size of novnc consoles. I found for ubuntu (https://docs.openstack.org/nova/rocky/admin/remote-console-access.html) but not for centos-stream which I use with kolla-ansible. thanks in advance Franck

1 0

[cinder] yoga R-9 virtual midcycle on 26 January
by Brian Rosmaita 19 Jan '22

19 Jan '22

As decided at today's weekly meeting, the Cinder Yoga R-9 virtual midcycle will be held: DATE: Wednesday 26 January 2022 TIME: 1400-1600 UTC LOCATION: https://bluejeans.com/3228528973 The meeting will be recorded. Please add topics to the midcycle etherpad: https://etherpad.opendev.org/p/cinder-yoga-midcycles cheers, brian

1 0

[kolla] Calling Kolla-ansible in an ansible playbook
by J-P Methot 19 Jan '22

19 Jan '22

Hi, I've been trying to write an ansible-playbook to run some kolla tasks and I've been wondering if this is even possible? I have kolla running inside a virtual environment, so of course I'm running into issues having ansible running it. The current task looks like this: - name: run kolla-ansible upgrade on controllers command: "{{ venv }}/bin/kolla-ansible --limit {{ item }} -i multinode upgrade" loop: - control - monitoring - storage When run, it's complaining that ansible isn't installed in the current virtual environment. I was under the impression that specifying the whole path to my executable would have it automatically run in that virtual environment, but visibly this excludes access to ansible that's installed there. So, basically, is what I'm trying to do even possible? And if so, what would be the best way to do it? -- Jean-Philippe Méthot Senior Openstack system administrator Administrateur système Openstack sénior PlanetHoster inc.

2 2

[cinder] festival of XS reviews 21 January 2022
by Brian Rosmaita 19 Jan '22

19 Jan '22

Hello Argonauts, This is a reminder that the most recent edition of the Cinder Festival of XS Reviews will be held at the end of this week on Friday 21 January. who: Everyone! what: The Cinder Festival of XS Reviews when: Friday 21 January 2022 from 1400-1600 UTC where: https://meetpad.opendev.org/cinder-festival-of-reviews etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews This recurring meeting can be placed on your calendar by using this handy ICS file: http://eavesdrop.openstack.org/calendars/cinder-festival-of-reviews.ics See you there! brian

1 0

OpenInfra Summit Berlin 2022 Programming Committee Nominations Now Open
by Erin Disney 19 Jan '22

19 Jan '22

Hey everyone- Programming Committee nominations <https://openinfrafoundation.formstack.com/forms/programmingcommittee2022> for the 2022 OpenInfra Summit in Berlin (June 7-9, 2022) are now open! Programming Committees for each Track will help build the Summit schedule, and are made up of individuals working in open infrastructure. Responsibilities include: Help the Summit team put together the best possible content based on your subject matter expertise Promote the individual Tracks within your networks Review the submissions and Community voting results in your particular Track Determine if there are any major content gaps in your Track, and if so, potentially solicit additional speakers directly to submit Ensure diversity of speakers and companies represented in your Track Avoid vendor sales pitches, focusing more on real-world user stories and technical, in-the-trenches experiences Identify which submissions would make good content for OpenInfra Live, the virtual show hosted by the OpenInfra Foundation that encourages live questions from a global audience 2022 Summit Tracks: 5G, NFV & Edge AI, Machine Learning & HPC CI/CD Container Infrastructure Getting Started Hands-on Workshops NEW: Hardware Enablement Open Development Private & Hybrid Cloud Public Cloud Security Full track descriptions are available here <https://etherpad.opendev.org/p/r.86088dcd62bc50a6381c19f7f26995b6>. If you’re interested in nominating yourself or someone else to be a member of the Summit Programming Committee for a specific Track, please fill out the nomination form <https://openinfrafoundation.formstack.com/forms/programmingcommittee2022>. Nominations will close on January 19, 2022. Programming Committee selections will occur before we close the Call for Presentations (CFP) so that the Committees can host office hours to consult on submissions, and help promote the event. CFP will be opening in January, registration <https://www.eventbrite.com/e/openinfra-summit-berlin-2022-tickets-211374997…> and sponsorship <https://openinfra.dev/summit/> information are already available. Please email speakersupport(a)openinfra.dev with any questions or feedback. Cheers, Erin Disney Event Marketing Open Infrastructure Foundation

1 1