July 2021 - openstack-discuss - lists.openstack.org

[all][tc] OpenStack next release name is final- "OpenStack Yoga"
by Ghanshyam Mann 08 Jul '21

08 Jul '21

Hello Everyone, We have the final name selected for the OpenStack next release name. Its "OpenStack Yoga". As per the release name criteria[1], selection of release name is gone through three steps: Step1: Name nomination from community members[2]. Step2: TC voted on the nominated names[3]. Step3: Trademark checks by Foundation on winners from TC votes. In trademark check, “Yoga” is finalized as the best bet for this release. Thanks community members to participating in name nomination, TC to vote and Foundation for performing the trademark checks. "Yoga" is now good signal to extend our exercise and be more fit in Yoga cycle :) [1] https://governance.openstack.org/tc/reference/release-naming.html#release-n… [2] https://wiki.openstack.org/wiki/Release_Naming/Y_Proposals [3] https://civs1.civs.us/cgi-bin/results.pl?id=E_f065453ffd2537cb -gmann

4 6

[kolla] Date for the release of 10.2.1 ussuri (stable)
by KIM 1 Guy 08 Jul '21

08 Jul '21

Dear all, We are using the ansible kolla with the release 10.2.0. We are planning to upgrade it. So I would like to know when the stable 10.2.1 is released. On 10.2.1 "ussuri" : kolla-ansible (launchpad.net)<https://launchpad.net/kolla-ansible/+milestone/10.2.1>, the release date is not mentioned. Thank you in advance for your answer. Kind regards, Guy KIM This message and any attachments (the "message") is intended solely for the intended addressees and is confidential. If you receive this message in error,or are not the intended recipient(s), please delete it and any copies from your systems and immediately notify the sender. Any unauthorized view, use that does not comply with its purpose, dissemination or disclosure, either whole or partial, is prohibited. Since the internet cannot guarantee the integrity of this message which may not be reliable, BNP PARIBAS (and its subsidiaries) shall not be liable for the message if modified, changed or falsified. Do not print this message unless it is necessary, consider the environment. ---------------------------------------------------------------------------------------------------------------------------------- Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur ou s'il ne vous est pas destine, merci de le detruire ainsi que toute copie de votre systeme et d'en avertir immediatement l'expediteur. Toute lecture non autorisee, toute utilisation de ce message qui n'est pas conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite. L'Internet ne permettant pas d'assurer l'integrite de ce message electronique susceptible d'alteration, BNP Paribas (et ses filiales) decline(nt) toute responsabilite au titre de ce message dans l'hypothese ou il aurait ete modifie, deforme ou falsifie. N'imprimez ce message que si necessaire, pensez a l'environnement.

2 1

[kolla] PTL away next week, meeting cancelled
by Mark Goddard 08 Jul '21

08 Jul '21

Hi, I'm away from 12th - 16th July. As several other cores are also away, we agreed to cancel the meeting on 14th July. Thanks, Mark

1 0

[Neutron] PTL on holiday
by Slawek Kaplonski 07 Jul '21

07 Jul '21

Hi, I will be on PTO from 9.07 and I will be back on Monday 19.07.2021. For anything related to Neutron, please reach out to our drivers team [1] or core team [2]. For any release related things, please reach out to Akihiro who is our release liaison. Due to my holidays I'm also canceling our next week's meetings. There will be no team meeting and ci meeting on Tuesday 13.07 and no drivers meeting on 16.07. Have a great week and see You back on Monday 19.07 :) [1] https://review.opendev.org/admin/groups/ 5b063c96511f090638652067cf0939da1cb6efa7,members [2] https://review.opendev.org/admin/groups/ 9b227d5d1b27471dacbe9a9161904ec115a74138,members -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[all][tc] Technical Committee next weekly meeting on July 8th at 1500 UTC
by Ghanshyam Mann 07 Jul '21

07 Jul '21

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

1 1

[kolla][wallaby][manila] ambiguous network
by Ignazio Cassano 07 Jul '21

07 Jul '21

Hello All, I configured manually manila on stein with generic driver and driver handle share server true without issues. When I create a share on a share network it creates a service instance and bla bla bla. Now I am using kolla wallaby and share.log gives "ambiguous network error" with generic manila driver and dhss true. It works fine with netapp driver but dhss true with generic is not working anyone. Any suggestion, please? Ignazio

1 0

[cinder] Bug deputy report for week of 2021-07-07
by Sofia Enriquez 07 Jul '21

07 Jul '21

Hello, This is a bug report from 2021-30-06 to 2021-07-07. You're welcome to join the Cinder Bug Meeting today. Weekly on Wednesday at 1500 UTC on #openstack-cinder Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium: - https://bugs.launchpad.net/cinder/+bug/1934480 "Cinder can not use system scope due to endpoint". Unassigned. Low: - https://bugs.launchpad.net/cinder/+bug/1934823 "[RBD] --pool is deprecated". Unassigned -->* low-hanging-fruit *good for Open Source day at Grace Hopper Celebration. - https://bugs.launchpad.net/cinder/+bug/1934459 "Enabling OSprofiler in a Openstack cluster with Element OS , runs into an infinite loop recursion". Unassigned Wishlist - https://bugs.launchpad.net/cinder/+bug/1934435 "Element/Cinder driver fails with multiple Timeout exceptions during Element OS upgrade". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1934168 "cinder matrix - clarification of snapshot attachment feature". Unassigned Cheers, Sofia -- L. 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

[wallaby][octavia] worker Read timeout
by Ignazio Cassano 07 Jul '21

07 Jul '21

Hello All, I installed octavia kolla wallaby and when I create a lod balancer it remains in pending create. The controller worker log reports: Could not connect to instance. Retrying.: requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='10.102.191.23', port=9443): Read timed out. (read timeout=10.0) I am sure the controller can contect the amphora agent on port 8443 (I tried with telnet 10.102.191.23 9443). On the amphora vm I read the following in /var/log/amphora-agent.log: ciphers: None raw_paste_global_conf: [] strip_header_spaces: False [2021-07-07 06:03:03 +0000] [610] [INFO] Starting gunicorn 20.0.4 [2021-07-07 06:03:03 +0000] [610] [DEBUG] Arbiter booted [2021-07-07 06:03:03 +0000] [610] [INFO] Listening at: http://[::]:9443 (610) [2021-07-07 06:03:03 +0000] [610] [INFO] Using worker: sync [2021-07-07 06:03:03 +0000] [637] [INFO] Booting worker with pid: 637 [2021-07-07 06:03:03 +0000] [610] [DEBUG] 1 workers [2021-07-07 06:03:16 +0000] [637] [DEBUG] Closing connection. [2021-07-07 06:03:31 +0000] [637] [DEBUG] Closing connection. [2021-07-07 06:03:47 +0000] [637] [DEBUG] Closing connection. Please, what is wrong ? Ignazio

1 1

[tripleo] TripleO CI Summary: Unified Sprint 45-46
by Bhagyashri Shewale 07 Jul '21

07 Jul '21

Greetings, The TripleO CI team has just completed **Unified Sprint 45-46** (Jun 10 thru to Jun 30 wed 2021). The following is a summary of completed work during this sprint cycle: - Continue to track upstream / rdo work on CentOS-Stream-9 - Utilize the dependency pipelines to track and test the latest patches - At this time upstream is holding for https://review.rdoproject.org/r/c/testproject/+/33878/ - Successfully deployed production promoter server on vexxhost using new code (next gen) promoter code <https://hackmd.io/team/rh-openstack-ci?nav=search&q=promoter> - Continue to adopt new changes and improvements in the promoter : - https://review.rdoproject.org/r/c/rdo-infra/ci-config/+/32135 - https://review.rdoproject.org/r/c/rdo-infra/ci-config/+/33815 - Instead of pip install use rpm of tripleo-ansible for deployment - https://review.opendev.org/q/topic:%22remove_uneeded_tq_requirements <https://review.opendev.org/q/topic:%22remove_uneeded_tq_requirements%22+(st…> - https://review.opendev.org/c/openstack/tripleo-quickstart/+/789787 - TripleO Repos: - Refactoring tripleo-repos to use cliff as command line framework https://review.opendev.org/c/openstack/tripleo-repos/+/794801 - Python/ansible module to set yum module information More details, use cases and design here: https://hackmd.io/mU1te45ASEWbnLqpSexB_Q?both https://review.opendev.org/q/topic:%22tripleo-yum-config <https://review.opendev.org/q/topic:%22tripleo-yum-config%22+(status:open%20…> - Tempest: - Tempest skiplist design for upstream and downstream https://hackmd.io/9tB-rw0EQ4uHZAaBjDsT4g - Augment and refine update/upgrade jobs in upstream periodic, integration, component pipelines - https://review.opendev.org/c/openstack/tripleo-ci/+/794571 - https://review.opendev.org/c/openstack/tripleo-ci/+/796771 - https://review.opendev.org/c/openstack/tripleo-ci/+/797865 - https://review.opendev.org/q/topic:wallaby-upgrade-jobs - Ruck-rover tooling: https://review.rdoproject.org/r/c/rdo-infra/ci-config/+/34060 The planned work for the next sprint and leftover previous sprint work as following: - Continue to track upstream / rdo work on CentOS-Stream-9 - Utilize the dependency pipelines to track and test the latest patches - At this time upstream is holding for https://review.rdoproject.org/r/c/testproject/+/33878/ - Continue to adopt new changes and improvements in the promoter code - elastic-recheck containerization - https://hackmd.io/dmxF-brbS-yg7tkFB_kxXQ - Openstack health for tripleo - https://hackmd.io/HQ5hyGAOSuG44Le2x6YzUw - Tripleo-repos spec and implementation - Python/ansible module to set yum module information More details, use cases and design here: https://hackmd.io/mU1te45ASEWbnLqpSexB_Q?both https://review.opendev.org/q/topic:%22tripleo-yum-config <https://review.opendev.org/q/topic:%22tripleo-yum-config%22+(status:open%20…> - https://hackmd.io/v2jCX9RwSeuP8EEFDHRa8g?view - Patrole stable release: - We require the logging resource client in tempest to test the patrole logging policy actions in patrole https://hackmd.io/rBqcts18Rc-qCOqe1DM1gg - Centos-8-stream rpm version lock: https://hackmd.io/iYAL3ueUTzWCHE5qFA6jVQ - Pip version lock: https://hackmd.io/5-IjvGr4RUqxNkJ3Yr6c3Q The Ruck and Rover for this sprint are Bhagyashri Shewale(bhagyashris) and Chandan Kumar (chandankumar). Please direct questions or queries to them regarding CI status or issues in #tripleo, ideally to whomever has the ‘|ruck’ suffix on their nick. Ruck/rover notes to be tracked in hackmd. Thanks, Bhagyashri Shewale

1 0

examples or docs about Slurm cloud bursting on OpenStack ?
by Pablo Escobar Lopez 07 Jul '21

07 Jul '21

Hi, I am exploring the option to use the Slurm elastic computing support ( https://slurm.schedmd.com/elastic_computing.html ) together with the Slurm configless support ( https://slurm.schedmd.com/configless_slurm.html ) to deploy dynamic Slurm clusters on OpenStack which can automatically grow and shrink. In a quick search I couldn't find any example or documentation which is specific to Slurm + Openstack. Does anyone has any experience on this specific topic? Can you point me to any documentation or examples? Thanks in advance for any help or advice. Regards, Pablo.

1 0

How the add public ip address to access dashboard
by Salman Sheikh 06 Jul '21

06 Jul '21

Hi all, Suppose in LAN the dashboard is accessible on 192.168.0.3/dashboard, if we want to access it on the internet public ip for ex:124.124.222.34. How can we do this, so it can be accessible through both ips192.168.0.3 and 124.124.22.34. And how we can remove /dashboard from the url. so it can be accessible on 192.168.0.3 instead of 192.168.0.3/dashboard. Kind regards

1 0

PXE in Oracle VM Virtual Box
by Adivya Singh 06 Jul '21

06 Jul '21

Hi Team, is there any individual link for setup a PXE in Oracle VM Virtual Box I have setup the Network boot as first priority but once the VM comes up, it is giving me below error "No Such boot or media error, i can understand the error, but not able to get the correct steps to rectify this error Regards Adivya Singh

1 0

[all][policy] Disable & making policy rule's default change warning configurable
by Ghanshyam Mann 06 Jul '21

06 Jul '21

Hello Everyone, While implementing the new secure RBAC (scope and new defaults), you might have noticed the lot of warnings in the log and sometime failing jobs also due to size of logs. Then you had to disable those via "suppress_default_change_warnings" variable on policy enforcer. The oslo policy log the warnings if the default value of policy rule (if not overridden) is changed, so there are warnings for every policy rule on every API request, everytime policy is initialized which end up a lot of warnings (thousands) in log. It might be happening in production also. Many projects have disabled it via hardcoded "suppress_default_change_warnings". But there is no way for the operator to disable/enable these warnings (enable in case they would like to check the new policy RBAC). To handle it on oslo policy side and generically for all the projects I am planning to: 1. Disable it by default in oslo policy side itself. 2. Make it configurable so that operator can enable it on need basis. NOTE: This proposal is about warnings for default value change, not for the policy name change. I have submitted this proposal in gerrit too - https://review.opendev.org/c/openstack/oslo.policy/+/799539 Please let me know your opinon on this? -gmann

2 2

[Ironic] Vendor-neutral Disk names
by Mahnoor Asghar 06 Jul '21

06 Jul '21

Dear all, There is [a proposal][1] in the metal3-io/baremetal-operator repository to extend the hardware RAID configuration to support ‘physical_disks’ and ‘controller’ fields in the 'target_raid_config' section. The user should be able to specify the disks for RAID configuration, in a vendor-agnostic way. (This requirement comes from the Airship project.) The names of the disks should be indicative of the physical location of the disks within the server. An algorithm to construct disk names is therefore needed, for this purpose. One possible algorithm was found in the [inventory module][2] of the [Redfish Tacklebox scripts][3]. To construct a disk name, it uses Redfish properties, specifically the ‘Drive’ resource> ‘Physical Location’ object> ‘Part Location’ property> ‘Service Label’ property. ([Link][4] to code) ([Link][5] to Redfish ‘Drive’ resource) If this property is empty, the resource type (String uptil the first dot encountered in the @odata.type field), and the ‘Id’ properties of the Drive resource are used to construct the disk name. ([Link][6] to code) For example, if the 'Drive'.'Physical Location'.'Part Location'.'Service Label' field is ‘Disk.Bay1.Slot0’, this is what the disk name will be. If this field is empty, and the resource name is ‘Drive’ and the resource ‘Id’ is ‘Disk.Bay1.Slot0’, the disk name will be: ‘Drive: Disk.Bay1.Slot0’. We would like to understand the values different vendors give in: - ‘Drive’ resource> ‘Physical Location’ object> ‘Part Location’ property> ‘Service Label’ property - The resource type for a Drive (@odata.type field) - The ‘Id’ property of the Drive resource Also, it would be helpful to understand the existing logic used by vendors to construct the disk names, including the (Redfish or other) properties used. This is so that a consensus can be reached for an algorithm to construct disk names. Any suggestions are welcome, thank you so much! [1]: https://github.com/metal3-io/metal3-docs/pull/148 [2]: https://github.com/DMTF/Redfish-Tacklebox/blob/master/redfish_utilities/inv… [3]: https://github.com/DMTF/Redfish-Tacklebox [4]: https://github.com/DMTF/Redfish-Tacklebox/blob/e429f70a79cfe288756618498ce4… [5]: https://redfish.dmtf.org/schemas/v1/Drive.v1_12_1.json [6]: https://github.com/DMTF/Redfish-Tacklebox/blob/e429f70a79cfe288756618498ce4… Best regards, Mahnoor Asghar Software Design Engineer xFlow Research Inc. mahnoor.asghar(a)xflowresearch.com www.xflowresearch.com

4 6

[TripleO] next irc meeting Tuesday 06 July @ 1400 UTC in OFTC #tripleo
by Marios Andreou 06 Jul '21

06 Jul '21

Reminder the next TripleO irc meeting is today Tuesday 06 July 1400 UTC in OFTC irc channel #tripleo. agenda: https://wiki.openstack.org/wiki/Meetings/TripleO one-off items: https://etherpad.opendev.org/p/tripleo-meeting-items (feel free to add any tripleo status/ongoing work etc to the etherpad). Our last meeting was on Jun 22 - you can find logs @ http://eavesdrop.openstack.org/meetings/tripleo/2021/tripleo.2021-06-22-14.… Hope you can make it on Tuesday, regards, marios

1 0

[wallaby][nova] CPU topology and NUMA Nodes
by Ammad Syed 05 Jul '21

05 Jul '21

Hi, I am using openstack wallaby on ubuntu 20.04 and kvm. I am working to make optimized flavor properties that should provide optimal performance. I was reviewing the document below. https://docs.openstack.org/nova/wallaby/admin/cpu-topologies.html I have two socket AMD compute node. The workload running on nodes are mixed workload. My question is should I use default nova CPU topology and NUMA node that nova deploys instance by default OR should I use hw:cpu_sockets='2' and hw:numa_nodes='2'. Which one from above provide best instance performance ? or any other tuning should I do ? The note in the URL (CPU topology sesion) suggests that I should stay with default options that nova provides. Currently it also works with libvirt/QEMU driver but we don’t recommend it in production use cases. This is because vCPUs are actually running in one thread on host in qemu TCG (Tiny Code Generator), which is the backend for libvirt/QEMU driver. Work to enable full multi-threading support for TCG (a.k.a. MTTCG) is on going in QEMU community. Please see this MTTCG project <http://wiki.qemu.org/Features/tcg-multithread> page for detail. Ammad

5 9

[wallaby][neutron][ovn] Low network performance between instances on different compute nodes using OVN Geneve tunnels
by Malik Obaid 05 Jul '21

05 Jul '21

Hi, I am using Openstack Wallaby release with OVN on Ubuntu 20.04. My environment consists of 2 compute nodes and 1 controller node. ovs_version: "2.15.0" Ubuntu Kernel Version: 5.4.0-77-generic I am observing Network performance between instances on different compute nodes is slow. The network uses geneve tunnels.The environment is using 10Gbps network interface cards. However, iperf between instances on different compute nodes attains only speeds between a few hundred Mbit/s and a few Gb/s. Both instances are in the same tenant network. Note: iperf results between both compute nodes (hypervisors) across the geneve tunnel endpoints is perfect 10 Gbps. Below are the results of iperf commands. *iperf server:* 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8950 qdisc fq_codel state UP group default qlen 1000 link/ether fa:16:3e:4b:1d:29 brd ff:ff:ff:ff:ff:ff inet 192.168.100.111/24 brd 192.168.100.255 scope global dynamic ens3 valid_lft 42694sec preferred_lft 42694sec inet6 fe80::f816:3eff:fe4b:1d29/64 scope link valid_lft forever preferred_lft forever root@vm-01:~# iperf3 -s Server listening on 5201 Accepted connection from 192.168.100.69, port 45542 [ 5] local 192.168.100.111 port 5201 connected to 192.168.100.69 port 45544 [ 8] local 192.168.100.111 port 5201 connected to 192.168.100.69 port 45546 [ ID][Role] Interval Transfer Bitrate Retr Cwnd [ 5][RX-S] 0.00-1.00 sec 692 MBytes 5.81 Gbits/sec [ 8][TX-S] 0.00-1.00 sec 730 MBytes 6.12 Gbits/sec 0 3.14 MBytes [ 5][RX-S] 1.00-2.00 sec 598 MBytes 5.01 Gbits/sec [ 8][TX-S] 1.00-2.00 sec 879 MBytes 7.37 Gbits/sec 0 3.14 MBytes [ 5][RX-S] 2.00-3.00 sec 793 MBytes 6.65 Gbits/sec [ 8][TX-S] 2.00-3.00 sec 756 MBytes 6.34 Gbits/sec 0 3.14 MBytes [ 5][RX-S] 3.00-4.00 sec 653 MBytes 5.48 Gbits/sec [ 8][TX-S] 3.00-4.00 sec 871 MBytes 7.31 Gbits/sec 0 3.14 MBytes [ 5][RX-S] 4.00-5.00 sec 597 MBytes 5.01 Gbits/sec [ 8][TX-S] 4.00-5.00 sec 858 MBytes 7.20 Gbits/sec 0 3.14 MBytes [ 5][RX-S] 5.00-6.00 sec 734 MBytes 6.16 Gbits/sec [ 8][TX-S] 5.00-6.00 sec 818 MBytes 6.86 Gbits/sec 0 3.14 MBytes [ 5][RX-S] 6.00-7.00 sec 724 MBytes 6.06 Gbits/sec [ 8][TX-S] 6.00-7.00 sec 789 MBytes 6.60 Gbits/sec 0 3.14 MBytes [ 5][RX-S] 7.00-8.00 sec 735 MBytes 6.18 Gbits/sec [ 8][TX-S] 7.00-8.00 sec 835 MBytes 7.02 Gbits/sec 0 3.14 MBytes [ 5][RX-S] 8.00-9.00 sec 789 MBytes 6.62 Gbits/sec [ 8][TX-S] 8.00-9.00 sec 845 MBytes 7.09 Gbits/sec 0 3.14 MBytes [ 5][RX-S] 9.00-10.00 sec 599 MBytes 5.02 Gbits/sec [ 8][TX-S] 9.00-10.00 sec 806 MBytes 6.76 Gbits/sec 0 3.14 MBytes [ ID][Role] Interval Transfer Bitrate Retr [ 5][RX-S] 0.00-10.00 sec 6.75 GBytes 5.80 Gbits/sec receiver [ 8][TX-S] 0.00-10.00 sec 7.99 GBytes 6.87 Gbits/sec 0 sender Server listening on 5201 *Client side:* root@vm-03:~# iperf3 -c 192.168.100.111 --bidir Connecting to host 192.168.100.111, port 5201 [ 5] local 192.168.100.69 port 45544 connected to 192.168.100.111 port 5201 [ 7] local 192.168.100.69 port 45546 connected to 192.168.100.111 port 5201 [ ID][Role] Interval Transfer Bitrate Retr Cwnd [ 5][TX-C] 0.00-1.00 sec 700 MBytes 5.87 Gbits/sec 0 3.13 MBytes [ 7][RX-C] 0.00-1.00 sec 722 MBytes 6.06 Gbits/sec [ 5][TX-C] 1.00-2.00 sec 594 MBytes 4.98 Gbits/sec 0 3.13 MBytes [ 7][RX-C] 1.00-2.00 sec 883 MBytes 7.41 Gbits/sec [ 5][TX-C] 2.00-3.00 sec 796 MBytes 6.67 Gbits/sec 0 3.13 MBytes [ 7][RX-C] 2.00-3.00 sec 752 MBytes 6.31 Gbits/sec [ 5][TX-C] 3.00-4.00 sec 654 MBytes 5.49 Gbits/sec 0 3.13 MBytes [ 7][RX-C] 3.00-4.00 sec 876 MBytes 7.35 Gbits/sec [ 5][TX-C] 4.00-5.00 sec 598 MBytes 5.01 Gbits/sec 0 3.13 MBytes [ 7][RX-C] 4.00-5.00 sec 853 MBytes 7.16 Gbits/sec [ 5][TX-C] 5.00-6.00 sec 734 MBytes 6.15 Gbits/sec 0 3.13 MBytes [ 7][RX-C] 5.00-6.00 sec 818 MBytes 6.86 Gbits/sec [ 5][TX-C] 6.00-7.00 sec 726 MBytes 6.09 Gbits/sec 0 3.13 MBytes [ 7][RX-C] 6.00-7.00 sec 793 MBytes 6.65 Gbits/sec [ 5][TX-C] 7.00-8.00 sec 734 MBytes 6.15 Gbits/sec 0 3.13 MBytes [ 7][RX-C] 7.00-8.00 sec 831 MBytes 6.97 Gbits/sec [ 5][TX-C] 8.00-9.00 sec 788 MBytes 6.61 Gbits/sec 0 3.13 MBytes [ 7][RX-C] 8.00-9.00 sec 845 MBytes 7.09 Gbits/sec [ 5][TX-C] 9.00-10.00 sec 600 MBytes 5.03 Gbits/sec 0 3.13 MBytes [ 7][RX-C] 9.00-10.00 sec 805 MBytes 6.76 Gbits/sec [ ID][Role] Interval Transfer Bitrate Retr [ 5][TX-C] 0.00-10.00 sec 6.76 GBytes 5.81 Gbits/sec 0 sender [ 5][TX-C] 0.00-10.00 sec 6.75 GBytes 5.80 Gbits/sec receiver [ 7][RX-C] 0.00-10.00 sec 7.99 GBytes 6.87 Gbits/sec 0 sender [ 7][RX-C] 0.00-10.00 sec 7.99 GBytes 6.86 Gbits/sec receiver iperf Done. --------------------------------------------------------------------------------------------------------- *ovs-vsctl show on compute node1:* root@kvm01-a1-khi01:~# ovs-vsctl show 88e6b984-44dc-4f74-8a9a-891742dbbdbd Bridge br-eth1 Port ens224 Interface ens224 Port patch-provnet-440be99a-c347-4458-b7c1-6c0e6155eee9-to-br-int Interface patch-provnet-440be99a-c347-4458-b7c1-6c0e6155eee9-to-br-int type: patch options: {peer=patch-br-int-to-provnet-440be99a-c347-4458-b7c1-6c0e6155eee9} Port br-eth1 Interface br-eth1 type: internal Bridge br-int fail_mode: secure datapath_type: system Port tapde98b2d4-a0 Interface tapde98b2d4-a0 Port ovn-f51ef9-0 Interface ovn-f51ef9-0 type: vxlan options: {csum="true", key=flow, remote_ip="172.16.30.3"} bfd_status: {diagnostic="No Diagnostic", flap_count="1", forwarding="true", remote_diagnostic="No Diagnostic", remote_state=up, state=up} Port tap348fc6dc-3a Interface tap348fc6dc-3a Port br-int Interface br-int type: internal Port tap6d4d8e02-c0 Interface tap6d4d8e02-c0 error: "could not open network device tap6d4d8e02-c0 (No such device)" Port patch-br-int-to-provnet-440be99a-c347-4458-b7c1-6c0e6155eee9 Interface patch-br-int-to-provnet-440be99a-c347-4458-b7c1-6c0e6155eee9 type: patch options: {peer=patch-provnet-440be99a-c347-4458-b7c1-6c0e6155eee9-to-br-int} Port tap247fe5b2-ff Interface tap247fe5b2-ff ------------------------------------------------------------------------------------------------------ *ovs-vsctl show on compute node2:* root@kvm03-a1-khi01:~# ovs-vsctl show 24ce6475-89bb-4df5-a5ff-4ce58f2c2f68 Bridge br-eth1 Port patch-provnet-440be99a-c347-4458-b7c1-6c0e6155eee9-to-br-int Interface patch-provnet-440be99a-c347-4458-b7c1-6c0e6155eee9-to-br-int type: patch options: {peer=patch-br-int-to-provnet-440be99a-c347-4458-b7c1-6c0e6155eee9} Port br-eth1 Interface br-eth1 type: internal Port ens224 Interface ens224 Bridge br-int fail_mode: secure datapath_type: system Port patch-br-int-to-provnet-440be99a-c347-4458-b7c1-6c0e6155eee9 Interface patch-br-int-to-provnet-440be99a-c347-4458-b7c1-6c0e6155eee9 type: patch options: {peer=patch-provnet-440be99a-c347-4458-b7c1-6c0e6155eee9-to-br-int} Port tap2b0bbf7b-59 Interface tap2b0bbf7b-59 Port ovn-650be8-0 Interface ovn-650be8-0 type: vxlan options: {csum="true", key=flow, remote_ip="172.16.30.1"} bfd_status: {diagnostic="No Diagnostic", flap_count="1", forwarding="true", remote_diagnostic="No Diagnostic", remote_state=up, state=up} Port tap867d2174-83 Interface tap867d2174-83 Port tapde98b2d4-a0 Interface tapde98b2d4-a0 Port br-int Interface br-int type: internal -------------------------------------------------------------------------------------------------------- I would really appreciate any input in this regard. Thank you. Regards, Malik Obaid

2 3

[openstack-ansible][osa] Wallaby has been released with 23.0.0
by Dmitriy Rabotyagov 05 Jul '21

05 Jul '21

Hi everyone! We're happy to announce, that OpenStack-Ansible project has finally released stable/wallaby version with tag 23.0.0. This release includes more then 700 changes from over 50 contributors. And I'd love to thank everyone who made this release happen! The major changes since Victoria are: - Added experimental support of Debian Bullseye (11) and CentOS 8 Stream - Significantly improved workflow and status of Cloudkitty, Trove and Zun roles - Added PKI role, that generates local CA, so self-signed certificates will be trusted inside deployment - nspawn containers support has been removed For the full log of the changes, please reffer to the project Release Notes [1] [1] https://docs.openstack.org/releasenotes/openstack-ansible/wallaby.html -- Kind Regards, Dmitriy Rabotyagov

1 0

[nova] spec review day
by Balazs Gibizer 05 Jul '21

05 Jul '21

Hi, During the today's meeting it came up that we should have a spec review day around M1 (and later one more before M2). As M1 is 27th of May, I propose to do a spec review day on 25th of May, which is a Tuesday. Let me know if the timing does not good for you. The rules are the usual. Let's use this day to focus on open specs, trying to reach agreement on as many thing as possible with close cooperation during the day. Cheers, gibi

1 3

[release][murano] PTL validation
by Herve Beraud 05 Jul '21

05 Jul '21

Hello, Just a heads up about this patch https://review.opendev.org/c/openstack/releases/+/797996 Please can you validate this patch? Thanks in advance. -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 0

[neutron] IPv6 advertisement support for BGP neutron-dynamic-routing
by Manu B 05 Jul '21

05 Jul '21

Hi everyone, This is a doubt regarding existing IPv6 advertisement support for BGP in the current n-d-r repo. >From the documentation, it is mentioned that to enable advertising IPv6 prefixes, create an address scope with ip_version=6 and a BGP speaker with ip_version=6. We have a use case where v4 and v6 routes must be advertised using a single v4 peer. 1. How can we advertise both v4 and v6 routes using single v4 peer? Do we have to create 2 BGP speakers ( one for v4 and another for v6) Then create a single BGP v4 peer and add the same peer to both the speakers? Is this the correct approach or any other way? 1. Is there any other significance of version field in current BGP speaker model? Thanks, Manu

4 4

[largescale-sig] Next meeting: July 7, 15utc on #openstack-operators
by Thierry Carrez 05 Jul '21

05 Jul '21

Hi everyone, Our next Large Scale SIG meeting will be this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. You can doublecheck how that time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210707T15 A number of topics have already been added to the agenda, including discussing the contents of our next OpenInfra.Live show. Feel free to add other topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 0

swift_storage storage space
by Salman Sheikh 04 Jul '21

04 Jul '21

Hi experts, how we get the storage usage of object storage (swift). suppose at the time of installation through packstack we define the swift_storage 20G, if any other person wants to know how much space was used in swift, and how much space is available in the object storage. How we can get all this Regards salman

2 1

[neutron] bug deputy report June 28th to July 4th
by Miguel Lavalle 04 Jul '21

04 Jul '21

Hi, Here is this week's bugs deputy report: Needs attention or owner =================== https://bugs.launchpad.net/neutron/+bug/1934420 [OVN]ControllerAgent cannot be changed to ControllerGatewayAgent dynamically. In this case, an owner is required https://bugs.launchpad.net/neutron/+bug/1933813 OSError: Premature eof waiting for privileged process error in Ussuri release of Neutron. Submitter still debugging issue in his deployment with guidance from ralonsoh. Waiting for more information Medium ====== https://bugs.launchpad.net/neutron/+bug/1933638 neutron with ovn returns Conflict on security group rules delete https://bugs.launchpad.net/neutron/+bug/1934039 Neutron with noauth authentication strategy needs fake 'project_id' in request body. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/799162 https://bugs.launchpad.net/neutron/+bug/1934115 List security groups by project admin may return 500. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/798821 https://bugs.launchpad.net/neutron/+bug/1934466 Devstack install for ML2 OVS. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/799159 Low === https://bugs.launchpad.net/neutron/+bug/1933802 missing global_request_id in neutron_lib context from_dict method. Proposed fix: https://review.opendev.org/c/openstack/neutron-lib/+/798815 https://bugs.launchpad.net/neutron/+bug/1934256 neutron-lib duplicates os-resource-classes constants. Proposed fix: https://review.opendev.org/c/openstack/neutron-lib/+/799034 https://bugs.launchpad.net/neutron/+bug/1934420 [OVN]ControllerAgent cannot be changed to ControllerGatewayAgent dynamically. Needs an owner https://bugs.launchpad.net/neutron/+bug/1934512 Remove SG RPC "use_enhanced_rpc" check

1 0

[all][tc] What's happening in Technical Committee: summary 2nd July, 21: Reading: 5 min
by Ghanshyam Mann 03 Jul '21

03 Jul '21

Hello Everyone, Here is last week's summary of the Technical Committee activities. 1. What we completed this week: ========================= * Deprecated OpenStack-Ansible nspawn repositories [1] * Retired puppet-openstack-specs [2] * Retired in-active governance repos [3] - openstack/arch-wg - openstack/openstack-specs - openstack/project-navigator-data - openstack/enterprise-wg - openstack/workload-ref-archs - openstack/ops-tags-team - openstack/scientific-wg - openstack/governance-uc - openstack/uc-recognition 2. TC Meetings: ============ * TC held this week meeting on Thursday; you can find the full meeting logs in the below link: - https://meetings.opendev.org/meetings/tc/2021/tc.2021-07-01-15.00.log.html * We will have next week's meeting on July 8th, Thursday 15:00 UTC[4]. 3. Activities In progress: ================== TC Tracker for Xena cycle ------------------------------ TC is using the etherpad[5] for Xena cycle working item. We will be checking and updating the status biweekly in the same etherpad. Open Reviews ----------------- * Four open review for ongoing activities[6]. ELK services next plan and help status --------------------------------------------- * The Technical Committee brought the ELK help to the Board meeting held on June 30th[7].This is the presentation[8]. Please bring this to your company to broadcast it and get some help. * Join us in next TC meeting on July 8th to discuss the next plan. Migration from Freenode to OFTC ----------------------------------------- * Not much progress on project side wiki/doc page which is only thing left for this migration. * All the required work for this migration is tracked in this etherpad[9] 'Y' release naming process ------------------------------- * Y release naming election is closed now. As a last step, the foundation is doing trademark checks on elected ranking. * We should have final name by next week. Test support for TLS default: ---------------------------------- * Rico has started a separate email thread over testing with tls-proxy enabled[10], we encourage projects to participate in that testing and help to enable the tls-proxy in gate testing. Adding Ceph Dashboard charm to OpenStack charms --------------------------------------------------------------- * Proposal to add Ceph Dashboard charm to OpenStack charms[11] Retiring js-openstack-lib ---------------------------- * Proposal to retire js-openstack-lib [12]. Other Changes ------------------ * Charter change to handle the vacant seat situation[13] * Add DPL model also in 'Appointing leaders' section[14] 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[15]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [16] 3. Office hours: The Technical Committee offers a weekly office hour every Tuesday at 0100 UTC [17] 4. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://review.opendev.org/c/openstack/governance/+/797731 [2] https://review.opendev.org/c/openstack/governance/+/798711 [3] https://review.opendev.org/c/openstack/governance/+/797788 [4] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [5] https://etherpad.opendev.org/p/tc-xena-tracker [6] https://review.opendev.org/q/project:openstack/governance+status:open [7] https://wiki.openstack.org/wiki/Governance/Foundation/30Jun2021BoardMeeting [8] https://docs.google.com/presentation/d/1ugdwMI2ZM2L8z1sobzHJwDpbvlyWKH02PH7… [9] https://etherpad.opendev.org/p/openstack-irc-migration-to-oftc [10] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023000.html [11] https://review.opendev.org/c/openstack/governance/+/797913 [12] https://review.opendev.org/c/openstack/governance/+/798540 [13] https://review.opendev.org/c/openstack/governance/+/797912 [14] https://review.opendev.org/c/openstack/governance/+/797985 [15] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [16] http://eavesdrop.openstack.org/#Technical_Committee_Meeting [17] http://eavesdrop.openstack.org/#Technical_Committee_Office_hours -gmann

1 0

No server with a name or ID of "blabla' exists
by Pete Zhang 02 Jul '21

02 Jul '21

Hey, We are seeing this for the FIRST time once we rebuilt MariaDB/Galera and RabbitMQ cluster, after a period of failure/downtime. Probably there are some inconsistencies among components/services. How to clean up those hosts in BUILD state? thx. 1) There are multiple uuid of the same host stuck in BUILD 2) Deleting server failed with this error: No server with a name or ID of "blabal" exists. ERROR (CommandError): Unable to delete the specified server(s). [image: Screen Shot 2021-07-02 at 3.04.34 PM.png] -- <https://smart.salesforce.com/sig/peiyong.zhang//us_mb/default/link.html>

1 0

[Interop][Refstack] meeting time changed for the summer
by Arkady Kanevsky 02 Jul '21

02 Jul '21

Team, The group meeting will be on Fridays 2 hours earlier at 14pm UTC. Meeting info and minutes are still the same https://meetpad.opendev.org/interop <https://www.google.com/url?q=https://meetpad.opendev.org/interop&sa=D&sourc…> https://etherpad.opendev.org/p/interop <https://www.google.com/url?q=https://etherpad.opendev.org/p/interop&sa=D&so…> -- Arkady Kanevsky, Ph.D. Phone: 972 707-6456 Corporate Phone: 919 729-5744 ext. 8176456

1 0

No server with a name or ID of "blabla' exists
by Pete Zhang 02 Jul '21

02 Jul '21

Hey, We are seeing this for the FIRST time once we rebuilt MariaDB/Galera and RabbitMQ cluster, after a period of failure/downtime. Probably there are some inconsistencies among components/services. How to clean up those hosts in BUILD state? thx. 1) There are multiple uuid of the same host stuck in BUILD 2) Deleting server failed with this error: No server with a name or ID of "blabal" exists. ERROR (CommandError): Unable to delete the specified server(s). [image: Screen Shot 2021-07-02 at 2.29.44 PM.png] [image: Screen Shot 2021-07-02 at 2.27.56 PM.png] -- <https://smart.salesforce.com/sig/peiyong.zhang//us_mb/default/link.html>

1 0

[all] [] Mentors Needed! Open Source Day Summer
by Kendall Nelson 02 Jul '21

02 Jul '21

Hello! As you may or may not know, the Grace Hopper Conference is now running TWO Open Source Day events a year! The upcoming event is on July 15th[0]. If you are interested in mentoring a few individuals- i.e helping them work on some low hanging fruit for your project, please sign up here[1] and let me know! After you've done the signup and replied here, I will reach out to the organizers to make sure you are approved. At that point, please collect a few bugs you think would be good first patches for attendees and link them in the etherpad here[2]. Thank you so much! Can't wait to work with you :) -Kendall Nelson (diablo_rojo) [0] https://anitab-org.github.io/open-source-day/upcoming/ [1] https://anitab-org.github.io/open-source-day/become_a_mentor/ [2] https://etherpad.opendev.org/p/ghc-osd-summer-2021

2 1

[victoria][barbican] - UI installation
by Luke Camilleri 02 Jul '21

02 Jul '21

Hi there, I have an openstack deployment installed as a bare-metal/manual installation and would like to install the Barbican UI. Barbican is already installed and running. In my case Horizon is already installed so I guess if I follow these steps https://github.com/openstack/barbican-ui#manual-installation I would not need to clone the horizon part and also my installation already contains the local_settings.py file with all the required settings mentioned. At this point when moving into the "Install Barbican UI with all dependencies in your virtual environment" step I do not have the tools folder so I cannot really proceed with the pip install (missing virtual environment )and copying the barbican-ui/barbican_ui/enabled/_90_project_barbican_panelgroup.py and barbican-ui/barbican_ui/enabled/_91_project_barbican_secrets_panel.py to the /usr/share/openstack-dashboard/openstack_dashboard/local/enabled obviously fails A similar issue is reported here https://storyboard.openstack.org/#!/story/2008259 Thanks in advance

1 0

Extension of disk in cinder
by Salman Sheikh 02 Jul '21

02 Jul '21

Hi all, How we can add the more disk to cinder, as I have created the cinder-volumes on one disk (/sdb) the sdb is 500Gb, if i want to increase the the size of cinder-volumes then how we extend the size of cinder-volumes. how we can add more disk in order to increase the size of cinder-volume. Kindly advise

2 3

[charms] Trilio Charms 21.06 release is now available
by Billy Olsen 01 Jul '21

01 Jul '21

The 21.06 release of the Trilio charms are now available. Please see the Release Notes for full details: https://docs.openstack.org/charm-guide/latest/2106_Trilio.html == Highlights == * TrilioVault 4.1 HF1 The charms have added options to support new configurations presented in the TrilioVault 4.1 HF1 release. * S3 Support The charms now support using S3 storage as a backup target. == Thank you == Lots of thanks to the following people who contributed to this release via code changes, documentation updates and testing efforts. Alex Kavanagh Billy Olsen Chris MacNaughton Corey Bryant David Ames Liam Young Marian Gasparovic Peter Matulis -- OpenStack Charms Team

1 0

[release][tc][neutron] how to EOL unofficial branches under offical repositories
by Akihiro Motoki 01 Jul '21

01 Jul '21

Hi, I have a question about how to mark stable branches as EOL when such branches were not part of official releases at the moment of corresponding releases but the repositories which contain them became official after the release. One example happens in a repository under the neutron team. networking-odl is now part of the neutron governance but as of Ocata release it was not official. Ocata branches under the neutron stadium were marked as EOL recently, but networking-odl was not marked as EOL as it was not an official repository as of Ocata. The openstack/releases repository handles official branches under a specific release, but all branches in official repositories are under control of the openstack/releases repo. I wonder how we can mark stable/ocata branch of networking-odl repo as EOL and delete stable/ocata branch. What is the recommended way to mark such branches described above as EOL? Thanks in advance, Akihiro Motoki (irc: amotoki)

3 3

[Kolla-Ansible] Regarding stability of Ironic deployment with Kolla-Ansible
by Amit Mahajan 01 Jul '21

01 Jul '21

Hi All, We are exploring Kolla-Ansible for our multinode production grade deployment. In our setup, some workloads will also run on bare-metal, so Ironic is the key requirement. We came across the following text on the Kolla-Ansible documentation page for Rocky release. "Ironic works well in Kolla, though it is not currently tested as part of Kolla CI, so may be subject to instability." Our query is that is deployment of Ironic using Kolla-Ansible production grade for the latest OpenStack release?

3 6

[kayobe][victoria] no module named docker - deploy fail after deploy successful
by Tony Pearce 01 Jul '21

01 Jul '21

I had a successful deployment of Openstack Victoria via Kayobe with an all-in-one node running controller and compute roles. I wanted to then add 2 controller nodes to make 3 controllers and one compute. The 2 additional controllers have a different interface naming so I needed to modify the inventory. I checked this ansible documentation to figure out the changes I’d need to make [1]. The first try, I misunderstood the layout because kayobe tried to configure the new nodes interfaces with incorrect naming. In my first try I tried this inventory layout: Move existing configuration: [kayobe config] / Inventory / * To [kayobe config] / Inventory / Ciscohosts / Create new from copy of existing:[kayobe config] / Inventory / Ciscohosts / > [kayobe config] / Inventory / Otherhosts / The Otherhosts had its own host file with the 2 controllers and group_vars/controllers network interface configuration as per these two hosts. But anyway it didnt achieve the desired result so I rechecked the ansible doc [1] and decided to do this another way as follows: In my second try I first reversed the inventory change: Delete the new dir: [kayobe config] / Inventory / Otherhosts / Move back the config: [kayobe config] / Inventory / Ciscohosts / * > [kayobe config] / Inventory / Delete the empty dir: [kayobe config] / Inventory / Ciscohosts / Then create host_vars for the two individual hosts: [kayobe config] / Inventory / host_vars / cnode2 [kayobe config] / Inventory / host_vars / cnode3 And updated the single hosts inventory file [kayobe config] / Inventory / hosts This seemed to work fine, the “kayobe overcloud host configure” was successful and the hosts interfaces were set up as I desired. The issue came when doing the “kayobe overcloud service deploy” and failed with "/usr/bin/python3", "-c", "import docker” = ModuleNotFoundError: No module named 'docker' for all three nodes, where previously it (the deployment) had been successful for the all-in-one node. I do not know if this task had run or skipped before but the task is run against "baremetal" group and controllers and compute are in this group so I assume that it had been ran successfully in previous deployments and this is the weird thing because no other changes have been made apart from as described here. Verbose error output: [3] After the above error, I reverted the inventory back to the “working” state, which is basically to update the inventory hosts and removed the 2 controllers. As well as remove the whole host_vars directory. After doing this however, the same error is still seen /usr/bin/python3", "-c", "import docker” = ModuleNotFoundError. I logged into the host and tried to run this manually on the CLI and I see the same output. What I don’t understand is why this error is occurring now after previous successful deployments. To try and resolve /workaround this issue I have tried to no avail: - recreating virtual environments on all-in-one node - recreating virtual environments on ACH - deleting the [kolla config] directory - deleting .ansible and /tmp/ caches - turning off pipelining After doing the above I needed to do the control host bootstrap and host configure before service deploy however the same error persisted and I could not work around it with any of the above steps being performed. As a test, I decided to turn off this task in the playbook [4] and the yml file runs as follows: [2]. This results in a (maybe pseudo) successful deployment again, in a sense that it deploys without failure because that task does not run. After this was successful in deploying once again as it had previously had been, I added the two controller nodes using the “host_vars” and then I was able to successfully deploy again with HA controllers. Well, it is successful apart from Designate issue due to Designate already having the config [5]. I can log in to the horizon dashboard and under system information I can see all three controllers there. Could I ask the community for help with: 1. Regarding the kayobe inventory, is anything wrong with the 2nd attempt in line with Kayobe? 2. Has anyone come across this docker issue (or similar within this context of failing after being successful) and can suggest? I repeatedly get these odd issues where successful deployments then fail in the future. This often occurs after making a config change and then rolling back but the roll back does not return to a working deployment state. The fix/workaround for me in these cases is to “kayobe overcloud service destroy --yes-i-really-really-mean-it” and also re-deploy the host. [1] Best Practices — Ansible Documentation <https://docs.ansible.com/ansible/2.8/user_guide/playbooks_best_practices.ht…> [2] modified Checking docker SDK version# command: "{{ ansible_python.execut - Pastebin.com <https://pastebin.com/xXJFHc0N> [3] TASK [prechecks : Checking docker SDK version] ********************************* - Pastebin.com <https://pastebin.com/ZmLs4LUZ> [4] /home/cv-user/kayobe-victoria/venvs/kolla-ansible/share/kolla-ansible/ansible/roles/prechecks/tasks/package_checks.yml [5] TASK [designate : Update DNS pools] ******************************************** - Pastebin.com <https://pastebin.com/USiCAXpT> Kind regards,

2 2

[kayobe][kolla-ansible][victoria]
by Tony Pearce 01 Jul '21

01 Jul '21

How do I configure the glance container to use a host-mounted NFS share? It is not covered in the kolla-ansible documentation [1]. What it does say is to set the file path using "glance_file_datadir_volume". I believe that this is relative to the container (not the host). Do I need to mount the local host (nfs) directory as a docker volume for glance as additional step? If so, how do I achieve this with kayobe / kolla-ansible? Some background: After a successful deployment of 3 controller nodes I have one glance service which is dependent on one of these controller nodes being available always. My intent is to provide a NFS share for glance that removes the dependency. [1] OpenStack Docs: Glance - Image service <https://docs.openstack.org/kolla-ansible/victoria/reference/shared-services…> Kind regards, Tony Pearce

2 2

[nova][placement] Openstack only building one VM per machine in cluster, then runs out of resources
by Jeffrey Mazzone 01 Jul '21

01 Jul '21

Hello, I am installing Openstack Ussuri and am running into an issue when using Availability Zones. I initially thought it was a quota issue but that no longer seems to be the case. I started a thread on serverfault and was recommended to submit these questions here as well. Here is the original link: https://serverfault.com/questions/1064579/openstack-only-building-one-vm-pe… The issue is still, I can successfully build vms on every host, but only one vm per host. The size of the initial vm does not matter. Since I posted the thread above, I have redeployed the entire cluster, by hand, using the docs on openstack.org<http://openstack.org>. Everything worked as it should, I created 3 test aggregates, 3 test availability zones, with no issues for about a month. All of a sudden, the system reverted to no longer allowing more than one machine to be placed per host. There has been no changes to the controller. I have enabled placement logging now so I can see more information but I don’t understand why its happening. Example. Start with a host that has no vms on it: ~# openstack resource provider usage show 3f9d0deb-936c-474a-bdee-d3df049f073d +----------------+-------+ | resource_class | usage | +----------------+-------+ | VCPU | 0 | | MEMORY_MB | 0 | | DISK_GB | 0 | +----------------+-------+ Create 1 vm with 4 cores ~# openstack resource provider usage show 3f9d0deb-936c-474a-bdee-d3df049f073d +----------------+-------+ | resource_class | usage | +----------------+-------+ | VCPU | 4 | | MEMORY_MB | 0 | | DISK_GB | 0 | +----------------+-------+ The inventory list for that provider is: ~# openstack resource provider inventory list 3f9d0deb-936c-474a-bdee-d3df049f073d +----------------+------------------+----------+----------+----------+-----------+--------+ | resource_class | allocation_ratio | min_unit | max_unit | reserved | step_size | total | +----------------+------------------+----------+----------+----------+-----------+--------+ | VCPU | 16.0 | 1 | 64 | 0 | 1 | 64 | | MEMORY_MB | 1.5 | 1 | 515655 | 512 | 1 | 515655 | | DISK_GB | 1.0 | 1 | 7096 | 0 | 1 | 7096 | +----------------+------------------+----------+----------+----------+-----------+--------+ Trying to start another vm on that host fails with the following log entries: scheduler.log "status": 409, "title": "Conflict", "detail": "There was a conflict when trying to complete your request.\n\n Unable to allocate inventory: Unable to create allocation for 'VCPU' on resource provider conductor.log Failed to schedule instances: nova.exception_Remote.NoValidHost_Remote: No valid host was found. There are not enough hosts available. placement.log Over capacity for VCPU on resource provider 3f9d0deb-936c-474a-bdee-d3df049f073d. Needed: 4, Used: 8206, Capacity: 1024.0 As you can see, the used value is suddenly 8206 after a single 4 core vm is placed on it. I don’t understand what im missing or could be doing wrong. Im really unsure where this value is being calculated from. All the entries in the database and via openstack commands show the correct values except in this log entry. Has anyone experienced the same or similar behavior? I would appreciate any insight as to what the issue could be. Thanks in advance! -Jeff M

5 14

[neutron] Drivers meeting agenda for 2.07.2021
by Slawek Kaplonski 01 Jul '21

01 Jul '21

Hi, We have 2 RFEs to discuss on tomorrow's meeting: https://bugs.launchpad.net/neutron/+bug/1933517 - [RFE][OVN] Create an intermediate OVS bridge between VM and intergration bridge to improve the live-migration process https://bugs.launchpad.net/neutron/+bug/1930866 - [RFE] preventing from deleting a port used by an instance (locked instance can be rendered broken by deleting port) We also have 2 not yet triaged RFEs: https://bugs.launchpad.net/neutron/+bug/1932154 https://bugs.launchpad.net/neutron/+bug/1933222 Please check them, ask questions/comments/whatever You need to triage them so we can discuss on next drivers meetings :) -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Fwd: [TRIPLEO] - ZUN Support in TripleO
by Lokendra Rathour 30 Jun '21

30 Jun '21

Hello Everyone, We are curious in understanding the usage of ZUN Sevice in TripleO with respect to which we have questions as below: 1. Does TripleO Support ZUN? 2. If not then, is there any alternative to deploy containerize services in TripleO? Any support with respect to the questions raised will definitely help us in deciding the tripleO usage. -- ~ Lokendra skype: lokendrarathour

6 7

[openstack] [DC-DC Setup] [Replication] Correct approach to a DC-DC setup for Openstack (victoria)
by Swogat Pradhan 30 Jun '21

30 Jun '21

Hi, I am trying to setup a DC-DC setup in openstack victoria, I have 2 numbers of all in one setup (controller, compute) with shared mysql and rabbitmq cluster and am using ceph image replication and configuring cinder replication on top of it. So when the 1st node goes down then i will perform a 'cinder failover-host node1' and then do a nova-evacuate to failover to the 2nd DC setup and once the node 1 comes up i will use cinder failback and live migration from node2 to node1. **i am facing some minor issues in this setup which I will ask once I know this is the right approach to the DC-DC concept. Can you please shed some light on this being the right approach or not and if not then how can i improve it? With regards Swogat pradhan

1 1

[all][tc] Technical Committee next weekly meeting on July 1st at 1500 UTC
by Ghanshyam Mann 30 Jun '21

30 Jun '21

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

1 1

[Swift] Object replication failures on newly upgraded servers
by Mark Kirkwood 30 Jun '21

30 Jun '21

HI, I'm in the process of upgrading a Swift cluster from 2.7/Mitaka to 2.23/Train. While in general it seems to be going well, I'm noticing non-zero object replication failures on the upgraded nodes only, e.g: $ curl http://localhost:6000/recon/replication/object {"replication_last": 1622156911.019487, "replication_stats": {"rsync": 40580, "success": 4141229, "attempted": 2081856, "remove": 4083, "suffix_count": 14960481, "failure": 26550, "hashmatch": 4127197, "failure_nodes": {"10.11.18.67": {"obj08": 2348, "obj09": 60, "obj10": 3030, "obj02": 34, "obj03": 25, "obj01": 44, "obj06": 1498, "obj07": 28, "obj04": 69, "obj05": 36}, "10.11.18.68": {"obj03": 6901, "obj01": 293, "obj06": 1901, "obj04": 10281, "obj10": 1}, "10.12.18.76": {"obj10": 1}}, "suffix_sync": 1785, "suffix_hash": 2778}, "object_replication_last": 1622156911.019487, "replication_time": 1094.7836411476135, "object_replication_time": 1094.7836411476135} Examining the logs (/var/log/swift/object.log and /var/log/syslog) these are not throwing up any red flags (i.e no failing rsyncs noted). Any suggesting about how to get more information about what went wrong e.g: "10.11.18.67": {"obj08": 2348}, how to find what those 2348 errors were? regards Mark P.s: basic sanity checking is ok - uploaded objects go where they should and can be retrieved for 2.7 or 2.23 servers ok (the old and new version servers agree about object placement)

2 4