openstack-discuss
Threads by month
- ----- 2026 -----
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
November 2022
- 99 participants
- 151 discussions
23 Apr '25
Looking for someone who knows OpenStack with OpenVSwitch, and in additionto that, DPDK with OpenStack and OVS.I am using OpenStack Queens, withOpenVSwitch. The architecture I am using is documented here:https://docs.openstack.org/neutron/queens/admin/deploy-ovs-provider.htmlTheOVS I am using on the Compute Node, is compiled with DPDK, and I haveenabled 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 actuallysure about whether to tinker with this bridge, and wondered what datapathit was using.Then, I realized there is a parameter in theopenvswitch_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 = systemdatapath_type = netdevSo in tinkering with this, what I realized, is that when you set thisdatapath_type to system or netdev, it will adjust the br-int bridge to thatdatapath type.So here is my question. How can I launch a non-DPDK VM, ifall of the bridges are using the netdev datapath type?Here is anotherquestion. What if one of the flavors don’t have the largepages property seton them? I assumed OpenStack would revert to a system datapath and not useDPDK for those VM interfaces. Well, I found out in testing, that is not thecase. If you set all your bridges up for netdev, and you don’t set theproperty on the Flavor of the VM (largepages), the VM will launch, but itsimply won’t work.Is there no way, on a specific Compute Host, to supportboth DPDK (netdev datapaths) and non-DPDK (system datapaths)?Either on a VMinterface level (VM has one interface that is netdev DPDK and another thatis system datapath non-DPDK)?Or on a VM by VM basis (VM 1 has 1 or morenetdev datapath interfaces and VM 2 has 1 or more system datapathinterfaces)?Am I right here? Once you set up a Compute Host for DPDK, it’sDPDK or nothing on that Compute Host? (edited)
3 2
22 Apr '25
Hi....as far I understand ovs does support dpdk compute to be deployed. I'mreferring 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 networkingopenstack? 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
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 23 Dec '24
by Swogat Pradhan 23 Dec '24
23 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 --outputnetworks-deployed-environment.yaml custom_network_data.yaml# openstack overcloud network vip provision --stack overcloud --outputvip-deployed-environment.yaml custom_vip_data.yaml# openstack overcloud node provision --stack overcloud--overcloud-ssh-key /home/stack/sshkey/id_rsaovercloud-baremetal-deploy.yamland used the environment files in the openstack overcloud deploy command:(undercloud) [stack@hkg2director ~]$ cat deploy.sh#!/bin/bashTHT=/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.yamlNow when i run the ./deploy.sh script i encounter an error stating:ERROR openstack [-] ResourceOS::TripleO::Network::Ports::ControlPlaneVipPort maps to typeOS::Neutron::Port and the Neutron service is not available when usingephemeral Heat. The generated environments from 'openstack overcloudbaremetal provision' and 'openstack overcloud network provision' must beincluded with the deployment command.:tripleoclient.exceptions.InvalidConfiguration: ResourceOS::TripleO::Network::Ports::ControlPlaneVipPort maps to typeOS::Neutron::Port and the Neutron service is not available when usingephemeral Heat. The generated environments from 'openstack overcloudbaremetal provision' and 'openstack overcloud network provision' must beincluded with the deployment command.2022-04-19 13:47:16.582 735924 INFO osc_lib.shell [-] END return value: 1Can someone tell me where the mistake is?With regards,Swogat Pradhan
4 4
10 Oct '24
Hi,I'm attempting to use Kolla Ansible 14.6.0 to deploy OpenStack Yoga on asmall 3-node Ubuntu 20.04 cluster. The nodes have 128 GB RAM each, dualXeon processors, and dual 10G Intel NICs. The NICs are connected to accessports on a 10G switch with separate VLANs for the local and externalnetworks.All the playbooks run cleanly, but cloud-init is failing in theUbuntu 20.04 and 22.04 VMs I attempt to boot. The VM images are unmodifiedfromhttps://cloud-images.ubuntu.com/, and cloud-init works fine if I mounta second volume with user-data. The error is a timeout attempting toreach 169.254.169.254. This occurs both when booting a VM in an internalrouted network and directly in an external network.I tried various neutron plugin agents (ovn, linuxbridge, and openvswitchboth 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 sameresult. Running tcpdump looking for 169.254.169.254 shows nothing. As apossible clue, the virtual NICs are unable to pass any traffic (e.g., toreach an external DHCP server) unless I completely disable port security onthe interface (even if the associated security group is wide open). Butdisabling port security does not fix cloud-init (not to mention I don'treally want to disable port security).Are there any additional requirements related to deploying OpenStack withKolla on Ubuntu 20.04?This is a fairly vanilla configuration using the multinode inventory as astarting point. I tried to follow the Quick Start<https://docs.openstack.org/kolla-ansible/yoga/user/quickstart.html> asclosely as possible; the only material difference I see is that I'm usingthe same 3 nodes for control + compute. I am using MAAS so it's easy to geta clean OS install on all three nodes ahead of each attempt. I plan to tryagain with the standard (non-HWE) kernel just in case, but otherwise I amrunning out of ideas. In case of any additional clues, here are myglobals.yml and inventory file, along with the playbook I'm using toconfigure the network, images, VMs, etc., after bootstrapping the cluster:https://gist.github.com/tobiasmcnulty/7dbbdbc67abc08cbb013bf5983852ed6Thank you in advance for any advice!Cheers,Tobias
5 9
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-4025Tried 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
23 Aug '23
Hello,I went through the current core reviewers and found out that the currentlist includessome people no longer working in the OpenStack community.I'd like to propose removing the following persons from the core reviewerteamas we haven't seen these people making any activity in the communityrecently.* 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 modulesAlso, I confirmed that Wes Hayutin is no longer working for OpenStack andhe agreedto 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/feedbackabout 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
22 Jul '23
Hello Kai,Great to hear that you’re interested!I’m currently just testing this as a POC directly in devstack so there is real-world testing (not should it yet I think, needs more development first).Best regardsTobias> On 30 Aug 2022, at 18:32, Kai Bojens <kb(a)kbojens.de> wrote:> > Am 29.08.22 um 15:46 schrieb Tobias Urdin:> >> If anybody, or any company, out there would be interested in collaborating in a project to bring this support and maintain it feel free to>> reach out. I’m hoping somebody will bite but atleast I’ve put it out there for all of you.> > Hi,> I am very much interested to take a closer look at your work and maybe contribute to it. Although I'm working with OpenStack for my employer at the moment, I'd do this in my spare time as I'm not sure that I can convince him to add another staging system with a full OpenStack installation just for developing a RabbitMQ replacement. That's not on our agenda as we are mostly users and not developers of OpenStack.> > As I'm pretty new to the messaging topic and had just heard of NATS and your idea, I'll first would have to dive into NATS and then I would take a closer look at your code and maybe try to create some documentation or tests. So, I can't promise anything but as I said I'm very interested in your approach as I also see the massive load from RabbitMQ.> > This brings me to the most important question: Where do you run and test your code?> > Greetings,> Kai
8 30
[ironic][stable] Proposing EOL of ironic project branches older than Wallaby
by Jay Faulkner 01 Jun '23
by Jay Faulkner 01 Jun '23
01 Jun '23
Hi all,Ironic has a large amount of stable branches still in EM. We need to takeaction to ensure those branches are either retired or have CI repaired tothe point of being usable.Specifically, I'm looking at these branches across all Ironic projects:- stable/queens- stable/rocky- stable/stein- stable/train- stable/ussuri- stable/victoriaIn lieu of any volunteers to maintain the CI, my recommendation for all thebranches listed above is that they be marked EOL. If someone wants tovolunteer to maintain CI for those branches, they can propose one of thebelow paths be taken instead:1 - Someone volunteers to maintain these branches, and also report thestatus of CI of these older branches periodically on the Ironic whiteboardand in Ironic meetings. If you feel strongly that one of these branchesneeds to continue to be in service; volunteering in this way is how to savethem.2 - We seriously reduce CI. Basically removing all tempest tests to ensurethat CI remains reliable and able to merge emergency or security fixes whenneeded. In some cases; this still requires CI fixes as some older inspectorbranches are failing *installing packages* in unit tests. I would stilllike, in this case, that someone volunteers to ensure the minimalist CIremains happy.My intention is to let this message serve as notice and a waiting period;and if I've not heard any response here or in Monday's Ironic meeting (in 6days), I will begin taking action on retiring these branches.This is simply a start; other branches (including bugfix branches) are alsoin bad shape in CI, but getting these retired will significantly reduce thesurface area of projects and branches to evaluate.I know it's painful to drop support for these branches; but we've providedgood EM support for these branches for a long time and by pruning themaway, we'll be able to save time to dedicate to other items.Thanks,Jay Faulkner
3 5
15 Mar '23
helloon openstack with ceph backend is it possible to live resize instances ? Iwant to change flavor without any down time .
5 6
[kolla-ansible] [yoga] [magnum] [k8s] cannot attach persistent volume to pod
by Stuart Whitman 24 Feb '23
by Stuart Whitman 24 Feb '23
24 Feb '23
Hello,When I try to attach a persistent cinder volume to a pod, I get FailedMount and FailedAttachVolume timeout events. I also get these errors in the log of the csi-cinder-controllerplugin-0 pod:E1020 13:38:41.747511 1 reflector.go:126] k8s.io/client-go/informers/factory.go:133: Failed to list *v1beta1.VolumeAttachment: the server could not find the requested resourceE1020 13:38:41.748187 1 reflector.go:126] k8s.io/client-go/informers/factory.go:133: Failed to list *v1beta1.CSINode: the server could not find the requested resourceI fixed a CrashLoopBackoff error with the csi-snapshotter container in the csi-cinder-controllerplugin-0 pod by providing the label "csi_snapshotter_tag=v4.0.0" when I created the cluster template. I found that suggestion in an issue on the GitHub cloud-provider-openstack project.I'm not finding any help with this error on Google.Thanks,-Stu_____________________________________The information contained in this e-mail and any attachments from Group W may contain confidential and/or proprietary information and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, be aware that any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately of that fact by return e-mail and permanently delete the e-mail and any attachments to it.
3 5