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

[kolla] [rabbitmq] Another RMQ config question
by Albert Braden 25 Mar '22

25 Mar '22

We’re running kolla-ansible Train and implementing durable queues. I was able to make it work by adding these lines to etc/kolla/config/global.conf: [oslo_messaging_rabbit] amqp_durable_queues = True But we want to do it one cluster at a time, so I tried commenting that out and adding line: amqp_durable_queues: "True" to group_vars/<region>/vars.yml but that seems to have no effect. Where can I put this value to enable durable queues per-cluster?

2 1

[tripleo] CI jobs broken due to #1966382
by Chandan Kumar 25 Mar '22

25 Mar '22

Hello, The tripleo-ci jobs are broken due to the following bug. https://bugs.launchpad.net/tripleo/+bug/1966382 - Multiple tripleo jobs are failing because of "error: Multiple top-level packages discovered in a flat-layout" The latest release of setuptools 61.0 caused it and more info is added here: https://github.com/pypa/setuptools/issues/3197 The team is working on fixing it https://review.opendev.org/q/topic:lp%252F1966382. Till then please hold the rechecks and avoid workflowing patches. Thanks, Chandan Kumar

2 1

[all][tc][goals] : Consistent and Secure Default RBAC: Yoga Timeline updates
by Ghanshyam Mann 25 Mar '22

25 Mar '22

Hello Everyone, As you know, "Consistent and Secure Default RBAC" is one of the currently selected community-wide goals and we have divided it into multiple milestones (cycle)[1]. Our first milestone was Yoga release[2] and in this email, I am going to summarize the progress of Yoga timeline targets. With Lance's role change in his company and we finalized the direction in between of Yoga cycle, there is less progress than what we targeted. Gerrit Topic: https://review.opendev.org/q/topic:%2522secure-rbac%2522+(status:open+OR+st… Tracking: https://etherpad.opendev.org/p/rbac-goal-tracking Completed: ========= * Keystone is already implemented the RBAC as per the new direction. * Nova completed the RBAC as per the new direction[3]. In-progress: ========= * Neutron has started the policy update as per the new direction[4]. Yoga Targets and their progress: ======================== 1. Keystone implements a new default role called manager: Spec merged[5], implementation yet to start. 2. Keystone implements a new default role called service: Spec under discussion[6] 3. Keystone enforces scope by default: Not yet done. We can do it at the start of the Zed cycle. 4. Services start implementing Phase 1: Done. The target was to do at least in one of the services and Nova completed it. 5. OpenStack-wide Personas Documentation: Not yet done. [1] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rb… [2] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rb… [3] https://blueprints.launchpad.net/nova/+spec/policy-defaults-refresh-2 [4] https://review.opendev.org/c/openstack/neutron/+/821208 [5] https://review.opendev.org/c/openstack/keystone-specs/+/818603 [6] https://review.opendev.org/c/openstack/keystone-specs/+/818616 -gmann

1 0

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

25 Mar '22

Development Focus ----------------- We will be releasing the coordinated OpenStack Yoga release Wednesday next week, on March 30th. Thanks to everyone involved in the Yoga cycle! We are now in pre-release freeze, so no new deliverable will be created until final release, unless a release-critical regression is spotted. Otherwise, teams attending the (virtual) PTG should start to plan what they will be discussing there, by creating and filling team etherpads. You can access the list of PTG etherpads at: http://ptg.opendev.org/etherpads.html General Information ------------------- On release day, the release team will produce final versions of deliverables following the cycle-with-rc release model, by re-tagging the commit used for the last RC. A patch doing just that will be proposed. PTLs and release liaisons should watch for that final release patch from the release team. While not required, we would appreciate having an ack from each team before we approve it on the 30th, so that their approval is included in the metadata that goes onto the signed tag. Upcoming Deadlines & Dates -------------------------- Final Yoga release: March 30th, 2022 PTG: April 4 - 8, 2022 (virtual) OpenInfra Summit: June 7-9, 2022 (Berlin) ElődIllés irc: elodilles

1 0

[requirements][all] We are now branched for stable/yoga
by Matthew Thode 25 Mar '22

25 Mar '22

As the title states, openstack/requirements just branched. This means that master can start moving forward with upper-constraints and global-requirements changes. 1. If you have not branched yet you may start seeing dependency changes for the 'Z' release in your development branch (Yoga if you've not branched it yet). 2. If you have changes going into requirements' devepment branch but want to back port to yoga, remember that you'll have to create a backport patch for yoga (and other previous branches). -- Matthew Thode

1 0

[cinder][drivers][stable-policy] propose adding DataCore driver to train
by Karthik Viswanath 25 Mar '22

25 Mar '22

Hi OpenStack community, I am the product manager for SANsymphony, a software defined SAN storage offering, at DataCore<http://www.datacore.com/>. A little bit of history on the current request. DataCore had a Cinder driver in Queen’s branch few years back. Due to organizational restructuring and change in priorities we had to scale back on our efforts towards OpenStack solutions. Because of this we were unable to be active in the community and as a result we got ousted out of Rocky branch due to lack of CI. Details here<https://review.opendev.org/c/openstack/cinder/+/638029>. Currently we have multiple open opportunities with our European customers requiring us to certify RHOSP Cinder driver for both iSCSI and FC protocols. All our current customers are on RHOSP 16.x and would continue to be on that release for another 12-14 months. As a storage solutions provider, we will have to support our customers on 16.x release. As per OpenStack’s Cinder driver policy, this change is considered as *new* driver request and we are unable to backport the changes directly. Given that this has direct revenue impact for DataCore and is time sensitive, we request the community to approve our request to add Cinder driver patch to 16.x maintenance releases ( mainly for Trains branch). Thanks! Karthik Viswanath Sr Product Manager, DataCore Cell: 9886032686 [https://www.datacoreassets.com/email-signatures/logo-email-signature.png]<https://www.datacore.com/?utm_source=signature&utm_medium=email&utm_content…> DataCore Software · The Authority on Software-Defined Storage 1901 Cypress Creek Road Ste. 200 Ft. Lauderdale, FL 33309 [cid1612899890*image002.png(a)01D83EF4.5833C600]

5 4

[cinder] Yoga retrospective surveys! Win fabulous prizes!
by Brian Rosmaita 24 Mar '22

24 Mar '22

Hello Argonauts, As discussed at yesterday's Cinder meeting, we'll have a Yoga cycle retrospective during the next weekly cinder meeting on Wednesday 30 March. I'm actually going to broaden it a bit, so feel free to express your gripes (or kudos) for the Wallaby-Xena-Yoga cycles. Because IRC and video don't allow for much anonymity, you can fill out one (or both) of these anonymous surveys that we can use as the basis for discussion: Cinder Wallaby-Xena-Yoga Retrospective - https://rosmaita.wufoo.com/forms/m1gc1dfo1s42947/ Cinder W-X-Y Retrospective Survey for Drivers - https://rosmaita.wufoo.com/forms/zab0fdr1dg4nwo/ These are really short. The best manager I ever had always just asked 3 questions when he wanted an evaluation of someone, and that's what I'm doing too. That means you only have to give 3 answers! I will be interested to learn stuff I can use if I'm not reincarnated as a cockroach, and Rajat will be able to get some feedback about how the team feels about how things are going. So please take the surveys. cheers, brian

1 0

Re: [TripleO] Offline Installation Support
by Anirudh Gupta 24 Mar '22

24 Mar '22

Hi Harald, Thanks for sharing the steps and apologies for the late reply. I tried setting up Local Repo Server and Registry Server on one machine. Using that I successfully deployed Openstack Ussuri Undercloud and Overcloud in an offline mode. Now, in order to test Upgrade from USSURI to VICTORIA, I updated the repo file and podman registry at my local server for Victoria. On Undercloud , repo file content is as follows: [tripleo] baseurl = http://30.30.30.8/software/repos/tripleo_victoria enabled = 1 gpgcheck = 0 module_hotfixes=1 name = tripleo where 30.30.30.8 is the IP of my reposerver. With this I have successfully updated the required packages using the command: *sudo yum update python*-tripleoclient openstack-tripleo-common openstack-tripleo-heat-templates* Also the container image prepare file, now has the following content parameter_defaults: ContainerImagePrepare: - push_destination: true set: name_prefix: openstack- name_suffix: '' namespace: myserver.com:5000/tripleovictoria neutron_driver: ovn rhel_containers: false tag: current-tripleo tag_from_label: rdo_version But once I run the command "*openstack undercloud upgrade*", I get the following error 2022-03-23 09:53:24,527 p=380392 u=root n=ansible | 2022-03-23 09:53:24.527073 | 5254007b-2040-558f-a68f-0000000000ac | FATAL | Ensure DNF modules have the right stream | undercloud | item={'module': 'container-tools', 'stream': '3.0'} | error={ "ansible_loop_var": "item", "changed": false, "invocation": { "module_args": { "allow_downgrade": false, "autoremove": false, "bugfix": false, "conf_file": null, "disable_excludes": null, "disable_gpg_check": false, "disable_plugin": [], "disablerepo": [], "download_dir": null, "download_only": false, "enable_plugin": [], "enablerepo": [], "exclude": [], "install_repoquery": true, "install_weak_deps": true, "installroot": "/", "list": null, "lock_timeout": 30, "name": [ "@container-tools:3.0/common" ], "releasever": null, "security": false, "skip_broken": false, "state": "present", "update_cache": false, "update_only": false, "validate_certs": true } }, "item": { "module": "container-tools", "stream": "3.0" }, "msg": "*No group container-tools:3.0/common available*.", "results": [] } Can you please help in resolving this issue. Regards Anirudh Gupta On Wed, Mar 23, 2022 at 2:06 PM Lokendra Rathour <lokendrarathour(a)gmail.com> wrote: > > > ---------- Forwarded message --------- > From: Harald Jensas <hjensas(a)redhat.com> > Date: Wed, Feb 23, 2022 at 9:57 PM > Subject: Re: [TripleO] Offline Installation Support > To: <openstack-discuss(a)lists.openstack.org> > > > On 2/16/22 13:58, Anirudh Gupta wrote: > > 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? > > I don't know the exact steps, and I am not aware of upstream > documentation page explaining this. > > You will probalby want to use the 'rsync' tool to sync RDO RPM > repositories and create a local repo on you staging machine. Sync > packages, use `createrepo` tool to generate yum/dnf repo metadata. Then > set up a webserver to make the repository available over HTTP. Search > the internets for "Create local RPM repository / mirror", there are many > generic guides that will help you. > > > For containers you need to set up a local container registry. Then I > would suggest useing the `skopeo`[1] tool to sync containers from the > public registry to your local registry. > > > 2. What modifications would be required in undercloud/overcloud and > > other configuration files to support this? > > > > You need to set up the undercloud to use the RPM repositries on the > staging server. Put config in /etc/yum.repos.d/*.repo files. Once the > overcloud is deployed you would want to add the repo config there as well. > > You need to use a custom containers-prepare file when deploying the > undercloud and overcloud, you must set the namespaces to point to your > local registry. Something like this: > > parameter_defaults: > ContainerImagePrepare: > - push_destination: false > set: > name_prefix: openstack- > name_suffix: '' > namespace: staging.example.com:5000/tripleotrain > neutron_driver: null > tag: current-tripleo > ... > > I would suggest generating the container prepare env file with the > `openstack tripleo container image prepare` command[2] and then edit the > generated file. > > > [1] https://github.com/containers/skopeo > [2] > > https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deploym… > > > > > -- > >

3 3

[all][tc] Canceling TC next two weekly meetings
by Ghanshyam Mann 24 Mar '22

24 Mar '22

Hello Everyone, Because of OpenInfra episode of "Yoga release" on March 31st and PTG on April 7th, we agreed to cancel the TC weekly meeting for the next two weeks (31st March and 7th April). We will continue our weekly meeting from April 14th onwards. -gmann

1 0

[qa] Retire os-testr
by Stephen Finucane 24 Mar '22

24 Mar '22

Hey, I think it's time we retired os-testr. It is already effectively unmaintained and we made a concerted effort some cycles ago to migrate all projects to stestr. I think it's time we finally closed that out. For any projects still using os-testr, stestr effectively provides a drop-in replacement. I'll propose patches to do this shortly. Please let me know if anyone has any concerns about this course of action. Cheers, Stephen

5 7