May 2024 - openstack-discuss - lists.openstack.org

[publiccloud-sig] Summary Foundation Forum @ OpenInfra Day Berlin 2024
by Felix Kronlage-Dammers 17 May '24

17 May '24

Hi, this Wednesday the OpenInfra Day Berlin 2024 happened. Thanks to the various people (such as Nils Magnus, Kurt Garloff, Robert Holling and Friederike Zelke) who were involved in organizing this event. As part of the OpenInfra Day there was a Forum-style session on Interoperability between clouds. The session was initiated by Josephine Seifert, Artem Goncharov, Tobias Rydberg, Adrien Cunin and myself. The etherpad is here: https://etherpad.opendev.org/p/Interop-Forum The intro slides to the session are here: https://input.scs.community/p/KWywBKwBW#/ The 45 minutes we had quickly passed in the discussion - it (once again) did show that this is a topic that does need to be dealt with and it is not enough to just do it every now and then (doh!) - these topics will be picked up as part of the Public-Cloud SIG. However, the Public-Cloud SIG needs more people joining (which was another part of the idea of this session: make advertisement for our work in the Public-Cloud SIG and get more people to join). Tobias and I will see that we will schedule some Public-Cloud SIG calls that are timezone-friendly for the US-/Canada people as well. The next regular call of the Public-Cloud SIG will be on May 29th at 0700 UTC (but a reminder will be sent out couple days in advance). felix

1 0

[nova] May 22th meeting is CANCELLED
by Sylvain Bauza 17 May '24

17 May '24

As said above, the weekly nova meeting on May 22 2024 is CANCELLED. You can join us in #openstack-nova if you have some questions. Thanks, -Sylvain

1 0

[ptl][tc] OpenStack packages PyPi additional external maintainers audit & cleanup
by Ghanshyam Mann 17 May '24

17 May '24

Hi PTLs, As you might know or have seen for your project package on PyPi, OpenStack deliverables on PyPi have additional maintainers, For example, https://pypi.org/project/murano/, https://pypi.org/project/glance/ We should keep only 'openstackci' as a maintainer in PyPi so that releases of OpenStack deliverables can be managed in a single place. Otherwise, we might face the two sets of maintainers' places and packages might get released in PyPi by additional maintainers without the OpenStack project team knowing about it. One such case is in Horizon repo 'xstatic-font-awesome' where a new maintainer is added by an existing additional maintainer and this package was released without the Horizon team knowing about the changes and release. - https://github.com/openstack/xstatic-font-awesome/pull/2 To avoid the 'xstatic-font-awesome' case for other packages, TC discussed it in their weekly meetings[1] and agreed to audit all the OpenStack packages and then clean up the additional maintainers in PyPi (keep only 'openstackci' as maintainers). To help in this task, TC requests project PTL to perform the audit for their project's repo and add comments in the below etherpad. - https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup Thanks to knikolla to automate the listing of the OpenStack packages with additional maintainers in PyPi which you can find the result in output.txt at the bottom of this link. I have added the project list of who needs to check their repo in etherpad. - https://gist.github.com/knikolla/7303a65a5ddaa2be553fc6e54619a7a1 Please complete the audit for your project before March 15 so that TC can discuss the next step in vPTG. [1] https://meetings.opendev.org/meetings/tc/2023/tc.2023-01-11-16.00.log.html#… -gmann

18 27

openstack / sahara Project
by Moein Engineer 16 May '24

16 May '24

Hello Greetings We have decided to use platform openstack / sahara to set up a big data cluster in our company. Has the support and development of project openstack / sahara ended? I checked the last commit is for the last 6 months and for version 19. If project openstack / sahara is not developed and ends, what project has replaced it? Regards

2 1

openstack / sahara
by Moein 15 May '24

15 May '24

1 0

Logscraper host and OpenSearch service upgrade
by Daniel Pawlik 15 May '24

15 May '24

Hello, We would like to notify you that the OpenSearch service [1] would be updated to a newer version on 2024-05-15 at 01:00 PM UTC. This procedure might take a while, depending of the cluster size. During that time, the OpenSearch service would not be available. If anyone has any doubts, please reply to the email. Dan [1] - https://opensearch.logs.openstack.org/_dashboards/app/home

1 1

[kolla-ansible] support for FWaaS/LBaaS?
by garcetto 15 May '24

15 May '24

good morning, does kolla support fwaas or lbaas? thank you

3 4

Antelope compute: failure to live migrate VMs from Yoga compute
by Michel Jouvin 15 May '24

15 May '24

Hi, In a Yoga cloud, I upgraded all the core services and 1 compute to Antelope (directly from Yoga, using a SLURP upgrade). This cloud has 4 compute servers, all using the same HW (Dell FX2/FC630 with Broadwell CPUs). After the upgrade, any attempt to live migrate a VM from a Yoga compute to the Antelope compute fails with the following error in destination/Antelope nova-compute.log: nova.exception.MigrationPreCheckError: Migration pre-check error: Unacceptable CPU info: CPU doesn't have compatibility. This looks weird. I don't see anything in the release notes related to this problem, except a mention that the API used to do the comparison has changed ("This change replaces the usage of older API, compareCPU(), with the new one, compareHypervisorCPU()."). "virsh capabilities" reports the same thing for a Yoga and an Antelope compute, except the addition of a feature 'flush-l1d' in Antelope and the addition of 2 new attributes in the '<cpu>' section: <signature family='6' model='79' stepping='1'/> <maxphysaddr mode='emulate' bits='46'/> I tend to think that additions are not a problem in general and so it doesn't seem to explain the problem I'm facing. Anybody with a similar experience? It seems to me a different problem that the one that has been faced in the past (before Nova 20 if I'm right) and described in several posts, with CPU model improperly detected (in particular Broadwell vs. Icelake). Thanks in advance for any hint/suggestion. Best regards, Michel

3 4

[largescale-sig] Next meeting: May 15, 9utc
by Thierry Carrez 15 May '24

15 May '24

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 9UTC. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240515T09 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

2 2

launch vm and its LVM cinder volumes on same host
by Morteza FarkhondePour 15 May '24

15 May '24

0 <https://serverfault.com/posts/1159435/timeline> I have an OpenStack *Antelope* version installed via Kolla-Ansible, and I have several compute hosts with LVM volume types. When I create an instance using an LVM volume, I expect both the volume and the instance create on the same host. However, they end up on different hosts. For example, the volume is located on d13-compute43@localA#localA, whereas the instance is on d13-compute51

1 0