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

OpenStack User Survey
by Jimmy McArthur 12 Aug '22

12 Aug '22

Hi Everyone - Just a quick reminder to please take the OpenStack User Survey [1] This vitally important survey provides direct, anonymized feedback to our Project Teams to help them build better software. If you run a deployment, no matter the size, please take 30 min out of your day to take this survey! Thank you, Jimmy [1] https://openstack.org/user-survey/

1 0

[release] Release countdown for week R-7, Aug 15 - 19
by Előd Illés 12 Aug '22

12 Aug '22

Development Focus ----------------- We are entering the last weeks of the Zed development cycle. From now until the final release, we'll send a countdown email like this every week. It's probably a good time for teams to take stock of their library and client work that needs to be completed yet. The non-client library freeze is coming up, followed closely by the client lib freeze. Please plan accordingly to avoid any last minute rushes to get key functionality in. General Information ------------------- Next week is the Extra-ATC freeze, in preparation for elections. All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. Please list active contributors to your project team who do not have a code contribution this cycle, and therefore won't automatically be considered an Active Technical Contributor and allowed to vote. This is done by adding extra-atcs to https://opendev.org/openstack/governance/src/branch/master/reference/projec… before the Extra-ATC freeze on August 18th, 2022. A quick reminder of the upcoming 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 25th, 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 (September 15th, 2022) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (September 29th, 2022) Finally, now is also a good time to start planning what highlights you want for your deliverables in the cycle highlights. The deadline to submit an initial version for those is set to Feature freeze (September 1st, 2022). Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html Project Team Guide, Cycle-Highlights: https://docs.openstack.org/project-team-guide/release-management.html#cycle… knelson [at] openstack.org/diablo_rojo on IRC is available if you need help selecting or writing your highlights Upcoming Deadlines & Dates -------------------------- Extra-ATC freeze: August 18th, 2022 (R-7 week) Non-client library freeze: August 25th, 2022 (R-6 week) Client library freeze: September 1st, 2022 (R-5 week) Zed-3 milestone: September 1st, 2022 (R-5 week) Next PTG: October 17-21, 2022 (virtual PTG!!!) Előd Illés irc: elodilles

1 0

[tripleo] gate blocker tripleo-ci-centos-9-undercloud-upgrade
by Marios Andreou 12 Aug '22

12 Aug '22

o/ tripleo please hold rechecks on master tripleo branch - we have a gate blocker for tripleo-ci-centos-9-undercloud-upgrade https://bugs.launchpad.net/tripleo/+bug/1984175 package/conflict/mirror issue not clear yet - grateful for pointers if you have them

5 10

About the meaning of compute nodes
by 정재철 11 Aug '22

11 Aug '22

If there are many nodes, is it possible to create a high-performance VM? (e.g. Can 2 1 core cpu nodes create 1 2 core cpu VM)

5 5

[tc] August 2022 OpenInfra Board Sync
by Jeremy Stanley 11 Aug '22

11 Aug '22

The Open Infrastructure Foundation Board of Directors is endeavoring to engage in regular check-ins with official OpenInfra projects. The goal is for a loosely structured discussion one-hour in length, involving members of the board and the OpenStack TC, along with other interested community members. This is not intended to be a formal presentation, and no materials need to be prepared in advance. I've started an Etherpad where participants can brainstorm potential topics of conversation, time-permitting: https://etherpad.opendev.org/p/2022-08-board-openstack-sync I've also created a Framadate poll has in order to identify a few preferred dates and times. Responses must be submitted by Friday, 2022-07-15, in order to provide the board members with time to pick from the available options. The poll can be found here: https://framadate.org/atdFRM8YeUtauSgC Feel free to reply here on the mailing list, or you can reach out to me directly by E-mail or as fungi in the #openstack-tc IRC channel, with any questions you may have. -- Jeremy Stanley

1 3

[kolla] Best way to restart controllers
by Yves Gd 11 Aug '22

11 Aug '22

Hi all, We are looking for the best way to process system upgrades on our controller nodes and especially the best way to restart them (we have 3 controllers nodes with routers ha). If we just restart them one by one (waiting long time between each), we have already seen rabbitmq cluster errors (needing a complete restart of rabbitmq). With a kolla stop, a restart and a kolla deploy, some docker containers are restarted on others nodes. The administration guides describes how to add or remove a node but not this simple case. How do you proceed securely? Thanks for all, Yves

1 0

[all][tc] Technical Committee next weekly meeting on 2022 Aug 11 at 1500 UTC
by Ghanshyam Mann 10 Aug '22

10 Aug '22

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

1 1

[cinder] Bug deputy report for week of 08-10-2022
by Sofia Enriquez 10 Aug '22

10 Aug '22

This is a bug report from 08-03-2022 to 08-10-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1984169 "RBD pool stats are reported inaccurately." Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1984000 "Infinidat Cinder driver consistency groups feature is broken." Fix proposed to master. 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

[neutron][ovn] ovn-bgp-agent EVPN mode question
by Satish Patel 10 Aug '22

10 Aug '22

Folks, I am trying to set up the following lab and so far everything looks good and working but I have some doubts or questions to make sure it's really working as expected. Lab Ref: https://ltomasbo.wordpress.com/2021/06/25/openstack-networking-with-evpn/ rack-1-host-1 (controller) rack-1-host-2 (compute1 - This is hosting cr-lrp ports, inshort router) rack-2-host-1 (compute2) I have created two vms vagrant@rack-1-host-1:~$ nova list nova CLI is deprecated and will be a removed in a future release +--------------------------------------+------+--------+------------+-------------+--------------------------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+------+--------+------------+-------------+--------------------------------------+ | aecb4f10-c46f-4551-b112-44e4dc007e88 | vm1 | ACTIVE | - | Running | private-test=10.0.0.105 | | ceae14b9-70c2-4dbc-8071-0d64d9a0ca84 | vm2 | ACTIVE | - | Running | private-test=10.0.0.86, 172.16.1.200 | +--------------------------------------+------+--------+------------+-------------+--------------------------------------+ # on rack-1-host-2 when i spun up vm2 which endup on rack-1-host-2 hence it created vrf-2001 on dummy lo-2001 interface and exposed vm2 ip address 10.0.0.86/32 96: vrf-2001: <NOARP,MASTER,UP,LOWER_UP> mtu 65575 qdisc noqueue state UP group default qlen 1000 link/ether 22:cc:25:b3:7b:96 brd ff:ff:ff:ff:ff:ff 97: br-2001: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vrf-2001 state UP group default qlen 1000 link/ether 0a:c3:23:7a:8f:0c brd ff:ff:ff:ff:ff:ff inet6 fe80::851:67ff:fe64:b2c3/64 scope link valid_lft forever preferred_lft forever 98: vxlan-2001: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-2001 state UNKNOWN group default qlen 1000 link/ether 0a:c3:23:7a:8f:0c brd ff:ff:ff:ff:ff:ff inet6 fe80::8c3:23ff:fe7a:8f0c/64 scope link valid_lft forever preferred_lft forever 99: lo-2001: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue master vrf-2001 state UNKNOWN group default qlen 1000 link/ether d6:60:da:91:2e:6d brd ff:ff:ff:ff:ff:ff inet 10.0.0.86/32 scope global lo-2001 valid_lft forever preferred_lft forever inet6 fe80::d460:daff:fe91:2e6d/64 scope link valid_lft forever preferred_lft forever # on rack-2-host-1 when i created vm1 which endup on rack-2-host-1 but it doesn't expose the vm ip address. Is that normal behavior? When I attach a floating ip to vm2 then why does my floating ip address not get exposed in BGP? Thank you in advance

1 0

Openstack Graphical processors virtualisation
by KK CHN 10 Aug '22

10 Aug '22

1. Does Openstack support GPU virtualization ? We are running a cloud using ussuri with KVM hypervisors. Is creation of vGPUs possible? Does KVM support GPU virtualization or any limitations? 2. What are the supported GPU types? (GRID GPU or GPUs attached to physical blades ) 3. If it supports GPU attached to physical blades, will live migration of the VM be supported. Will OpenStack be able to identify the next host which has an attached GPU and perform live migration, in case of the Failure of One Blade with attached GPU with resident VM. 4. What are the virtualization options if vGPU options are not supported by a particular GPU model? Thanks in advance, Krish

4 4

[PTG] [ironic] Antelope PTG new Etherpad
by Iury Gregory 10 Aug '22

10 Aug '22

Hello everyone, We changed the etherpad link to track the topics we will discuss at the PTG, instead of https://etherpad.opendev.org/p/ironic-ptg-planing-Columbus-OH we will be using https://etherpad.opendev.org/p/ironic-antelope-ptg Feel free to add any topics =) -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL * *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 0

Need help on rabbitmq
by AJ_ sunny 10 Aug '22

10 Aug '22

Hi team I am using kolla-ansible based openstack infra and getting below error in logs seems frequent rabbitmq disconnections <0.5023.16> closing AMQP connection <0.5023.16> (10.80.0.13:40356 -> 10.80.0.13:5672 - mod_wsgi:19:d3196668-57e5-46dc-8b69-78d73b5873a0): missed heartbeats from client, timeout: 60s AMQP server on 10.80.0.13:5672 is unreachable: [Errno 104] Connection reset by peer. Trying again in 1 seconds.: ConnectionResetError: [Errno 104] Connection reset by peer Is this bug or any resolution for fixing this issue? Thanks Arihant Jain

4 4

[tacker] IRC meeting on Aug 16 cancelled
by Yasufumi Ogawa 10 Aug '22

10 Aug '22

Hi team, Since many of us are going to have a vacation next week, I'll cancel the meeting on Aug 16th. Thanks, Yasufumi

1 0

Correct way to add firewall rules in tripleo | Wallaby
by Swogat Pradhan 10 Aug '22

10 Aug '22

Hi, I am trying to add a rule for zabbix in my tripleo wallaby setup on top of centos 8 stream. i followed https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/feature… but got the error message: [ERROR]: Failed, module return: {'msg': 'value of action must be one of: append, insert, got: accept', 'failed': True, 'invocation': {'module_args': {'state': 'present', 'action': 'accept', 'jump': 'ACCEPT', 'chain': 'INPUT', 'protocol': 'tcp', 'source': '172.25.161.50', 'ctstate': ['NEW'], 'ip_version': 'ipv4', 'comment': '301 allow zabbix ipv4', 'destination_port': '10050', 'table': 'filter', 'match': [], 'syn': 'ignore', 'flush': False}}, 'warnings': ["The value 10050 (type int) in a string field was converted to '10050' (type string). If this does not look like what you expect, quote the entire value to ensure it does not change."], '_ansible_parsed': True} [ERROR]: Failed, return data: {'stdout': None, 'stderr': None, 'msg': 'value of action must be one of: append, insert, got: accept', 'cmd': None, 'rc': 0, 'failed': True} 2022-07-21 01:27:33.335477 | 48d539a1-1679-1e80-25fd-000000005aa1 | TASK | Manage firewall rules 2022-07-21 01:27:33.351515 | 48d539a1-1679-1e80-25fd-000000005542 | FATAL | Manage firewall rules | overcloud-controller-0 | error={"changed": false, "cmd": null, "msg": "value of action must be one of: append, insert, got: accept", "rc": 0, "stderr": null, "stdout": null} When i tried the following link: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15… <https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15…> my script is running fine but rules are not updated in iptables for zabbix. Can you please suggest a correct approach to open port 10050 in tripleo? With regards, Swogat Pradhan

2 1

Security vulnerabilities in Horizon dashboard | Openstack Wallaby | Tripleo | Openstack Horizon
by Swogat Pradhan 09 Aug '22

09 Aug '22

Hi, I am setting up an openstack wallaby cloud for a client using tripleo. After setting everything up the client ran a WEB scan and found some vulnerabilities (attached snapshot for reference). Can you please guide me on how to fix these vulnerabilities in the dashboard service? With regards, Swogat pradhan

2 3

[openstack-ansible] Meeting on August 16 is cancelled
by Dmitriy Rabotyagov 09 Aug '22

09 Aug '22

Hi everyone, Since several core participants won't be able to present at the meeting it was decided to cancel the Team meeting on 16th of August 2022.

1 0

[nova] Review guide for PCI tracking for Placement patches
by Balazs Gibizer 09 Aug '22

09 Aug '22

Hi Nova, The first batch of patches are up for review for the PCI tracking for Placement feature. These mostly covers two aspects of the spec[1]: 1) renaming [pci]passthrough_whitelist to [pci]device_spec 2) pci inventory reporting to placement, excluding existing PCI allocation healing in placement This covers the first 4 sub chapters of Proposed Change chapter of the spec[1] up until "PCI alias configuration". I noted intentional deviations from the spec in the spec review [2] and I will push a follow up to the spec at some point fixing those. I tried to do it in small steps hence the long list of commits[3]: #2) pci inventory reporting to placement, excluding existing PCI allocation healing in placement 5827d56310 Stop if tracking is disable after it was enabled before a4b5788858 Support [pci]device_spec reconfiguration 10642c787a Reject devname based device_spec config b0ad05fb69 Ignore PCI devs with physical_network tag f5a34ee441 Reject mixed VF rc and trait config c60b26014f Reject PCI dependent device config 5cf7325221 Extend device_spec with resource_class and traits eff0df6a98 Basics for PCI Placement reporting #1) renaming [pci]passthrough_whitelist to [pci]device_spec adfe34080a Rename whitelist in tests ea955a0c15 Rename exception.PciConfigInvalidWhitelist to PciConfigInvalidSpec 55770e4c14 Rename [pci]passthrough_whitelist to device_spec There is a side track branching out from "adfe34080a Rename whitelist in tests" to clean up the device spec handling[4]: 514500b5a4 Move __str__ to the PciAddressSpec base class 3a6198c8fb Fix type annotation of pci.Whitelist class f70adbb613 Remove unused PF checking from get_function_by_ifname b7eef53b1d Clean up mapping input to address spec types 93bbd67101 Poison /sys access via various calls in test 467ef91a86 Remove dead code from PhysicalPciAddress 233212d30f Fix PciAddressSpec descendants to call super.__init__ ad5bd46f46 Unparent PciDeviceSpec from PciAddressSpec cef0d2de4c Extra tests for remote managed dev spec 2fa2825afb Add more test coverage for devname base dev spec adfe34080a Rename whitelist in tests This is not a mandatory part of the feature but I think they improve the code in hand and even fixing some small bugs. I will continue with adding allocation healing for existing PCI allocations. Any feedback is highly appreciated. Cheers, gibi [1] https://specs.openstack.org/openstack/nova-specs/specs/zed/approved/pci-dev… [2] https://review.opendev.org/c/openstack/nova-specs/+/791047 [3] https://review.opendev.org/q/topic:bp/pci-device-tracking-in-placement [4] https://review.opendev.org/q/topic:bp/pci-device-spec-cleanup

1 2

[publiccloud-sig] A new start for Public Cloud SIG
by Tobias Rydberg 09 Aug '22

09 Aug '22

Hi everyone, In Berlin it became clear that there is a big interest in restarting the Public Cloud SIG. Thank you all for your contributions in that forum session [0] and the interest in participating in the work of this SIG. A lot of good ideas of what we should focus on was identified, with a clear focus of interoperability and standardization, to make the experience of using OpenStack as an end-user even better. Standardization of images and flavors - naming, metadata etc - being one of them, working closely with InterOp WG regarding the checks and governance of the OpenStack Powered Program another. The ultimate goal could be to reach a state where it is possible to start to federate between the public clouds, but for that to be possible on a more global scale we need to start with aligning the simple things. To kick this off, we will start with bi-weekly IRC meetings again, shape the goals kick of some work towards identified goals. Since we have an IRC channel (#openstck-publiccloud) my suggestion is that we will start there. Let's decide on suggestions for day and time for our bi-weekly meetings during the kick off meeting. Kick off meeting =========== When: Wednesday 10th of August at 1400 UTC Where: IRC in channel #openstack-publiccloud I created an etherpad for our first meeting [1], feel free to add items to the agenda or other suggestions on goals etc that you might have prior to the meeting. Hope to see at IRC in August! [0] https://etherpad.opendev.org/p/berlin-summit-future-public-cloud-sig [1] https://etherpad.opendev.org/p/publiccloud-sig-kickoff BR, Tobias Rydberg

2 2

[announcement] [debian] Debian Buster with OpenStack Rocky will receive LTS support
by Thomas Goirand 08 Aug '22

08 Aug '22

Hi! After some discussion with the folks taking care of the Debian LTS project, we decided that we will attempt to support OpenStack Rocky, running on Debian 10 (aka: Buster), for another 2 years, together with the rest of the distribution. In the past, we decided that we wouldn't do it, and that OpenStack would be part of the list of unsupported packages, because it was too difficult to maintain. However, it is my opinion that this has changed, because: - The codebase is evolving slower - I do have all the tooling to re-do a Rocky deployment if needed - There's a lot less CVE per year than it used to be (10 years ago, it was 1 every 2 weeks on average, now we have like 2 grave issue per year...). - I'm confident that if there's a grave issue, I'll be able to find help from the this wonderful community (it happened in the past...). Also, some sponsors of the Debian LTS project are actually running OpenStack Rocky on Debian. So it makes sense to help them. It is to be noted that I will not be the person doing the actual security backports, but I'll be there in case the person doing it needs help from me (for example, to do a deployment and manual regression testing). Hoping this will help OpenStack users running on Debian, Cheers, Thomas Goirand (zigo)

1 0

[all] Automatic update of Python jobs in Zuul project configuration
by Pierre Riteau 08 Aug '22

08 Aug '22

Hello, A patch submitted to python-blazarclient by yoctozepto [1] made me realise the automatic change of Python jobs from yoga to zed missed various repositories [2], mostly python clients. Is there a reason for this? Also, one can easily find projects which are using even older job templates (xena or earlier). Thanks, Pierre Riteau (priteau) [1] https://review.opendev.org/c/openstack/python-blazarclient/+/851903 [2] https://codesearch.openstack.org/?q=openstack-python3-yoga-jobs&i=nope&lite…

3 6

[kolla-ansible] why does not the bootstrap create the docker bridge?
by wodel youchi 08 Aug '22

08 Aug '22

Hi, The bootstrap installs docker but it does not create the docker bridge, why? Regards.

2 1

[Oslo] IRC meeting.
by Daniel Mats Niklas Bengtsson 08 Aug '22

08 Aug '22

Hi there, I'm sorry, I was on vacation and then I had personal problems. We are still in the summer period and I think there are still people on vacation, I suggest resuming meetings in September. What do you think?

1 0

[neutron] Bug Deputy Report August 01 - 07
by Elvira Garcia Ruiz 08 Aug '22

08 Aug '22

Hi, I was the bug deputy last week. Find the summary below: High: ------- - [ovn]router_interface port probability cannot be up https://bugs.launchpad.net/neutron/+bug/1983530 Fix: https://review.opendev.org/c/openstack/neutron/+/851997 - l2_pop does unnecessary db fetches for incompatible network types https://bugs.launchpad.net/neutron/+bug/1983558 Fix: https://review.opendev.org/c/openstack/neutron/+/852089 Medium: ----------- - [OVN] Old DNS servers are served by DHCP after dns_servers option is updated https://bugs.launchpad.net/neutron/+bug/1983270 Assigned to me Low: ------- - Neutron should clean up ACLs in OVN NB DB when a remote security group is deleted https://bugs.launchpad.net/neutron/+bug/1983600 Unassigned Kind regards! Elvira

1 0

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

08 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