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

Fwd: DPDK+OVS with OpenStack
by Mark Wittling 23 Apr '25

23 Apr '25

Looking for someone who knows OpenStack with OpenVSwitch, and in addition to that, DPDK with OpenStack and OVS.I am using OpenStack Queens, with OpenVSwitch. The architecture I am using is documented here: https://docs.openstack.org/neutron/queens/admin/deploy-ovs-provider.htmlThe OVS I am using on the Compute Node, is compiled with DPDK, and I have enabled the datapath to netdev (DPDK) on br-prv (provider network bridge), and br-tun (tunneling bridge). But these two bridges, br-tun and br-prv, are patched into another OpenStack bridge, called br-int. I wasn’t actually sure about whether to tinker with this bridge, and wondered what datapath it was using.Then, I realized there is a parameter in the openvswitch_agent.ini file, which I will list here: # OVS datapath to use. 'system' is the default value and corresponds to the # kernel datapath. To enable the userspace datapath set this value to 'netdev'. # (string value) # Possible values: # system - <No description provided> # netdev - <No description provided> #datapath_type = system datapath_type = netdev So in tinkering with this, what I realized, is that when you set this datapath_type to system or netdev, it will adjust the br-int bridge to that datapath type.So here is my question. How can I launch a non-DPDK VM, if all of the bridges are using the netdev datapath type?Here is another question. What if one of the flavors don’t have the largepages property set on them? I assumed OpenStack would revert to a system datapath and not use DPDK for those VM interfaces. Well, I found out in testing, that is not the case. If you set all your bridges up for netdev, and you don’t set the property on the Flavor of the VM (largepages), the VM will launch, but it simply won’t work.Is there no way, on a specific Compute Host, to support both DPDK (netdev datapaths) and non-DPDK (system datapaths)?Either on a VM interface level (VM has one interface that is netdev DPDK and another that is system datapath non-DPDK)?Or on a VM by VM basis (VM 1 has 1 or more netdev datapath interfaces and VM 2 has 1 or more system datapath interfaces)?Am I right here? Once you set up a Compute Host for DPDK, it’s DPDK or nothing on that Compute Host? (edited)

3 2

How to config DPDK compute in OVN
by dangerzone ar 22 Apr '25

22 Apr '25

Hi....as far I understand ovs does support dpdk compute to be deployed. I'm referring to the guideline ' *https://docs.openstack.org/networking-ovn/queens/admin/dpdk.html <https://docs.openstack.org/networking-ovn/queens/admin/dpdk.html>* ' ... It's too brief.. May I know how to config dpdk compute in OVN networking openstack? Hope someone could help what is the config to be done.... Currently compute is run without dpdk over openstack train ovn based. Please need some info on how I can proceed. Thank you

2 1

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

06 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

[all] Dynamic Zuul results table in Gerrit 3
by Radosław Piliszek 04 Aug '22

04 Aug '22

Hello Fellow OpenStack and OpenDev Folks! TL;DR click on [3] and enjoy. I am starting this thread to not hijack the discussion happening on [1]. First of all, I would like to thank gibi (Balazs Gibizer) for hacking a way to get the place to render the table in the first place (pun intended). I have been a long-time-now user of [2]. I have improved and customised it for myself but never really got to share back the changes I made. The new Gerrit obviously broke the whole script so it was of no use to share at that particular state. However, inspired by gibi's work, I decided to finally sit down and fix it to work with Gerrit 3 and here it comes: [3]. Works well on Chrome with Tampermonkey. Not tested others. I hope you will enjoy this little helper (I do). I know the script looks super fugly but it generally boils down to a mix of styles of 3 people and Gerrit having funky UI rendering. Finally, I'd also like to thank hrw (Marcin Juszkiewicz) for linking me to the original Michel's script in 2019. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-November/019051… [2] https://opendev.org/x/coats/src/commit/444c95738677593dcfed0cfd9667d4c4f0d5… [3] https://gist.github.com/yoctozepto/7ea1271c299d143388b7c1b1802ee75e Kind regards, -yoctozepto

5 7

[all] PyCharm Licenses Renewed till July 2021
by Swapnil Kulkarni 13 Jul '22

13 Jul '22

Hello, Happy to inform you the open source developer license for Pycharm has been renewed for 1 additional year till July 2021. Best Regards, Swapnil Kulkarni coolsvap at gmail dot com

8 13

Nova not updating to new size of an extended in-use / attached cinder volume (Ceph RBD) to guest
by Christian Rohmann 28 Jun '22

28 Jun '22

Hello Openstack-Discuss, after some digging I found out that cinder learned to resize attached (in-use) volumes quite a while ago with the introduction of the initial "extend 'in-use' volume" feature: https://review.opendev.org/c/openstack/cinder/+/454287/ The support was then extended to also cover Ceph RBD backed volumes with: https://review.opendev.org/c/openstack/nova/+/613039/ Since this is only about the cinder part, I was wondering if nova would ever find out and would actively rescan the device / volume and quintessentially present an increased new size to the guest. Apparently this is where a certain volume-extended event comes into play: https://review.opendev.org/c/openstack/nova/+/454322/ that is to be emitted by cinder when a volume had been extened. I then went head and tried this with the openstack cli (as Horizon does not seem to support / offer to resize in-use volumes. I run Openstack Train with Ceph RBD as storage. First I ran into an issue with the openstack cli (https://bugs.launchpad.net/cinder/+bug/1871759/comments/2 <https://bugs.launchpad.net/cinder/+bug/1871759/comments/2>) but using cinder extend $volumeid $newsize I was able to resize in-use volumes just fine. The only thing missing was the propagation to the guest. I played around with SCSI rescans, but that did not work, reboots also failed to do anyting in this regards. Stopping and starting the VM did work, but why having the capability to online-resize an attached volume when not being able to resize the guest volume as well? Apparently there seems to be an old and somewhat similar observation / bug with https://bugs.launchpad.net/nova/+bug/1369465 So I was simply wondering if this is expected to be working? Are there any special settings / options I need to set to enable this feature? Thanks and with kind regards Christian

4 9

[nova][dev] Revisiting qemu emulation where guest arch != host arch
by Apsey, Christopher 05 Jan '22

05 Jan '22

All, A few years ago I asked a question[1] about why nova, when given a hw_architecture property from glance for an image, would not end up using the correct qemu-system-xx binary when starting the guest process on a compute node if that compute nodes architecture did not match the proposed guest architecture. As an example, if we had all x86 hosts, but wanted to run an emulated ppc guest, we should be able to do that given that at least one compute node had qemu-system-ppc already installed and libvirt was successfully reporting that as a supported architecture to nova. It seemed like a heavy lift at the time, so it was put on the back burner. I am now in a position to fund a contract developer to make this happen, so the question is: would this be a useful blueprint that would potentially be accepted? Most of the time when people want to run an emulated guest they would just nest it inside of an already running guest of the native architecture, but that severely limits observability and the task of managing any more than a handful of instances in this manner quickly becomes a tangled nightmare of networking, etc. I see real benefit in allowing this scenario to run natively so all of the tooling that exists for fleet management 'just works'. This would also be a significant differentiator for OpenStack as a whole. Thoughts? [1] http://lists.openstack.org/pipermail/openstack-operators/2018-August/015653… Chris Apsey Director | Georgia Cyber Range GEORGIA CYBER CENTER 100 Grace Hopper Lane | Augusta, Georgia | 30901 https://www.gacybercenter.org

2 2

[all][sphinx] "rST localisation for language "foo" not found" error
by Stephen Finucane 24 Nov '21

24 Nov '21

We've seen issues in some projects, whereby attempting to build translations as part of the 'openstack-tox-docs' zuul job [1] can result in the following warning: Warning, treated as error: ../doc/source/contributor/contributing.rst::rST localisation for language "id" not found. Based on [2], this issue appears to have been introduced by a recent version bump of docutils, which was in turn introduced by the introduction of Sphinx 4.x. We don't have a resolution for this bug yet but we'll update when we do. Hopefully this email will improve the "Google'ability" of this bug. Stephen [1] https://opendev.org/openstack/openstackdocstheme/src/commit/08461c5311aa692… [2] https://lists.freebsd.org/pipermail/freebsd-ports/2021-April/120848.html

2 2

[docs] Double headings on every page
by Peter Matulis 04 Nov '21

04 Nov '21

Hi, I'm hitting an oddity in one of my projects where the titles of all pages show up twice. Example: https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/wall… Source file is here: https://opendev.org/openstack/charm-deployment-guide/src/branch/master/depl… Does anyone see what can be causing this? It appears to happen only for the current stable release ('wallaby') and 'latest'. Thanks, Peter

5 6

[all][tc] Yoga TC-PTG Planning
by Ghanshyam Mann 20 Oct '21

20 Oct '21

Hello Everyone, As you already know that the Yoga cycle virtual PTG will be held between 18th - 22nd October[1]. To plan the Technical Committee PTG sessions, please do the following: 1. Fill the below doodle poll as per your availability. Please fill it soon as deadline to book the slot is 21th July. - https://doodle.com/poll/6dfdmdfi4s8wc7cd 2. Add the topics you would like to discuss to the below etherpad. - https://etherpad.opendev.org/p/tc-yoga-ptg NOTE: this is not limited to TC members only; I would like all community members to fill the doodle poll and, add the topics you would like or want TC members to discuss in PTG. [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023540.html -gmann

1 2

[tacker] Yoga vPTG planning
by yasufum 15 Oct '21

15 Oct '21

Hi everyone, The next vPTG will be held on 18-22 October as I shared at the previous IRC meeting [1]. Registration has already opened [2]. We've decided to have the next vPTG session on the same timeslots, 6-8 UTC, as previous for most of us join from India and APAC regions. I've prepared etherpad for the next vPTG [3]. If you have any suggestion, please add your topic on it. [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023540.html [2] https://openinfra-ptg.eventbrite.com/ [3] https://etherpad.opendev.org/p/tacker-yoga-ptg Thanks, Yasufumi

2 1

[kuryr] Virtual PTG October 2021
by Maysa De Macedo Souza 12 Oct '21

12 Oct '21

Hello, I booked the following slots for Kuryr during the Yoga PTG: Oct 19 7-8 UTC and Oct 22 13-14 UTC. If you have any topic ideas you would like to discuss, please include them in the etherpad[1], also it would be interesting to include your name there if you plan to attend any Kuryr session. See you on the next PTG. Cheers, Maysa. [1] https://etherpad.opendev.org/p/kuryr-yoga-ptg

1 2

Help with eventlet 0.26.1 and dnspython >= 2
by Thomas Goirand 04 Oct '21

04 Oct '21

Hi, As you may know, eventlet is incompatible with dnspython >= 2.0.0.0rc1. See [1] for the details. However, Debian unstable has 2.0.0. Would there be some good soul willing to help me fix this situation? I would need a patch to fix this, but I'm really not sure how to start. Cheers, Thomas Goirand (zigo)

8 15

[ironic] Yoga PTG
by Iury Gregory 23 Sep '21

23 Sep '21

Hello Ironicers! We are approaching the time of the next PTG (it's in October but we need to make some decisions). Our yoga etherpad is available[1], feel free to add any topics we shall discuss. In the ethercalc[2] you can find the slots we already booked, we may add more slots for APAC if someone is willing to run the meeting and discussions. Don't forget to register! [3]. [1] https://etherpad.opendev.org/p/ironic-yoga-ptg [2] https://ethercalc.openstack.org/8tum5yl1bx43 [3] https://openinfra-ptg.eventbrite.com -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 1

[all][tc][goals] Project Specific PTL and Contributor Documentation: Week R-20 Update
by Ghanshyam Mann 17 Sep '21

17 Sep '21

Hello Everyone, As you know, we did not select any community-wide goal for Xena cycle and in PTG, TC decided to spend more time on the previous cycle pending community-wide goal work[1] One of the previous cycle (Ussuri) goals is 'Project Specific PTL and Contributor Documentation' which still not completed by many projects. - https://governance.openstack.org/tc/goals/selected/ussuri/project-ptl-and-c… I am starting the work to finish this goal which is pretty straight forwards and sending the updates in this ML thread. Please review the patches and merge them or push the patches for your project's repo if not yet done. Gerrit Topic: https://review.opendev.org/q/topic:%22project-ptl-and-contrib-docs%22+(stat… Tracking: https://storyboard.openstack.org/#!/story/2007236 Progress Summary: =============== * Projects completed: 32 * Projects for which patches are up and required to merge those: 10 * Projects for which patches are not yet up: 12 [1] https://etherpad.opendev.org/p/tc-xena-tracker (Item#2) -gmann

2 2

[all]Introduction to venus which is the project of log management and has been contributed to the OpenStack community
by Liye Pang(逄立业) 10 Sep '21

10 Sep '21

Hello everyone, after feedback from a large number of operations and maintenance personnel in InCloud OpenStack, we developed the log management project “Venus” for the OpenStack projects and that has contributed to the OpenStack community. The following is an introduction to “Venus”. If there is interest in the community, we are interested in proposing it to become an official OpenStack project in the future. Background In the day-to-day operation and maintenance of large-scale cloud platform, the following problems are encountered： l Time-consuming for log querying while the server increasing to thousands. l Difficult to retrieve logs, since there are many modules in the platform, e.g. systems service, compute, storage, network and other platform services. l The large amount and dispersion of log make faults are difficult to be discovered. l Because of distributed and interaction between components of the cloud platform, and scattered logs between components, it will take more time to locate problems. About Venus According to the key requirements of OpenStack in log storage, retrieval, analysis and so on, we introduced Venus project, a unified log management module. This module can provide a one-stop solution to log collection, cleaning, indexing, analysis, alarm, visualization, report generation and other needs, which involves helping operator or maintainer to quickly solve retrieve problems, grasp the operational health of the platform, and improve the management capabilities of the cloud platform. Additionally, this module plans to use machine learning algorithms to quickly locate IT failures and root causes, and improve operation and maintenance efficiency. Application scenario Venus played a key role in the following scenarios： l Retrieval: Provide a simple and easy-to-use way to retrieve all log and the context. l Analysis: Realize log association, field value statistics, and provide multi-scene and multi-dimensional visual analysis reports. l Alerts：Convert retrieval into active alerts to realize the error finding in massive logs. l Issue location: Establish a chain relationship and knowledge graphs to quickly locate problems. Overall structure The architecture of log management system based on Venus and elastic search is as follows: Diagram 0: Architecture of Venus venus_api: API module，provide API、rest-api service. venus_manager: Internal timing task module to realize the core functions of the log system. Current progress The current progress of the Venus project is as follows: l Collection：Develop fluentd collection tasks based on collectd to read, filter, format and send plug-ins for OpenStack, operating systems, and platform services, etc. l Index：Dealing with multi-dimensional index data in elasticsearch, and provide more concise and comprehensive authentication interface to return query results. l Analysis：Analyzing and display the related module errors, Mariadb connection errors, and Rabbitmq connection errors. l Alerts：Develop alarm task code to set threshold for the number of error logs of different modules at different times, and provides alarm services and notification services. l Location：Develop the call chain analysis function based on global_requested series, which can show the execution sequence, time and error information, etc., and provide the export operation. l Management：Develop configuration management functions in the log system, such as alarm threshold setting, timing task management, and log saving time setting, etc. Application examples Two examples of Venus application scenarios are as follows. 1. The virtual machine creation operation was performed on the cloud platform and it was found that the virtual machine was not created successfully. First, we can find the request id of the operation and jump to the virtual machine creation call chain page. Then, we can query the calling process, view and download the details of the log of the call. 2. In the cloud platform, the error log of each module can be converted into alarms to remind the users. Further, we can retrieve the details of the error log and error log statistics. Next step The next step of the Venus project is as follows: * Collection：In addition to fluent, other collection plugins such as logstash will be integrated. * Analysis: Explore more operation and maintenance scenarios, and conduct statistical analysis and alarm on key data. * display: The configuration, analysis and alarm of Venus will be integrated into horizon in the form of plugin. * location: Form clustering log and construct knowledge map, and integrate algorithm class library to locate the root cause of the fault. Venus Project Registry Venus library: https://opendev.org/inspur/venus You can grab the source code using the following git command: git clone https://opendev.org/inspur/venus.git Venus Demo Youtu.be: <https://youtu.be/mE2MoEx3awM> https://youtu.be/mE2MoEx3awM

7 15

[Kolla][Kolla-Ansible] Ironic Node Cleaning Failed
by Anirudh Gupta 01 Sep '21

01 Sep '21

Hi Team, We have deployed 2 node kolla ansible *12.0.0* in order to deploy openstack *wallaby* release. We have also enabled ironic in order to provision the bare metal nodes. On each server we have 3 nics - *eno1* - OAM for external connectivity and endpoint's publicURL - *eno2* - Mgmt for internal communication between various openstack services. - *ens2f0* - Data Interface Corresponding to this we have defined the following fields in globals.yml - kolla_base_distro: "centos" - kolla_install_type: "source" - openstack_release: "wallaby" - network_interface: "eno2" # MGMT interface - kolla_external_vip_interface: "eno1" # OAM Interface - kolla_internal_vip_address: "192.168.10.3" # MGMT Subnet free ip - kolla_external_vip_address: "10.0.1.136" # OAM subnet free IP - neutron_external_interface: "ens2f0" # Data Interface - enable_neutron_provider_networks: "yes" Note: Only relevant fields are being shown in this query Also, for ironic following fields have been defined in globals.yml - enable_ironic: "yes" - enable_ironic_neutron_agent: "{{ enable_neutron | bool and enable_ironic | bool }}" - enable_horizon_ironic: "{{ enable_ironic | bool }}" - ironic_dnsmasq_interface: "*ens2f0*" # Data interface - ironic_dnsmasq_dhcp_range: "20.20.20.10,20.20.20.100" - ironic_dnsmasq_boot_file: "pxelinux.0" - ironic_cleaning_network: "public1" - ironic_dnsmasq_default_gateway: "20.20.20.1" After successful deployment, a flat provider network with the name public1 is being created in openstack using the below commands: - openstack network create public1 --provider-network-type flat --provider-physical-network physnet1 - openstack subnet create subnet1 --network public1 --subnet-range 20.20.20.0/24 --allocation-pool start=20.20.20.10,end=20.20.20.100 --ip-version=4 --gateway=20.20.20.1 --dhcp Issue/Queries: - Is the configuration done in globals.yml correct or is there anything else that needs to be done in order to separate control and data plane traffic? - Also I have set automated_cleaning as "true" in ironic-conductor conatiner settings.But after creating the baremetal node, we run "node manage" command which runs successfully. Running "*openstack baremetal node provide <node id>"* command powers on the machine, sets the boot mode on Network Boot but no DHCP request for that particular mac is obtained on the controller. Is there anything I am missing that needs to be done in order to make ironic work? Note: I have also verified that the nic is PXE enabled in system configuration setting Regards Anirudh Gupta

3 15

[devstack][neutron][manila] Instances having trouble getting to external network with OVN
by Goutham Pacha Ravi 26 Aug '21

26 Aug '21

Hi, Some third party storage CI running against manila repos has had issues setting up VMs and providing access to external resources in devstack; these issues started around the time that the default ml2 plugin was switched to OVN. Folks in the manila team aren't familiar with devstack/CI networking to determine how to resolve these; and we'd totally appreciate help from networking experts in this regard. A sample local.conf file used by the CI is here: http://paste.openstack.org/show/807449/ Manila's tests: - create a private tenant network - setup a router that connects the private network to the public network - create a nova VM on the private tenant network - attempt to mount a share via NFS from within this VM The final step fails because the NFS mount command times out within the test VM: tempest.lib.exceptions.SSHExecCommandFailed: Command 'sudo mount -vt nfs "10.16.xx.xx:/share-96ae8d0c-8bab-4fcd-b278-51a6f473e03c-manila" /mnt', exit status: 32, stderr: mount.nfs: mount(2): Connection timed out mount.nfs: Connection timed out stdout: mount.nfs: timeout set for Mon Jun 28 14:47:19 2021 mount.nfs: trying text-based options 'vers=4.2,addr=10.16.xx.xx,clientaddr=10.1.0.26' The timeout seems to be because the VM is unable to reach the NFS server that's external to the devstack host. The NFS server is reachable from the devstack host. Have there been any changes to devstack configuration that we need to be aware of, wrt VMs having access to the external network? Thanks, Goutham

3 5

[masakari] Deprecating process monitor - querying the community in this thread
by Radosław Piliszek 23 Aug '21

23 Aug '21

Hello users of Masakari, As the Masakari core team, we have discussed the deprecation/retirement of one of the monitors - the process monitor. The reason is simple - we consider its mission is better handled by other software such as Kubernetes, Docker, or systemd, depending on how you deploy your OpenStack cluster. I believe the process monitor might have made sense in the pre-containerisation, pre-systemd world but it does not seem to any longer. Please let us know, by replying to this mail, if you have a use case for the process monitor that cannot be handled by the aforementioned software. -yoctozepto

1 1

[tripleo] Changing TripleO's release model
by Wesley Hayutin 20 Aug '21

20 Aug '21

Greetings TripleO community! At the most recent TripleO community meetings we have discussed formally changing the OpenStack release model for TripleO [1]. The previous released projects can be found here [2]. TripleO has previously released with release-type[‘trailing’, ‘cycle-with-intermediary’]. To quote the release model doc: ‘Trailing deliverables trail the release, so they cannot, by definition, be independent. They need to pick between cycle-with-rc <https://releases.openstack.org/reference/release_models.html#cycle-with-rc> or cycle-with-intermediary <https://releases.openstack.org/reference/release_models.html#cycle-with-int…> models.’ We are proposing to update the release-model to ‘independent’. This would give the TripleO community more flexibility in when we choose to cut a release. In turn this would mean less backporting, less upstream and 3rd party resources used by potentially some future releases. To quote the release model doc: ‘Some projects opt to completely bypass the 6-month cycle and release independently. For example, that is the case of projects that support the development infrastructure. The “independent” model describes such projects.’ The discussion here is to merely inform the greater community with regards to the proposal and conversations regarding the release model. This thread is NOT meant to discuss previous releases or their supported status, merely changing the release model here [3] [0] https://etherpad.opendev.org/p/tripleo-meeting-items [1] https://releases.openstack.org/reference/release_models.html [2] https://releases.openstack.org/teams/tripleo.html [3] https://opendev.org/openstack/releases/src/branch/master/deliverables/xena

9 17

It's time to submit your OpenStack User Survey
by Allison Price 19 Aug '21

19 Aug '21

Hi everyone, Here’s my annual email requesting you complete the OpenStack User Survey [1] and share with your local communities / community friends who are operating OpenStack. Anonymous reposes and aggregated data from the User Survey are shared with the OPenStack PTLs and overall community to help understand operator software requirements. If you have never taken it before, please do! We welcome your feedback and I am happy to answer any questions you may have. If you are one of the many who have, all of your previous information should be stored, so you will just need to provide updates where relevant and re-save. Thank you all! Cheers, Allison [1] https://www.openstack.org/user-survey/survey-2021 <https://www.openstack.org/user-survey/survey-2021> Allison Price Director of Marketing & Community OpenInfra Foundation e: allison(a)openstack.org <mailto:allison@openstack.org>

1 1

[masakari] Compute service with name XXXXX not found.
by at 19 Aug '21

19 Aug '21

Hi, I have some problem with masakari. I can create segment (from CLI and Horizon), but can't create host (the same result from Horizon and CLI). openstack segment host create XXXXX COMPUTE SSH segment_id returns BadRequest: Compute service with name XXXXX could not be found. XXXXX is the name which Horizon suggest, and it's a name of compute host. openstack compute service list returns proper list with state up/enabled on compute hosts (zone nova) Maybe I misunderstood some parameters of host create? As "type" I use COMPUTE, what value should it be? From "Binary" column of openstack compute service list? What is "control_attributes" field, because documentation lacks preceise information what value should be there and what is it use for. Tried to found some info on this error but I haven't found anything... Thanks in advance for any help. Best regards Adam Tomas

4 7

[tc][all] Please Help On Collecting Pain Points
by Rico Lin 16 Aug '21

16 Aug '21

Dear all As a proposal for pre-select goals for Yoga [1]. We need to figure out the possibility. *I would like to ask each project team, SIG, and pop-up if you can kindly provide the major pain point you have (and better to be fixable by bugs/features).* *What you can help with is added in pain point information in [2].* *Information like pain point topic, description, and ideas on how to targeting them.* *Why this is important?* I think this data allows us to see clearly if we can have goals like `eliminate pain points`. *What's after this?* If we can make sure this can be a goal material, we might be able to have this as a goal and allow project teams to focus on one of their most important issues. As an alternative, we might be able to collect from user side with a user survey, but that's more like a really long-term plan for this. [1] https://etherpad.opendev.org/p/y-series-goals [2] https://etherpad.opendev.org/p/pain-point-elimination *Rico Lin* OIF Board director, OpenStack TC, Multi-arch SIG chair, Heat PTL, Senior Software Engineer@EasyStack

3 4

Pls help newbie :) bare metal new Ansible deployment
by Nicola Ferrari (#554252) 14 Aug '21

14 Aug '21

Dears, I'm new to the list. We're just trying to introduce a demo install of openstack in our network. Our intention was to use 5 machine, already installed with ubuntu-mini 20.04. ostack1 as control node ostack2 -| ostack3 -| AS COMPUTE NODE ostack4 -| ostack5 -| ostack4 - ostack5 also as block storage node, they are connected on a direct storage (sas) where we deployed lvm with a vg named "cinder_volumes". All nodes both are on a /24 network (192.168.32.0/24) behind a router (32.254) and also on a "private" network (10.255.255.0/24) which just interconnect nodes themselves. We inteded to deploy openstack using openstack-ansible, available on github, last stable release. You can see our user_config as attachment. setup-hosts playbook runs with no errors. setup-infrastructure playbook hangs on RUNNING HANDLER [repo_server : reload nginx] **************************************************************************************** FAILED - RETRYING: reload nginx (1 retries left). fatal: [ostack1_repo_container-aabb6a12]: FAILED! => {"attempts": 5, "changed": false, "msg": "Unable to start service nginx: Job for nginx.service failed because the control process exited with error code.\nSee \"systemctl status nginx.service\" and \"journalctl -xe\" for details.\n"} Looking at log I can see that nginx coudn't start due to "Cannot assign requested address: 99" error. I suppose that must be a mistake in the deploy file? Many thanks for your suggestion, and pls, be sorry for my poor english :) Nick

2 2

[neutron] Status of networking-mlnx: Is it still maintained ?
by Takashi Kajinami 11 Aug '21

11 Aug '21

Hello, I noticed the networking-mlnx repo[1] is not updated for a while and looks unmaintained. The repo doesn't have a stable/wallaby release created, and its setup.cfg doesn't include python 3.8 as a supported platform. https://opendev.org/x/networking-mlnx Is anybody still maintaining this repo ? If the repo is no longer maintained, I'll propose deprecating support for the plugin from puppet-neutron. Please let me know if you have any concern with that deprecation. I appreciate any input about this $topic. Thank you, Takashi Kajinami

1 2

[PTLs][release] Xena Cycle Highlights
by helena＠openstack.org 11 Aug '21

11 Aug '21

Hello Everyone!It's that time of the year once again! It's time to start thinking about calling out 'cycle-highlights' in your deliverables! As PTLs, you probably get many pings towards the end of every release cycle by various parties (marketing, management, journalists, etc) asking for highlights of what is new and what significant changes are coming in the new release. By putting them all in the same place it makes them easy to reference because they get compiled into a pretty website like this from the last few releases: Ussuri[1], Victoria[2]. We don't need a fully fledged marketing message, just a few highlights (3-4 ideally), from each project team. Looking through your release notes might be a good place to start. The deadline for cycle highlights is the end of the R-5 week [3] on September 3.How To Reminder: -------------------------Simply add them to the deliverables/$RELEASE/$PROJECT.yaml in the openstack/releases repo like this: cycle-highlights: - Introduced new service to use unused host to mine bitcoin.The formatting options for this tag are the same as what you are probably used to with Reno release notes.Also, you can check on the formatting of the output by either running locally: tox -e docsAnd then checking the resulting doc/build/html/$RELEASE/highlights.html file or the output of the build-openstack-sphinx-docs job under html/$RELEASE/highlights.html. Feel free to add Kendall Nelson (diablo_rojo) as a reviewer on your patches. Can't wait to see you all have accomplished this release! Thanks :) -Helena Spease (hspease) [1] [ https://releases.openstack.org/ussuri/highlights.html ]( https://releases.openstack.org/ussuri/highlights.html ) [2] https://releases.openstack.org/victoria/highlights.html [3] https://releases.openstack.org/xena/schedule.html

1 1

[interop][cinder] review of next.json (part 2)
by Brian Rosmaita 09 Aug '21

09 Aug '21

Hello Interop WG, The Cinder team completed its discussion of what capabilities should be added as advisory in next.json at yesterday's weekly cinder meeting [0]. The tldr; is that we don't have anything to propose for inclusion in next.json at the present time. The team does have some general questions that would help us determine the suitability of some proposed capabilities. We'd like to invite someone from the Interop WG to the cinder xena R-9 virtual midcycle (Wednesday 4 August 2021, 1400-1600 UTC) so we can discuss this "live". So if someone could put 1400 UTC 4 August on their schedule for a 20 minute discussion, that would be very helpful. cheers, brian [0] http://eavesdrop.openstack.org/meetings/cinder/2021/cinder.2021-05-12-14.00…

3 8

Re: [neutron-vpnaas][kolla-ansible][victoria] Growing memory consumption with only one VPN connection
by at 09 Aug '21

09 Aug '21

Hi, 1. There is only one, bidirectional vpn connection between project networks in two regions 2. there is no (or almost no) traffic on this vpn link 3. second region is on one host (kolla all-in-one) and situation looks the same- with vpn service enabled there is excessive Memory use (growing also about 5-6MB/ minute and forcing the system to use swapfile) there is no big cpu usage (ofcourse also due to no traffic inside VPN) It's the same case even if there's no vpn connection configured. Best regards Adam Tomas Wysłane z iPhone'a > Wiadomość napisana przez Vinh Nguyen Duc <vinhducnguyen1708(a)gmail.com> w dniu 29.06.2021, o godz. 11:04: > > > Hi Adam, > Do you think the VPN connection is use CPU and memory to encrypt the VPN traffic? > > On Mon, Jun 28, 2021 at 14:30 Adam Tomas <bkslash(a)poczta.onet.pl <mailto:bkslash@poczta.onet.pl>> wrote: > Hi, > I have problem with neutron vpnaas - after enabling vpnaas plugin everything was ok at first. I was able to create VPN connection and communication is correct. But after a week of running vpnaas (only one VPN connection created/working!) I’ve noticed, that neutron-vpnaas takes more and more memory. I have 5 processes on each controller (there should be always five? Or it is changing dynamically?): > > 42435 1545384 0.6 8.6 5802516 5712412 ? S Jun15 110:50 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > 42435 1545389 0.6 8.5 5735832 5645856 ? S Jun15 112:16 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > 42435 1545378 0.5 8.5 5734192 5643620 ? S Jun15 108:09 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > 42435 1545372 0.5 8.5 5731128 5641436 ? S Jun15 109:07 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > 42435 1545369 0.6 8.4 5637084 5547392 ? S Jun15 114:21 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > > now neutron_server takes over 27G of RAM on each controller: > > neutron_server running 10.2 27.2G > > After stopping all neutron containers and starting it again neutron takes a lot less memory: > > neutron_server running 0.5 583M > > but memory usage keeps growing (about 5-6 M every minute). > What’s wrong? When I disable vpnaas globally there’s no problem with excessive memory usage, so it’s vpnaas for sure… > > Best regards > Adam Tomas

3 2

[neutron][ops] VLAN Provider Network
by DHilsbos＠performair.com 06 Aug '21

06 Aug '21

All; We're using OpenStack Victoria, with OVS networking (no OVN). I'm having some problems with a VLAN provider network that I added to my OpenStack. I have other VLAN provider networks, that I based this one off of. Instances are getting the tap interfaces, but these interfaces are not getting IP addresses, and when a static IP is given, they can't ping either the DHCP address or the gateway address. I have checked the switch configuration, to verify the VLAN is bound appropriately. I rebooted the whole cluster to ensure the configuration change applied. Here's a snip our plugin.ini [ml2_type_vlan] network_vlan_ranges = provider_core:55:55,provider_core:64:64,... 64 works, 55, doesn't. I'm not seeing anything concerning in /var/log/openvswitch/ovs-vswitchd.log I'm sure it's something dumb, but I'm not seeing it. Any suggestions for what else to look at? Thank you, Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

2 2

[wallaby][neutron][ovn] Multiple VLAN ranges and FLAT network
by Malik Obaid 06 Aug '21

06 Aug '21

Hi, I am using Openstack Wallaby release on Ubuntu 20.04. I am configuring openstack neutron for production and just want to know is there a way to specify different vlan ranges with multiple physical networks. I would really appreciate any input in this regard. Thank you. Regards, Malik Obaid

2 1

gerrit no longer lading from iphone
by Sorin Sbarnea 05 Aug '21

05 Aug '21

I am wondering if something was changed on our gerrit deployment recently as it seems to no longer load on ios safari. I know,… not the most common use case… still adding the usual recheck can prove useful after checking zuul comment. /zbr -- -- /zbr

5 7

Migrating VM's
by Derek O keeffe 04 Aug '21

04 Aug '21

Hi all, I have a question. If we have an old openstack deployment (Queens) that have VM's (with & without volumes attached) and we want to migrate those to a new deploy (Victoria) can this be achieved by the owners of the VM's through horizon in some way? We can take snapshots of the vm's that don't have volumes attached, copy them to the new controller and re instantiate them but we haven't found a solution for the volumes yet. This give us more work though as it all needs to be done over cli so the user is taken out of the loop and it falls on us 3 admins to move over 300 VM's. Any advice or info would be greatly appreciated. Thanks in advance. Derek

3 7

[nova][neutron][deployment-projects] Re secbug #1734320
by Radosław Piliszek 04 Aug '21

04 Aug '21

Hello Folks! I am writing this because a recent patch proposed to DevStack [1] mentioned "when using ml2/ovs vif isolation should always be used to prevent cross tenant traffic during a live migration" which is related to secbug #1734320 "Eavesdropping private traffic" [2]. However, I've found that none of the publicly-available deployment projects seem to be using ``isolate_vif``. [3] [4] Should this be corrected? PS: I used the deployment-projects tag as a collective tag to avoid mentioning all the projects (as it is too long to write :-) ). I hope that relevant people see this if need be or someone passes the information to them. For now, I am curious whether this should actually be enforced by default with ML2/OVS. [1] https://review.opendev.org/c/openstack/devstack/+/796826 [2] https://bugs.launchpad.net/neutron/+bug/1734320 [3] https://codesearch.opendev.org/?q=%5Cbisolate_vif%5Cb&i=nope&files=&exclude… [4] https://github.com/search?p=1&q=isolate_vif&type=Code -yoctozepto

3 2

stackalytics.com/api/1.0/activity
by Csatari, Gergely (Nokia - FI/Espoo) 03 Aug '21

03 Aug '21

Hi, We plan to use the API of stackalytics.com and we realized that the data it provides ([1<https://www.stackalytics.com/api/1.0/activity?page_size=100>]) is never more recent than March 2021. Does anyone know what is the reason for this? Thanks, Gergely 1: https://www.stackalytics.com/api/1.0/activity?page_size=100

5 5

[swift] EC data left in old location after rebalance
by Reid Guyett 02 Aug '21

02 Aug '21

Hello, We started using EC policies in a new cluster a few months ago and added more capacity. During the rebalance (started June 30), it seems that all the data was copied to the new locations but it didn't clean up the old locations. This was identified through our handoff monitoring. OS: Ubuntu 18.04 Swift: 2.17.1 Example: List of devices for partition ~$ swift-get-nodes /etc/swift/object-4.ring.gz -p 14242 ... removed ... Server:Port Device x.x.x.31:6031 d31 Server:Port Device x.x.x.66:6030 d30 Server:Port Device x.x.x.25:6029 d29 Server:Port Device x.x.x.33:6027 d27 Server:Port Device x.x.x.36:6020 d20 Server:Port Device x.x.x.29:6018 d18 Server:Port Device x.x.x.21:6033 d33 Server:Port Device x.x.x.27:6025 d25 Server:Port Device x.x.x.35:6022 d22 Server:Port Device x.x.x.39:6031 d31 Server:Port Device x.x.x.28:6032 d32 Server:Port Device x.x.x.23:6021 d21 Server:Port Device x.x.x.26:6022 d22 Server:Port Device x.x.x.34:6023 d23 Server:Port Device x.x.x.37:6019 d19 Server:Port Device x.x.x.30:6017 d17 Server:Port Device x.x.x.22:6027 d27 Server:Port Device x.x.x.24:6031 d31 Server:Port Device x.x.x.32:6032 d32 Partitions look to have the correct data on them: ~$ ssh root(a)x.x.x.31 "ls -lah ${DEVICE:-/srv/node*}/d31/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.66 "ls -lah ${DEVICE:-/srv/node*}/d30/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.25 "ls -lah ${DEVICE:-/srv/node*}/d29/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.33 "ls -lah ${DEVICE:-/srv/node*}/d27/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.36 "ls -lah ${DEVICE:-/srv/node*}/d20/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.29 "ls -lah ${DEVICE:-/srv/node*}/d18/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.21 "ls -lah ${DEVICE:-/srv/node*}/d33/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.27 "ls -lah ${DEVICE:-/srv/node*}/d25/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.35 "ls -lah ${DEVICE:-/srv/node*}/d22/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.39 "ls -lah ${DEVICE:-/srv/node*}/d31/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.28 "ls -lah ${DEVICE:-/srv/node*}/d32/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.23 "ls -lah ${DEVICE:-/srv/node*}/d21/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.26 "ls -lah ${DEVICE:-/srv/node*}/d22/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.34 "ls -lah ${DEVICE:-/srv/node*}/d23/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.37 "ls -lah ${DEVICE:-/srv/node*}/d19/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.30 "ls -lah ${DEVICE:-/srv/node*}/d17/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.22 "ls -lah ${DEVICE:-/srv/node*}/d27/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.24 "ls -lah ${DEVICE:-/srv/node*}/d31/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.32 "ls -lah ${DEVICE:-/srv/node*}/d32/objects-4/14242 | wc -l" 664 >From one of the nodes that does not belong to the list above. This partition should not exist on this node after the rebalance. x.x.x.20:~# ls /srv/node/d28/objects-4/14242 | wc -l 627 The reconstructor is throwing a lot of these unexpected response errors in the logs. Manually running it from the node that should not have the partition, I can reproduce the error. x.x.y.0/24 is the replication network. x.x.x.20:~# swift-object-reconstructor /etc/swift/object-server.conf -d d28 -p 14242 -o -v object-reconstructor: x.x.y.42:6200/d30/14242 Unexpected response: ":ERROR: 500 'ERROR: With :UPDATES: 36 failures to 0 successes'" There looked to have been some partition locations cleaned up around July 11. Our expectation is that the old partition locations should be cleaned gradually since June 30 but we're not seeing that. I Was hoping for some ideas on what may be the problem (if any) and how we can make sure that the old partitions are cleaned up. Thanks, Reid

2 4

[ironic] Xena Mid-cycle
by Iury Gregory 02 Aug '21

02 Aug '21

Hello Ironicers! In our upstream meeting we decided we should do a virtual mid-cycle! If you are interested please fill out the doodle[1] and add topics in the etherpad[2]. Keep in mind we have contributors in many time zones, if you think we should add more time windows, please let me know. Maybe we can have multiple sessions each day so we can accommodate APAC TZ. I will close the doodle before our upstream meeting next week. [1] https://doodle.com/poll/mhh959u4s4rturxi [2] https://etherpad.opendev.org/p/ironic-xena-midcycle -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 1

[nova][gate] nova-tox-functional-* jobs failing on master branch
by melanie witt 02 Aug '21

02 Aug '21

Hey all, The nova-tox-functional-* jobs on the openstack/nova master branch are currently failing 100% of the time: https://zuul.openstack.org/builds?job_name=nova-tox-functional-py38&branch=… This is due to another issue with time overrides (a lack thereof) in the test_archive_task_logs functional tests. The same bug has happened in the past and the fix is now known to have been unsuccessful: https://bugs.launchpad.net/nova/+bug/1934519 Another fix has been proposed here: https://review.opendev.org/c/openstack/nova/+/803106 Please hold your rechecks until the fix merges and apologies for the trouble. -melwitt

2 2

[TripleO] centos7 gate blocker (stable/train) please hold rechecks
by Marios Andreou 02 Aug '21

02 Aug '21

Hello tripleo o/ new gate blocker for centos7 hitting stable/train tripleo repos https://zuul.opendev.org/t/openstack/builds?job_name=tripleo-ci-centos-7-co… bug is at https://bugs.launchpad.net/tripleo/+bug/1938079 - hitting stable/train (we only run c7 jobs there). investigation/resolution ongoing please hold rechecks for centos7 jobs. thank you

2 3

[cinder-backup][ceph] replicate volume between sites
by Tony Liu 31 Jul '21

31 Jul '21

Hi, I have two sites with OpenStack Victoria deployed by Kolla and Ceph Octopus deployed by cephadm. As what I know, either Swift (implemented by RADOSGW) or RBD is supported to be the backend of cinder-backup. My intention is to use one of those option to replicate Cinder volume from one site to another, based on RADOSGW multi-site support or RBD mirroring. I wonder if anyone has done this and could share some opinions, like pros, cons, which way is better for which case? One specific thing I am not clear is that, how to import RBD volume into Cinder when it gets to another site. There used to be a way, but it's replicated. Any comments is appreciated. Thanks! Tony

1 1

[neutron] dnsmasq refusing to provide ipv6 address over dhcpv6 after a server rebuild
by Thomas Goirand 31 Jul '21

31 Jul '21

Hi, I've filled this bug in Debian concerning our official image: https://bugs.debian.org/991613 tl;dr: When doing "openstack server rebuild", dnsmasq refuses to provide an ipv6 when the instance does a dhcpv6 request, because after a rebuild, the instance generates a different DUID. So I wonder if there's a way to fix this by configuring dnsmasq in some ways, maybe by telling it to not use the DUID at all. So far, I haven't found a way yet. Does anyone have a good answer to this problem? Ideally, I'd like to find a way to fix on both side (ie: OpenStack *AND* the official Debian image), so I can make sure to never encounter the issue ever again. Cheers, Thomas Goirand (zigo)

1 0

Routed provider networks
by Gk Gk 31 Jul '21

31 Jul '21

Hi, I learnt that routed provider networks from the below links: https://docs.openstack.org/neutron/latest/admin/config-routed-networks.html https://www.youtube.com/watch?v=HwQFmzXdqZM This concept, according to them solves two issues: 1. Large broadcast L2 domains with failure domains 2. If there are multiple L2 provider networks, users are confused, unable to choose a particular network. My question is, how does routed provider networks solve the second problem mentioned above ? If one user wants to use external network for internet, how can he choose from this one single routed provider network ? Or, if another user wants another provider network, how can he choose that particular network ? Also the same can also be achieved by creating nova aggregates or availability zones and mapping computes with particular provider network connections and ask users to use that particular nova AZ, without creating routed provider networks at all ? Can someone clarify this for me ? Thanks Kumar

2 2

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

30 Jul '21

Hello Everyone, Here is last week's summary of the Technical Committee activities. 1. What we completed this week: ========================= * Retired tripleo-common-tempest-plugin[1] 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-29-15.00.log.html * We will have next week's meeting on Aug 5th, Thursday 15:00 UTC[2]. 3. Activities In progress: ================== TC Tracker for Xena cycle ------------------------------ TC is using the etherpad[3] for Xena cycle working item. We will be checking and updating the status biweekly in the same etherpad. Open Reviews ----------------- * Three open reviews for ongoing activities[4]. Migration from Freenode to OFTC ----------------------------------------- * Only few repo patches are left to merge. requesting core team of those repos to merge them. ** https://review.opendev.org/q/topic:%2522oftc%2522+status:open * openstack blog site is updated for freenode->oftc, Thanks Jimmy for taking care of it. * All the required work for this migration is tracked in this etherpad[5] Test support for TLS default: ---------------------------------- * Rico has started a separate email thread over testing with tls-proxy enabled[6], we encourage projects to participate in that testing and help to enable the tls-proxy in gate testing. Project updates: ------------------- * Retiring js-openstack-lib [7] * Adding tap-as-a-service back to neutron stadium[8] Yoga release community-wide goal ----------------------------------------- * Please add the possible candidates in this etherpad [9]. * Current status: One goal "Secure RBAC" is proposed. Other Changes ------------------ * Defining Yoga release testing runtime[10] PTG planning ---------------- * TC booked three slots: ** 1. Monday 15-17 UTC for TC + Community Leaders ** 2. Thursday 13-17 UTC ** 3. Friday 13-17UTC * We are collecting the PTG topics in etherpad[11], feel free to add any topic you want to discuss. 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[12]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [13] 3. Office hours: The Technical Committee offers a weekly office hour every Tuesday at 0100 UTC [14] 4. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://review.opendev.org/c/openstack/governance/+/800432 [2] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [3] https://etherpad.opendev.org/p/tc-xena-tracker [4] https://review.opendev.org/q/project:openstack/governance+status:open [5] https://etherpad.opendev.org/p/openstack-irc-migration-to-oftc [6] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023000.html [7] https://review.opendev.org/c/openstack/governance/+/798540 [8] https://review.opendev.org/c/openstack/governance/+/802833 [9] https://etherpad.opendev.org/p/y-series-goals [10] https://review.opendev.org/c/openstack/governance/+/799927 [11] https://etherpad.opendev.org/p/tc-yoga-ptg [12] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [13] http://eavesdrop.openstack.org/#Technical_Committee_Meeting [14] http://eavesdrop.openstack.org/#Technical_Committee_Office_hours -gmann

1 0

Redhat RHEV Virtualisation and logical data volumes
by KK CHN 30 Jul '21

30 Jul '21

Is it practically or theoretically possible to export image/Disk as single image /Disk from RHEV/Virtualization Manager where VMs have logical volumes attached to it ? Any other data/information do I need to provide for the above question let know. Problem scenario is this: We have hosted VMs on RHEV virtualization environment. Each VM has associated Logical Volumes attached to the VM. We are planning to migrate our VMs to OpenStack (Ussuri, qemu KVM and Glance) Right now Our System Integrator who maintains these VMs on their RHEV virtualization environment exporting each VM as Three separate images. One for OS image, other for boot and third one for data volume disk image ( they use logical volumes for data storage, might be added disks when data storage was insufficient at any point of time. ) But I want to get each VM with data volumes as a single disk image . IS THIS THEORETICALLY or PRACTICALLY POSSIBLE using RHEV Virtualization tools ? if so how ? ( OR any other methods do this ?) OR am I asking a STUPID QUESTION ? If so WHY ? Kindly enlighten me !!! I am at the end of the rope with this issue. Thanks in advance, Kris

1 0

[sahara][stable] periodic-stable errors
by Előd Illés 30 Jul '21

30 Jul '21

Hi Sahara Team, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've seen that Sahara's stable branches started to fail as well so collected the recent failures with examples. Please take a look at them and try to fix them. The errors seem to be related to cinder's v2 removal ("No module named 'cinderclient.v2'"): sahara: stein - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/77f0f18b297240fa92eb5b22c8200598 sahara: train - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/23c860b5af74449bbed561d5853963ea sahara: ussuri - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/6e8ec09a4cc54eadaeaa9fe88eb249d9 sahara: victoria - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/db254fea259e482ab3ff3b404feeed28 sahara: wallaby - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/1e50a52edefe4f8191f0f0d529db7a63 [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

2 2

[cinder][qa][devstack][ci] need help running centos-8/opensuse-15 on stable/victoria
by Brian Rosmaita 30 Jul '21

30 Jul '21

Does anyone have any zuul jobs running in stable/victoria that use either of these nodesets: - devstack-single-node-centos-8 - devstack-single-node-opensuse-15 I can't get devstack to complete building on either (missing package, though different for each distro). I figure that someone in openstack must have this working, given that Python 3.6 and Centos-8 and OpenSUSE-15 are listed in the Tested Runtimes for Victoria [0]. Here's the failing patch if anyone would be kind enough to point out what I'm mis-configuring: https://review.opendev.org/c/openstack/python-cinderclient/+/800635/ thanks! brian [0] https://governance.openstack.org/tc/reference/runtimes/victoria.html

6 7

[nova][wallaby] Nova policy rule project_member_api not effective
by Taltavull Jean-Francois 30 Jul '21

30 Jul '21

Hi All, Despite the fact that oslopolicy-policy-generator --namespace nova shows the rules "project_member_api": "role:member and project_id:%(project_id)s" and "os_compute_api:servers:create": "rule:project_member_api", it is still possible to create a server even if you only have the role "member" on the project. Is this behavior normal or not ? Must we consider that we are in a phase of transition about nova default policies ? Thanks, Jean-Francois

2 3

[trove][stable] periodic-stable errors
by Előd Illés 30 Jul '21

30 Jul '21

Hi Trove Team, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've collected the recent failures with examples that are failing constantly. Please take a look at them and try to fix them wherever it is possible. Since the old branches seem quite abandoned in some cases, they might need maintainers to step up to keep those gates healthy, or in case there are no maintainers, then it might worth to think of transitioning those broken old branches to End of Life. :/ And the list (with possible root causes): * bandit should be constrained: trove: pike - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/c8da125f4a7f4dafaa5f3b337a0d14c2 trove: pike - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/9973f556913e439a912455712ecbd54a trove: queens - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/6ed08e9f7d25414e8ee04db14a753649 trove: queens - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/0a3b1f6668a740c69f888c7272e24d58 trove: rocky - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/208c02dfcbc9487bbaca1eccc53e8a67 trove: rocky - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/f13cc87c4f104727ab4f4696ad7ed160 trove: stein - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/9aff516680074e11b52ea07fac389fa0 trove: train - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/db3b97cec2604318a7bd129fa8cd3bc2 * version conflict revealed with the new pip resolver: trove: stein - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/30f8f8a99fea4a93bab55b694c9e79e9 trove: train - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/00b400d2485a45fc997ebd35d48a506d trove: train - openstack-tox-py36 -- https://zuul.opendev.org/t/openstack/build/5e6a8f14ea93456ba70f5e1e3ee689a9 trove: train - openstack-tox-py37 -- https://zuul.opendev.org/t/openstack/build/e3c9201c92874e3fa25357171741cad2 [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

1 0

[neutron][stable] periodic-stable errors
by Előd Illés 30 Jul '21

30 Jul '21

Hi Neutron Team, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've collected the recent failures with examples that are failing constantly. Please take a look at them and try to fix them wherever it is possible. Since the old branches seem quite abandoned in some cases, they might need maintainers to step up to keep those gates healthy, or in case there are no maintainers, then it might worth to think of transitioning those broken old branches to End of Life. :/ And the list (with possible root causes): * horizon's pike + queens were deprecated: networking-bgpvpn: pike - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/553d4923eeca421c9ac56d193781b487 networking-bgpvpn: pike - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/0fe12998347c4fa19ce3e04450bd914d networking-bgpvpn: queens - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/d804b266bfdc408dbd1dd517b5901914 networking-bgpvpn: queens - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/9151ba1cb74e4f569d863b7a90a8b702 * some dependency issues + unit tests are broken: neutron-vpnaas: queens - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/64d92abffe7d48b1bcc3d3f42f8a1a24 neutron-vpnaas: queens - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/743f561a2bb34875b86917cfe8861a53 neutron-vpnaas: rocky - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/e700494509934ba995f8c4b0e69f4627 neutron-vpnaas: stein - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/4339034bc4014a0292310fd013d46caa neutron-vpnaas: victoria - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/83d8251153b64de488bae3972968256f neutron-vpnaas: victoria - openstack-tox-py36 -- https://zuul.opendev.org/t/openstack/build/02e214a1483a4778986697ba6c85cbf9 neutron-vpnaas: victoria - openstack-tox-py38 -- https://zuul.opendev.org/t/openstack/build/a746a0bc5a1c4caeb6b813a7dd83878c [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

1 0

[murano][stable] periodic-stable errors
by Előd Illés 30 Jul '21

30 Jul '21

Hi Murano Team, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've collected the recent failures with examples that are failing constantly. Please take a look at them and try to fix them wherever it is possible. Since the old branches seem quite abandoned in some cases, they might need maintainers to step up to keep those gates healthy, or in case there are no maintainers, then it might worth to think of transitioning those broken old branches to End of Life. :/ And the list (with possible root causes): * bandit should be constrained: murano: pike - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/6ee6c9548d6b47e79361151964992ddf murano: pike - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/fbfe0f67b90f4b3189a13e02a5b7f274 murano: queens - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/c254a7f764f547e4a5bf8467cbcbe24b murano: queens - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/b9646137d45c49ab8f10c2031135d21e murano: rocky - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/63f53b3df8a940f6b86c450617882cfc murano: stein - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/be63abe6be9a4d1f90c8d74fd9c4a407 * broken unittest: murano: victoria - openstack-tox-py36 -- https://zuul.opendev.org/t/openstack/build/b403e1a7431a484e90b23738a56669c7 murano: victoria - openstack-tox-py38 -- https://zuul.opendev.org/t/openstack/build/7f886d7e21864f4d941ad0a03d61ec4d murano: wallaby - openstack-tox-py36 -- https://zuul.opendev.org/t/openstack/build/dc61998732ff4d13a6e8c9d1f82ccd8d murano: wallaby - openstack-tox-py38 -- https://zuul.opendev.org/t/openstack/build/cc2fa00e650d4cd1973fd76dc1649624 * and also master is broken. [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

1 0

[designate][stable] periodic-stable errors
by Előd Illés 30 Jul '21

30 Jul '21

Hi Designate Team, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've collected the recent failures with examples that are failing constantly. Please take a look at them and try to fix them wherever it is possible. Since the old branches seem quite abandoned in some cases, they might need maintainers to step up to keep those gates healthy, or in case there are no maintainers, then it might worth to think of transitioning those broken old branches to End of Life. :/ And the list (with possible root cause): * bandit should be constrained: designate: pike - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/810cf80432dc4b90a7367b5f2107147e designate: pike - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/11d042ab2e82478db75d877f3c62cd62 designate: queens - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/4cd73558ffb3402e8f25f602d85aec94 designate: queens - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/6c0b8dd6cee24b7eab9153bfc0e1dd61 designate: rocky - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/8d4d56e05ec94870823d3e057ee8ea4a [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

1 0