- openstack-discuss - lists.openstack.org

The Next OpenStack Release Name Is...
by Erin Disney 04 Jan '23

04 Jan '23

Hey everyone- Voting for the upcoming OpenStack B release name has ended and we have a winner... BOBCAT! Thanks to everyone who voted and helped us pick the next name. Thanks, Erin Erin Disney Event Marketing OpenInfra Foundation

1 0

[cinder][drivers] third-party CI for os-brick changes
by Brian Rosmaita 04 Jan '23

04 Jan '23

To all third-party CI maintainers, As you are aware, cinder third-party CI systems are required to run on all cinder changes. However, the os-brick library used in cinder CI testing is the latest appropriate *released* version of os-brick. Thus, it is possible for changes to be happening in os-brick development that might impact the functionality of your driver. If you aren't testing os-brick changes, you won't find out about these until *after* the next os-brick release, which is bad news all around. Therefore, at last week's cinder midcycle [0], the cinder project team agreed to require that cinder third-party CI systems run on all os-brick changes in addition to all cinder changes. This is a nice-to-have for the current (Zed) development cycle, but will be required in order for a driver to be considered 'supported' in the 2023.1 (Antelope) release [1]. If you have comments or concerns about this policy, please reply on the list to this email or put an item on the agenda [2] for the cinder weekly meeting. [0] https://etherpad.opendev.org/p/cinder-zed-midcycles [1] https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#What_changes… [2] https://etherpad.opendev.org/p/cinder-zed-meetings

2 1

[nova] Do openstack support USB passthrough
by 韩光宇 04 Jan '23

04 Jan '23

Hi, all I want to ask if openstack support USB passthrough now? Or if I want the instance to recognize the USB flash drive on the host, do you have any suggestions? Thanks, Han

6 5

[TripleO] Tripleo-ci-centos-9-content-provider jobs are failing in check line
by Amol Kahat 04 Jan '23

04 Jan '23

Hello All, Centos-9 content provider jobs are failing in the check line. We are investigating failures related to build-containers[1]. Please hold your recheck until the issue[2] is fixed. [1] https://zuul.opendev.org/t/openstack/builds?job_name=tripleo-ci-centos-9-co… [2] https://bugs.launchpad.net/tripleo/+bug/2001626 Thanks -- *Amol Kahat* Software Engineer *Red Hat India Pvt. Ltd. Pune, India.* akahat(a)redhat.com B764 E6F8 F4C1 A1AF 816C 6840 FDD3 BA6C 832D 7715

1 0

Don't set 'py_modules=[]' unless you know what you're doing
by Stephen Finucane 04 Jan '23

04 Jan '23

Bit of PSA. I've a seen a number of tox4 fixup-related patches where people are adding the following to the 'setup.py' file: py_modules=[] If you're thinking about doing this, please stop. If you recently did this, consider proposing a patch to it again [*]. It's not doing what you think it is. This value should only be set for projects that do not actually distribute any Python code as part of their sdist (for example: puppet modules). Assuming you're not in this category, what you're actually seeing is a bug [1] which requires a fix in pbr [2]. This is a fix for pbr that means the pbr machinery will correctly function under tox4. This should be released very soon. Stephen [*] This obviously can't merge until the pbr fix is released. [1] https://github.com/tox-dev/tox/issues/2712 [2] https://review.opendev.org/c/openstack/pbr/+/869082

1 0

[ops] QOS on flavor breaking live migration from CentOS 7 to 8
by Jahson Babel 04 Jan '23

04 Jan '23

Hello, I'm trying to live migrate some VMs from CentOS 7 to Rocky 8. Everything run smoothly when there is no extra specs on flavors but things getting more complicated when those are fixed. Especially when using quota:vif_burst for QOS. I know that we aren't supposed to use this for QOS now but it's an old cluster and it was done that way at the time. So VMs kinda have all those specs tied to them. When live migrate a VM this show up in the nova's logs : driver.py _live_migration_operation nova.virt.libvirt.driver Live Migration failure: internal error: Child process (tc class add dev tapxxxxxxxx-xx parent 1: classid 1:1 htb rate 250000kbps ceil 2000000kbps burst 60000000kb quantum 21333) unexpected exit status 1: Illegal "burst" This bug cover the problem : https://bugs.launchpad.net/nova/+bug/1960840 So it's seems to be a normal behavior. Plus I forgot to mention that I'm on OpenStack Train version and the file mentioned in the launchpad is not present for this version. By using Rocky 8 I have to use an updated libvirt that won't accept the burst parameter we used to set. All available versions of libvirt on Rocky 8 have changed behavior concerning the burst parameter. I've done some testing to make things works including removing the extra_specs on flavors and in the DB, removing it through libvirt and trying to modify tc rules used by a VM but it didn't worked. I have not tried yet to patch Nova or Libvirt but I don't really know where to look for. The only thing that did work was to resize the VM to an identical flavor without the extra_specs. But this induce a complete reboot of the VM. I would like, if possible, to be able to live migrate the VMs which is quite easier. Is it possible to remove the extra_specs on the VMs and then live migrate ? Or should I just plan to resize/reboot all VMs without those extra_specs ? Any advise will be appreciated. Thank you for any help, Best regards. Jahson

2 2

Re: openstack-discuss Digest, Vol 51, Issue 6
by Kerem Çeliker 04 Jan '23

04 Jan '23

Hello Stephen, Yes, OpenStack does support USB passthrough. You can pass through USB devices to instances running in OpenStack by using the nova.virt.libvirt.vif.LibvirtGenericVIFDriver driver and the qemu:commandline option in the nova.conf file. Best, Kerem Çeliker keremceliker.medium.com Sent from my iPhone > On 4 Jan 2023, at 02:25, openstack-discuss-request(a)lists.openstack.org wrote: > > 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. Re: [nova] Do openstack support USB passthrough (Sean Mooney) > 2. Re: [ops] QOS on flavor breaking live migration from CentOS 7 > to 8 (Sean Mooney) > 3. Re: [cloudkitty] Instances billing based on tags (Satish Patel) > 4. [nova][keystone] workload identity? (Mohammed Naser) > 5. Re: [cloudkitty] Instances billing based on tags > (Rafael Weing?rtner) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 03 Jan 2023 19:03:23 +0000 > From: Sean Mooney <smooney(a)redhat.com> > To: Stephen Finucane <stephenfin(a)redhat.com>, ??? > <hanguangyu2(a)gmail.com>, openstack-discuss > <openstack-discuss(a)lists.openstack.org> > Subject: Re: [nova] Do openstack support USB passthrough > Message-ID: > <765850d1c170a510d34dafb4253ab97528829351.camel(a)redhat.com> > Content-Type: text/plain; charset="UTF-8" > >> On Tue, 2023-01-03 at 14:54 +0000, Stephen Finucane wrote: >>> On Mon, 2022-12-26 at 10:04 +0000, ??? wrote: >>> Hi, all >>> >>> I want to ask if openstack support USB passthrough now? >>> >>> Or if I want the instance to recognize the USB flash drive on the >>> host, do you have any suggestions? >>> >>> Thanks, >>> Han >> >> This isn't supported in nova and probably never will be. The closest you can get >> is to passthrough an entire USB controller as suggested by this blog [1], but >> that's really a hack and I 100% would not use it in production. > > ya so we have discussed usb passthough supprot a few times and its somethign nova could add but there has > neither been the demand or desire to add it stongly enough in the core team to actully do it. > > the shorted path to enableing usb passthoug would likely be to add support to cyborg and then add support for that ot nova. > i am perhaps the most open of the nova cores to supporting usb passthough since i have wanted to add it in the past but > if we were to support it it would have to be similar to howe we support pci passhtough. static provisioning and likely only of > stateless devices which rules out usb falsh drives. > > usb gps recivers for precision time stamping was one of the usecause raised in the past which we were somewhat open too > the other was usb programmers/debuggers forh cases when vms where used in industral test and automation workflows. > > as stephen said the only way to do it today is to piggyback on pci passthough and passhtough a usb contoller not a single device. > > if we were to ever support this in nova directly i would proably extend the pci tracker or support other buses like usb or use the generic > resouce table created for persistent memory to model the devices. in eitehr case we would want this capablity to be placement native from the > start if we added this capablity so it would be more and less work then you might imagine to do this right. > less work if we maintain the requirement for statless devices only (ie no usb flash drives) more if you also need to handel multi tenancy and > move operation include data copying, erasure and or encypetion. > > i would not expect this to change in the next few release unless multiple operators provide feedback that this is a broadly deired capablity. > with out a top level generic device api for mutple type of devices (vgpu, usb, pci) that was decoupled form the flaovr or an abstraction like > the cyborg device-profile or pci alias it is hard to see a clean way to model this in our api. that is why enabling it in cyborg and then extneding > nova ot support device profiles with a device type of usb is the simplar solution form a nova perspecitve but that is non trivial from an operational > perspective as you requrie cyborg to utilise the feature. doing it via a usb_alias in the flavor has all the draw backs of the pci_alias, static > configuration that must match on all compute nodes and futher proliferation of flavor explostion. this is one of the reasons we have not added this in > the past. the work to do it in the libvirt driver would not be hard but the maintaince and operational overhead of using it for operators is non > trivial. > >> >> Stephen >> >> [1] https://egallen.com/openstack-usb-passthrough/ >> >> > > > > > ------------------------------ > > Message: 2 > Date: Tue, 03 Jan 2023 19:20:50 +0000 > From: Sean Mooney <smooney(a)redhat.com> > To: Jahson Babel <jahson.babel(a)cc.in2p3.fr>, > openstack-discuss(a)lists.openstack.org > Subject: Re: [ops] QOS on flavor breaking live migration from CentOS 7 > to 8 > Message-ID: > <b0f13cde177cd8b5f7e6e5b20445decab7dbc8b8.camel(a)redhat.com> > Content-Type: text/plain; charset="UTF-8" > > hi yes this is a know issue. > > so the simple answer is resize all affected vms instead of live migrating them > the longer answer is we have been dissing this internally at redhat on and off for > some time now. > https://bugs.launchpad.net/nova/+bug/1960840 is one example where this happens. > > there is another case for the cpu based quotas that happens when going form rhel/centos 8->9 > basically in the 8->9 change the cgroups implemantion changes form v1 to v2 > https://bugzilla.redhat.com/show_bug.cgi?id=2035518 > > when adressing that we did not have a good universal solution for instnace that hardcoded a value that > was incompatible with the cgroups_v2 api in the kernel except resize. > > in https://review.opendev.org/c/openstack/nova/+/824048/ we removed automatically adding the > cpu_shares cgroup option to enable booting vms with more then 8 cpus > > we did not come up with any option other then resize for the other quotas that were in a similar situation. > the one option that we considerd possibel to do was extend nova-mange to allow the embeded flaour to be updated > this would be similar to what we did to enable the image property to be modifed for chaing machine types. > > https://docs.openstack.org/nova/latest/cli/nova-manage.html#image-property-… > > we didcussed at the time that while we did not want to allow falvor extra specs to be modifed we might recondier that > if the quota issue forced our hand or we had a similar need due to foces beyond our contol. i.e. we needed to provide a way beyond > resize e.g. due ot operating system changes. what make image properties and flavor extra spec different is that image proerties can > only be updated by rebuild which is a destructive operation. extra specs are upsted by resize which is not a destructive operation. > that is one of the reasons we have special considertion to image properties and did not do the same for extra specs. > > if we allow the same for flavor extra specs you would still have to stop the instance, make the change and then migrate the instnace > resize automates that so it is generall a better fit. we were also conceren that adding it to nova manage would result in it being abused > to modify instnace in ways that were either invalid for the host(changing the numa toplogy, adding traits/resouce request not trackedcxd in placemnt) > or otherwise break the instnace in weird ways. that could happen via image properites too but its less likely. > > > >> On Tue, 2023-01-03 at 17:25 +0100, Jahson Babel wrote: >> Hello, >> >> I'm trying to live migrate some VMs from CentOS 7 to Rocky 8. >> Everything run smoothly when there is no extra specs on flavors but >> things getting more complicated when those are fixed. Especially when >> using quota:vif_burst for QOS. >> I know that we aren't supposed to use this for QOS now but it's an old >> cluster and it was done that way at the time. So VMs kinda have all >> those specs tied to them. >> >> When live migrate a VM this show up in the nova's logs : >> driver.py _live_migration_operation nova.virt.libvirt.driver? Live >> Migration failure: internal error: Child process (tc class add dev >> tapxxxxxxxx-xx parent 1: classid 1:1 htb rate 250000kbps ceil >> 2000000kbps burst 60000000kb quantum 21333) unexpected exit status 1: >> Illegal "burst" >> This bug cover the problem : https://bugs.launchpad.net/nova/+bug/1960840 >> So it's seems to be a normal behavior. Plus I forgot to mention that I'm >> on OpenStack Train version and the file mentioned in the launchpad is >> not present for this version. >> By using Rocky 8 I have to use an updated libvirt that won't accept the >> burst parameter we used to set. All available versions of libvirt on >> Rocky 8 have changed behavior concerning the burst parameter. >> >> I've done some testing to make things works including removing the >> extra_specs on flavors and in the DB, removing it through libvirt and >> trying to modify tc rules used by a VM but it didn't worked. >> I have not tried yet to patch Nova or Libvirt but I don't really know >> where to look for. >> The only thing that did work was to resize the VM to an identical flavor >> without the extra_specs. But this induce a complete reboot of the VM. I >> would like, if possible, to be able to live migrate the VMs which is >> quite easier. >> >> Is it possible to remove the extra_specs on the VMs and then live >> migrate ? Or should I just plan to resize/reboot all VMs without those >> extra_specs ? >> Any advise will be appreciated. >> >> Thank you for any help, >> Best regards. >> >> Jahson > > > > > ------------------------------ > > Message: 3 > Date: Tue, 3 Jan 2023 15:23:19 -0500 > From: Satish Patel <satish.txt(a)gmail.com> > To: Rafael Weing?rtner <rafaelweingartner(a)gmail.com> > Cc: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > Subject: Re: [cloudkitty] Instances billing based on tags > Message-ID: > <CAPgF-fpGyO-Z8bt7KMdP7CAhi9kne3136ptoE+8coURyFwi7yw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Wow! very interesting, I will poke around and see how it's feasible. Very > curious how it will represent that data in horizon UI. Currently I am > seeing rates based on project_id so assuming it will show based on > customer_id. correct? > > > On Tue, Jan 3, 2023 at 8:13 AM Rafael Weing?rtner < > rafaelweingartner(a)gmail.com> wrote: > >> You can do that. Basically, you can start collecting those attributes you >> want for billing (e.g. tags) via Ceilometer dynamic pollster (that is the >> easiest way to achieve this). Then, you need to configure the resource type >> in Gnocchi to store this extra attribute, and of course, configure >> CloudKitty to collect/use it. Both in the metrics.yml and then in the >> hashmap or Pyscript rules. >> >>> On Mon, Jan 2, 2023 at 11:01 PM Satish Patel <satish.txt(a)gmail.com> wrote: >>> >>> Folks, >>> >>> We have an AWS project and in a single project we run multiple customers >>> so for billing we use tags. In short every vm instance has a tag (customer >>> name) and that way we can produce bills for each customer. >>> >>> Recently I am playing with openstack cloudkitty and it works with >>> standard cases like project based billing. But does it support tags based >>> billing just similar to what i have explained in the above aws example? >>> >>> >>> >> >> -- >> Rafael Weing?rtner >> >

1 0

[cinder] Bug Report from 01-04-2023
by Sofia Enriquez 04 Jan '23

04 Jan '23

This is a bug report from 12-21-2022 to 01-04-2023. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/cinder/+bug/2000436 "250 unit test failures under Python 3.11." Unassigned. - https://bugs.launchpad.net/cinder/+bug/2000489 "Dell Powerstore won't delete volume when storage migrate." Unassigned. Medium - https://bugs.launchpad.net/cinder/+bug/2000724 "cinder should not send external events when extending online is called by glance." In Progress. 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

2023 PTGs + Virtual Team Signup
by Kendall Nelson 03 Jan '23

03 Jan '23

Hello Everyone! The next PTG on the calendar will be our usual virtual format and it will take place March 27 -31 right after the 2023.1 release. The project signup survey is already ready to go! If your team is interested in participating, sign them up here[1]! Registration is also open now[2] We have also heard many requests from the contributor community to bring back in person events and also heard that with global travel reduction, it would be better travel wise for the community at large to combine it with the OpenInfra Summit[3]. So, an in-person PTG will take place Wednesday and Thursday! June 14 -15th. OpenInfra Summit registration will be required to participate, and contributor pricing and travel support[4] will be available. We will also be planning another virtual PTG in the latter half of the year. The exact date is still being finalized. This will give you three opportunities to get your team together in 2023: two virtual and one in-person. - Virtual: March 27-31 - In- Person: June 14-15 collocated with the OpenInfra Summit - Virtual: TBD, but second half of the year As any project in our community, you are free to take advantage of all or some of the PTGs this coming year. I, for one, hope to see you and your project at as many as make sense for your team! To make sure we are as inclusive as possible I will continue to encourage team moderators to write summaries of their discussions to gather and promote after the events as well. Stay tuned for more info as we get closer, but the team signup survey[1] has opened for the first virtual PTG and is ready for you! -Kendall (diablo_rojo) [1] https://openinfrafoundation.formstack.com/forms/march2023_vptg_survey [2] https://openinfra-ptg.eventbrite.com [3]https://openinfra.dev/summit/vancouver-2023 [4] https://openinfrafoundation.formstack.com/forms/openinfra_tsp

1 1

[all][tc] Technical Committee next weekly meeting on 2023 Jan 4 at 1600 UTC
by Ghanshyam Mann 03 Jan '23

03 Jan '23

Hello Everyone, The technical Committee's next weekly meeting is scheduled for 2023 Jan 4, at 1600 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Tuesday, Jan 3 at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[cloudkitty] Instances billing based on tags
by Satish Patel 03 Jan '23

03 Jan '23

Folks, We have an AWS project and in a single project we run multiple customers so for billing we use tags. In short every vm instance has a tag (customer name) and that way we can produce bills for each customer. Recently I am playing with openstack cloudkitty and it works with standard cases like project based billing. But does it support tags based billing just similar to what i have explained in the above aws example?

2 3

[nova][keystone] workload identity?
by Mohammed Naser 03 Jan '23

03 Jan '23

Hi folks: I’m wondering if there’s anyone who’s had some thought or perhaps some work/progress/thoughts on workload identity (example service accounts for VMs) — is that something that’s really far away for us? Has someone thought about outlining what’s needed? Thanks Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

[nova][placement] Specs freeze will be on Jan 12th
by Sylvain Bauza 03 Jan '23

03 Jan '23

Hey, As we didn't have a quorum for today's meeting, I prefer to move our deadline for freezing the Antelope accepted specs by one week, instead of this Thursday. This means we will continue to review open specs until January the 12th. That being said, as a reminder, our Feature Freeze is on February 16th [1] which means we will only have *five* weeks for reviewing all the implementations, so please start to work on your feature branch and don't wait for your spec to be accepted or we wouldn't have time for reviewing all the open features. Thanks, -Sylvain [1] https://releases.openstack.org/antelope/schedule.html#a-ff

1 0

Kolla-ansible Yoga Magnum csi-cinder-controllerplugin-0 CrashLoopBackOff
by Oliver Weinmann 03 Jan '23

03 Jan '23

Dear all, I have a strange issue with Magnum on Yoga deployed by kolla-ansible. I noticed this on a prod cluster and so I deployed a fresh cluster from scratch and here I'm facing the very same issue. When deploying a a new K8s cluster the csi-cinder-controllerplugin-0 pod is in CrashLoopBackOff state. kubectl get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE kube-system coredns-56448757b9-62lxw 1/1 Running 0 11d kube-system coredns-56448757b9-6mvtr 1/1 Running 0 11d kube-system csi-cinder-controllerplugin-0 4/5 CrashLoopBackOff 3339 (92s ago) 11d kube-system csi-cinder-nodeplugin-88ttn 2/2 Running 0 11d kube-system csi-cinder-nodeplugin-tnxpt 2/2 Running 0 11d kube-system dashboard-metrics-scraper-67f57ff746-2vhgb 1/1 Running 0 11d kube-system k8s-keystone-auth-5djxh 1/1 Running 0 11d kube-system kube-dns-autoscaler-6d5b5dc777-mm7qs 1/1 Running 0 11d kube-system kube-flannel-ds-795hj 1/1 Running 0 11d kube-system kube-flannel-ds-p76rf 1/1 Running 0 11d kube-system kubernetes-dashboard-7b88d986b4-5bhnf 1/1 Running 0 11d kube-system magnum-metrics-server-6c4c77844b-jbpml 1/1 Running 0 11d kube-system npd-sqsbr 1/1 Running 0 11d kube-system openstack-cloud-controller-manager-c5prb 1/1 Running 0 11d I searched the mailing list and noticed that I reported the very same issue last year: https://lists.openstack.org/pipermail/openstack-discuss/2022-May/028517.html but then I was either able to fix it or not able to reproduce it. I searched the web and found other users having the same issue: https://storyboard.openstack.org/#!/story/2010023 https://github.com/kubernetes/cloud-provider-openstack/issues/1845 They suggest to change the csi_snapshotter_tag to v4.0.0. I haven't tried it yet, but I have the feeling that something in my deployment is not correct since it wants to use v1.2.2 which is a very old version. Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Pulling 26m (x3382 over 12d) kubelet Pulling image "quay.io/k8scsi/csi-snapshotter:v1.2.2" Warning BackOff 81s (x79755 over 12d) kubelet Back-off restarting failed container kubectl get nodes -o wide NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME k8s-admin-test-old-ygahdfhciitx-master-0 Ready master 12d v1.23.3 10.0.0.132 172.28.4.124 Fedora CoreOS 35.20220410.3.1 5.16.18-200.fc35.x86_64 docker://20.10.12 k8s-admin-test-old-ygahdfhciitx-node-0 Ready <none> 12d v1.23.3 10.0.0.160 172.28.4.128 Fedora CoreOS 35.20220410.3.1 5.16.18-200.fc35.x86_64 docker://20.10.12 I deployed on Rocky Linux 8.7 using latest Kolla-ansible for Yoga: [vagrant@seed ~]$ kolla-ansible --version 14.7.1 [vagrant@seed ~]$ cat /etc/os-release NAME="Rocky Linux" VERSION="8.7 (Green Obsidian)" ID="rocky" ID_LIKE="rhel centos fedora" VERSION_ID="8.7" PLATFORM_ID="platform:el8" PRETTY_NAME="Rocky Linux 8.7 (Green Obsidian)" ANSI_COLOR="0;32" LOGO="fedora-logo-icon" CPE_NAME="cpe:/o:rocky:rocky:8:GA" HOME_URL="https://rockylinux.org/" BUG_REPORT_URL="https://bugs.rockylinux.org/" ROCKY_SUPPORT_PRODUCT="Rocky-Linux-8" ROCKY_SUPPORT_PRODUCT_VERSION="8.7" REDHAT_SUPPORT_PRODUCT="Rocky Linux" REDHAT_SUPPORT_PRODUCT_VERSION="8.7" Can you please help or clarify? Best Regards, Oliver

1 0

[cloudkitty][horizon] change service name list in GUI
by Satish Patel 03 Jan '23

03 Jan '23

Folks, I am trying to configure rating for network data bytes in/out but what I have seen is that the ceilometer uses a different name than what cloudkitty GUI drop down-menu has. Ceilometer using "network.outgoing.bytes" and "network.incoming.bytes" Cloudkitty GUI drop-down list has "network.outgoing.bytes.rate" & "network.incoming.bytes.rate" I have tried to change it in cloudkitty metrics.yml file to match it with the ceilometer but the rating is not calculating until I change that in cloudkitty. Please advise how to change it in cloudkitty.

2 1

[TripleO] Tripleo-ci-centos-9-content-provider jobs are failing in check line
by Amol Kahat 03 Jan '23

03 Jan '23

Hello All, We are investigating centos-9-content-provider check failure, related to build-test-packages. Jobs link[1] Details are in the related launchpad bug[2]. [1] https://zuul.opendev.org/t/openstack/builds?job_name=tripleo-ci-centos-9-co… [2] https://bugs.launchpad.net/tripleo/+bug/2000897/ -- *Amol Kahat* Software Engineer *Red Hat India Pvt. Ltd. Pune, India.* akahat(a)redhat.com B764 E6F8 F4C1 A1AF 816C 6840 FDD3 BA6C 832D 7715

1 0

[neutron] bug deputy report for week of 2022-12-26
by Bence Romsics 03 Jan '23

03 Jan '23

Hi, During the winter holidays we had hardly any new bugs reported: Medium: * https://bugs.launchpad.net/neutron/+bug/2000634 [OVN] Maintenance task for availability zones changes failing proposed fix: https://review.opendev.org/c/openstack/neutron/+/868746 Incomplete: * https://bugs.launchpad.net/neutron/+bug/2000495 See error "HashRingIsEmpty" when create instance waiting for more information Cheers, Bence

1 0

[ansible][ACO] - Contribution questions
by Gaël THEROND 31 Dec '22

31 Dec '22

Hi ansible collections openstack team! I finally had time to list all my issues met with the project, created few bug reports and even contributed to a patch today (minor, mainly copy/paste) however I’ve few questions regarding the CI process! Overall, what’s the rule with the CI code testing? I’ve read the contributing guide and had an eye on previous patches to see how it’s used but I’m having a hard time to find a real unified method. For instance, it seems that some module miss CI tasks (such as compute_service_info) or did I missed something? Thanks a lot for all the good job!

4 7

[release] Release countdown for week R-11, Jan 2 - 6
by Thierry Carrez 30 Dec '22

30 Dec '22

Development Focus ----------------- The Antelope-2 milestone is next week, on January 5, 2023! Antelope-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/antelope/schedule.html for details. General Information ------------------- Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library that has not been otherwise released since milestone 1. PTL's and release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well. A +1 would be appreciated, but if we do not hear anything at all by the end of the week, we will assume things are OK to proceed. Remember that non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. Next week is also the deadline to freeze the contents of the final release. All new 'Antelope' deliverables need to have a deliverable file in https://opendev.org/openstack/releases/src/branch/master/deliverables and need to have done a release by milestone-2. Changes proposing those deliverables for inclusion in Antelope have been posted, please update them with an actual release request before the milestone-2 deadline if you plan on including that deliverable in Antelope, or -1 if you need one more cycle to be ready. Upcoming Deadlines & Dates -------------------------- Antelope-2 Milestone: January 5th, 2023 OpenInfra Summit Vancouver CFP deadline: January 10th, 2023 Final 2023.1 Antelope release: March 22nd, 2023 -- Thierry Carrez (ttx)

2 1

Re: [ops][nova] RBD IOPS bottleneck on client-side
by Ümit Seren 30 Dec '22

30 Dec '22

We had a similar performance issue with networking (via openswitch) instead of I/O. Our hypervisor and VM configuration were like yours (VCPU pinning + isolcpus). We saw a 50% drop in virtualized networking throughput (measure via iperf). This was because the vhost_net kthreads which are responsible for the virtualized networking were pinned to 2 cores per socket and this quickly became the bottleneck. This was with OpenStack Queens and RHEL 7.6. We ended up keeping the VCPU pinning but removing the isolcpus kernel setting. This fixed the performance regression. Unfortunately, we didn’t further investigate this, so I don’t know why a newer kernel and/or newer Openstack release improves it. Hope this still helps Best Ümit On 27.12.22, 13:33, "Can Özyurt" <acozyurt(a)gmail.com> wrote: Hi everyone, I hope you are all doing well. We are trying to pinpoint an IOPS problem with RBD and decided to ask you for your take on it. 1 control plane 1 compute node 5 storage with 8 SSD disks each Openstack Stein/Ceph Mimic deployed with kolla-ansible on ubuntu-1804 (kernel 5.4) isolcpus 4-127 on compute vcpu_pin_set 4-127 in nova.conf image_metadatas: hw_scsi_model: virtio-scsi hw_disk_bus: scsi flavor_metadatas: hw:cpu_policy: dedicated What we have tested: fio --directory=. --ioengine=libaio --direct=1 --name=benchmark_random_read_write --filename=test_rand --bs=4k --iodepth=32 --size=1G --readwrite=randrw --rwmixread=50 --time_based --runtime=300s --numjobs=16 1. First we run the fio test above on a guest VM, we see average 5K/5K read/write IOPS consistently. What we realize is that during the test, one single core on compute host is used at max, which is the first of the pinned cpus of the guest. 'top -Hp $qemupid' shows that some threads (notably tp_librbd) share the very same core throughout the test. (also emulatorpin set = vcpupin set as expected) 2. We remove isolcpus and every other configuration stays the same. Now fio tests now show 11K/11K read/write IOPS. No bottlenecked single cpu on the host, observed threads seem to visit all emulatorpins. 3. We bring isolcpus back and redeploy the cluster with Train/Nautilus on ubuntu-1804. Observations are identical to #1. 4. We tried replacing vcpu_pin_set to cpu_shared_set and cpu_dedicated_set to be able to pin emulator cpuset to 0-4 to no avail. Multiple guests on a host can easily deplete resources and IOPS drops. 5. Isolcpus are still in place and we deploy Ussuri with kolla-ansible and Train (to limit the moving parts) with ceph-ansible both on ubuntu-1804. Now we see 7K/7K read/write IOPS. 6. We destroy only the compute node and boot it with ubuntu-2004 with isolcpus set. Add it back to the existing cluster and fio shows slightly above 10K/10K read/write IOPS. What we think happens: 1. Since isolcpus disables scheduling between given cpus, qemu process and its threads are stuck at the same cpu which created the bottleneck. They should be runnable on any given emulatorpin cpus. 2. Ussuri is more performant despite isolcpus, with the improvements made over time. 3. Ubuntu-2004 is more performant despite isolcpus, with the improvements made over time in the kernel. Now the questions are: 1. What else are we missing here? 2. Are any of those assumptions false? 3. If all true, what can we do to solve this issue given that we cannot upgrade openstack nor ceph on production overnight? 4. Has anyone dealt with this issue before? We welcome any opinion and suggestions at this point as we need to make sure that we are on the right path regarding the problem and upgrade is not the only solution. Thanks in advance.

3 2

Glance api deployed only on a single controller on multi-controller deployment [kolla]
by A Monster 30 Dec '22

30 Dec '22

I've deployed openstack xena using kolla ansible on a centos 8 stream cluster, using two controller nodes, however I found out after the deployment that glance api is not available in one node, I tried redeploying but I got the same behavior, although the deployment finished without displaying any error. Thank you. Regards

4 4

[all][requirements][qa]: requirement-checks job broken for <=stable/yoga because it run on ubuntu-jammy on stable branch
by Ghanshyam Mann 29 Dec '22

29 Dec '22

Hello Everyone, While base jobs in opendev moved to run on ubuntu-jammy, requirement-checks job start running on ubuntu-jammy which is ok for the master but not for stable branches. As result, requirement-checks on stable branch running on ubuntu-jammy and started failing for stable/yoga and less: Error: No package matching 'python-dev' is available - https://zuul.opendev.org/t/openstack/build/811ca9311b894b97bfae4438070e5e22 Fixing it by setting the nodeset explicitly in that job so that it does not get changed in future when we move to ubuntu new version for testing. - https://review.opendev.org/q/Ie676079c0b798335ab2a82c03fe4715e0eee4d57 If you see the requirement-checks job failing (if there is a requirement change in the stable branch backport), please hold the recheck until the above fixes are merged. As tox4 fails the requirement gate, pushing the above fixes on top of tox4 fixes - https://review.opendev.org/q/I7bc7c98954395765f16cc943e5c826983db5dba0 -gmann

1 0

kolla openstack the freezer end point is not reachable
by K Santhosh 29 Dec '22

29 Dec '22

Hai , In kolla openstack the freezer end point is not reachable and the freezer api couldn't reach in web browser if any document is there make it to me

1 0

Container trying to access mounted device file
by vincent lee 29 Dec '22

29 Dec '22

Hi all, I am trying to access a mounted device file from my node to my newly created container. I am currently using Kolla-ansible for the deployment, and it is in the yoga version. For example, when I mount a device to my node, such as a radio receiver, the device file (/dev/mounted device name) is accessible on my node directly. However, I am looking for an option to enable the newly created container to access that device file. Best, Vincent

1 0

[Glance] Extending Specs Freeze Deadline by 2 weeks
by Pranali Deore 28 Dec '22

28 Dec '22

Hello All, As discussed in last glance meeting [1] we are extending the glance specs freeze deadline by 2 weeks due to unavailability of core members and less review bandwidth because of year end holidays. Current Spec Freeze date (for Glance) : 5th Jan 2023 New Spec Freeze date (for Glance) : 19th Jan 2023 Please make sure your specs are updated before the new deadline. [1]: https://meetings.opendev.org/meetings/glance/2022/glance.2022-12-22-14.00.l… Thanks, Pranali deore

1 0

Re: openstack-discuss Digest, Vol 50, Issue 63
by Kerem Çeliker 28 Dec '22

28 Dec '22

Hello Can, To fix an RBD (Rados Block Device) IOPS bottleneck on the client side in OpenStack, you can try the following: Monitor the CPU and memory usage on the client machine to ensure that it has sufficient resources. You can use tools like top or htop to view real-time resource usage. Check the network bandwidth between the client and the storage system to ensure that it is not a bottleneck. You can use tools like iperf or tcpdump to measure network performance. Review the configuration of the storage system to ensure that it is optimized for the workload. This may include adjusting the number and type of disks used, as well as the RAID level and chunk size. Consider using a storage system with a higher IOPS rating to see if it can improve performance. This may involve upgrading to faster disks or using a storage solution with more disks or SSDs. Try using a different client machine with more resources (e.g., a machine with a faster CPU and more memory) to see if it can issue more I/O requests. Consider using a different network connection between the client and the storage system, such as a faster network card or a direct connection rather than a network switch. If you are using Ceph as the underlying storage system, you can try adjusting the Ceph configuration to improve performance. This may include adjusting the number of placement groups, the object size, or the number of OSDs (object storage devices). It's also worth noting that an IOPS bottleneck can also occur on the server side (i.e., within the storage system itself). In this case, you may need to adjust the configuration of the storage system or add more resources (e.g., disks or SSDs) to improve performance. BR, Kerem Çeliker keremceliker.medium.com IBM | Red Hat Champion Sent from my iPhone > On 28 Dec 2022, at 08:13, openstack-discuss-request(a)lists.openstack.org wrote: > > 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. [ops][nova] RBD IOPS bottleneck on client-side (Can ?zyurt) > 2. [keystone][Meeting] Reminder Keystone meeting is cancelled > today (Dave Wilde) > 3. Nova libvirt/kvm sound device (Zakhar Kirpichenko) > 4. Re: [Tacker][SRBAC] Update regarding implementation of > project personas in Tacker (Yasufumi Ogawa) > 5. Re: [Tacker][SRBAC] Update regarding implementation of > project personas in Tacker (manpreet kaur) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 27 Dec 2022 15:33:56 +0300 > From: Can ?zyurt <acozyurt(a)gmail.com> > To: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> > Subject: [ops][nova] RBD IOPS bottleneck on client-side > Message-ID: > <CAMf4N71awOfNyBk4FfpM6UCjH4AZWz+QuJwUnOv+itvqvPbTjw(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hi everyone, > > I hope you are all doing well. We are trying to pinpoint an IOPS > problem with RBD and decided to ask you for your take on it. > > 1 control plane > 1 compute node > 5 storage with 8 SSD disks each > Openstack Stein/Ceph Mimic deployed with kolla-ansible on ubuntu-1804 > (kernel 5.4) > isolcpus 4-127 on compute > vcpu_pin_set 4-127 in nova.conf > > image_metadatas: > hw_scsi_model: virtio-scsi > hw_disk_bus: scsi > flavor_metadatas: > hw:cpu_policy: dedicated > > What we have tested: > fio --directory=. --ioengine=libaio --direct=1 > --name=benchmark_random_read_write --filename=test_rand --bs=4k > --iodepth=32 --size=1G --readwrite=randrw --rwmixread=50 --time_based > --runtime=300s --numjobs=16 > > 1. First we run the fio test above on a guest VM, we see average 5K/5K > read/write IOPS consistently. What we realize is that during the test, > one single core on compute host is used at max, which is the first of > the pinned cpus of the guest. 'top -Hp $qemupid' shows that some > threads (notably tp_librbd) share the very same core throughout the > test. (also emulatorpin set = vcpupin set as expected) > 2. We remove isolcpus and every other configuration stays the same. > Now fio tests now show 11K/11K read/write IOPS. No bottlenecked single > cpu on the host, observed threads seem to visit all emulatorpins. > 3. We bring isolcpus back and redeploy the cluster with Train/Nautilus > on ubuntu-1804. Observations are identical to #1. > 4. We tried replacing vcpu_pin_set to cpu_shared_set and > cpu_dedicated_set to be able to pin emulator cpuset to 0-4 to no > avail. Multiple guests on a host can easily deplete resources and IOPS > drops. > 5. Isolcpus are still in place and we deploy Ussuri with kolla-ansible > and Train (to limit the moving parts) with ceph-ansible both on > ubuntu-1804. Now we see 7K/7K read/write IOPS. > 6. We destroy only the compute node and boot it with ubuntu-2004 with > isolcpus set. Add it back to the existing cluster and fio shows > slightly above 10K/10K read/write IOPS. > > > What we think happens: > > 1. Since isolcpus disables scheduling between given cpus, qemu process > and its threads are stuck at the same cpu which created the > bottleneck. They should be runnable on any given emulatorpin cpus. > 2. Ussuri is more performant despite isolcpus, with the improvements > made over time. > 3. Ubuntu-2004 is more performant despite isolcpus, with the > improvements made over time in the kernel. > > Now the questions are: > > 1. What else are we missing here? > 2. Are any of those assumptions false? > 3. If all true, what can we do to solve this issue given that we > cannot upgrade openstack nor ceph on production overnight? > 4. Has anyone dealt with this issue before? > > We welcome any opinion and suggestions at this point as we need to > make sure that we are on the right path regarding the problem and > upgrade is not the only solution. Thanks in advance. > > > > ------------------------------ > > Message: 2 > Date: Tue, 27 Dec 2022 07:00:30 -0800 > From: Dave Wilde <dwilde(a)redhat.com> > To: openstack-discuss(a)lists.openstack.org > Subject: [keystone][Meeting] Reminder Keystone meeting is cancelled > today > Message-ID: > <CAJEkJ+qYCHZayR-t9w4e=ZB846CZSrggcqdYKE85fWkj2XAo5w(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Just a quick reminder that there won?t be the keystone weekly meeting > today. We?ll resume our regulararly scheduled programming on 03-Jan-2023. > Please update the agenda if you have anything you?d like to discuess. The > reviewathon is also cancelled this week, to be resumed on 06-Jan-2023. > > /Dave >

1 0

[Tacker][SRBAC] Update regarding implementation of project personas in Tacker
by manpreet kaur 27 Dec '22

27 Dec '22

Hi Ogawa san and Tacker team, This mailer is regarding the SRBAC implementation happening in Tacker. In the Tacker release 2023.1 virtual PTG [1], it was decided by the Tacker community to partially implement the project personas (project-reader role) in the current release. And in upcoming releases, we will implement the remaining project-member role. To address the above requirement, I have prepared a specification [2] and pushed the same in Gerrit for community review. Ghanshyam san reviewed the specification and shared TC's opinion and suggestion to implement both the project-reader and project-member roles. The complete persona implementation will depreciate the 'owner' rule, and help in restricting any other role to accessing project-based resources. Additionally, intact legacy admin (current admin), works in the same way so that we do not break things and introduce the project personas which should be additional things to be available for operators to adopt. Current Status: Incorporated the new requirement and uploaded a new patch set to address the review comment. Note: The Tacker spec freeze date is 28th Dec 2022, there might be some delay in merging the specification in shared timelines. [1] https://etherpad.opendev.org/p/tacker-antelope-ptg#L186 [2] https://review.opendev.org/c/openstack/tacker-specs/+/866956 Thanks & Regards, Manpreet Kaur

3 3

Re: openstack-discuss Digest, Vol 50, Issue 62
by Kerem Çeliker 27 Dec '22

27 Dec '22

Hello Vincent, To allow a user from a container to access files on OpenStack, you can use the --volume or -v option when creating the container to mount a host file or directory as a volume inside the container. For example: Copy code docker run -it --volume /path/on/host:/path/in/container image_name This will mount the host file or directory located at /path/on/host as a volume inside the container at /path/in/container. The user inside the container will be able to access the files in the volume at /path/in/container. You can also use the --mount option to mount a volume. This option provides more control over the volume, such as specifying the volume driver and options. For example: Copy code docker run -it --mount type=bind,source=/path/on/host,target=/path/in/container image_name This will also mount the host file or directory located at /path/on/host as a volume inside the container at /path/in/container, and the user inside the container will be able to access the files in the volume at /path/in/container. Note that the /path/on/host must be an absolute path and must exist on the host system. The /path/in/container can be any path inside the container and does not need to exist prior to the mount. It's also important to note that the user inside the container must have the appropriate permissions to access the mounted files. You can use the --user option to specify the user that the container should run as, or you can set the ownership and permissions of the mounted files on the host system to allow the user inside the container to access them. Hope it works for you.. — Best, Regards, Kerem Çeliker IBM | Red Hat Champion keremceliker.medium.com Sent from my iPhone > On 27 Dec 2022, at 15:07, openstack-discuss-request(a)lists.openstack.org wrote: > 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. Container access mounted device (vincent lee) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 27 Dec 2022 19:01:21 +0800 > From: vincent lee <vincentlee676(a)gmail.com> > To: openstack-discuss(a)lists.openstack.org > Subject: Container access mounted device > Message-ID: > > > Hi, I have deployed a working OpenStack and would like to know if there are > any possible options I can enable so that when creating a new container, > files can be mounted to it, and a user from the container can access it. > For instance, having a mounted device from the compute host and allowing > the /dev/(mounted device name) file to be accessible in the container. > > Best regards, > Vincent >

1 0

[keystone][Meeting] Reminder Keystone meeting is cancelled today
by Dave Wilde 27 Dec '22

27 Dec '22

Just a quick reminder that there won’t be the keystone weekly meeting today. We’ll resume our regulararly scheduled programming on 03-Jan-2023. Please update the agenda if you have anything you’d like to discuess. The reviewathon is also cancelled this week, to be resumed on 06-Jan-2023. /Dave

1 0

[ops][nova] RBD IOPS bottleneck on client-side
by Can Özyurt 27 Dec '22

27 Dec '22

Hi everyone, I hope you are all doing well. We are trying to pinpoint an IOPS problem with RBD and decided to ask you for your take on it. 1 control plane 1 compute node 5 storage with 8 SSD disks each Openstack Stein/Ceph Mimic deployed with kolla-ansible on ubuntu-1804 (kernel 5.4) isolcpus 4-127 on compute vcpu_pin_set 4-127 in nova.conf image_metadatas: hw_scsi_model: virtio-scsi hw_disk_bus: scsi flavor_metadatas: hw:cpu_policy: dedicated What we have tested: fio --directory=. --ioengine=libaio --direct=1 --name=benchmark_random_read_write --filename=test_rand --bs=4k --iodepth=32 --size=1G --readwrite=randrw --rwmixread=50 --time_based --runtime=300s --numjobs=16 1. First we run the fio test above on a guest VM, we see average 5K/5K read/write IOPS consistently. What we realize is that during the test, one single core on compute host is used at max, which is the first of the pinned cpus of the guest. 'top -Hp $qemupid' shows that some threads (notably tp_librbd) share the very same core throughout the test. (also emulatorpin set = vcpupin set as expected) 2. We remove isolcpus and every other configuration stays the same. Now fio tests now show 11K/11K read/write IOPS. No bottlenecked single cpu on the host, observed threads seem to visit all emulatorpins. 3. We bring isolcpus back and redeploy the cluster with Train/Nautilus on ubuntu-1804. Observations are identical to #1. 4. We tried replacing vcpu_pin_set to cpu_shared_set and cpu_dedicated_set to be able to pin emulator cpuset to 0-4 to no avail. Multiple guests on a host can easily deplete resources and IOPS drops. 5. Isolcpus are still in place and we deploy Ussuri with kolla-ansible and Train (to limit the moving parts) with ceph-ansible both on ubuntu-1804. Now we see 7K/7K read/write IOPS. 6. We destroy only the compute node and boot it with ubuntu-2004 with isolcpus set. Add it back to the existing cluster and fio shows slightly above 10K/10K read/write IOPS. What we think happens: 1. Since isolcpus disables scheduling between given cpus, qemu process and its threads are stuck at the same cpu which created the bottleneck. They should be runnable on any given emulatorpin cpus. 2. Ussuri is more performant despite isolcpus, with the improvements made over time. 3. Ubuntu-2004 is more performant despite isolcpus, with the improvements made over time in the kernel. Now the questions are: 1. What else are we missing here? 2. Are any of those assumptions false? 3. If all true, what can we do to solve this issue given that we cannot upgrade openstack nor ceph on production overnight? 4. Has anyone dealt with this issue before? We welcome any opinion and suggestions at this point as we need to make sure that we are on the right path regarding the problem and upgrade is not the only solution. Thanks in advance.

1 0

Container access mounted device
by vincent lee 27 Dec '22

27 Dec '22

Hi, I have deployed a working OpenStack and would like to know if there are any possible options I can enable so that when creating a new container, files can be mounted to it, and a user from the container can access it. For instance, having a mounted device from the compute host and allowing the /dev/(mounted device name) file to be accessible in the container. Best regards, Vincent

1 0

[openstacksdk][cinder] openstacksdk-functional-devstack job is failing
by Rajat Dhasmana 26 Dec '22

26 Dec '22

Hi, Currently the *openstacksdk-functional-devstack* job is failing on the cinder gate[1] due to which gate is blocked. This seems to be due to the new tox 4 enforcement and could be an issue for other projects as well. We've a patch in OpenstackSDK that fixes this issue[2] but that is also failing on the* osc-tox-py38-tips* job. The patch has no update since 21st December which is concerning since it's blocking other projects (at least cinder). I've proposed a patch[3] to make the *openstacksdk-functional-devstack *job non-voting until the situation is resolved on the OpenStackSDK side. [1] https://zuul.opendev.org/t/openstack/build/29c0eb15abd144a8a4f167e70fe61530 [2] https://review.opendev.org/c/openstack/openstacksdk/+/867827 [3] https://review.opendev.org/c/openstack/cinder/+/868596 Thanks Rajat Dhasmana

2 2

[openstack][cinder] Cinder volume id wont change when retype volume
by Nguyễn Hữu Khôi 26 Dec '22

26 Dec '22

Hello guys, I have a problem with cinder: I use cinder volume retype to move my volume to another backend. It worked but when I check on new backend, volume id doest match with id which on Horizon dash board.It expects to have same volume id on Horizon and new backend. I use DellSC and DellPowerstore. Thank you. Nguyen Huu Khoi

2 2

Help overriding Nova policies (Ussuri)
by Jérôme BECOT 26 Dec '22

26 Dec '22

Hello, I should miss something, and I need some help. I've updated some rules that I placed in the /etc/nova/policy.yaml file. I use all defaults for the olso policies (ie scope is not enabled). When I generate the fulle policy with oslopolicy-policy-generator, the rules are applied in the generated output. If I test the policy with oslopolicy-checker under the user's token, the results matches the permissions, but Nova API continue to refuse the operation Policy check for os_compute_api:os-flavor-manage:create failed with credentials I'm using the openstack cli to make the request (openstack flavor create) Thanks for your help J

2 2

[tacker] Cancelling next irc meetings
by Yasufumi Ogawa 25 Dec '22

25 Dec '22

Hi team, Due to the holidays, we are cancelling next two meetings on 27th Dec and 3rd Jun. Cheers, Yasufumi

1 0

[kolla-ansible] telemetry data
by Satish Patel 25 Dec '22

25 Dec '22

Folks, I am deployed kolla-ansible and trying to set up telemetry for billing etc. But not able to get it working may be broken or something. In global.yml I turned on the following options and deployed kolla and it did install all the components but I am not seeing it deploy a ceilometer agent on compute nodes. How does it collect data from compute nodes if the ceilometer agent is not running on compute nodes? Did I miss something here? enable_ceilometer: "yes" enable_gnocchi: "yes" enable_cloudkitty: "yes"

2 2

The CFP for the OpenInfra Summit 2023 is open!
by Erin Disney 25 Dec '22

25 Dec '22

Hi Everyone! The CFP for the 2023 OpenInfra Summit (June 13-15, 2023) is NOW LIVE [1]! Check out the full list of tracks and submit a talk on your topic of expertise [2]. The CFP closes January 10, 2023, at 11:59 p.m. PT We are also now accepting submissions for Forum sessions [3]! What should you submit to the forum vs. the traditional CFP? For the Forum, submit discussion-oriented sessions, including challenges around different software components, working group progress or best practices to tackle common issues. Looking for other resources? Registration [4], sponsorships [5], travel support [6] and visa requests [7] are also all open! Find all the information on the OpenInfra Summit 2023 in one place [8]! Cheers, Erin [1] https://cfp.openinfra.dev/app/vancouver-2023/19/presentations <https://cfp.openinfra.dev/app/vancouver-2023/19/presentationshttps://cfp.op…> [2] https://openinfra.dev/summit/vancouver-2023/summit-tracks/ <https://openinfra.dev/summit/vancouver-2023/summit-tracks/> [3] https://cfp.openinfra.dev/app/vancouver-2023/20/ <https://cfp.openinfra.dev/app/vancouver-2023/20/> [4] http://openinfra.dev/summit/registration <http://openinfra.dev/summit/registration> [5] http://openinfra.dev/summit/vancouver-2023/summit-sponsor/ <http://openinfra.dev/summit/vancouver-2023/summit-sponsor/> [6] https://openinfrafoundation.formstack.com/forms/openinfra_tsp <https://openinfrafoundation.formstack.com/forms/openinfra_tsp> [7] https://openinfrafoundation.formstack.com/forms/visa_yvrsummit2023 <https://openinfrafoundation.formstack.com/forms/visa_yvrsummit2023> [8] https://openinfra.dev/summit/vancouver-2023 <https://openinfra.dev/summit/vancouver-2023>

2 1

the zun service run is OK , but at dashboard web no view zun serivce!
by 无数的星球 24 Dec '22

24 Dec '22

After I successfully installed the zun service, I logged in to the dashboard, but I could not see the zun entry I've rebooted all the machines，but invalid. thanks you !

2 1

Container access mounted device
by vincent lee 24 Dec '22

24 Dec '22

Hi, I have deployed a working OpenStack and would like to know if there are any possible options I can enable so that when creating a new container, files can be mounted to it, and a user from the container can access it. For instance, having a mounted device from the compute host and allowing the /dev/(mounted device name) file to be accessible in the container. Best regards, Vincent

2 1

the zun server (zun-api) in controller host error(s)
by 无数的星球 24 Dec '22

24 Dec '22

iAfter I followed the official documentation and fixed a 'pip3' error, it still failed to run successfully. This is an error reported by the zun api. Other components work normally. If you need my profile, it is attached root@controller:~# systemctl status zun-api ● zun-api.service - OpenStack Container Service API      Loaded: loaded (/etc/systemd/system/zun-api.service; enabled; vendor preset: enabled)      Active: failed (Result: exit-code) since Sun 2022-12-11 11:43:04 CST; 1min 38s ago     Process: 1017 ExecStart=/usr/local/bin/zun-api (code=exited, status=1/FAILURE)    Main PID: 1017 (code=exited, status=1/FAILURE) Dec 11 11:43:04 controller zun-api[1017]:     from zun import objects Dec 11 11:43:04 controller zun-api[1017]:   File "/usr/local/lib/python3.8/dist-packages/zun/objects/__init__.py", line 13, in <module> Dec 11 11:43:04 controller zun-api[1017]:     from zun.objects import compute_node Dec 11 11:43:04 controller zun-api[1017]:   File "/usr/local/lib/python3.8/dist-packages/zun/objects/compute_node.py", line 16, in <module> Dec 11 11:43:04 controller zun-api[1017]:     from zun.db import api as dbapi Dec 11 11:43:04 controller zun-api[1017]:   File "/usr/local/lib/python3.8/dist-packages/zun/db/api.py", line 32, in <module> Dec 11 11:43:04 controller zun-api[1017]:     (a)profiler.trace("db") Dec 11 11:43:04 controller zun-api[1017]: AttributeError: partially initialized module 'zun.common.profiler' has no attribute 'trace' (most likely due to a circular import) Dec 11 11:43:04 controller systemd[1]: zun-api.service: Main process exited, code=exited, status=1/FAILURE Dec 11 11:43:04 controller systemd[1]: zun-api.service: Failed with result 'exit-code'.

2 1

[all][tc] What's happening in Technical Committee: summary 2022 Dec 23: Reading: 5 min
by Ghanshyam Mann 23 Dec '22

23 Dec '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Dec 21. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-12-21-16.00.log.html * The TC meeting on Dec 28 is cancelled [1]. The next TC weekly meeting will be on Jan 4 Wed at 16:00 UTC, Feel free to add the topic to the agenda[2] by Jan 3. 2. What we completed this week: ========================= * Made inactive projects timeline as release milestone-2 of the cycle[3] 3. Activities In progress: ================== TC Tracker for the 2023.1 cycle ------------------------------------- * Current cycle working items and their progress are present in the 2023.1 tracker etherpad[4]. Open Reviews ----------------- * Three open reviews for ongoing activities[5]. IMPORTANT: Tox 4 failure and time to fix them -------------------------------------------------------- tox is uncapped in ensure-tox [6]. With that tox4 is used in unit/functional tests job (or any job using ensure-role. If you are seeing failure in your project's jobs, please fix those on priority and if it needs time then you can cap tox it in your project zuul.yaml or for the particular job via 'ensure_tox_version' var. Mistral release and more maintainers ------------------------------------------- avanzagh who is the new maintainer of Mistral is in discussion with the release team for the required work for the Mistral release. We will keep monitoring the situation until the proposal for Mistral release deprecation is closed[7]. Project updates ------------------- * Add Cinder Huawei charm[8] 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[9]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [10] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-December/03156… [2] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggesti… [3] https://review.opendev.org/c/openstack/governance/+/867062 [4] https://etherpad.opendev.org/p/tc-2023.1-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] https://review.opendev.org/c/zuul/zuul-jobs/+/866943 [7] https://review.opendev.org/c/openstack/governance/+/866562 [8] https://review.opendev.org/c/openstack/governance/+/867588 [9] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [10] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[manila] Cancelling Dec 29th weekly meeting
by Carlos Silva 23 Dec '22

23 Dec '22

Hello, Zorillas! As discussed in yesterday's weekly meeting, next week's IRC meeting (Dec 29th) is cancelled due to most of us being offline. The next weekly meeting is on January 5th. Happy holidays to those celebrating! Cheers, carloss

1 0

[neutron] bug deputy report December 19th -23th
by Miguel Lavalle 23 Dec '22

23 Dec '22

Hi, Here's this week's bugs deputy report: Under investigation at the moment of this report ==================================== https://bugs.launchpad.net/neutron/+bug/2000378 [OVN] orphaned virtual parent ports break new ports. Under investigation by ralonsoh Medium ====== https://bugs.launchpad.net/neutron/+bug/2000163 [FT] Error in "test_get_datapath_id". Proposed fix: https://review.opendev.org/c/openstack/neutron/+/868311 https://bugs.launchpad.net/neutron/+bug/2000164 [FT] Error in "test_dvr_update_gateway_port_with_no_gw_port_in_namespace". Needs owner https://bugs.launchpad.net/neutron/+bug/2000252 [OVN] "DBInconsistenciesPeriodics.check_for_inconsistencies" failing during port deletion. Needs owner https://bugs.launchpad.net/neutron/+bug/2000314 [OVS] Call to "driver.unregister" failing. Needs owner Low === https://bugs.launchpad.net/neutron/+bug/2000238 [FT] Remove the "Running command:" messages in the logs. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/868304

1 0

[nova] Isolating scheduler
by Dominik Danelski 23 Dec '22

23 Dec '22

Hello, I'd like to create and test some new filters and weights for the scheduler. Ideally, I would mimic an existing OpenStack deployment I have access to. I already installed placement component, to which the scheduler would connect and now I'd like to isolate it. I'm not sure how to approach it, as scheduler is part of Nova and not a stand-alone component as placement. My intention is to initially fill placement's database with information about the infrastructure, set up the scheduler and then query it for consecutive requests (linear, no need for locks if that changes anything) to log the decisions it would make with modified weights/filters and the state of the system in-between requests. What is, in your opinion, the best way to detach the scheduler as much as possible from the rest of Nova, in order to test it under configuration most resembling the real-world setup? Should I use the test framework and mimic how it is set up for the unit tests or is there a better way to go? Thank you for your time. Regards Dominik Danelski

1 0

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 23 Dec '22

23 Dec '22

Hello Neutrinos: Due to the lack of agenda, today's drivers meeting is cancelled. Please spend some time reviewing the active specs from the RFEs approved last week: https://review.opendev.org/q/project:openstack/neutron-specs+status:open+-a… . See you next year!

1 0

[all][tc] Canceling next week TC meetings
by Ghanshyam Mann 22 Dec '22

22 Dec '22

Hello Everyone, Due to the holidays, we are cancelling next week's (Dec 28) TC meeting. -gmann

1 0

[Glance] Cancelling Weekly meeting for Next 2 weeks
by Pranali Deore 22 Dec '22

22 Dec '22

Hello, Upstream glance weekly meeting for next 2 weeks is cancelled as most of the team members will be on New Year Holidays. The Next weekly meeting will be on Jan 12th ! Wishing everyone a Wonderful Holiday Season & a Joyful New Year. Thanks, Pranali

1 0

[Octavia] cancelling meeting Dec 28
by Gregory Thiemonge 22 Dec '22

22 Dec '22

Hi, Next week's meeting (Dec 28th) is cancelled, The next weekly meeting will be on Jan 4th! Gregory

1 0

Kolla ansible, add a service to a running openstack deployment
by A Monster 21 Dec '22

21 Dec '22

is there a way to add a service such as elasticsearch to an already done openstack deployment using kolla-ansible?

2 1

[cinder] Cancelling meeting on 28th December
by Rajat Dhasmana 21 Dec '22

21 Dec '22

Hello Argonauts, As discussed in today's meeting[1], we will be cancelling the upstream cinder meeting on 28st December, 2022 and will meet in the meeting on 4th January, 2023. Wishing everyone Merry Christmas and a happy new year! [1] https://meetings.opendev.org/meetings/cinder/2022/cinder.2022-12-21-14.00.l… Thanks Rajat Dhasmana

1 0