June 2024 - openstack-discuss - lists.openstack.org

[publiccloud-sig] Reminder - next meeting June 26th - 0700 UTC
by Felix Kronlage-Dammers 25 Jun '24

25 Jun '24

Hi everyone, This Wednesday (June 26th, that is tomorrow) the next meeting of the public cloud sig is going to happen. We’ll be meeting at 0700 UTC here: https://meetpad.opendev.org/publiccloud-sig <https://meetpad.opendev.org/publiccloud-sig> See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG <https://wiki.openstack.org/wiki/PublicCloudSIG> See you on Wednesday! felix -- Felix Kronlage-Dammers Sovereign Cloud Stack — standardized, built and operated by many Ein Projekt der Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com <mailto:fkr@osb-alliance.com>

1 0

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2024.2/R-14)
by Goutham Pacha Ravi 25 Jun '24

25 Jun '24

Hello Stackers, We're halfway through the 2024.2 release cycle! Next Thursday (2024-07-04) is milestone 2 [1] of this "Dalmatian" release cycle. This is an important milestone for OpenStack project teams to target bug fixes and it serves as a deadline for project-specific activities. The Technical Committee also uses this milestone to vet project activity to adjust the list of Emerging and Inactive OpenStack projects [2]. We'll likely see some proposals regarding this in the next week. During this past week, we merged governance proposals to nominate a PTL for the OpenStack Charms project and to nominate individual TC members as liaisons to projects with distributed project leadership. Looking ahead at the next release; there are a few important activities that need your attention: - The Virtual OpenInfra Project Teams Gathering is scheduled for October 21-25, 2024. Please read Kendall Nelson's (diablo_rojo) note here [3]. Project teams will be signing up over the next several weeks; I'd encourage you all to confirm your attendance by grabbing a ticket! [4] - Allison Price (aprice) sent out a poll to find a codename for the 2025.1 release. I encourage you all to participate - the deadline is June 28th, 2024! [5] I don't know if we have officially accepted that we have an animal theme going; shouldn't we? :) CentOS 8 Stream has reached end-of-life, and Clark Boylan (clarkb) informed OpenDev infrastructure consumers that centos-8-stream nodes will be removed from nodepool/Zuul CI [6]. Project teams are encouraged to check their use of centos-8-stream across all maintained/"unmaintained" branches in their repositories and modify/delete such jobs. Don't forget to address any documentation within your project teams! === Weekly Meeting === Last week's IRC meeting [7] began with a recap of the effort to secure our deliverables on PyPI. Our efforts to rein in "unowned" packages and packages with inconsistent metadata will continue. We considered the idea of adding a second maintainer account across all packages. While we agree on the benefits of a second maintainer account, given that there's no viable API to automate adding/adjusting maintainers, achieving this will be a laborious manual process. We have shelved the idea for now and are going to watch for updates on PyPI's community accounts or for a meaningful maintainer API. We then delved into persistent CI failures and gate stability. We took an action item to skip slow tests in integrated jobs using Ceph that are frequently timing out or finishing just around the permitted timeout. The next OpenStack PTL and TC Election season begins in approximately 50 days (Nomination period opens August 14th [1]). We'll attempt to get any election-related changes in place before the election season. Our next IRC weekly meeting will be held tomorrow (2024-06-25) at 18:00 UTC in OFTC's #openstack-tc channel. Please find the agenda at [8] and do join us! === Governance Proposals === ==== Merged ==== Fixing the validate-legacy script | https://review.opendev.org/c/openstack/governance/+/920848 Appoint James Page as OpenStack Charms PTL | https://review.opendev.org/c/openstack/governance/+/921731 Add TC liaison in DPL model implementation | https://review.opendev.org/c/openstack/governance/+/917516 ==== Open for review/discussion ==== Retire kuryr-kubernetes and kuryr-tempest-plugin | https://review.opendev.org/c/openstack/governance/+/922507 Update criteria for the inactive projects to become active again | https://review.opendev.org/c/openstack/governance/+/921500 Adding a rule to manage the affiliation diversity requirement in the TC | https://review.opendev.org/c/openstack/governance/+/922512 Remove Eventlet From Openstack | https://review.opendev.org/c/openstack/governance/+/902585 Show TC and SIG repos under reference | https://review.opendev.org/c/openstack/governance/+/918488 Adding a rule to manage the affiliation diversity requirement in the TC | https://review.opendev.org/c/openstack/governance/+/922512 How to contact the TC: ================== You can reach out to the TC in multiple ways: 1. Email: you can send the email with tag [tc] on this email list. 2. Ping us using 'tc-members' keyword on #openstack-tc IRC channel 3. Join us at our weekly meeting: The Technical Committee meets every week on Tuesdays at 1800 UTC [6] Upcoming Events: ============== 2024-07-01: Monthly Technical Committee Video+IRC meeting 2024-07-02: OpenInfra Board Meeting -: https://board.openinfra.dev/meetings/2024-07-02 2024-07-04: Milestone-2 of the 2024.2 release cycle Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] Release Schedule: https://releases.openstack.org/dalmatian/schedule.html [2] Emerging Technology and Inactive Projects: https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [3] 2025.1 PTG: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [4] PTG Registration: https://ptg.openinfra.dev/#registration=1 [5] Poll for naming the 2025.1 release: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [6] CentOS-8-stream node removal: https://lists.opendev.org/archives/list/service-announce@lists.opendev.org/… [7] TC Meeting Log: https://meetings.opendev.org/meetings/tc/2024/tc.2024-06-18-18.00.log.html [8] TC Meeting Agenda: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[publiccloud-sig] Reminder - next meeting June 26th - 0700 UTC
by Felix Kronlage-Dammers 25 Jun '24

25 Jun '24

Hi everyone, This Wednesday (June 26th) the next meeting of the public cloud sig is going to happen. We’ll be meeting at 0700 UTC here: https://meetpad.opendev.org/publiccloud-sig <https://meetpad.opendev.org/publiccloud-sig> See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG <https://wiki.openstack.org/wiki/PublicCloudSIG> See you on Wednesday! felix -- Felix Kronlage-Dammers Sovereign Cloud Stack — standardized, built and operated by many Ein Projekt der Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com <mailto:fkr@osb-alliance.com>

1 0

[nova] Enabling UEFI for BFV instances
by Mohammed Naser 24 Jun '24

24 Jun '24

Hi everyone, I’m working on an open source tool right now which can do online migration of VMware instances to OpenStack. It uses VDDK and some other neat pieces of open source technology (nbdkit, libnbd, virt-v2v). It’s working great so far and I have a few challenges before release. When migrating a VM that was using UEFI in VMware, the VM will not boot inside OpenStack because it needs `hw_machine_type` to be set to `uefi`. However, the way that I’m doing migrations, I’m mounting a volume inside a migration “appliance VM” and copying data into it (to make it generic enough to work with all backends). Is there a way we can mark a volume as UEFI bootable by any chance so that Nova picks it up? Thanks, Mohammed

3 3

[swift][s3api] Same bucket object storage policy
by Rafael Tavares Oliveira 24 Jun '24

24 Jun '24

Hey there! We would very much like to allow multiple objects in the same bucket to have multiple storage policies, different from their container. Since we noticed that this is not possible now, we'd like to take a shot at it. But first, any suggestions or ideas on implementing this? The idea we are following here and trying to implement would be to use the same logic as the `+segments` bucket: each bucket would have a `+cold` counterpart, in the cold storage policy, which would store such objects, and we would keep a manifest/symlink in the original bucket, which we can use to retrieve the content from cold storage. Just as a piece of context, we are basing this solution on yoga release and using S3 apis mainly. Thanks for the help! Rafael

2 1

[oslo] Specs proposal to use cotyledon and futurist.
by Daniel Bengtsson 24 Jun '24

24 Jun '24

Hi there, Further to my previous mail, I have decided to create a specs proposal[1] within oslo. The idea is to use cotyledon and futurist in oslo.service and not to deprecate the project. Please don't hesitate to send me feedback. [1] https://review.opendev.org/c/openstack/oslo-specs/+/922597 -- Daniel Bengtsson Software Engineer

2 2

Regarding Cinder- Volume error in OpenStack-ansible
by Adivya Singh 24 Jun '24

24 Jun '24

Hi Team, I am trying to configure the Cinder Volume service with NFS server as a backend and this is my user_variables File cinder_backends: default: volume_backend_name: nfs volume_driver: cinder.volume.drivers.nfs.NfsDriver nfs_shares_config: /etc/cinder/nfs_shares nfs_qcow2_volumes: true nfs_mount_options: vers=4,nfsvers=4,noatime,rw,bg,intr,async,timeo=60 nfs_snapshot_support: true shares: - ip: 172.29.244.103 share: /cinder/volume My NFS server Configuration is Like this /img/glance 172.29.244.0/22(rw,insecure,sync,no_subtree_check,no_root_squash) /cinder/volume 172.29.244.0/22(vrw,insecure,sync,no_subtree_check,no_root_squash) now what i am seeing is below error 2024-06-24 08:11:42.892 4807 ERROR cinder.volume.drivers.remotefs [None req-85e0d72a-f403-4c8e-8880-1ced0413f760 - - - - - -] Exception during mounting NFS mount failed for share 172.29.244.103:/cinder/volume. Error - {'nfs': "Unexpected error while running command.\nCommand: sudo cinder-rootwrap /etc/cinder/rootwrap.conf mount -t nfs -o vers=4,nfsvers=4,noatime,rw,bg,intr,async,timeo=60 172.29.244.103:/cinder/volume /var/lib/cinder/mnt/cd53d1ffa6d608fee908e8f1668ce63d\nExit code: 32\nStdout: ''\nStderr: 'mount.nfs: multiple version options not permitted\\n'"}: cinder.exception.NfsException: NFS mount failed for share 172.29.244.103:/cinder/volume. Error - {'nfs': "Unexpected error while running command.\nCommand: sudo cinder-rootwrap /etc/cinder/rootwrap.conf mount -t nfs -o vers=4,nfsvers=4,noatime,rw,bg,intr,async,timeo=60 172.29.244.103:/cinder/volume /var/lib/cinder/mnt/cd53d1ffa6d608fee908e8f1668ce63d\nExit code: 32\nStdout: ''\nStderr: 'mount.nfs: multiple version options not permitted\\n'"} Any clue on this, How to fix it Regards Adivya Singh

2 1

[barbican][openstack-helm][tacker] Request to Include Barbican Installation Guide in OpenStack-Helm Documentation
by JUSO WATARU(十楚　航) 21 Jun '24

21 Jun '24

Hello, We are presently in the process of enhancing the official OpenStack-Helm documentation by including a procedural guide for deploying Tacker using helmchart. Through discussions with members of the openstack-helm community, it has been emphasized that Barbican is an indispensable component for Tacker. Hence, it would be highly beneficial for users to have comprehensive instructions for installing Barbican with helmchart included in the official OpenStack-Helm documentation [1]. Consequently, we suggest that the Barbican community integrate the installation guide for the Barbican component into the official OpenStack-Helm documentation. This addition is poised to significantly enhance the clarity and accessibility of deployment procedures for users. We eagerly welcome your opinions and feedback on this proposal, as we aim to ensure that the documentation for openstack deployment with helmchart meets the needs of our community. [1] https://docs.openstack.org/openstack-helm/latest/install/openstack.html Regards, Wataru

2 2

[nova] Cannot (live)migrate due to host mismatch?
by sinan86polat＠gmail.com 20 Jun '24

20 Jun '24

Hello, When I try to live migrate a VM and specify a target host, I am getting the following: $ openstack server migrate <id> --live --os-compute-api-version 2.30 --host hypervisor-05 No valid host was found. There are not enough hosts available. (HTTP 400) (Request-ID: req-bee8f8b1-7218-4ae7-aa71-c4e5a3a84ba5) And the following is logged in nova-scheduler: No hosts matched due to not matching requested destination (hypervisor-05, hypervisor-05.sub.domain.com) When I do "openstack hypervisor list" I see my hypervisors with its fqdn (hypervisor-05.sub.domain.com) So, it might be a mismatch in the nova database? How do I verify and correct it?

2 2

[qa] Cancel office hour on odd weeks
by Martin Kopec 20 Jun '24

20 Jun '24

Hi everyone, I'm going to cancel office hours every odd week, at least during the summer, due to a small attendance. Office hours will be held biweekly every Tuesday (even weeks) at 15:00 UTC. The other time slot we had, Wednesday biweekly at 17:00 UTC (odd weeks), is cancelled for now. Thank you, -- Martin Kopec Principal Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 0