March 2022 - openstack-discuss - lists.openstack.org

[puppet] Proposing Alan Bishop (abishop) for puppet-manila core
by Takashi Kajinami 18 Mar '22

18 Mar '22

Hi Team, Alan is currently a partial core reviewer in Puppet OpenStack and covers puppet-cinder and puppet-glance. He has made great reviews in these two modules since he joined the team, but in addition, he has been reviewing patches for puppet-manila and providing good feedback for the past two cycle. https://www.stackalytics.io/?user_id=alan-bishop Based on that fact, I'd like to propose extending his coverage and adding Alan to the puppet-manila core reviewers. If you have any feedback please share it in this thread. I'll add him to the group if we don't hear any objections for 1 week. I'd like to take this moment to thank Alan for his great work and help in this project ! Thank you, Takashi KAJINAMI

3 3

Re: L3 agent issues
by Slawek Kaplonski 18 Mar '22

18 Mar '22

Hi, On piątek, 18 marca 2022 09:22:03 CET Wada Akor wrote: > Thanks Slawek > I just had feeling it is a bug or something has to with my hardware HP > proliant gen 7 might affect the performance of the L3 Agent. Bug where? In Neutron? I don't think so as Neutron is not deployment tool. I don't know exactly what tool are You using to deploy OpenStack but if there is any bug, You should look there. > > > On Fri, Mar 18, 2022 at 7:57 AM Slawek Kaplonski <skaplons(a)redhat.com> > wrote: > > > Hi, > > > > On czwartek, 17 marca 2022 22:19:22 CET Wada Akor wrote: > > > > > Good to all the openstack community, > > > > > Base on the above subject i was deploying openstack for a proof of > > concept > > > > > (POC) at the university of Jos ,Plateau State Nigeria . > > > > > > > > > > after deploying the neutron on the controller and compute node > > > > > then I ran the command # *openstack network agent list* > > > > > command output # is only 3 agent on the list as follow linuxbridge agent > > > > > ,metadata agent ,DHCP agent no l3 agent on the list > > > > > > > > > > 2) No log file for l3 agent at */var/log/neutron/**neuton*- linuxbridge > > > > > agent ,metadata agent ,DHCP agent on log no l3 agent . > > > > > > > > > > My deployment hardware is HP gen 7 for the POC > > > > > > > > > > please i need the community support > > > > > > > > > > thanks > > > > > > > > > > Wada k Jeremiah > > > > > > > > > L3 agent isn't something what is deployed automatically. You can deploy it > > on any node - sometimes You may want dedicated networking node with L3 > > agent for example. > > > > Please check our documentation [1] for more details. > > > > [1] https://docs.openstack.org/neutron/latest/install/index.html > > > > -- > > > > Slawek Kaplonski > > > > Principal Software Engineer > > > > Red Hat > > > -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

L3 agent issues
by Wada Akor 17 Mar '22

17 Mar '22

Good to all the openstack community, Base on the above subject i was deploying openstack for a proof of concept (POC) at the university of Jos ,Plateau State Nigeria . after deploying the neutron on the controller and compute node then I ran the command # *openstack network agent list* command output # is only 3 agent on the list as follow linuxbridge agent ,metadata agent ,DHCP agent no l3 agent on the list 2) No log file for l3 agent at */var/log/neutron/**neuton*- linuxbridge agent ,metadata agent ,DHCP agent on log no l3 agent . My deployment hardware is HP gen 7 for the POC please i need the community support thanks Wada k Jeremiah

3 2

are Gpu's needed to get fast openstack instances with GUI
by A Monster 17 Mar '22

17 Mar '22

I've deployed an openstack cloud using kolla-ansible, but the vm instances which has gui are very slow, do I need GPUs in order to get fast instances ?

2 1

[neutron] Drivers meeting agenda - 18.03.2022.
by Lajos Katona 17 Mar '22

17 Mar '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. * Recheck 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 * [QoS][OvS] implement QoS bandwidth limitation by leveraging ovs meter (#link https://bugs.launchpad.net/neutron/+bug/1964342 ) * DHCP agent scheduler filtering ignored when agent service restarted (#link https://bugs.launchpad.net/neutron/+bug/1964765 ) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[blazar][release][requirements] blazar-nova and nova requirements
by Pierre Riteau 17 Mar '22

17 Mar '22

Hello release team, blazar-nova is a package including a nova scheduler filter, which must be installed together with nova to be used. The blazar-nova deliverable for Yoga was tagged with 2.4.0 at the time of the final release for non-client libraries. A few days ago, stable/yoga patches were automatically proposed. This is when I discovered that the lower-constraints job was broken because nova bumped some requirements / lower-constraints after we released [1] [2]. Because blazar-nova and nova are installed together, we keep our requirements in sync for testing purposes. Now, I believe it is just the lower-constraints testing that is broken, since nova requirements are still compatible with what blazar-nova requires: nova just requires more recent versions of some packages. I can run "pip install blazar-nova git+ https://opendev.org/openstack/nova.git@master#egg=nova" fine. I fixed the issue on the blazar-nova master branch [3] and proposed a backport to stable/yoga [4], but realised this was probably breaking release policy. Should we leave stable/yoga as released and just drop the lower-constraints job? As an aside, would it be possible to requalify blazar-nova as a cycle-with-rc deliverable for the next release? It is typed as a library but nothing depends on it: if anything, it depends on nova itself. Thanks, Pierre Riteau (priteau) [1] https://review.opendev.org/c/openstack/nova/+/712139 [2] https://review.opendev.org/c/openstack/nova/+/821606 [3] https://review.opendev.org/c/openstack/blazar-nova/+/831741 [4] https://review.opendev.org/c/openstack/blazar-nova/+/831832

3 4

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

16 Mar '22

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

1 1

[largescale-sig] Next meeting: Mar 16th, 15utc
by Thierry Carrez 16 Mar '22

16 Mar '22

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. Note that this means the meeting is one hour later than usual for people based in the US! You can doublecheck how that time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220316T15 Feel free to add topics to the agenda: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[heat][rbac] Management of "system resources" with SRBAC enforced
by Takashi Kajinami 16 Mar '22

16 Mar '22

Hello, I've been working on updating policy rules in heat according to the latest guideline for SRBAC implementation. Based on the recent direction change[1], now only project users are allowed to create project-based resources like instances or networks. I'm updating policy rules in heat so that only project users can manage project resources in Heat like stacks or resources. [1] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rb… However this change reveals one potential issue with system resources. In heat there are some resource types like OS::Nova::Flavor or OS::Keystone::User which is allowed for only system users. (I'll call these resources as "system resources" here) Because heat uses user credentials to create resources in backend services, if we require project scope for stack/resource management then we are no longer able to create these system resources as part of stack. (*1) There are some options I can think of at this moment. 1. Deprecate and remove all resources which require system scope Pros - This is most easy solution to be implemented Cons - This one has the biggest user impact 2. Use service credential for resource creation Pros: - This might have smallest user impact Cons: - This requires a relatively big change in heat's architecture, which I've not yet evaluated. - We need to determine the project scope role to be allowed to do system operation. 3. Implement additional project-role in each service to allow creation via stack creation. Pros: - This would avoid user impact. Cons: - requires work in multiple components. - We need to determine the project scope role to be allowed to do system operation. I'm not quite sure which one would be the best. If I can ask for some feedback about these options (or any other new options) from heat's perspective and rbac's perspective then it would be nice. (*1) As of now, nova and neutron no longer allow creating system users to create project resources, so system users are no longer able to create stacks with project resources like instances or networks with default "new" policies. Thank you, Takashi

3 9

[announce][debian] OpenStack Yoga preview Debian packages are ready
by Thomas Goirand 16 Mar '22

16 Mar '22

Hi, Today, my first Yoga VM pings. I haven't done the Tempest/refstack work yet, but it's ongoing. In the mean time, anyone can already try and use the packages as a preview for the Yoga release. They are available through extrepo as usual, or from the osbpo.debian.net repo directly: apt-get install extrepo extrepo enable openstack_yoga apt-get update I'll make a proper announcement once we pass all Refstack tests. Note this is a record-breaking availability, as the RCs were published only at the end of last week. So thanks everyone for this very smooth release. Also to be noted: a few packages are missing, due to unit test failures: magnum, murano, trove, sahara and zaqar. Many of these unit tests fall in the debtcollector that wines about "tenant" not "projects". I'll investigate these later on, but they seem of no real consequence, so I may just skip them. See you in Berlin! Cheers, Thomas Goirand (zigo)

1 0