January 2022 - openstack-discuss - lists.openstack.org

[nova][powervm][zvm] Time to mark powervm and zvm drivers as deprecated for removal?
by Stephen Finucane 28 Jan '22

28 Jan '22

I've had a PR open against the pypowervm library for over a fortnight now [1] with no activity. This has prompted me to go looking into the state of the powervm driver and what I've found isn't great. It doesn't seem there has been any feature development on the driver for many years, and the last change I can see that wasn't simply of a case of "I need to do this to get tests to pass" was over three years ago [2]. The CI also doesn't appear to have been touched in years. The situation for zvm isn't any better. The last functional change to that driver was nearly 2 years ago and I wasn't able to spot any CI running (though it's possible I just missed this). This means the powervm and zvm drivers stand out from the other non-libvirt drivers in-tree, each of which are getting at least some activity (albeit out- of-tree for Hyper-V, from what I recall). It also begs the question: are these drivers something we want to keep around? If we do, how are we going to maintain them long term? If not, how aggressive should we be in removing that now dead code? I'll open patches to mark both powervm and zvm as deprecated shortly so that, assuming nothing changes in the interim, we can look to remove it early in the Z cycle. Please respond here or on the reviews if you have concerns. Stephen [1] https://github.com/powervm/pypowervm/pull/17 [2] Change ID I89ad36f19672368a1f795e1f29c5af6368ccfeec

1 1

[cyborg] cancel weekly meeting in on February 4, 2022
by Brin Zhang(张百林) 28 Jan '22

28 Jan '22

Hi all, February 1~ February 6, 2022 are the Spring Festival of China, so we will cancel next weekly meeting, if you have some questions you can ping us by email. best regard brinzhang

1 0

[neutron] Drivers meeting agenda - 28.01.2022
by Lajos Katona 27 Jan '22

27 Jan '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. There is no RFE proposed this week, but I would like to discuss again how to handle neutron-fwaas. To simplify things TC asked to keep neutron-fwaas under openstack/ namespace, see the discussion on #openstack-tc: https://meetings.opendev.org/irclogs/%23openstack-tc/%23openstack-tc.2022-0… [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[rbac][keystone][kolla][osa][tripleo][charms] RBAC in Yoga for deployment projects
by Mark Goddard 27 Jan '22

27 Jan '22

Hi, If you haven't been paying close attention, it would be easy to miss some of the upcoming RBAC changes which will have an impact on deployment projects. I thought I'd start a thread so that we can share how we are approaching this, get answers to open questions, and ideally all end up with a fairly consistent approach. The secure RBAC work has a long history, and continues to evolve. According to [1], we should start to see some fairly substantial changes over the next few releases. That spec is fairly long, but worth a read. In the yoga timeline [2], there is one change in particular that has an impact on deployment projects, "3. Keystone enforces scope by default". After this change, all of the deprecated policies that many still rely on in Keystone will be removed. In kolla-ansible, we have an etherpad [5] with some notes, questions and half-baked plans. We made some changes in Xena [3] to use system scope in some places when interacting with system APIs in Ansible tasks. The next change we have staged is to add the service role to all service users [4], in preparation for [2]. Question: should the role be added with system scope or in the existing service project? The obvious main use for this is token validation, which seems to allow system or project scope. We anticipate that some service users may still require some project-scoped roles, e.g. when creating resources for octavia. We'll deal with those on a case by case basis. In anticipation of keystone setting enforce_scope=True and removing old default policies (which I assume effectively removes enforce_new_defaults?), we will set this in kolla-ansible, and try to deal with any fallout. Hopefully the previous work will make this minimal. How does that line up with other projects' approaches? What have we missed? Mark [1] https://opendev.org/openstack/governance/src/branch/master/goals/selected/c… [2] https://opendev.org/openstack/governance/src/branch/master/goals/selected/c… [3] https://opendev.org/openstack/kolla-ansible/commit/2e933dceb591c3505f35c2c1… [4] https://review.opendev.org/c/openstack/kolla-ansible/+/815577 [5] https://etherpad.opendev.org/p/enabling-system-scope-in-kolla-ansible

6 23

[manila][cinder][glance][nova] Pop-up team for design and development of a Cephadm DevStack plugin
by Victoria Martínez de la Cruz 27 Jan '22

27 Jan '22

Hi all, I'm reaching out to you to let you know that we will start the design and development of a Cephadm DevStack plugin. Some of the reasons on why we want to take this approach: - devstack-plugin-ceph worked for us for a lot of years, but the development of it relies on several hacks to adapt to the different Ceph versions we use and the different distros we support. This led to a monolithic script that sometimes is hard to debug and break our development environments and our CI - cephadm is the deployment tool developed and maintained by the Ceph community, it allows their users to get specific Ceph versions very easily and enforces good practices for Ceph clusters. From their docs, "Cephadm manages the full lifecycle of a Ceph cluster. It starts by bootstrapping a tiny Ceph cluster on a single node (one monitor and one manager) and then uses the orchestration interface (“day 2” commands) to expand the cluster to include all hosts and to provision all Ceph daemons and services. [0]" - OpenStack deployment tools are starting to use cephadm as their way to deploy Ceph, so it would be nice to include cephadm in our development process to be closer with what is being done in the field I started the development of this in [1], but it might be better to change devstack-plugin-ceph to do this instead of having a new plugin. This is something I would love to discuss in a first meeting. Having said this, I propose using the channel #openstack-cephadm in the OFTC network to talk about this and set up a first meeting with people interested in contributing to this effort. Thanks, Victoria [0] https://docs.ceph.com/en/pacific/cephadm/ [1] https://github.com/vkmc/devstack-plugin-cephadm

5 6

[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 27 Jan '22

27 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