January 2022 - openstack-discuss - lists.openstack.org

Monasca in kolla-ansible
by Karera Tony 10 Jan '22

10 Jan '22

Dear Team, I hope all is well. I have deployed Openstack with kolla-ansible and enabled Monasca among the projects. The deployment was successful but unfortunately I can't see Logging in the Dashn=board. Kindly advise If I could be missing something. Regards Tony Karera

2 2

[nova][requirements] fasteners===0.16.3 held back by nova
by Matthew Thode 10 Jan '22

10 Jan '22

This one is simple, and iirc is blocked on upstream fixing something (but cannot find the reference). fasteners===0.16.3 https://review.opendev.org/823470 and https://review.opendev.org/804246 both test this change. -- Matthew Thode

4 4

[glance] Does glance not support using local filesystem storage in a cluster
by 韩光宇 10 Jan '22

10 Jan '22

Deal all, Sorry that maybe I ask a stupid question. But I'm really confused with it and didn't find discuss in glance document(https://docs.openstack.org/glance/latest/). I have a OpenStack Victoria cluster with three all-in-one node in centos8. I implemented it with reference to https://docs.openstack.org/ha-guide/. So this cluster use Pacemaker, HAproxy and Galera. "To implement high availability, run an instance of the database on each controller node and use Galera Cluster to provide replication between them." I found that I will encounter an error If I configure Glance backend to use local storage driver to store image files on the local disk. If I upload a image, this image only will be storaged in one node. But the database only storage the file path of image such as "/v2/images/aa3cbee0-717f-4699-8cca-61243302d693/file", don't have the host information. The database data is same in three node. If I upload a image in node1, image only is storaged in node1. The database of three node stores the local filesystem path of image. And If The create Instance task is assigned to node2, It will find image in node2, but image can't be found in node2. So we get the "Image has no associated data" error. So I want to ask: 1. Wheter glance does not support using local filesystem storage in a cluster? 2. If 1 was right, why do we do this design instead of storing information about the host on which images is located, as nova does with instance. I would appreciate any kind of guidance or help. Thank you, Han Guangyu

5 7

Huge Fake tap device creating on some Compute node || Open vSwitch
by Md. Hejbul Tawhid MUNNA 09 Jan '22

09 Jan '22

1 0

[kolla] Updating libvirt container images without VM downtime
by J-P Methot 09 Jan '22

09 Jan '22

Hi, I'm looking for validation regarding the way Kolla and containers work in regard to upgrading the libvirt containers. Essentially, when you upgrade the libvirt container to a new container image, the container needs to be restarted, thus creating downtime for the VMs. There is no way to avoid this downtime, unless you migrate the VMs to another node and then move them back once the container has restarted, right? -- Jean-Philippe Méthot Senior Openstack system administrator Administrateur système Openstack sénior PlanetHoster inc.

4 4

Logging (Monasca) not in Dashboard
by Karera Tony 08 Jan '22

08 Jan '22

Dear Team, I hope all is well. I have deployed Openstack with kolla-ansible and enabled Monasca among the projects. The deployment was successful but unfortunately I can't see Logging in the Dashn=board. Kindly advise If I could be missing something. Regards Tony Karera

1 0

[release] Release countdown for week R-11, Jan 10-14
by Előd Illés 07 Jan '22

07 Jan '22

Development Focus ----------------- We are now past the Yoga-2 milestone, and entering the last development phase of the cycle. Teams should be focused on implementing planned work for the cycle. Now is a good time to review those plans and reprioritize anything if needed based on the what progress has been made and what looks realistic to complete in the next few weeks. General Information ------------------- Looking ahead to the end of the release cycle, please be aware of the feature freeze dates. Those vary depending on deliverable type: * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (February 17th, 2022). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (February 24th, 2022) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, February 24th, 2022. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (March 10th, 2022) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases beforeMarch 25th, 2022 (Final RC deadline) Upcoming Deadlines & Dates -------------------------- Non-client library freeze: February 17th, 2022(R-6 week) Client library freeze: February 24th, 2022(R-5 week) Yoga-3 milestone: February 24th, 2022(R-5 week) Yogafinalrelease: March 30th, 2022 Next PTG: April 4 - 8, 2022 (virtual) Előd Illés irc: elodilles

1 0

[TripleO] Overcloud deployment failing with Network Seggregation
by Anirudh Gupta 07 Jan '22

07 Jan '22

Hi Team, I am trying to deploy an Openstack Train using TripleO having 3 Controllers and 1 Compute. Without Network Isolation, I have deployed it successfully. Now, I am trying to segregate my network traffic using multiple-nics-vlan configuration generated via the below command /tools/process-templates.py -o ~/openstack-tripleo-heat-templates-rendered -n /home/stack/network_data.yaml -r /home/stack/templates/roles_data.yaml The command used for deploying the overcloud is openstack overcloud deploy --templates \ *-n /home/stack/templates/network_data.yaml \* -r /home/stack/templates/roles_data.yaml \ -e /home/stack/templates/node-info.yaml \ *...* *-e /home/stack/templates/environments/network-isolation.yaml \-e /home/stack/templates/environments/network-environment.yaml \* *...* It is failing just after the ovs bridge gets created and external nic vlan is attached to the bridge. [image: MicrosoftTeams-image (1).png] MAC Address of br-ex is same as the MAC of the interface specified in file network/config/multiple-nics-vlan/controller.yaml For testing, If I assign an IP address to that interface, it is reachable to GW. But, in case IP is assigned to VLAN 418 and it is added in the br-ex, Gateway remains unreachable. Please suggest

1 0

[neutron] Drivers meeting - Friday 7.1.2022 - cancelled
by Lajos Katona 06 Jan '22

06 Jan '22

Hi Neutron Drivers! Tomorrow we have not enough drivers to vote (see previous mail from mlavalle: [0]), so let's cancel tomorrow's meeting, and meet a week later: January 14th. [0]: http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026549.… See You on the meeting next week. Lajos Katona (lajoskatona)

1 0

[all][Neutron][devstack] Deprecate lib/neutron
by Lajos Katona 06 Jan '22

06 Jan '22

Hi, In devstack we have two more or less overlapping lib for deploying Neutron: lib/neutron and lib/neutron-legacy. lib/neutron-legacy was recently "undeprecated" (see [0]), and Openstack CI mostly (fully?) uses it. To avoid double maintenance, and confusion in settings we would like to deprecate lib/neutron, for recent discussions see [1] and [2]. The plan is to keep lib/neutron for 2 cycles (that will be AA or the release after Z) and delete lib/neutron then, and rename lib/neutron-legacy to lib/neutron. As You can see from the discussions below there are questions like how to name the processes, log-files etc..., as lib/neutron-legacy uses q-* and lib/neutron uses neutron-* names. The best would be to keep both in the long term (we love q-* as historical tradition, but neutron-* looks like so fresh and modern;)) If you have any thoughts suggestions or questions please answer to this mail or comment on the deprecation patch: [3] [0]: https://review.opendev.org/c/openstack/devstack/+/704829 [1]: https://meetings.opendev.org/meetings/networking/2022/networking.2022-01-04… [2]: https://meetings.opendev.org/irclogs/%23openstack-qa/%23openstack-qa.2022-0… [3]: https://review.opendev.org/c/openstack/devstack/+/823653

1 0

[neutron] Dadfailed of ipv6 metadata IP in qdhcp namespace and disappearing dhcp namespaces
by Kamil Madáč 06 Jan '22

06 Jan '22

Hello, In our small cloud environment, we started to see weird behavior during last 2 months. Dhcp namespaces started to disappear randomly, which caused that VMs losed connectivity once dhcp lease expired. After the investigation I found out following issue/bug: 1. ipv6 metadata address of tap interface in some qdhcp-xxxx namespaces are stucked in "dadfailed tentative" state (i do not know why yet) 2. 3. root@cloud01:~# ip netns exec qdhcp-3094b264-829b-4381-9ca2-59b3a3fc1ea1 ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2585: tap1797d9b1-e1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether fa:16:3e:77:64:0d brd ff:ff:ff:ff:ff:ff inet 169.254.169.254/32 brd 169.254.169.254 scope global tap1797d9b1-e1 valid_lft forever preferred_lft forever inet 192.168.0.2/24 brd 192.168.0.255 scope global tap1797d9b1-e1 valid_lft forever preferred_lft forever inet6 fe80::a9fe:a9fe/64 scope link dadfailed tentative valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fe77:640d/64 scope link valid_lft forever preferred_lft forever 4. 5. This blocked dhcp agent to finish sync_state function, and NetworkCache was not updated with subnets of such neutron network 6. During creation of VM assigned to such network, agent does not detect any subnets (see point 2), so he thinks (reload_allocations()) there is no dhcp needed and deletes qdhcp-xxxx namespace, so no DHCP and no Metadata are working on such network since that moment, and after 24h we see connectivity issues. 7. Restart of DHCP agent recreates missing qdhcp-xxxx namespaces, but NetworkCache in dhcp agent is again empty, so creation of VM deletes the qdhcp-xxxx namespace again 🙁 Workaround is to remove dhcp agent from that network and add it again. Interestingly, sometimes I need to do it multiple times, because in few cases tap interface in new qdhcp finishes again in dadfailed tentative state. After year in production we have 20 networks out of 60 in such state. We are using kolla-ansible deployment on Ubuntu 20.04, kernel 5.4.0-65-generic. Openstack version Victoria and neutron is in version 17.2.2.dev70. Is that bug in neutron, or is it misconfiguration of OS on our side? I'm locally testing patch which disables ipv6 dad in qdhcp-xxxx namespace (net.ipv6.conf.default.accept_dad = 1), but I'm not sure it is good solution when it comes to other neutron features? Kamil Madáč Slovensko IT a.s.

3 3

[horizon] Bump XStatic-Angular-FileUpload to 12.2.13
by Thomas Goirand 06 Jan '22

06 Jan '22

Hi, After someone unrelated to OpenStack maintenance uploaded libjs-angular-file-upload 12.2.13, I tested it, and it didn't break Horizon (at least, when I manually uploaded a file, it worked...). So IMO, it would be fine to just bump to that version. Cheers, Thomas Goirand (zigo)

1 0

[keystone][requirements] keystone holding back pysaml2-7.1.x update
by Matthew Thode 05 Jan '22

05 Jan '22

Hi again, pysaml2===7.1.0 has been breaking updates for a while now. https://review.opendev.org/818612 -- Matthew Thode

1 0

[horizon][requirements] falling behind on requirements updates
by Matthew Thode 05 Jan '22

05 Jan '22

Hi, The following requirements updates have been stalled. XStatic-Angular===1.8.2.1 Has been held back for at least 7 months, but I think closer to a year now. Some review history is here: https://review.opendev.org/794258 django-compressor===2.4.1 rcssmin===1.1.0 rjsmin===1.1.0 These come as a group and have been holding things back for about a month. I'm not sure what's holding things back here on the horizon side. Review bundled with XStatic-Angular here: https://review.opendev.org/823449 -- Matthew Thode

1 0

[all][tc] Technical Committee next weekly meeting on Jan 6th at 1500 UTC
by Ghanshyam Mann 05 Jan '22

05 Jan '22

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

1 1

[infra] Missing releases from opendev.org/opendev/git-review/tags
by Pete Zaitcev 05 Jan '22

05 Jan '22

Greetings: I noticed that the list of tags for git-review in the website does not include the 2.2.x tags, which exist in git: [zaitcev@niphredil git-review-0]$ grep url .git/config url = https://opendev.org/opendev/git-review.git [zaitcev@niphredil git-review-0]$ git tag -l --format='%(objectname) %(objecttype) %(refname)'| grep 2\\.2 bb81051c2481d4ac983ec0b28bd62b590d361141 tag refs/tags/2.2.0 [zaitcev@niphredil git-review-0]$ git show bb81051c2481d4ac983ec0b28bd62b590d361141 | head -5 tag 2.2.0 Tagger: Jeremy Stanley <fungi(a)yuggoth.org> Date: Wed Nov 24 02:20:05 2021 +0000 Release 2.2.0 [zaitcev@niphredil git-review-0]$ The 2.2.0 is missing from https://opendev.org/opendev/git-review/tags Coincidentally, it is also missing from https://tarballs.opendev.org/openstack/git-review/ Is this something that the infrastructure team did on purpose? Or is this just a bug to be reported? -- Pete

3 7

RE: [nova][dev] Revisiting qemu emulation where guest arch != host arch
by Race, Jonathan 05 Jan '22

05 Jan '22

That makes sense which is the best method I saw as well. For your example "use HW_ARCH_X86 to idenfiy the host as being x86 and COMPUTE_ARCH_X86 for emulated", I actually implemented a new field called hw_emulation_architecture as to not conflict with any existing nova operations and to eliminate confusion. This allows for setting this specific value as an image meta property in glance, and if it is set then it will execute emulation via qemu for the designated architecture. If it is not set then operations will occur as normal. https://review.opendev.org/c/openstack/nova/+/822053 is really just an initial response for the bug, that was submitted. And our long-term goal is to collab on this existing blueprint https://blueprints.launchpad.net/nova/+spec/pick-guest-arch-based-on-host-a… for a more full set of capabilities. Jonathan Race Cyber Range Engineer | Georgia Cyber Range GEORGIA CYBER CENTER On Wed, 2020-07-15 at 14:17 +0000, Apsey, Christopher wrote: > 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? > yes, i cant really speak to how much use it would get or how useful it woudl be to the majoriy fo user but i would be supportive of adding this capablity. We have to be a little carful to get the design wright for example we might want to differnciate between the native architecture and emulated architectures e.g. use HW_ARCH_X86 to idenfiy the host as being x86 and COMPUTE_ARCH_X86 for emulated with the new "in" suppot being added to placment we can use required=in:HW_ARCH_X86,COMPUTE_ARCH_X86 in cases where you dont care and by default if you wanted native only you could use the HW_ARCH_* traits in the image and we can have a prefileter add the both triats by default if the architrue is set in the iamge and there is not arch trait in the flavor or image. i will certenly review a spec if you proporse one but you might now have time to get it approved this cycle the spec deadlien woudl have been thursday btu it has been moved to next week. > 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…<https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.open…> > > Chris Apsey > Director | Georgia Cyber Range > GEORGIA CYBER CENTER > > 100 Grace Hopper Lane | Augusta, Georgia | 30901 > https://www.gacybercenter.org<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.gacyb…> >

1 0

[largescale-sig] Next meeting: Jan 5th, 15utc
by Thierry Carrez 05 Jan '22

05 Jan '22

Hi everyone, and happy new year! To kick off 2022, the Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. You can doublecheck how that time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220105T15 We will be discussing our upcoming activities and our next OpenInfra Live episode, as well as any topic you may add to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[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

openstack-kolla with GlusterFS integration
by Satish Patel 05 Jan '22

05 Jan '22

Folks, Recently I have started playing with the Openstack Kolla Project because of some requirements. I want to integrate kolla with GlusterFS for nova vm backend storage. I have functional Glsuter storage and want to mount on compute node to use for vm backend but not sure how do i do that because i am new to containers I can see kolla use following to bind volume with nova_compute container { "Type": "volume", "Name": "nova_compute", "Source": "/var/lib/docker/volumes/nova_compute/_data", "Destination": "/var/lib/nova", "Driver": "local", "Mode": "rw", "RW": true, "Propagation": "" } If I can mount GlusterFS in /mnt directory then how do I tell docker to use /mnt to create volume for nova_compute?

2 6

Logical Volume migration to a New Openstack environment
by KK CHN 05 Jan '22

05 Jan '22

List, I am in need to migrate a Virtual machine ( running in an old OpenStack environment with only one controller). This VM has its own disk file + a logical volume attached to it with application data on it. Only Cinder backend( No rbd/ceph backend configured ) for this environment. Now I am migrating this Virtual machine to another OpenStack(ussuri with three controllers, three compute nodes and three storage nodes) environment with ceph/rbd backend. I am able to export the VM with its disk file and import it to the other openstack environment and able to boot the machine. But How to export the attached logical volume from the old VM and attach to the VM in the other environment ? what is the methodology to follow to export this logical volume in the old openstack VM and import to the new VM running in the other openstack environment ? kindly share your suggestions/expertise to perform this Thanks in advance for your valuable guidance. Krish

3 2

[cinder] Bug deputy report for week of 01-05-2022
by Sofia Enriquez 05 Jan '22

05 Jan '22

No meeting today. This is a bug report from 12-29-2021 to 01-05-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- No bugs in this period :P 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

[nova][placement] Spec approval freeze punted to Jan13st
by Sylvain Bauza 05 Jan '22

05 Jan '22

Hi folks, As agreed on yesterday's nova meeting [1], we accepted to punt the spec approval freeze for one week, ie. at January 13st. That said, we won't accept any exception for a spec approval after this day as we will only have 6 weeks after Jan 13st until FeatureFreeze. Thanks (and happy new 2022 by the way), -Sylvain [1] https://meetings.opendev.org/meetings/nova/2022/nova.2022-01-04-16.00.log.h…

1 0

OpenInfra Live - January 6 at 9am CT
by Allison Price 04 Jan '22

04 Jan '22

Hi everyone, This week, I will be hosting the first OpenInfra Live <http://openinfra.live/> episode of 2022, brought to you by the OpenStack, Kata Containers, Zuul, and StarlingX communities! It's been one year since the formation of the OpenInfra Foundation and the global community has produced more software, more production use cases, more collaboration than ever before. Join us as we look back at 2021, the software milestones, production growth, and momentum across the OpenInfra landscape. Episode: A Year in Review: OpenInfra Highlights from 2021 Date and time: Thursday, January 6 at 9am CT (1500 UTC) You can watch us live on: YouTube <https://www.youtube.com/watch?v=MhAK2efrl9I> LinkedIn <https://www.linkedin.com/video/event/urn:li:ugcPost:6884201840976764928/> Facebook <https://www.facebook.com/104139126308032/posts/4704702346251664/> WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Ghanshyam Mann, OpenStack TC Chair Tao Peng, Kata Containers Architecture Committee Member James Blair, Zuul Maintainer Greg Waines, StarlingX Technical Steering Committee Member Have an idea for a future episode? Share it now at ideas.openinfra.live <https://openinfrafoundation.formstack.com/forms/openinfralive>. Have you heard that the OpenInfra Summit is going back to Berlin, June 7-9? Registration and sponsorship opportunities are now available here: https://openinfra.dev/summit/ <https://openinfra.dev/summit/>. Thanks, Allison

1 0

[charms] nominate Hemanth Nakkina for charms-core
by Edward Hope-Morley 04 Jan '22

04 Jan '22

I would like propose Hemanth Nakkina for charms-core. Hemanth has really stepped up his efforts to provide invaluable contributions both in code and reviews and I beleive he is in a good position to be considered for core where he will be able to provide additional value to the project. Hemanth has demonstrated rigour for quality through his contributions and is always keen to help others with his deep knowledge of the charms and Openstack. Here is a list of all his contributions: patches: https://review.opendev.org/q/owner:hemanth.nakkina%2540canonical.com reviews: https://review.opendev.org/q/reviewedby:hemanth.nakkina%2540canonical.com I hope you will join me in voting for Hemanth. - Ed

6 5