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

[neutron] CI meeting - Tuesday 19.07.2022
by Slawek Kaplonski 19 Jul '22

19 Jul '22

Hi, This is just a reminder about today's Neutron CI meeting which will be on meetpad [1] at 1500 UTC. Agenda is in the etherpad at [2]. [1] https://meetpad.opendev.org/neutron-ci-meetings[1] [2] https://etherpad.opendev.org/p/neutron-ci-meetings[2] -- Slawek Kaplonski Principal Software Engineer Red Hat -------- [1] https://meetpad.opendev.org/neutron-ci-meetings [2] https://etherpad.opendev.org/p/neutron-ci-meetings

1 0

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

19 Jul '22

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

1 0

Regarding Open Stack Internal IP not responding for compute nodes
by Adivya Singh 19 Jul '22

19 Jul '22

hi Team, I had an issue over the weekend where OpenStack Installed on the XENA version suddenly stopped responding on its internal IP. I checked the switch, Switch was never rebooted and did not see any errors, When I rebooted the Compute node , it fixed the issue. Rabbit-mq was showing errors regards to Network Intermittent connectivity , But that is ok since the Internal IP was not reachable But as a Whole i do not see any specific errors which cause OpenStack Internal Networking to stop Regards Adivya Singh

2 1

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