July 2022 - openstack-discuss - lists.openstack.org

Upgrading to a more recent version of jsonschema
by Thomas Goirand 19 Jul '22

19 Jul '22

Hi, A few DDs are pushing me to upgrade jsonschema in Debian Unstable. However, OpenStack global requirements are still stuck at 3.2.0. Is there any reason for it, or should we attempt to upgrade to 4.6.0? I'd really appreciate if someone (else than me) was driving this... Cheers, Thomas Goirand (zigo)

6 18

[nova][placement] Spec appoval freeze TODAY
by Sylvain Bauza 18 Jul '22

18 Jul '22

Hi Compute-ers, As we agreed on the last PTG, July 14th was set as a deadline for spec approvals for the Zed cycle. We granted a few more days until today but I eventually tell that TODAY we stop accepting specs for this Zed cycle. That being said, we still have two open specs : - https://review.opendev.org/c/openstack/nova-specs/+/842015 is at the moment a discussion for knowing how to fix a Ironic issue. This is not really a spec so it won't need to be stopping to discuss this change. Please continue to provide your comments if you want, as we need to find a consensus for the fix. - https://review.opendev.org/c/openstack/nova-specs/+/849488 will have an exception until tomorrow's meeting. We'll discuss this spec in the meeting and if we have a consensus, we could accept it. If we don't, then this spec won't be accepted for Zed. Also, given we're now on Zed-3, I'll abandon all the open Yoga specs : https://review.opendev.org/q/project:openstack/nova-specs+is:open+file:%255… Thanks, -Sylvain

1 0

[OpenStack-Ansible][Nova] OSA install Yoga on Debian Bullseye Backports
by Dave Hall 18 Jul '22

18 Jul '22

Hello, I've just worked most of the way through a fresh install of Yoga on 5 Debian Bullseye systems. All systems are updated to include the Bullseye backports. The documentation doesn't mention backports, but I always install Debian this way - almost without thinking. The specific config is based on openstack-user-config.yaml.prod.example with 3 infrastructure host, two compute hosts, and cinder/glance running on the infrastructure hosts as in the prod example file. First, one surprise: For version of GlusterFS in Bullseye Backports, /usr/sbin/gluster as been moved to a separate package - glusterfs-cli. I installed this manually in the repo containers to get through setup-infrastructure.yml. In setup-openstack.yml, I'm stopped at "TASK [os_nova : Run nova-status upgrade check to validate a healthy configuration]". "nova-status upgrade check" is failing. "nova-manage cell_v2 list_hosts" is not showing any. Oh, and there are warnings about eventlet monkey patching and urllib3. So I'm not quite sure how to dig into this. The nova-api container seems to be running on the infra hosts, and nova-compute.service is up on both compute hosts, although there are warnings about "Timed out waiting for nova-conductor" The nova-api containers are able to ing the compute hosts on br-mgmt. I do have to wonder if this has anything to do with being upgraded to backpors. Any hints on how to analyse this (or how to fix it)? Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

2 2

[skyline]A problem with skyline packaging RPM
by 任亮 18 Jul '22

18 Jul '22

Hello, a series of packages for skyline are provided at https://pypi.org/user/99cloud/, but only the package of skyline-apiserver. skyline-apiserver requires dependencies of other packages when building. For example, skyline-config,skyline-log,skyline-policy-manager. These packages do not provide the corresponding source packages, we want to package these packages into rpm. Please provide source packages or other better ways to build.

2 1

You're invited to Open Infrastructure Days Mexico 2022
by Alvaro Soto 17 Jul '22

17 Jul '22

15 Aug 2022 You're invited to Open Infrastructure Days Mexico 2022 Hello, We’d love for you to join us for Open Infrastructure Days Mexico 2022. Using the Eventee platform, you can view all event sessions, engage with speakers, and much more. We will also inform you about all event updates, so you will always have the latest information. Open Infrastructure Days Mexico 2022 is fully accessible from both desktop and native mobile app. https://openinfradays.mx <https://meet.meetup.com/ls/click?upn=SDNnya-2FgLI6CfUa8do8Zd03To0qCnG4Szsis…> https://eventee.co/en/e/open-infrastructure-days-mexico-2022-13797 <https://meet.meetup.com/ls/click?upn=SDNnya-2FgLI6CfUa8do8ZdwkOQiDWzZ-2BHDW…> Looking forward to seeing you there, OpenInfraCDMX community. OpenInfraGDL community. -- Alvaro Soto *Note: My work hours may not be your work hours. Please do not feel the need to respond during a time that is not convenient for you.* ---------------------------------------------------------- Great people talk about ideas, ordinary people talk about things, small people talk... about other people.

1 0

[placement] running out of VCPU resource
by Przemyslaw Basa 16 Jul '22

16 Jul '22

Hello I have a fresh Xena deployment. I'm able to spawn one VM per project per compute node then I get placement errors like Jul 13 15:32:27 g-os-controller-placement-container-a796c019 placement-api[1821]: 2022-07-13 15:32:27.683 1821 WARNING placement.objects.allocation [req-314a1352-457e-4166-8d8c-ef58e6d926ad 81c8738a7d4e46b3a0ae270eccf852c9 36e66b27e5144df5ba4a2270695fea34 - default default] Over capacity for VCPU on resource provider 16f620c0-8c6f-4984-8d58-e2c00d1b32da. Needed: 1, Used: 13318, Capacity: 256.0 Number in Used field seemed strange, it looked to me more like memory sum not used VCPU count. root@os-install:~# openstack resource provider show 16f620c0-8c6f-4984-8d58-e2c00d1b32da --allocations -c allocations -f value {'b6da8a02-a96c-464e-a6c4-19c96c83dd44': {'resources': {'MEMORY_MB': 12288, 'VCPU': 4}}, '212798a3-6753-443d-8e7c-5c3be3f4ab54': {'resources': {'DISK_GB': 1, 'MEMORY_MB': 1024, 'VCPU': 1}}} I've done some digging in sources and found SQL (in placement/objects/allocation.py) that is supposed to generate these values. MariaDB [placement]> SELECT rp.id, rp.uuid, rp.generation, inv.resource_class_id, inv.total, inv.reserved, inv.allocation_ratio, allocs.used FROM resource_providers AS rp JOIN inventories AS inv ON rp.id = inv.resource_provider_id LEFT JOIN ( SELECT resource_provider_id, resource_class_id, SUM(used) AS used FROM allocations WHERE resource_class_id IN (0, 1, 2) AND resource_provider_id IN (5) GROUP BY resource_provider_id, resource_class_id ) AS allocs ON inv.resource_provider_id = allocs.resource_provider_id AND inv.resource_class_id = allocs.resource_class_id WHERE rp.id IN (5) AND inv.resource_class_id IN (0, 1, 2); +----+--------------------------------------+------------+-------------------+---------+----------+------------------+-------+ | id | uuid | generation | resource_class_id | total | reserved | allocation_ratio | used | +----+--------------------------------------+------------+-------------------+---------+----------+------------------+-------+ | 5 | 16f620c0-8c6f-4984-8d58-e2c00d1b32da | 37 | 0 | 128 | 0 | 2 | 13318 | | 5 | 16f620c0-8c6f-4984-8d58-e2c00d1b32da | 37 | 1 | 1031723 | 2048 | 1 | NULL | | 5 | 16f620c0-8c6f-4984-8d58-e2c00d1b32da | 37 | 2 | 901965 | 2 | 1 | NULL | +----+--------------------------------------+------------+-------------------+---------+----------+------------------+-------+ Individual parts shows correct data, join messing up numbers: MariaDB [placement]> SELECT resource_provider_id, resource_class_id, SUM(used) AS used FROM allocations WHERE resource_class_id IN (0, 1, 2) AND resource_provider_id IN (5) GROUP BY resource_provider_id, resource_class_id; +----------------------+-------------------+-------+ | resource_provider_id | resource_class_id | used | +----------------------+-------------------+-------+ | 5 | 0 | 5 | | 5 | 1 | 13312 | | 5 | 2 | 1 | +----------------------+-------------------+-------+ MariaDB [placement]> SELECT rp.id, rp.uuid, rp.generation, inv.resource_class_id, inv.total, inv.reserved, inv.allocation_ratio, inv.resource_provider_id, inv.resource_class_id FROM resource_providers AS rp JOIN inventories AS inv ON rp.id = inv.resource_provider_id WHERE rp.id IN (5) AND inv.resource_class_id IN (0, 1, 2); +----+--------------------------------------+------------+-------------------+---------+----------+------------------+----------------------+-------------------+ | id | uuid | generation | resource_class_id | total | reserved | allocation_ratio | resource_provider_id | resource_class_id | +----+--------------------------------------+------------+-------------------+---------+----------+------------------+----------------------+-------------------+ | 5 | 16f620c0-8c6f-4984-8d58-e2c00d1b32da | 38 | 0 | 128 | 0 | 2 | 5 | 0 | | 5 | 16f620c0-8c6f-4984-8d58-e2c00d1b32da | 38 | 1 | 1031723 | 2048 | 1 | 5 | 1 | | 5 | 16f620c0-8c6f-4984-8d58-e2c00d1b32da | 38 | 2 | 901965 | 2 | 1 | 5 | 2 | +----+--------------------------------------+------------+-------------------+---------+----------+------------------+----------------------+-------------------+ Query behaves differently when there is more than one resource_provider_id, it shows correct values then. Any tips how to fix this situation? I'm not brave enough to tinker with this query myself. Regards, Przemyslaw Basa

2 2

[all][tc] What's happening in Technical Committee: summary 15 July 2022: Reading: 5 min
by Ghanshyam Mann 16 Jul '22

16 Jul '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on 14 July. Most of the meeting discussions are summarized in this email. Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-07-14-15.00.log.html * Next TC weekly meeting will be on 21 July Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by 20 July. 2. What we completed this week: ========================= * We continued the CentOS steam testing discussion and by considering all the point we agreed to make CentOS stream jobs testing periodic but keep it in testing runtime. Monitor, debug, and report the failure to CentOS stream team. 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[2], Two are completed and others items are in-progress. Open Reviews ----------------- * Seven open reviews for ongoing activities[3]. Consistent and Secure Default RBAC ------------------------------------------- We have a good amount of discussion and review in the goal document updates[4] and I have updated the patch by resolving the review comments. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[5]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- Dale Smith volunteer to be PTL for Adjutant project [6] Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[7][8]. Project updates ------------------- * Add charmed k8s operators to OpenStack Charms[9] * Adding Skyline as Emerging Technology[10] 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[11]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [12] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/847413 [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://review.opendev.org/c/openstack/governance/+/847418 [5] https://review.opendev.org/c/openstack/governance/+/836888 [6] https://review.opendev.org/c/openstack/governance/+/849606 [7] https://etherpad.opendev.org/p/zuul-config-error-openstack [8] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [9] https://review.opendev.org/c/openstack/governance/+/849997 [10] https://review.opendev.org/c/openstack/governance/+/849155 [11] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [12] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[release] Release countdown for week R-11, Jul 18 - 22
by Előd Illés 16 Jul '22

16 Jul '22

Development Focus ----------------- We are now past the Zed-2 milestone, and entering the last development phase of the cycle. Teams should be focused on implementing planned work for the cycle. Now is a good time to review those plans and reprioritize anything if needed based on the what progress has been made and what looks realistic to complete in the next few weeks. General Information ------------------- Looking ahead to the end of the release cycle, please be aware of the feature freeze dates. Those vary depending on deliverable type: * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (August 26th, 2022). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (September 1st, 2022) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, September 1st, 2022. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (September12th, 2022) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (September 29th, 2022) Upcoming Deadlines & Dates -------------------------- Non-client library freeze: August 26th, 2022 (R-6 week) Client library freeze: September 1st, 2022 (R-5 week) Zed-3 milestone: September 1st, 2022 (R-5 week) Előd Illés irc: elodilles

1 0

[neutron] change of API performance from Pike to Yoga
by Bence Romsics 15 Jul '22

15 Jul '22

Hi Neutrinos! Inspired by Julia Kreger's presentation on the summit [1] I wanted to gather some ideas about the change in Neutron API performance. For that I used Rally with Neutron's usual Rally task definition [2]. I measured against an all-in-one devstack - running always in a same sized VM, keeping its local.conf the same between versions as much as possible. Neutron was configured with ml2/ovs. Measuring other backends would also be interesting, but first I wanted to keep the config the same as I was going back to earlier versions as long as possible. Without much pain I managed to collect data starting from Yoga back to Pike. You can download all Rally reports in this tarball (6 MiB): https://drive.google.com/file/d/1TjFV7UWtX_sofjw3_njL6-6ezD7IPmsj/view?usp=… The tarball also contains data about how to reproduce these tests. It is currently available at my personal Google Drive. I will keep this around at least to the end of July. I would be happy to upload it to somewhere else better suited for long term storage. Let me also attach a single plot (I hope the mailing list configuration allows this) that shows the load_duration (actually the average of 3 runs each) for each Rally scenario by OpenStack release. Which I hope is the single picture summary of these test runs. However the Rally reports contain much more data, feel free to download and browse them. If the mailing list strips the attachment, the picture is included in the tarball too. Cheers, Bence (rubasov) [1] https://youtu.be/OqcnXxTbIxk [2] https://opendev.org/openstack/neutron/src/commit/a9912caf3fa1e258621965ea8c…

3 4

Propose to add Tobias Urdin as Tooz core reviewer
by Herve Beraud 15 Jul '22

15 Jul '22

Hello everybody, It is my pleasure to propose Tobias Urdin (tobias-urdin) as a new member of the Tooz project core team. During the last months Tobias has been a significant contributor to the Tooz project. Obviously we think he'd make a good addition to the core team. If there are no objections, I'll make that happen in a week. Thanks. -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

2 2

Propose to add Takashi Kajinami as Oslo core reviewer
by Herve Beraud 15 Jul '22

15 Jul '22

Hello everybody, It is my pleasure to propose Takashi Kajinami (tkajinam) as a new member of the oslo core team. During the last months Takashi has been a significant contributor to the oslo projects. Obviously we think he'd make a good addition to the core team. If there are no objections, I'll make that happen in a week. Thanks. -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

4 4

[kuryr] Proposal to clean up Kuryr core reviewers
by Maysa De Macedo Souza 15 Jul '22

15 Jul '22

Hello, We went through the list of current Kuryr core reviewers on the last PTG session and we noticed a couple of people that are not active Kuryr contributors anymore. I would to propose removing the following contributors from the Kuryr core team: - Irena Berezovsky - Gal Sagie - Liping Mao I take this opportunity to thank all of them for their contributions to the Kuryr project. I will wait one week for any feedback before proceeding with the removal. Thank you, Maysa Macedo

2 1

[adjutant][tc][all] Call for volunteers to be a PTL and maintainers
by Slawek Kaplonski 15 Jul '22

15 Jul '22

Hi, After last PTL elections [1] Adjutant project don't have any PTL. It also didn't had PTL in the Yoga cycle already. So this is call for maintainters for Adjutant. If You are using it or interested in it, and if You are willing to help maintaining this project, please contact TC members through this mailing list or directly on the #openstack-tc channel @OFTC. We can talk possibilities to make someone a PTL of the project or going with this project to the Distributed Project Leadership [2] model. [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027411… [2] https://governance.openstack.org/tc/resolutions/20200803-distributed-projec… -- Slawek Kaplonski Principal Software Engineer Red Hat

4 8

[nova][ops] seeking input about local/ephemeral disk encryption feature naming
by melanie witt 15 Jul '22

15 Jul '22

Hi everyone, A potential issue regarding naming has come up during review of the ephemeral storage encryption feature [1][2] patch series [3] and we're looking for input before moving forward with any naming/terminology changes across the specs and the entire patch series. The concern that has been raised is around use of the term "ephemeral" for the name of this feature including traits, extra specs, and image properties [4]. For context, the objective of this feature is to provide users with the ability to specify that all local disks for the instance be encrypted. This includes the root disk and any other local disks. The initial concern is around use of the word "ephemeral" for the root disk. My general interpretation of the word "ephemeral" for storage in nova has been that it means attached storage that only persists for the lifetime of the instance and is destroyed if and when the instance is destroyed. This is in contrast to attached cinder volumes which can persist after instance deletion. But should "ephemeral" ever be used to describe a root disk? Is it incorrect and/or ambiguous to refer to it as such? This is part of what is being discussed in [4]. During discussion, I also realized there is a separate gap in the above interpretation of "ephemeral" in nova. When cinder volumes are attached to an instance, their persistence after the instance is deleted depends on whether the 'delete_on_termination' attribute is set to true in the request payload when the instance is created [5] or when attaching a volume to the instance [6] or updating a volume attached to the instance [7]. This means that in the currently proposed patches, if a user specifies hw:ephemeral_encryption in the extra_specs, for example, and they also have a volume with delete_on_termination=True attached, only the root disk will be encrypted via the extra spec -- the volume would not be encrypted. Encryption of the volume has to be requested in cinder. Could this mislead a user into thinking both the root disk and cinder volume are encrypted when only the root disk is? Because of the above issues, we are considering whether we should change the terminology used in this feature at this stage. Some ideas include "local encryption", "local disk encryption", "disk encryption". IMHO "disk_encryption" is ambiguous in its own way because an attached cinder volume also has a disk. Changing the naming will be a non-trivial amount of work, so we wanted to get additional input before going ahead with such a change. Another thing noted in a comment on another patch in the series [8] is that the os-traits for this feature have already been merged [9]. If we decide to change the naming, should we go ahead and use these traits as-is and have them not match the naming in nova or should we deprecate them and add new traits that match the new name and use those? I hope this makes sense and your input would be much appreciated. Cheers, -melwitt [1] https://specs.openstack.org/openstack/nova-specs/specs/yoga/approved/epheme… [2] https://specs.openstack.org/openstack/nova-specs/specs/yoga/approved/epheme… [3] https://review.opendev.org/q/topic:specs%252Fyoga%252Fapproved%252Fephemera… [4] https://review.opendev.org/c/openstack/nova/+/764486/10/nova/api/validation… [5] https://docs.openstack.org/api-ref/compute/?expanded=create-server-detail#c… [6] https://docs.openstack.org/api-ref/compute/?expanded=attach-a-volume-to-an-… [7] https://docs.openstack.org/api-ref/compute/?expanded=update-a-volume-attach… [8] https://review.opendev.org/c/openstack/nova/+/760456/10/nova/scheduler/requ… [9] https://github.com/openstack/os-traits/blob/f64d50e4dd2f21558fb73dd4b59cd1d…

2 1

[neutron] Drivers meeting - Friday 14.7.2022 - cancelled
by Lajos Katona 15 Jul '22

15 Jul '22

Hi Neutron Drivers! Due to the lack of agenda, let's cancel tomorrow's drivers meeting. See You on the meeting next week. Lajos Katona (lajoskatona)

1 0

[cinder] Festival of XS reviews
by Rajat Dhasmana 14 Jul '22

14 Jul '22

Hello Argonauts, We will be having our monthly festival of XS reviews tomorrow i.e. 15th July (Friday) from 1400-1600 UTC. Following are some additional details: Date: 15th July, 2022 Time: 1400-1600 UTC Meeting link: https://meetpad.opendev.org/cinder-festival-of-reviews etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews Thanks and regards Rajat Dhasmana

1 0

Changing Ubuntu Cloud Repo On Instance
by Adam Pankow 14 Jul '22

14 Jul '22

Ubuntu instance images seem to utilize "nova.clouds.archive.ubuntu.com" as their default repository. It seems that either this server does not efficiently route to an alternate mirror, or it itself is a mirror. This results in quite abysmal download speeds that I have seen. Would there be any downside to picking any other Ubuntu mirror, that is definitively more geographically close to me, but not explicitly labeled a Nova/Cloud mirror? i.e. would there be issues encountered, or features lost, by not using Ubuntu's designated Nova/Cloud repo?

3 2

[tripleo] new gate blocker: tripleo-ci-centos-9-scenario010-standalone and ovn master jobs
by Ronelle Landy 14 Jul '22

14 Jul '22

Hello All, We have a new gate blocker impacting tripleo-ci-centos-9-scenario010-standalone and ovn-provider master jobs. The deployment fails and the error in the nova_libvirt_init_secret/stdout.log log shows: Error: /etc/ceph/ceph.conf contained an empty fsid definition Check your ceph configuration Details of the failure are in https://bugs.launchpad.net/tripleo/+bug/1981634. Please hold rechecks until we can touch base with the Ceph team to discuss. Thank you, TripleO CI

4 5

[cinder] Extending Driver Merge Deadline
by Rajat Dhasmana 14 Jul '22

14 Jul '22

Hello Argonauts, As discussed in yesterday's Cinder meeting[1], given the number of drivers proposed for Zed cycle (8 new Drivers[2]) and the limited review bandwidth (cores are working on development tasks), we've decided to extend the driver merge deadline from R-12 to R-10 i.e. from 15th July to 29th July. R-10 is also the deadline for Manila driver merge deadline[3]. [1] https://meetings.opendev.org/meetings/cinder/2022/cinder.2022-07-13-14.00.l… [2] https://etherpad.opendev.org/p/cinder-zed-new-drivers [3] https://releases.openstack.org/zed/schedule.html#z-manila-new-driver-deadli… Thanks and regards Rajat Dhasmana

1 0

[all][tc] Technical Committee next weekly meeting on 14 July 2022 at 1500 UTC
by Ghanshyam Mann 14 Jul '22

14 Jul '22

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

1 1

[infra] Tarballs are not accessible anymore
by Jose Castro Leon 14 Jul '22

14 Jul '22

Hi, I don't know if someone noticed already but the tarballs are not accessible anymore, is that expected? https://tarballs.opendev.org/openstack/ Cheers Jose Castro Leon CERN Cloud Infrastructure

4 4

CRITICAL rally [-] Unhandled error: KeyError: 'openstack' Edit | Openstack wallaby tripleo | centos 8 stream
by Swogat Pradhan 14 Jul '22

14 Jul '22

Hi, I am using openstack wallaby in tripleo architecture. I googled around and found i can use openstack-rally for testing the openstack deployment and will be able to genrate report also. so i tried installing openstack rally using "yum install openstack-rally", "pip3 install openstack-rally" and finally cloned the git repo and ran "python3 setup.py install" but no matter what i do i am getting the error 'unhandled error : keyerror 'openstack'' (overcloud) [root@hkg2director ~]# rally deployment create --fromenv --name=existing +--------------------------------------+----------------------------+----------+------------------+--------+ | uuid | created_at | name | status | active | +--------------------------------------+----------------------------+----------+------------------+--------+ | 484aae52-a690-4163-828b-16adcaa0d8fb | 2022-06-07T05:48:39.039296 | existing | deploy->finished | | +--------------------------------------+----------------------------+----------+------------------+--------+ Using deployment: 484aae52-a690-4163-828b-16adcaa0d8fb (overcloud) [root@hkg2director ~]# rally deployment show 484aae52-a690-4163-828b-16adcaa0d8fb Command failed, please check log for more info 2022-06-07 13:48:58.651 482053 CRITICAL rally [-] Unhandled error: KeyError: 'openstack' 2022-06-07 13:48:58.651 482053 ERROR rally Traceback (most recent call last): 2022-06-07 13:48:58.651 482053 ERROR rally File "/bin/rally", line 10, in <module> 2022-06-07 13:48:58.651 482053 ERROR rally sys.exit(main()) 2022-06-07 13:48:58.651 482053 ERROR rally File "/usr/local/lib/python3.6/site-packages/rally/cli/main.py", line 40, in main 2022-06-07 13:48:58.651 482053 ERROR rally return cliutils.run(sys.argv, categories) 2022-06-07 13:48:58.651 482053 ERROR rally File "/usr/local/lib/python3.6/site-packages/rally/cli/cliutils.py", line 669, in run 2022-06-07 13:48:58.651 482053 ERROR rally ret = fn(*fn_args, **fn_kwargs) 2022-06-07 13:48:58.651 482053 ERROR rally File "/usr/local/lib/python3.6/site-packages/rally/cli/envutils.py", line 142, in inner 2022-06-07 13:48:58.651 482053 ERROR rally return func(*args, **kwargs) 2022-06-07 13:48:58.651 482053 ERROR rally File "/usr/local/lib/python3.6/site-packages/rally/plugins/__init__.py", line 59, in wrapper 2022-06-07 13:48:58.651 482053 ERROR rally return func(*args, **kwargs) 2022-06-07 13:48:58.651 482053 ERROR rally File "/usr/local/lib/python3.6/site-packages/rally/cli/commands/deployment.py", line 205, in show 2022-06-07 13:48:58.651 482053 ERROR rally creds = deployment["credentials"]["openstack"][0] 2022-06-07 13:48:58.651 482053 ERROR rally KeyError: 'openstack' 2022-06-07 13:48:58.651 482053 ERROR rally can someone please help me in fixing this issue or give any suggestion on which tool to use to test the openstack deployment and benchmark. Also is tempest available for wallaby?? i checked the opendev and github repos last tags available are for victoria. With regards, Swogat pradhan

2 1

Re: [OpenStack-Ansible][Neutron] Guide for Openstack installation with HA, OVN ?
by Dave Hall 13 Jul '22

13 Jul '22

Hello. I would like to extend Park's question with a specific question of my own that could be used as an example the 'first time deployer' experience. My question is about Neutron deployment as it is specified in the various openstack_user_config.yml examples. openstack_user_config.yml.prod.example declares network-infra_hosts and network-agent_hosts, whereas openstack_user_config.yml.singlebond.example only declares network_hosts. For the novice trying to choose which example file to customize for our deployment, the following concerns arise: - If I use network_hosts, does that deploy both the infra and the agent on each network_host? - If I use network-infra_hosts and network-agent_hosts, but give both the same set of host names/IPs, will it deploy correctly and produce a working Neutron service? - If I successfully deploy a smaller cluster using network_hosts, and then grow my cluster, what criteria indicate the point at which I need to switch to infra_hosts and agent_hosts, and how many of each should I deploy? In reading through the Neutron documentation, I see some 'what' and some 'how', but very little 'why'. Perhaps a section titled 'Practical Deployment Considerations'? At this point I just want to know how to make Neutron deployment work right and how to be able to tell, after deployment, that it is working right. Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu On Wed, Jul 13, 2022 at 1:46 AM 박경원 <park0kyung0won(a)dgist.ac.kr> wrote: > Hello > > > I've tried minimal installation of openstack following official > documentation > > Now I want to install openstack with > > > 1. High availability configuration - keystone, placement, neutron, glance, > cinder, ... > > 2. Open Virtual Network for neutron driver > > > But it's hard to find documentation online > > Could you provide some links for the material? > > > Thank you! >

2 1

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

13 Jul '22

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

8 13

[cinder] Bug deputy report for week of 07-13-2022
by Sofia Enriquez 13 Jul '22

13 Jul '22

This is a bug report from 07-06-2022 to 07-13-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/os-brick/+bug/1981455 "RBD disconnect fails with AttributeError for startswith." Fix proposed to master. Medium - https://bugs.launchpad.net/cinder/+bug/1981068 "Dell PowerStore - cinder cannot delete volumes." No patch proposed to master yet. - https://bugs.launchpad.net/cinder/+bug/1981420 "Dell PowerMax - error when creating synchronous volumes." Low - https://bugs.launchpad.net/cinder/+bug/1980870 "Dell PowerMax driver may deadlock moving volumes between SGs." Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1981354 "Infinidat Cinder driver does not return all iSCSI portals for multipath storage." Fix proposed to master. Incomplete - https://bugs.launchpad.net/cinder/+bug/1981211 "[stable/yoga] Update attachment failed for attachment." Unassigned. Cheers, Sofia -- 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