July 2023 - openstack-discuss - lists.openstack.org

ERROR openstack [-] Resource OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type OS::Neutron::Port and the Neutron service is not available when using ephemeral Heat.| Openstack tripleo wallaby version
by Swogat Pradhan 24 Dec '24

24 Dec '24

Hi, I am currently trying to deploy openstack wallaby using tripleo arch. I created the network jinja templates, ran the following commands also: #openstack overcloud network provision --stack overcloud --output networks-deployed-environment.yaml custom_network_data.yaml # openstack overcloud network vip provision --stack overcloud --output vip-deployed-environment.yaml custom_vip_data.yaml # openstack overcloud node provision --stack overcloud --overcloud-ssh-key /home/stack/sshkey/id_rsa overcloud-baremetal-deploy.yaml and used the environment files in the openstack overcloud deploy command: (undercloud) [stack@hkg2director ~]$ cat deploy.sh #!/bin/bash THT=/usr/share/openstack-tripleo-heat-templates/ CNF=/home/stack/ openstack overcloud deploy --templates $THT \ -r $CNF/templates/roles_data.yaml \ -n $CNF/workplace/custom_network_data.yaml \ -e ~/containers-prepare-parameter.yaml \ -e $CNF/templates/node-info.yaml \ -e $CNF/templates/scheduler-hints.yaml \ -e $CNF/workplace/networks-deployed-environment.yaml \ -e $CNF/workplace/vip-deployed-environment.yaml \ -e $CNF/workplace/overcloud-baremetal-deployed.yaml \ -e $CNF/workplace/custom-net-bond-with-vlans.yaml Now when i run the ./deploy.sh script i encounter an error stating: ERROR openstack [-] Resource OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type OS::Neutron::Port and the Neutron service is not available when using ephemeral Heat. The generated environments from 'openstack overcloud baremetal provision' and 'openstack overcloud network provision' must be included with the deployment command.: tripleoclient.exceptions.InvalidConfiguration: Resource OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type OS::Neutron::Port and the Neutron service is not available when using ephemeral Heat. The generated environments from 'openstack overcloud baremetal provision' and 'openstack overcloud network provision' must be included with the deployment command. 2022-04-19 13:47:16.582 735924 INFO osc_lib.shell [-] END return value: 1 Can someone tell me where the mistake is? With regards, Swogat Pradhan

4 4

[kolla] [openeuler] CI jobs status
by Michał Nasiadka 26 Nov '24

26 Nov '24

Hello Koalas, OpenEuler jobs in master (to be Antelope) are failing for a long time. If no one is interested in maintaining OpenEuler support in Kolla-Ansible - I will propose dropping it’s support on Wednesday Kolla meeting. Best regards, Michal

4 3

Kolla Ansible on Ubuntu 20.04 - cloud-init & other network issues
by Tobias McNulty 10 Oct '24

10 Oct '24

Hi, I'm attempting to use Kolla Ansible 14.6.0 to deploy OpenStack Yoga on a small 3-node Ubuntu 20.04 cluster. The nodes have 128 GB RAM each, dual Xeon processors, and dual 10G Intel NICs. The NICs are connected to access ports on a 10G switch with separate VLANs for the local and external networks. All the playbooks run cleanly, but cloud-init is failing in the Ubuntu 20.04 and 22.04 VMs I attempt to boot. The VM images are unmodified from https://cloud-images.ubuntu.com/, and cloud-init works fine if I mount a second volume with user-data. The error is a timeout attempting to reach 169.254.169.254. This occurs both when booting a VM in an internal routed network and directly in an external network. I tried various neutron plugin agents (ovn, linuxbridge, and openvswitch both with and without firewall_driver = openvswitch <https://docs.openstack.org/kolla-ansible/latest/reference/networking/neutro…>) first with a clean install of the entire OS each time, all with the same result. Running tcpdump looking for 169.254.169.254 shows nothing. As a possible clue, the virtual NICs are unable to pass any traffic (e.g., to reach an external DHCP server) unless I completely disable port security on the interface (even if the associated security group is wide open). But disabling port security does not fix cloud-init (not to mention I don't really want to disable port security). Are there any additional requirements related to deploying OpenStack with Kolla on Ubuntu 20.04? This is a fairly vanilla configuration using the multinode inventory as a starting point. I tried to follow the Quick Start <https://docs.openstack.org/kolla-ansible/yoga/user/quickstart.html> as closely as possible; the only material difference I see is that I'm using the same 3 nodes for control + compute. I am using MAAS so it's easy to get a clean OS install on all three nodes ahead of each attempt. I plan to try again with the standard (non-HWE) kernel just in case, but otherwise I am running out of ideas. In case of any additional clues, here are my globals.yml and inventory file, along with the playbook I'm using to configure the network, images, VMs, etc., after bootstrapping the cluster: https://gist.github.com/tobiasmcnulty/7dbbdbc67abc08cbb013bf5983852ed6 Thank you in advance for any advice! Cheers, Tobias

5 9

Live migration fails
by Szabo, Istvan (Agoda) 07 Aug '24

07 Aug '24

Hi, I have couple of compute nodes where the live migration fails with existing vms. When I quickly spawn a vm and try live migration it works so I assume shouldn't be a big problem with the compute node. However I have many existing vms where it fails with a servername not found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 ERROR nova.conductor.tasks.migrate [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Unable to find record for source node servername on servername: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Failed to compute_task_migrate_server: Compute host servername could not be found.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Setting instance to ACTIVE state.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.672 227612 ERROR oslo_messaging.rpc.server [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Exception during message handling: ComputeHostNotFound: Compute host am-osfecn-4025 Tried with this command: nova live-migration --block-migrate id. Any idea? Thank you. ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.

5 16

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

17 May '24

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

18 27

[Watcher] How use Watcher to scheduler Openstack resource without cpu_usage
by Nguyễn Hữu Khôi 06 Mar '24

06 Mar '24

Hello guys. I want to use watcher to scheduler openstack resources but some openstack versions are missing cpu_usage metric. How do we use Watcher without it? Thank you. Nguyen Huu Khoi

3 5

[neutron][vpnaas][ovn] Pushing VPNaaS support through OVN
by Mohammed Naser 12 Feb '24

12 Feb '24

Hi all! One of the biggest show stoppers for us for OVN is VPNaaS but I think it’s time that we’d like to be involved in getting it over the line, I want to thank Bodo who has shown a lot of patience in getting the code necessary, and it seems that the code works for them in production as well. I’d like to ask if possible for folks to review these two outstanding changes: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/847007 https://review.opendev.org/c/openstack/neutron-vpnaas/+/765353 I know Slawek had some concerns, so hoping that raising via the email list if Bodo can address those and over the next bit of time we can get this landed in, since it even has actual proper testing both in CI and with user feedback. Thanks! Mohammed

6 8

[designate] Proposal to deprecate the agent framework and agent based backends
by Michael Johnson 09 Jan '24

09 Jan '24

TLDR: The Designate team would like to deprecate the backend agent framework and the agent based backends due to lack of development and design issues with the current implementation. The following backends would be deprecated: Bind9 (Agent), Denominator, Microsoft DNS (Agent), Djbdns (Agent), Gdnsd (Agent), and Knot2 (Agent). Designate includes many backend DNS server drivers[1], many of which are "native" (also known as xfr type backends) backend implementations. In addition to the "native" backends, Designate has an agent backend[2] that supports other backends via an agent process. To quote the agent backend documentation[2]: This backend uses an extension[3] of the DNS protocol itself to send management requests to the remote agent processes, where the requests will be actioned. The rpc traffic between designate and the agent is both unauthenticated and unencrypted. Do not run this traffic over unsecured networks. Here are the reasons we are proposing to deprecate the agent framework now: 1. The agent protocol used by Designate is using an "unassigned"[4][5] DNS opcode (14) that is causing problems with the dnspython library >= 2.3.0 which is now validating the opcode when building DNS messages. It is a bad practice to use "unassigned" values as they may be officially assigned at any time, likely with an incompatible message format. 2. The agent backends are not tested in the OpenStack jobs[1]. 3. Many of the agent backends have been marked as "Experimental" since 2016 with no additional contributions beyond general repository code maintenance. 4. The protocol between the Designate worker process and the agent process is unauthenticated and unencrypted. 5. We do not know of a development resource to rewrite the agent framework protocol to address issue #1 and #4 above. 6. The introduction of catalog zones[6] may eliminate the need for some of the agent based backend drivers. By marking the agent framework and agent based backends "deprecated" in the Antelope cycle, we would remove the code no earlier than the "C" release of OpenStack (per the OpenStack deprecation policy[7]). In the meantime, issue #1 has been worked around by overriding the dnspython opcode validation[7] as needed in the Designate code (similar to a monkey patch). This is not a sustainable long term solution. The following backend agent based drivers would be marked "deprecated" in addition to the agent framework itself: Bind9 (Agent) Denominator Microsoft DNS (Agent) Djbdns (Agent) Gdnsd (Agent) Knot2 (Agent) We plan to propose patches for the deprecation over the next week, but will not merge them until at least January 24th to allow time for comment from the community. If you have concerns about this deprecation plan or are interested in rewriting the agent framework protocol to address the above issues, please reply to this announcement. Michael [1] https://docs.openstack.org/designate/latest/admin/support-matrix.html [2] https://docs.openstack.org/designate/latest/admin/backends/agent.html [3] https://github.com/openstack/designate/blob/master/designate/backend/privat… [4] https://www.rfc-editor.org/rfc/rfc6895.html#section-2.2 [5] https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-pa… [6] https://www.ietf.org/archive/id/draft-ietf-dnsop-dns-catalog-zones-08.txt [7] https://docs.openstack.org/project-team-guide/deprecation.html [8] https://review.opendev.org/c/openstack/designate/+/870678

3 13

[OPENSTACK][rabbitmq] using quorum queues
by Nguyễn Hữu Khôi 17 Oct '23

17 Oct '23

Hello guys. IS there any guy who uses the quorum queue for openstack? Could you give some feedback to compare with classic queue? Thank you. Nguyen Huu Khoi

9 19

[ptl][tc][winstackers] Final call for Winstackers PTL and maintainers
by James Page 11 Sep '23

11 Sep '23

Hi All As announced by Lucian last November (see [0]) Cloudbase Solutions are no longer in a position to maintain support for running OpenStack on Windows and have also ceased operation of their 3rd party CI for the windows support across a number of OpenStack projects. This situation has resulted in the Winstackers project becoming PTL-less for the 2023.2 cycle with no volunteers responding to the TC's call to fill this role and take this feature in OpenStack forward (see [1]). This is the final call for any maintainers to step forward if this feature is important to them in OpenStack. The last user survey in 2022 indicated that 2% of respondents were running on Hyper-V so this might be important enough to warrant a commitment from someone operating OpenStack on Windows to maintain these features going forward. Here is a reminder from Lucian's original email on the full list of projects which are impacted in some way: * nova hyper-v driver - in-tree plus out-of-tree compute-hyperv driver * os-win - common Windows library for Openstack * neutron hyperv ml2 plugin and agent * ovs on Windows and neutron ovs agent support * cinder drivers - SMB and Windows iSCSI * os-brick Windows connectors - iSCSI, FC, SMB, RBD * ceilometer Windows poller * manila Windows driver * glance Windows support * freerdp gateway The lack of 3rd party CI for testing all of this really needs to be addressed as well. If no maintainers are forthcoming between now and the next PTG in June the TC will need to officially retire the project and start the process of removing support for Windows across the various projects that support this operating system in some way - either directly or through the use of os-win. For clarity this call refers to the use of the Hyper-V virtualisation driver and associated Windows server components to provide WIndows based OpenStack Hypervisors and does not relate to the ability to run Windows images as guests on OpenStack. Regards James [0] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03104… [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-March/032888.h…

5 9

[openstack-ansible] Recommended branch for a production environment?
by Roger Rivera 05 Sep '23

05 Sep '23

Hello, We have deployed Openstack-Ansible in a test environment and we were wondering what the recommended repository branch is to deploy in a production environment that will be integrated with a separate Ceph cluster. 1. We are thinking about pinning to the stable/zed. Is that recommended over the master branch? 2. Are bugs ironed out on both master and stable/zed with the same cadence? 3. Additionally, is Debian 11 a better alternative than Ubuntu 22 for target hosts? We noticed Ubuntu 22.04 support was added recently, whereas Debian 11 has been supported for quite some time now which leads us to believe its stability/integration could be more mature at this point? Any suggestions will be appreciated. Thank you, -- *Roger *

3 7

[Rally]
by Aayushi Gautam 31 Aug '23

31 Aug '23

Hello, I am Aayushi , an intern with Redhat working on ESI ( Elastic secure Infracstructure) group. We were trying to use Rally to test the performance of our codebase. I have created a Plugin and task . And getting an error. The same bug is also asked on the bug page of Rally, but it was not answered. I have attached the code of the plugin and task and the error message. Looking forward to hearing from you.

2 5

[ptls][tc] OpenStack User Survey Updates
by Allison Price 29 Aug '23

29 Aug '23

Hi Everyone, Like Helena mentioned last week, we are closing the 2023 OpenStack User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers. If you and your team would like to update the question, please let me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey. In the meantime, please continue to promote openstack.org/usersurvey to anyone (and everyone!) you know who is running OpenStack or planning to in the future. We want to get as much feedback as we possibly can. Cheers, Allison

7 24

TripleO deployment over IPV6
by Kushagr Gupta 26 Aug '23

26 Aug '23

Hi Team, We were trying to perform IPV6-based deployment of TripleO. We are following the link: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16… As per our environment, we set the "ipv6_address_mode" to "dhcpv6-stateful" and tried undercloud deployment. It was successful. But when we try node introspection, openstack is not providing an IP that will be used for PXE booting the system. We have enabled PXE booting on the IPV6 network. On Dell machines, we get the following error: "PXE-E16: No offer received." For your reference, the undercloud file which we used is attached. We also tried to find the communication happening on the br-ctlplane interface when the machine tries to boot over IPV6 PXE boot. I am attaching those tcpdump records as well. We are unable to find the MAC address of our machines. *Questions:* 1. Is it even possible to perform tripleO deployment with IPV6? 2. Do we need to do some extra settings, so that our baremetal machines can be PXE booted? Thanks and Regards

3 9

[puppet] Proposing core team clean up
by Takashi Kajinami 23 Aug '23

23 Aug '23

Hello, I went through the current core reviewers and found out that the current list includes some people no longer working in the OpenStack community. I'd like to propose removing the following persons from the core reviewer team as we haven't seen these people making any activity in the community recently. * Pradeep Kilambi - puppet-aodh, puppet-ceilometer, puppet-gnocchi, puppet-panko * Richard Megginson - puppet-keystone * Denis Egorenko - puppet-murano * Serg Melikyan - puppet-murano * Sergey Kolekonov - puppet-neutron * David Moreau Simard - puppet-openstack-integration * Yu xingchao - all modules Also, I confirmed that Wes Hayutin is no longer working for OpenStack and he agreed to retire from the core reviewer position. Thus I'll remove him as well. I'll be open for any feedback for one week to hear any thoughts/feedback about this removal. I'd like to take this moment to thank all people for their past work. We always welcome them back if they resume their work in this project. Thank you, Takashi KAJINAMI

3 4

[charms] Nominate Martin Kalcok for charms-core
by Frode Nordahl 21 Aug '23

21 Aug '23

Hello all, I would like to nominate Martin Kalcok for charms-core. He has been part of the extended charms teams for some time now, and has provided many contributions to OpenStack, Ceph and OVN charms [0]. He is diligent and thorough in his contributions, and has recently become a full time member of the focused OVN team. 0: https://review.opendev.org/q/owner:martin.kalcok%2540canonical.com -- Frode Nordahl

5 4

[olso.messaging] RabbitMQ and streams
by Arnaud Morin 16 Aug '23

16 Aug '23

Hey all, Is there any chance that someone already worked on integrating RabbitMQ streams (see [1]) to replace fanouts in oslo rabbitmq driver? We are wondering if this would help lowering the rabbit usage, and maybe increase the rabbit stability? Our deployment is relying a lot on fanouts to delivers messages to computes (mostly neutron, e.g. secgroup update / remote cache population), this is leading to a massive number of messages beeing delivered by seconds. Cheers, Arnaud [1] https://www.rabbitmq.com/streams.html

2 2

LDAP failover fails
by Albert Braden 14 Aug '23

14 Aug '23

We are experiencing the LDAP failover issue described in [1]. Redhat’s solution is to not bother fixing the bug, and to tell customers to put the LDAP server behind a load-balancer. According to Redhat, that is not a good solution for FreeIPA, as explained in [2] and further elucidated in the blog post [3] that it references. I see that the community has a bug open for this [4] and the bug is being worked on here [5] but there has been no activity since 10/22. What is the status of this bugfix? Does it just need someone to review and merge it, or is there more work to be done? How are other FreeIPA users working around this problem? [1] https://bugzilla.redhat.com/show_bug.cgi?id=2024602#c3 [2] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/ht… [3] http://ssimo.org/blog/id_019.html [4] https://bugs.launchpad.net/keystone/+bug/1953622 [5] https://review.opendev.org/c/openstack/keystone/+/821086

2 4

[openstack][neutron[nova][kolla-ansible]instance cannot ping after live migrate
by Nguyễn Hữu Khôi 02 Aug '23

02 Aug '23

Hello guys. I am using openstack yoga with kolla ansible. When I migrate: instance1 from host A to host B after that I cannot ping this instance(telnet also). I must restart neutron_openvswitch_agent or move this instance back to host B then this problem has gone. this is my settings: ----------------- neutron.conf ----------------- [nova] live_migration_events = True ------------------------------------------------ ----------------- nova.conf ----------------- [DEFAULT] vif_plugging_timeout = 600 vif_plugging_is_fatal = False debug = True [compute] live_migration_wait_for_vif_plug = True [workarounds] enable_qemu_monitor_announce_self = True ----------------- openvswitch_agent.ini----------------- [securitygroup] firewall_driver = openvswitch [ovs] openflow_processed_per_port = true I check nova, neutron, ops logs but they are ok. Thank you. Nguyen Huu Khoi

4 12

Tap as a service on openstack with Juju and MaaS
by Jean-Bernard Altidor 01 Aug '23

01 Aug '23

Hello, I've been struggling to configure tap as a service on openstack for a few months now. I can't find any guide or anything about it. Can you suggest a method of port mirroring? I've even via the ovs bridge but I really need a way to mirror data and send it to an instance for analysis as I'm working on an IDS. Thanks in advance for any ideas ! JB

2 2

[nova] Scheduler Optimiser
by Dominik Danelski 31 Jul '23

31 Jul '23

Hello, I would like to introduce you to the tool developed under the working title "Scheduler Optimiser". It is meant to test the effectiveness of different Scheduler configurations, both weights and filters on a given list of VM orders and in a semi-realistic infrastructure. My company - CloudFerro - has been preparing in-house for the last few months and foresees publishing the project as FOSS once it reaches the MVP stage. To make the final result more useful to the community and speed up the development (and release), I humbly ask for your expertise: Are you aware of previous similar efforts? Do you notice some flaws in the current approach? What, in your opinion, are more important aspects of the infrastructure behaviour, and what can be relatively safely ignored in terms of the effect on Scheduler results/allocation? Project objectives: * Use Devstack (or another OpenStack deployer) with a real Scheduler to replay a list of compute VM orders, either real from one's infrastructure or artificially created. * Assess the effectiveness of the scheduling in various terms like: "How many machines of a given type can still be allocated at the moment?" using plug-in "success meters". In a strict sense, the project does not simulate THE Scheduler but interacts with it. * Use fake-virt to emulate huge architectures on a relatively tiny test bench. * Have as little as possible, and ideally no changes to the Devstack's code that could not be included in the upstream repository. The usage should be as simple as: 1. Install Devstack. 2. Configure Devstack's cluster with its infrastructure information like flavours and hosts. 3. Configure Scheduler for a new test case. 4. Replay VM orders. 5. Repeat steps 3 and 4 to find better Scheduler settings. * Facilitate creating a minimal required setup of the test bench. Not by replacing standard Devstack scripts, but mainly through tooling for quick rebuilding data like flavours, infrastructure state, and other factors relevant to the simulation. Outside of the scope: * Running continuous analysis on the production environment, even if some plug-ins could be extracted for this purpose. * Retaining information about users and projects when replaying orders. * (Probably / low priority) replaying actions other than VM creation/deletion as they form a minority of operations and ignoring them should not have a distinct effect on the comparison experiments. Current state: Implemented: * Recreating flavours from JSON file exported via OpenStack CLI. * Replaying a list of orders in the form of (creation_date, termination_date, resource_id (optional), flavor_id) with basic flavour properties like VCPU, RAM, and DISK GB. The orders are replayed consecutively. * Plug-in success-rater mechanism which runs rater classes (returning quantified success measure) after each VM add/delete action, retains their intermediate history and "total success" - how it is defined is implementation dependent. First classes interacting with Placement like: "How many VMs of flavours x (with basic parameters for now) can fit in the cluster?" or "How many hosts are empty?". Missing: * Recreating hosts, note the fake-virt remark from "Risks and Challenges". * Tools facilitating Scheduler configuration. * Creating VMs with more parameters like VGPU, traits, and aggregates. * (Lower priority) saving the intermediate state of the cluster during simulation i.e. allocations to analyse it without rerunning the experiment. Currently, only the quantified meters are saved. * Gently failing and saving all information in case of resource depletion: close to completion, handling one exception type in upper layers is needed. * More success meters. Risks and Challenges: * Currently, the tool replays actions one by one, it waits for each creation and deletion to be complete before running success raters and taking another order. Thus, the order of actions is important, but not their absolute time and temporal density. This might skip some side-effects of a realistic execution. * Similarly, to the above, fake-virt provides simple classes that will not reproduce some behaviours of real-world hypervisors. An explicit Scheduler avoids hosts that had recently failed to allocate a VM, but most likely fake-virt will not mock such behaviour. * Fake-virt should reproduce a real diverse infrastructure instead of x copies of the same flavour. This might be the only, but very important change to the OpenStack codebase. If successful, it could benefit other projects and tests as well. Even though the list of missing features is seemingly larger, the most important parts of the program are already there, so we hope to finish the MVP development in a relatively short amount of time. We are going to publish it as FOSS in either case, but as mentioned your observations would be very much welcome at this stage. I am also open to answering more questions about the project. Kind regards Dominik Danelski

3 3

[neutron] bug deputy report for week of 2023-07-24
by Bence Romsics 31 Jul '23

31 Jul '23

Hi All, We had the following new bugs in the last week or so: Unassigned: * https://bugs.launchpad.net/neutron/+bug/2028651 [ovn] IPv6 VIPs broken with ML2/OVN * https://bugs.launchpad.net/neutron/+bug/2028442 Support DNS for ovn_{nb,sb}_connection * https://bugs.launchpad.net/neutron/+bug/2028285 [unit test][xena+] test_port_deletion_prevention fails when runs in isolation Likely valid and high, but my dvr-fu is weak. dvr folks, please have a look: * https://bugs.launchpad.net/neutron/+bug/2028795 Restarting OVS with DVR creates a network loop fix proposed: https://review.opendev.org/c/openstack/neutron/+/889752 High: * https://bugs.launchpad.net/neutron/+bug/2028185 Large number of FIPs causes slow sync_routers response fix proposed: https://review.opendev.org/c/openstack/neutron/+/888915 * https://bugs.launchpad.net/neutron/+bug/2028846 FIP PF don't works with vlan tenant network and ovn backend fix proposed: https://review.opendev.org/c/openstack/neutron/+/889871 Medium: * https://bugs.launchpad.net/neutron/+bug/2028161 [ovn-octavia-provider] FIP not included into LogicalSwitchPortUpdate event handler method fix merged on master, backports proposed: https://review.opendev.org/q/Ibee3906e8e9575fba7811e989e3e111a026ce45b Low: * https://bugs.launchpad.net/neutron/+bug/2028724 neutron should forbid configuring agent_down_time that is known to crash due to CPython epoll limitation fix proposed: https://review.opendev.org/c/openstack/neutron/+/889373 RFE: * https://bugs.launchpad.net/neutron/+bug/2028660 [fwaas][rfe] support list type of port_range for firewall rule Incomplete: * https://bugs.launchpad.net/neutron/+bug/2028338 Router with l3_agent state unknown Invalid: * https://bugs.launchpad.net/neutron/+bug/2028544 dhcp agent binding count greather than dhcp_agents_per_network Cheers, Bence (rubasov)

1 0

[OSA] Failover at the storage level
by Murilo Morais 29 Jul '23

29 Jul '23

Good morning everybody! I'm trying to raise a scenario with redundancy at the storage level. I'm using CEPH with RBD-mirror. Cinder has a pretty clear documentation about it, but I didn't find anything about Glance and the "nova_libvirt_images_rbd_pool" and the "cinder_service_backup_driver". What would be the best approach? Only use Cinder with Mirror? If by chance the "nova_libvirt_images_rbd_pool" dies, if you are using config-drive the disk will die, correct? In this case, would it be better to leave local? I can't see what would be the best scenario for Failover cases with OSA. Thanks in advance!

2 1

[openstack-helm] [ceph deployment failed] error:- MountVolume.SetUp failed for volume "ceph-client-admin-keyring" secret "ceph-client-admin-keyring" not found
by Viswanath Ediga 29 Jul '23

29 Jul '23

Team, I am trying to deploy openstack using OSH. I am following documentation https://docs.openstack.org/openstack-helm/latest/install/multinode.html I am getting error while "Deploying ceph" phase. container creation is failing. Below is the error that I see in POD description Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedMount 24m (x73 over 3h7m) kubelet Unable to attach or mount volumes: unmounted volumes=[ceph-client-admin-keyring], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition Warning FailedMount 4m18s (x99 over 3h9m) kubelet MountVolume.SetUp failed for volume "ceph-client-admin-keyring" : secret "ceph-client-admin-keyring" not found Regards, Any help is appreciated. Kasi Viswanath

1 0

[manila] Collaborative Review session on resource locks
by Goutham Pacha Ravi 29 Jul '23

29 Jul '23

Hello Zorillas and other interested stackers, We're hosting a collab-review session on the changes pertaining to resource locks [1]. These changes are being pursued for the 2023.2/Bobcat release. The collab-review meeting will be at 1530 UTC on Thursday, Aug 3rd 2023 (gcal [2]). The meeting link will be published on the etherpad closer to the event, and shared during the IRC meeting that begins at 1500 UTC on the same day. [3] A reminder for the unfamiliar, a "collab-review" is a regular activity that the team does where patch authors provide a walkthrough of the code changes on a virtual community meeting and answer questions real time. This has helped us speed up reviews in past cycles. While the intention is to brainstorm synchronously, we will reflect all feedback - big and small, on Gerrit for posterity. In addition, the meeting call will be recorded, and the recording will be made available on the community's Youtube channel. [4] Hoping to see you there! Goutham [1] https://etherpad.opendev.org/p/manila-allow-locking-shares-against-deletion [2] https://red.ht/manila-bobcat-collab-review [3] https://wiki.openstack.org/wiki/Manila/Meetings#Next_Meeting [4] https://www.youtube.com/@openstackmanila

1 0

[charms][sunbeam] Proposing Guillaume Boutry for charms-core
by James Page 28 Jul '23

28 Jul '23

Hi All Guillaume has been working on the Sunbeam Charms for the last few months and has proven an able reviewer and contributor to the charms; we need to dis-entangle the sunbeam project charms from the main openstack charms set but until that work is completed I'd like to propose Guillaume as a member of the charms-core team. Cheers James

3 3

[nova] Nova meetings on Aug 1 and Aug 8 are CANCELLED
by Sylvain Bauza 28 Jul '23

28 Jul '23

As said above, we don't have quorum. Gibi will be chairing on Aug 15 1600UTC. As a reminder, any person is welcome (even if you are not a contributor) during our IRC meetings. You can find all our weekly minutes and our connection details in https://meetings.opendev.org/#Nova_Team_Meeting Thanks, -Sylvain

1 0

[cloudkitty] question to the scope_key in cloudkitty
by Noah Elias Feldt 28 Jul '23

28 Jul '23

Hello! I am currently trying to get CloudKitty to work with the Prometheus Collector and PyScripts. I noticed that the scope_key for Prometheus can only be changed once in the global configuration file. This was a problem for me because we need different scope_keys for different metrics. Many of the metrics still need the scope key "tenant_id" and some others "project_id". I have found in the documentation of CloudKitty no way to change this for each metric, so I have internally changed something in the source code and added the function to set the scope_key for each metric individually. I just wanted to ask if you would be interested if I submit the small change upstream? Thank you. Regards Noah Feldt

3 3

[Octavia] Weekly meetings cancelled
by Gregory Thiemonge 28 Jul '23

28 Jul '23

Hi, As discussed during the weekly meeting, the next 2 Octavia meetings are cancelled. The next meeting will be on Aug 16. Thanks Greg

1 0

[requirements] Blockdiag replacement (not working with Pillow 10)
by Karolina Kula 27 Jul '23

27 Jul '23

Hello, There are projects[1] which are depending on python-sphinxcontrib-blockdiag[2], which depend on blockdiag [3]. Blockdiag project has no recent changes and seems to be unmaintained. Current version of blockdiag is not compatible with Pillow 10 [4] which is included in current in-flight requirements update [5]. I was trying to contact the maintainer, but with no success. What'd be the best way to proceed? Are there any replacements for this project? [1] https://codesearch.opendev.org/?q=blockdiag&i=nope&literal=nope&files=requi… [2] https://github.com/blockdiag/sphinxcontrib-blockdiag [3] https://github.com/blockdiag/blockdiag [4] https://github.com/blockdiag/blockdiag/pull/174 [5] https://review.opendev.org/c/openstack/requirements/+/884564 Regards, Karolina Kula

3 2

Cinder API version
by Srinivasan T 27 Jul '23

27 Jul '23

2 2

[cinder] cinder-backup volume stuck in creating
by Satish Patel 27 Jul '23

27 Jul '23

Folks, I have configured nova and cinder with ceph storage. VMs running on ceph storage but now when i am trying to create a backup of cinder volume its getting stuck on creating and doing nothing. Logs also do not give any indication of bad. My cinder.conf [DEFAULT] enabled_backends = rbd-1 backup_driver = cinder.backup.drivers.ceph.CephBackupDriver backup_ceph_conf = /etc/ceph/ceph.conf backup_ceph_user = cinder-backup backup_ceph_chunk_size = 134217728 backup_ceph_pool = backups backup_ceph_stripe_unit = 0 backup_ceph_stripe_count = 0 restore_discard_excess_bytes = true osapi_volume_listen = 10.73.0.181 osapi_volume_listen_port = 8776 Output of "openstack volume service list" showing cinder-backup service is up but when i create a backup it's getting stuck in this stage and no activity. I am not seeing anything getting transferred to the ceph backups pool also. Any clue? or method to debug? # openstack volume backup list --all +--------------------------------------+------+-------------+----------+------+ | ID | Name | Description | Status | Size | +--------------------------------------+------+-------------+----------+------+ | bc844d55-8c5a-4bd3-b0e9-7c4c780c95ad | foo1 | | creating | 20 | +--------------------------------------+------+-------------+----------+------+

5 7

[release] Release countdown for week R-9, Jul 31-Aug 04
by Elõd Illés 27 Jul '23

27 Jul '23

General Information ------------------- The following cycle-with-intermediary deliverables have not done any intermediary release yet during this cycle. The cycle-with-rc release model is more suited for deliverables that plan to be released only once per cycle. As a result, we have detected that the following deliverables could be good candidates for a release model change: bifrost ironic-prometheus-exporter ironic-python-agent-builder ironic-ui networking-baremetal networking-generic-switch python-openstackclient swift PTLs and release liaisons for each of those deliverables should propose an intermediary release for their deliverables. If PTLs or release liaisons think that any of the deliverables should change to cycle-with-rc model then let us know and a patch needs to be created for the model change. We also published a proposed release schedule for the upcoming 2024.1 Caracal cycle. Please check out the separate thread: https://lists.openstack.org/pipermail/openstack-discuss/2023-July/034555.ht… Upcoming Deadlines & Dates -------------------------- Non-client library freeze: August 24th, 2023 (R-6 week) Client library freeze: August 31st, 2023 (R-5 week) Bobcat-3 milestone: August 31st, 2023 (R-5 week) Final 2023.2 Bobcat release: October 4th, 2023 Előd Illés irc: elodilles @ #openstack-release

1 0

[OSA][NEUTRON] DHCP port IP
by Murilo Morais 27 Jul '23

27 Jul '23

Good evening everyone! I'm using OVS + VLAN Provider Guys, is there any way to remove IP from DHCP (network:dhcp)? My gateway is external, I need the VMs to obtain the IPs directly on the interface without using SNAT/DNAT, but when enabling DHCP on the subnet, the DHCP interface consumes an IP (the first one available). Is there a way to remove this blessed IP? If not, what other path can I take? I'm thinking of other alternatives: 1. Use static IP 2. Use a DHCP Server on the Gateway (which makes me have to perform some manual operations to assign the correct IP) What would be more viable? Thanks in advance!

3 3

Proposed 2024.1 "Caracal" release schedule
by Elõd Illés 27 Jul '23

27 Jul '23

Hi, Here is the proposed schedule for the 2024.1 "Caracal" release: https://review.opendev.org/c/openstack/releases/+/888942 For easier review, you can access the HTML rendering at: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/… It's a 26-week cycle with a final release date on April 3, 2024. It has a longer milestone-2 period to accomodate Thanksgiving and end-of-year holidays. Please review & comment! Thanks, Előd Illés irc: elodilles @ #openstack-release

1 0

Version support matrix?
by Ken D'Ambrosio 27 Jul '23

27 Jul '23

Hey, all. I'm trying to figure out which OpenStack versions support which Linux distros and versions, both guest-side and controller/compute side. Does such a document exist, or is there a generally good place to look for each version of OpenStack? Thanks!

6 6

[tc] Reminder: 2023-08-09 OpenInfra Board Sync
by Jeremy Stanley 27 Jul '23

27 Jul '23

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/2023-08-board-openstack-sync As previously announced[*], we're planning to hold the next call at 20:00 UTC on Wednesday, August 9. A link to the conference bridge has been added to the pad and is also included in the schedule file attached to this message. [*] https://lists.openstack.org/pipermail/openstack-discuss/2023-May/033793.html -- Jeremy Stanley

2 2

[Glance] Weekly Meeting Cancelled
by Pranali Deore 27 Jul '23

27 Jul '23

Hi All, Canceling today's glance weekly meeting, I'm on sick leave today. Sorry for inconvenience! Thanks, Pranali D.

1 0

[cinder][all] Cinder to EOL all EM branches
by Rajat Dhasmana 26 Jul '23

26 Jul '23

Hi All, This is a followup to my last email[1] where a lot of discussion happened around the nature of EM branches and was/is it a successful model or not. This was also discussed during the Vancouver summit + PTG event and also recently in the TC meeting concluding that we will start a discussion again on ML regarding the EM model. However, my original intent of the mail was not to start a wider discussion about the EM model (which is a good discussion but not my intent) but a way to take feedback on Cinder team's decision to EOL the current EM branches and if it affects any operators, vendors etc. This mail is another reminder and a way to acquire more feedback on the above decision so the Cinder team can plan the process accordingly. We already have patches proposed to EOL all EM branches[2]. [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-June/033980.ht… [2] https://review.opendev.org/q/topic:cinder-eol-june2023 Thanks Rajat Dhasmana

6 12

Cinder Bug Report 2023-07-26
by Sofia Enriquez 26 Jul '23

26 Jul '23

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> Medium - [Pure Storage] Replication failover issue. <https://bugs.launchpad.net/cinder/+bug/2028380> - *Status*: Fix merged on master <https://review.opendev.org/c/openstack/cinder/+/817085> but needs backports to stable/yoga. Invalid - [tempest] Container not deleted when swift is used as a back up driver <https://bugs.launchpad.net/cinder/+bug/2028671>. - *Status*: Marked as invalid because cinder has never deleted the container when deleting a backup. Cheers, -- 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

[cinder] This week's meeting will be in video+IRC
by Rajat Dhasmana 26 Jul '23

26 Jul '23

Hello Argonauts, As we keep last meeting of the month in video + IRC mode, this week's meeting (today) will be held in video + IRC mode with details as follows: Date: 26th July, 2023 Time: 1400 UTC Meeting link: https://meet.google.com/mmb-fhtd-sjm IRC Channel: #openstack-meeting-alt Make sure you're connected to both the gmeet meeting and IRC. Thanks Rajat Dhasmana

1 0

[cinder] Resignation from Cinder core & Bug Deputy
by Sofia Enriquez 26 Jul '23

26 Jul '23

Hello Argonauts, I will be transitioning from my current role at Red Hat, and my availability for patch making and reviewing will be limited after July. Considering these circumstances, I believe it is appropriate for me to resign as a Cinder core reviewer and as Cinder Bug Deputy. Feel free to connect with me on LinkedIn <https://www.linkedin.com/in/enriquetaso/> and/or follow on Twitter <https://twitter.com/EnriquetaSo> / Github <https://github.com/enriquetaso/>. 🍻 I look forward to staying in touch and crossing paths again in the future. [image: denver_ptg.jpeg] Wishing you all the best, and thank you!🍻 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>

7 6

[neutron] Transition networking-bagpipe & networking-bgpvpn stable/victoria to EOL
by Lajos Katona 25 Jul '23

25 Jul '23

Hi Neutrinos (and everybody), The stable/victoria branch for networking-bagpipe and networking-bgpvpn is failing with tempest since long time. We tried to fix it (see [1] & [2]), and discussed it on our regular meeting (see [3]), but as the activity on this branch for these projects is low anyway I propose to EOL stable/victoria for networking-bagpipe and networking-bgpvpn. If you have any concerns, suggestions or questions, please let me know (via mail or IRC in the #openstack-neutron channel). Lajos (lajoskatona) [1]: https://review.opendev.org/c/openstack/networking-bgpvpn/+/888719 [2]: https://review.opendev.org/c/openstack/networking-bagpipe/+/862505 [3]: https://meetings.opendev.org/meetings/neutron_ci/2023/neutron_ci.2023-07-18…

1 0

[all][outreachy] ☕ Looking for at least two volunteers for a virtual coffee chat
by Sofia Enriquez 25 Jul '23

25 Jul '23

Hello, We're currently seeking two volunteers to engage in casual chats with our Outreachy interns, @Desire Barine <desirebarine16(a)gmail.com> and @toheeb.olawale.to23@gmail.com <toheeb.olawale.to23(a)gmail.com> Asking to network with someone can be intimidating. An informal chat, on the other hand, is a friendly conversation with another person about their career or role as a free software contributor. This provides valuable insight for the intern, allowing them to learn about a professional's work, career journey, and networking experiences within the free software community. After the chat, the intern can request three additional people to speak with, thus expanding their network! Here's how to conduct an informal chat: - The intern will ask you questions about your career. - The chat can take place through a half-hour gmeet session (without video) or via IRC chat. - You can share tips on maximizing networking opportunities and offer advice to those interested in exploring career prospects in open source. If you are interested in participating, please contact @Rajat Dhasmana <rdhasman(a)redhat.com> with the date and time you are available! 📖 The interns journey with Openstack has been featured on the Superuser blog: - Getting an Outreachy Internship with OpenStack <https://superuser.openinfra.dev/articles/getting-an-outreachy-internship-wi…> - What is OpenStack? A Fresh Look from a Clear Mind <https://superuser.openinfra.dev/articles/what-is-openstack-a-fresh-look-fro…> Thank you for your consideration! -- 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

Info Public Cloud SIG for openstack-discuss
by Felix Kronlage-Dammers 25 Jul '23

25 Jul '23

Hi, in the Public Cloud SIG we discussed on how to get more OpenStack Public Cloud Operators back into the Public Cloud SIG and concluded that we’ll have a lightning talk once per month as part of our Public Cloud SIG meeting. This means that once a month we will exchange the IRC-session for a videocall session (in the same timeslot). To make it easy for everyone we will paste the link at the time of the meeting onto #openstack-operators as well as it being included in the reminder mail sent to openstack-discuss@ beforehand. We will be starting with that after the current vacation period in September. We’ll be reaching out to the OpenInfra community as well as the various OpenStack based public clouds out there to get people involved :) Due to vacation the irc meeting on August 2nd (next week) will not be happening, since both Tobias and me are on vacation. felix (in the name of Tobias and myself ;) -- Felix Kronlage-Dammers Product Owner IaaS & Operations Sovereign Cloud Stack Sovereign Cloud Stack — standardized, built and operated by many Ein Projekt der Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

[openstack][nova] Resize nova instance with PCI devices to a flavor without PCI Devices
by Ha Noi 25 Jul '23

25 Jul '23

Hello everyone, I would like to resize an instance with PCI devices (GPU Passthrough) to a flavor without PCI Devices, but nova-api return no valid host. Response: No valid host was found. No valid host found for resize (HTTP 400) (Request-ID: req-9d6cf3f9-8f6f-482f-b0b1-95ec286a0fc3) I checked nova-scheduler log: Filtering removed all hosts for the request with instance ID 'e7b607ef-6be5-4bbc-9849-e31d622ecdfe'. Filter results: ['AggregateInstanceExtraSpecsFilter: (start: 85, end: 44)', 'RetryFilter: (start: 44, end: 44)', 'AvailabilityZoneFilter: (start: 44, end: 29)', 'ComputeFilter: (start: 29, end: 29)', 'ImagePropertiesFilter: (start: 29, end: 29)', 'ServerGroupAntiAffinityFilter: (start: 29, end: 29)', 'ServerGroupAffinityFilter: (start: 29, end: 29)', 'PciPassthroughFilter: (start: 29, end: 0)'] Actually, new flavor is not contain PCI specs, But It cannot pass PCI Filter. Thanks & Regards

1 0

Nova Ussuri: DB online migration cannot migrate (some) populate_user_id
by Michel Jouvin 25 Jul '23

25 Jul '23

Hi, We upgraded one of our clouds to Ussuri (we are late!) a couple of months ago. After the upgrade 'nova-manage db online_data_migration' was run. fill_virtual_interface_list and populate_user_id where non zero and after running the command fill_virtual_interface_list was 0 but populate_user_id stayed 24. Looking in nova-manage.log, I found the follwoing message (twice every time the command is run): Some instance mappings were not migratable. This may be transient due to in-flight instance builds, or could be due to stale data that will be cleaned up after running "nova-manage db archive_deleted_rows --purge". I ran the suggest command but the result is that fill_virtual_interface_list is non zero again (15) and there is no change to populate_user_i. If I run again online_data_migration, it clears again fill_virtual_interface_list... and so on. After 2 months the situation remains the same, no increase in populate_user_id but no possibility to fix them. We were wondering if it could have been caused by the fact that we had not yet upgraded all the compute nodes when we first ran the online_data_migration. We are planning to upgrade to Victoria and we'd like to fix the situation before as we understand that online data migration not done can be blocking for the next upgrade. We don't have any clue on the reason this happened. It is a test cloud with a very low usage. On our production cloud we have a somewhat similar problem but populate_user_id=1 and running the purge doesn't increase fill_virtual_interface_list. Thanks in advance for any hint! Best regards, Michel

2 1

Re: [openstack][largescale-sig] Openstack multi region deployment
by Nguyễn Hữu Khôi 25 Jul '23

25 Jul '23

Thanks for your explanation., Very details. This time, I have not much knowledge, But I will keep build and sharing with people as the same way you help me.

1 0

[openstack][largescale-sig] Openstack multi region deployment
by Karl Kloppenborg 25 Jul '23

25 Jul '23

Hi Nguy, We’ve deployed a large multi-region openstack deployment. As a rule of thumb we’ve got a “keystone” region which is as best we can highly available and very redundant. We then have all other regions talk back to this region, we just usually call it “keystone” or “core” and it’s hidden from the UI from users. We then just run a large well kept Galara cluster to support it. --Karl. From: openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> Date: Tuesday, 18 July 2023 at 9:25 pm To: openstack-discuss(a)lists.openstack.org <openstack-discuss(a)lists.openstack.org> Subject: openstack-discuss Digest, Vol 57, Issue 55 Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss or, via email, send a message with subject or body 'help' to openstack-discuss-request(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. [openstack][largescale-sig] Openstack multi region deployment (Nguy?n H?u Kh?i) 2. Re: [openstack][largescale-sig] Openstack multi region deployment (Felix Huettner) 3. Re: [openstack][largescale-sig] Openstack multi region deployment (Nguy?n H?u Kh?i) 4. Re: [neutron] unmanaged router resources - OVN interconnect (Rodolfo Alonso Hernandez) ---------------------------------------------------------------------- Message: 1 Date: Tue, 18 Jul 2023 12:07:12 +0700 From: Nguy?n H?u Kh?i <nguyenhuukhoinw(a)gmail.com> To: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> Subject: [openstack][largescale-sig] Openstack multi region deployment Message-ID: <CABAODReJ6QW8A4OENEjmhFCiM-15B0qc2La_aMr1EKfaENq9iw(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hello guys, I am going to deploy openstack multi regions and I know that keystone replication is the most challenging. I plan to set up 2 regions which use centralize galera cluster(3 nodes). and one standby edge galera cluster(3 nodes) When region 1 is node available, I will map region 2 to use standby edge galera cluster. I hope you give me some experience and advice with multi regions. Thank you very much.

3 6

[tc] Technical Committee next weekly meeting today on July 25, 2023
by Nikolla, Kristi 24 Jul '23

24 Jul '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held on Tuesday, July 25, 2023 at 1800 UTC on #openstack-tc on OFTC IRC. Please find below the agenda for the meeting • Roll call • Follow up on past action items • knikolla will amend proposal for Unmaintained branches. • tc-members to review https://review.opendev.org/c/openstack/project-team-guide/+/843457 • Extended Maintenance • https://etherpad.opendev.org/p/openstack-unmaintained-workflow • https://etherpad.opendev.org/p/openstack-exteneded-maintenance • Release notes guidelines for SLURP/NON-SLURP cadence • Gate health check • Open Discussion and Reviews • https://review.opendev.org/q/projects:openstack/governance+is:open Thank you, Kristi Nikolla

1 0