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

[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