August 2022 - openstack-discuss - lists.openstack.org

[Cinder][NFS][Openstack-Ansible]
by Dave Hall 07 Aug '22

07 Aug '22

Hello, I seem to have gotten myself in a bit of a mess trying to set up Cinder with an NFS back-end. After working with Glance and NFS, I started on Cinder. I noticed immediately that there weren't any NFS mounts in the Cinder-API containers like there were in the Glance-API containers. Also that there were no NFS packages in the Cinder-API containers. In reading some Cinder documentation, I also got the impression that each Cinder host/container needs to have its own NFS store. Pawing through the playbooks and documentation I saw that unlike Glance, Cinder is split into two pieces - Cinder-API and Cinder-Volume. I found cinder-volume.yml.example in env.d, activated it, and created Cinder-Volume containers on my 3 infra hosts. I also created 3 separate NFS shares and changed the storage-hosts section of my openstack_user_config.yml accordingly. After this I found that while I was able to create volumes, the prep_volume part of launching an instance was failing. Digging in, I found: # openstack volume service list +------------------+-------------------------------------------------------+------+---------+-------+----------------------------+ | Binary | Host | Zone | Status | State | Updated At | +------------------+-------------------------------------------------------+------+---------+-------+----------------------------+ | cinder-volume | C6220-9@nfs_volume | nova | enabled | down | 2022-07-23T02:46:13.000000 | | cinder-volume | C6220-10@nfs_volume | nova | enabled | down | 2022-07-23T02:46:14.000000 | | cinder-volume | C6220-11@nfs_volume | nova | enabled | down | 2022-07-23T02:46:14.000000 | | cinder-scheduler | infra36-cinder-api-container-da8e100f | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-scheduler | infra38-cinder-api-container-27219f93 | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-scheduler | infra37-cinder-api-container-ea7f847b | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-volume | C6220-9@nfs_volume1 | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-volume | infra37-cinder-volumes-container-5b9635ad@nfs_volume | nova | enabled | down | 2022-08-04T18:32:53.000000 | | cinder-volume | infra36-cinder-volumes-container-77190057@nfs_volume1 | nova | enabled | down | 2022-08-06T13:03:03.000000 | | cinder-volume | infra38-cinder-volumes-container-a7bcfc9b@nfs_volume | nova | enabled | down | 2022-08-04T18:32:53.000000 | | cinder-volume | infra37-cinder-volumes-container-5b9635ad@nfs_volume2 | nova | enabled | down | 2022-08-06T13:03:05.000000 | | cinder-volume | C6220-10@nfs_volume2 | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-volume | C6220-11@nfs_volume3 | nova | enabled | up | 2022-08-06T13:29:10.000000 | | cinder-volume | infra38-cinder-volumes-container-a7bcfc9b@nfs_volume3 | nova | enabled | down | 2022-08-06T13:03:03.000000 | +------------------+-------------------------------------------------------+------+---------+-------+----------------------------+ Thinking I could save this, I used containers-lxc-destroy.yml to destroy my cinder-volumes containers and deactivated cinder-volume.yml.example. Then I ran setup-hosts.yml, which has restored the cinder-volumes containers even though is_metal: false has been removed. Clearly a stronger intervention will be required. I would like to fully get rid of the cinder-volumes containers and go back to an is_metal: true scenario. I also need to get rid of the unnumbered nfs_volume referenes, which I assume are in some cinder config file somewhere. Below is a clip from my openstack_user_config.yml: storage_hosts: infra36: ip: 172.29.236.36 container_vars: cinder_backends: nfs_volume1: volume_backend_name: NFS_VOLUME1 volume_driver: cinder.volume.drivers.nfs.NfsDriver nfs_mount_options: "rsize=65535,wsize=65535,timeo=1200,actimeo=120" nfs_shares_config: /etc/cinder/nfs_shares_volume1 shares: - { ip: "172.29.244.27", share: "/NFS_VOLUME1" } infra37: ip: 172.29.236.37 container_vars: cinder_backends: nfs_volume2: volume_backend_name: NFS_VOLUME2 volume_driver: cinder.volume.drivers.nfs.NfsDriver nfs_mount_options: "rsize=65535,wsize=65535,timeo=1200,actimeo=120" nfs_shares_config: /etc/cinder/nfs_shares_volume2 shares: - { ip: "172.29.244.27", share: "/NFS_VOLUME2" } infra38: ip: 172.29.236.38 container_vars: cinder_backends: nfs_volume3: volume_backend_name: NFS_VOLUME3 volume_driver: cinder.volume.drivers.nfs.NfsDriver nfs_mount_options: "rsize=65535,wsize=65535,timeo=1200,actimeo=120" nfs_shares_config: /etc/cinder/nfs_shares_volume3 shares: - { ip: "172.29.244.27", share: "/NFS_VOLUME3" } Any advice would be greatly appreciated. Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

4 8

Guide for Openstack installation with HA, OVN ?
by 박경원 07 Aug '22

07 Aug '22

3 2

[release] Release countdown for week R-8, Aug 08 - 12
by Előd Illés 05 Aug '22

05 Aug '22

General Information ------------------- The following cycle-with-intermediary deliverables have not done any intermediary release yet during this cycle: Ironic: * bifrost * ironic-prometheus-exporter * ironic-python-agent-builder * ironic-ui * networking-baremetal * networking-generic-switch OpenStackSDK: * python-openstackclient Swift: * swift Since these deliverables are traditionally released after our warning, we did not propose to change the release model to cycle-with-rc for them this time. Please let us know if any of the above project is considering the release model change anyway and we propose those patches. Otherwise immediately release an intermediary release, or acknowledge that a release needs to be done before RC1! We also published a proposed release schedule for the upcoming Antelope cycle. Please check out the separate thread: https://lists.openstack.org/pipermail/openstack-discuss/2022-July/029767.ht… 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

[charms] General release of charmhub OpenStack xena/stable, ceph pacific/stable, OVN 21.09/stable tracks for Ubuntu 20.04 (focal) LTS
by Alex Kavanagh 05 Aug '22

05 Aug '22

Hi All The title may seem a bit odd because surely yoga is the current release, and zed is the current cycle? This is true, so a little explanation is in order. As the charm-guide [1] explains, in the previous cycle, the OpenStack, and supporting, charms moved from a single stable charm (for each component) that supported multiple releases, to a charm+track that targets a specific release [2]. The current release for the OpenStack charms is 'yoga' and thus there is a yoga/stable track. For a full explanation, please see [1]. Today, as part of our ongoing charmhub stable migration work this cycle, we have (re)released the 21.10 charms (that supported queens -> xena) as "xena" charms for OpenStack, "pacific" charms for Ceph, and "21.09" charms for OVN. The xena, pacific and 21.09-OVN channel charms have the same features as the existing 21.10 charms, include bug-fixes and relevant backports since the 21.10 charms were released, and have been re-tested and verified as a set prior to being released to the xena/stable channel. The full list of charms for a "Xena" OpenStack system, including ceph, OVN, mysql8, hacluster, rabbitmq-server, vault and others can be seen in the docs at [3]. The xena/pacific/21.09 charms have been designed to be upgradable from the 21.10 charms if you are running a xena OpenStack, but please consult the docs [4] about how to go about upgrading charms. The charms also are able to perform the OpenStack upgrade from wallaby -> xena, and again please consult the docs [5] for upgrading OpenStack. Our next stable maintenance release will be wallaby/pacific/20.12 (ovn), so please keep an eye out on the mailing lists. Thanks! [1] https://docs.openstack.org/charm-guide/latest/project/charm-delivery.html [2] https://juju.is/docs/olm/deploy-a-charm-from-charmhub#heading--specify-a-ch… [3] https://docs.openstack.org/charm-guide/latest/project/charm-delivery.html#c… [4] https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/late… [5] https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/late… -- Alex Kavanagh - Software Engineer OpenStack Engineering - Data Centre Development - Canonical Ltd

1 0

[all][tc] What's happening in Technical Committee: summary 2022 Aug 5: Reading: 5 min
by Ghanshyam Mann 05 Aug '22

05 Aug '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Aug 4. Most of the topics I am summarizing in this email. This was a video call and recordings are available @https://www.youtube.com/watch?v=2CFrDKJsnEY * Next TC weekly meeting will be on Aug 11 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Aug 10. 2. What we completed this week: ========================= * Added charmed k8s operators to OpenStack Charms[2] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[3], Two are completed and others items are in-progress. Open Reviews ----------------- * Three open reviews for ongoing activities[4]. 2023.1 cycle Technical Election (TC + PTL) planning ------------------------------------------------------------- As we are in the R-9 week, its time to plan for the 2023.1 cycle election. As first step, we have volunteer to help executing this election. In TC meeting, Amy, Knikolla, and Slaweq volunteer to help and Ian might be available any ways. If you would like to get involved in the elections help, please let us know in #openstack-tc IRC channel. 2023.1 cycle TC PTG planning ------------------------------------ In TC meeting, we were gathering the data on who all will be traveling to in-person PTG or we should consider virtual PTG. But as you might have seen the announcement today, coming PTG will be 100% virtual[5]. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[6]. Feel free to check and provide feedback. Zed cycle Leaderless projects ---------------------------------- Dale Smith volunteer to be PTL for Adjutant project [7] Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[8][9]. Project updates ------------------- * Retire openstack-helm-addons[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/+/849997 [3] https://etherpad.opendev.org/p/tc-zed-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029879.… [6] https://review.opendev.org/c/openstack/governance/+/836888 [7] https://review.opendev.org/c/openstack/governance/+/849606 [8] https://etherpad.opendev.org/p/zuul-config-error-openstack [9] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [10] https://review.opendev.org/c/openstack/governance/+/849997 [11] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [12] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Fwd: October PTG Update
by Kendall Nelson 05 Aug '22

05 Aug '22

Hello Everyone, I wanted to provide an update on the October Project Teams Gathering (PTG). After discussing with community members and prospective sponsors, we have made the decision to pivot the event to 100% virtual to be as inclusive as possible. I know that this is not the ideal outcome and there are a lot of factors contributing to this decision, but we think it’s the best decision for the global community at this time. We are continuing to receive feedback on the value and importance of in-person PTGs; we just need to wait for other factors to be less of an obstacle If you have already registered, you should have been contacted for a full refund. We are going to use the same week for a virtual PTG and it will be free to attend, just like the previous ones. The registration is already live [1]. If you have any questions or feedback on this decision, please let us know. We will continue to monitor feedback as we make plans for a 2023 PTG. Thank you, Kendall (diablo_rojo) [1] https://openinfra-ptg.eventbrite.com

1 0

[manila] Feature Proposal Freeze in effect
by Carlos Silva 05 Aug '22

05 Aug '22

Greetings, Zorillas and interested stackers! As we defined in the release schedule, this week is the Manila Feature Proposal Freeze [1]. It means that all featureful changes should be already proposed and substantially completed with unit, functional and integration tests by EOW. If you have not managed to submit your featureful changes to gerrit yet, and would like to request an exception, please let me know by responding to this email thread. In case your exception is granted, we can get you some extra time. [1] https://releases.openstack.org/zed/schedule.html#z-manila-fpfreeze Thank you! carloss

1 0

[openstack] how to speed up live migration?
by Ignazio Cassano 05 Aug '22

05 Aug '22

Hello All, I am looking for a solution to speed up live migration. Instances where ram is used heavily like java application servers, live migration take a long time (more than 20 minutes for 8GB ram instance) and converge mode is already set to True in nova.conf. I also tried with post_copy but it does not change. After the first live migration (very solow) if I try to migrate again it is very fast. I presume the first migration is slow because memory fragmentation when an instance is running on the same compute node for a long time. I am looking for a solution considering the on my computing node I can have a little ram overcommit. Any case I am increasing the number of compute nodes to reduce it. Thanks Ignazio

6 21

[tripleo] gate blocker - tripleo-ci-centos-9-content-provider-wallaby
by Ananya Banerjee 05 Aug '22

05 Aug '22

Hi, We have a failure in tripleo-ci-centos-9-content-provider-wallaby which is blocking the gate. We are reverting [1] to clear the gate. Related Bug : https://bugs.launchpad.net/tripleo/+bug/1983585 [1] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/multi-node-bridg… Thanks, Ananya -- Ananya Banerjee, RHCSA, RHCE-OSP Software Engineer Red Hat EMEA <https://www.redhat.com/> anbanerj(a)redhat.com M: +491784949931 IM: frenzy_friday @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/>

2 1

Large files multipart upload fails - OpenStack Object Storage (swift)
by Komarov, Aleksandr 05 Aug '22

05 Aug '22

Hi to all! Please suggest how to fix the situation. When uploading files larger than 100GB, at the stage of multipart-manifest validation, we get 404 error for some segments that were previously uploaded successfully. As a result, the client receives a 400 response. Uploading a large file is not possible. Logs: Aug 1 13:18:30 swift01-object01 object-server: IP - - [01/Aug/2022:13:18:30 +0000] "PUT /mpathc/12130/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucket/.file-segments/150.file/000 00032" 201 - "PUT http://domain-name/v1/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucket/.file-se…" "tx30e82374b98845bab6883-0062e7d225" "proxy-server 8367" 128.7641 "-" 21577 0 Aug 1 13:18:30 swift01-object01 container-server: IP - - [01/Aug/2022:13:18:30 +0000] "PUT /mpathb/952/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucket/.file-segments/150.file/00 000032" 201 - "PUT http://domain-name/mpathe/12130/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucke…" "tx30e82374b98845bab6883-0062 e7d225" "object-server 24710" 0.0005 "-" 13211 0 Aug 1 14:01:46 swift01-object01 object-server: IP - - [01/Aug/2022:14:01:46 +0000] "HEAD /mpathc/12130/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucket/.file-segments/150.file/00000032" 404 - "HEAD http://domain-name/v1/AUTH_5affc785b3454cddb2d1f69ce62b4441/bucket/.file-se…" "txf09676de38964ca299b77-0062e7dcc8" "proxy-server 8367" 0.0003 "-" 21579 0 At the same time, some segments successfully found. With files less than 50GB everything is fine.

2 2