March 2022 - openstack-discuss - lists.openstack.org

[VICTORIA] Not working SNAT over VXLAN?
by Gaël THEROND 15 Mar '22

15 Mar '22

Hi everyone! I’m facing a weird situation on a tenant of one of our Openstack cluster based on Victoria. On this tenant, the network topology is as follow: One DMZ network (192.168.0.0/24) linked to our public network through a neutron router where there is a VM acting as a bastion/router for the MGMT network. One MGMT network (172.16.31.0/24) where all VMs are linked to. On the DMZ network, there is a linux Debian 11, let’s call it VM-A with a Floating IP from the public pool, this VM is both attached to the DMZ network (ens3 / 192.168.0.12) AND the MGMT network (ens4 / 172.16.31.23). All other VMs, let’s call them VM-X are exclusively attached to the MGMT network (ens4). I’ve setup VM-A with ip_forward kernel module and the following iptables rule: # iptables -t nat -A POSTROUTING -o ens3 -J SNAT —to-source 192.168.0.12 My VM-X are on their own setup with a default gateway via VM-A: # ip route add default via 172.31.16.23 The setup seems to be working as if I don’t put the iptables rule and the kernel forwarding I can’t see any packets on my DMZ interface (ens3) on VM-A from VM-X. Ok so now that you get the whole schema, let dive into the issue. So when all rules, modules and gateway are set, I can fully see my VM-X traffic (ICMP ping to a dns server) going from VM-X (ens4) to VM-A (ens4) then forwarded to VM-A (ens3) and finally going to our public IP targeted service. What’s not working however is the response not reaching back to VM-X. I’ve tcpdump the whole traffic from VM-X to VM-A on each point of the platfrom: from inside the VM-X nic, on the tap device, on the qbr bridge, on the qvb veth, on the qvo second side of the veth through the ovs bridges and vice-versa. However the response packets aren’t reaching back further than on the VM-A qvo veth. Once it exit the VM-A the traffic never reaches the VM-X. What’s really suspicious in here is that a direct ping from VM-X (172.16.31.54) to VM-A (172.16.31.23) is coming back correctly, so it looks like if ovs detected that the response on a SNAT case isn’t legit or something similar. Is anyone able to get such setup working? Here are few additional information: Host runs on CentOS 8.5 latest update. Our platform is a Openstack Victoria deployed using kolla-ansible. We are using a OVS based deployment. Our tunnels are VXLAN. All VMs have a fully open secgroup applied and all ports have it (I checked it twice and even on host iptables). If you ever need additional information feel free to let me know !

2 10

[dev][trove] Self-introduction and request to merge PRs
by Hirotaka Wakabayashi 15 Mar '22

15 Mar '22

Hello, I am Hirotaka Wakabayashi from Tokyo. This is my first post to openstack-discuss. My goal in OpenStack Project is to learn the OpenStack Infrastructures anddevelop them together and to enlarge the community in Japan if I could. I am a software engineer. In this 10 years, I have been a backend developer in Yahoo Japan Corporation. I have been using FreeBSD, Fedora-based Linux Distros. I mostly use C/C++ and sometime use python recently. I am a Trove contributor from two years ago and I submitted the following PRs last week, but does anybody kindly merge them? I think they are verysmall code changes and easy to understand, but the #832786 and #833497are very important to make Trove on master branch work correctly. https://review.opendev.org/c/openstack/trove/+/832786 https://review.opendev.org/c/openstack/trove-dashboard/+/833497 https://review.opendev.org/c/openstack/trove/+/833361 https://review.opendev.org/c/openstack/trove/+/833501 I asked to merge them in #openstack-trove yesterday, but I got no response. So I posted this email here. Any questions are welcome! Thanks in advance, Hirotaka Wakabayashi GPG Key UID: "Hirotaka Wakabayashi <hiwkby(a)yahoo.com>" GPG fingerprint: "3F54 9D91 A73A 1F31 8CA8 8A9F 050F 5312 F0D7 DBCD"

1 0

VM instances too slow
by A Monster 14 Mar '22

14 Mar '22

After deploying openstack using Kolla ansible, the vm instances are too slow I'm using one node as controller and two nodes for compute Nodes have 64GB ram and two intel xeon e5 2660 CPUs.

4 3

Forum Brainstorming & Committee Setup
by Kendall Nelson 14 Mar '22

14 Mar '22

Hello Everyone! As the OpenInfra Summit approaches, so does the Forum! We would love 1 volunteer from the community for the Forum Selection Committee. Ideally, the volunteer would already be serving in some capacity in a governance role for your project. Please reach out to knelson(a)openinfra.dev if you're interested. Volunteers should respond on or before April 8, 2022. In addition to calling for volunteers for the Forum selection committee, this email kicks off the brainstorming period before the CFP tool opens for formal Forum submissions. The categories for brainstorming etherpads have already been setup here[1]. Please add your etherpads and ideas there! The CFP tool will open on March 21st and will close April 8th. For information on the upcoming Summit[2]. For more information on the Forum[3]. Thanks! - Kendall Nelson (diablo_rojo) [1] Forum 2022 Wiki: https://wiki.openstack.org/wiki/Forum/Berlin2022 [2] OpenInfra Summit Site: https://openinfra.dev/summit [3] General Forum Wiki: https://wiki.openstack.org/wiki/Forum

1 0

[charms] Can we update the Python runtimes for the 'openstack-python3-charms-jobs' template?
by Stephen Finucane 14 Mar '22

14 Mar '22

Related to the "Independent release jobs are still using old release job templates" email I just sent [1], I've proposed a change [2] that would modify the 'openstack-python3-charms-jobs' job template so that it mimics the behaviour of the proposed 'openstack-python3-jobs' template. That is, the 'openstack- python3-charms-jobs' release will now be updated at the start of each new release to test against the same runtimes proposed for this new release. However, frickler has noted that the use of older runtimes for the charms jobs may in fact be intentional. Could someone from the charms team please weigh in on [2]. If this is in fact intentional, it would be good to add a note to the job template indicating this fact to prevent people like me breaking it in the future :) Cheers, Stephen [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027676.ht… [2] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/833330/1

2 1

Opensearch service reinstallation - opensearch.logs.openstack.org
by Daniel Pawlik 14 Mar '22

14 Mar '22

Hi, We plan to reinstall the Opensearch (opensearch.logs.openstack.org) service on Saturday, 2021-03-12. The service will be unavailable for several hours. If someone has any concerns, please contact me. Regards, Dan

1 1

virt-v2v conversion error
by KK CHN 14 Mar '22

14 Mar '22

Hi , I am performing a migration of Windows 10 VM running on HyperV to OpenStack setup with Ussuri(qemu KVM) on Debian 10 nodes. I got the Windows VM exported disks as disk1.VHDX and disk2.avhdx files from my WIndows cloud Vendor. 1. As my understanding I need to convert these VM disks from HyperV using virt-v2v tool. ( Could someone explain what is the relevance of this step and is it mandatory for importing it to my Ussuri Openstack cloud which uses qemu-kvm hypervisor. 2. As I've read I tried to convert this disk1.VHDX file with the follwoing step #virt-v2v -i disk disk1.VHDX -o local -os /home/cloud this step fails with virt-v2v error : // Files system was mounted read only . even though we sked for it to be mounted read-write. This usually means that file system was not cleanly unmounted. Possible causes include trying to convert a guest which is running. or use Windows hibernation or Fast Restart . Original error message touch: open /8imepyi7: Read only file system ... Can anyone guide what causes this error and Is there a fix or work around available to solve this error in vrit-v2v conversion ? Thanks in advance krish

1 0

nvidia gpu
by Vikarna Tathe 12 Mar '22

12 Mar '22

Hello All, Can somebody help me with the procedure for GPU integration with openstack wallaby, Ubuntu 20.04. Below are the card details: da:00.0 VGA compatible controller: NVIDIA Corporation TU102GL [Quadro RTX 6000/8000] Vikarna

2 2

[all][tc] What's happening in Technical Committee: summary Mar 11th, 21: Reading: 10 min
by Ghanshyam Mann 11 Mar '22

11 Mar '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Mar 10th. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-03-10-15.00.log.html * Next week's meeting is on Mar 17th Thursday 15:00 UTC, feel free to add the topic on the agenda[1] by Mar 16th. Please note about the daylight time shift in US TZ happening this Sunday. 2. What we completed this week: ========================= * Release identification and release name ----------------------------------------------- Release naming/identification new proposal is merged[2]. Currently, it is adding the number in <year>.<1st or 2nd release of that year> format along with the release name. Please check the release naming process page for complete detail[3] * Add sushy-oem-idrac as Hardware Vendor SIG owned[4] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[5]. 3 out of 9 items are completed and many are in progress. Open Reviews ----------------- * Six open reviews for ongoing activities[6]. Direction on running FIPs goal/jobs ------------------------------------------ As you might have seen the FIPs work from Ade_lee and adding FIPs jobs in the check/gate pipeline which is not stable at this stage. We in TC meeting along with Ade_lee discussed the direction on making jobs stable and until then how we want to run jobs so that we do not overload infra resources with a lot of non-voting/unstable jobs. We agreed to run those as periodic (and experimental to trigger them manually) to make/check their stability [7]. Based on the job run data, in PTG we will discuss further on adding them as voting and selecting it as a goal. Zed cycle Leaderless projects ---------------------------------- We have 14 PTL assignments merged and 2 are in progress(Trove and Zaqar) [8]. With that only one project left to assign a leader (Adjutant) and we will wait until the end of March for Braden to get permission to maintain it[9]. PTG Preparation -------------------- TC slots are selected for coming PTG[10], please continue adding the topics in etherpad[11]. * Monday 14 - 16 UTC (TC + PTL for 2 hrs ) * Thursday 13-17 UTC (TC discussion for 4 hrs) * Friday 13-17 UTC (TC discussion for 4 hrs ) Dropping tags framework ------------------------------ part1 of this is merged[12], part-2 of updating release script and other tags migration is under-progress. TC position on release cadence ------------------------------------- Dan has sent the overview and things changed as per the new release model [13]. The next plan is: * Dan will explain/discuss it further in TC+PTL sessions on Monday [14]. * Projects can discuss it (from their project point of view) in their PTG sessions and collect the queries if any. * Join TC sessions on Thursday/Friday (I will schedule and update the exact time slot) to discuss those queries or plan the remaining work. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[15]. Project updates ------------------- * None for this week. 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[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [17] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/829563 [3] https://governance.openstack.org/tc/reference/release-naming.html [4] https://review.opendev.org/c/openstack/governance/+/832264 [5] https://etherpad.opendev.org/p/tc-yoga-tracker [6] https://review.opendev.org/q/projects:openstack/governance+status:open [7] https://meetings.opendev.org/meetings/tc/2022/tc.2022-03-10-15.00.log.html#… [8] https://etherpad.opendev.org/p/zed-leaderless [9] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [10] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027584.ht… [11] https://etherpad.opendev.org/p/tc-zed-ptg [12] https://review.opendev.org/c/openstack/governance/+/822900 [13] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027639.ht… [14] https://etherpad.opendev.org/p/tc-ptl-interaction-zed [15] https://etherpad.opendev.org/p/zuul-config-error-openstack [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[release] Release countdown for week R-2, Mar 14 - 18
by Előd Illés 11 Mar '22

11 Mar '22

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for all the Yoga deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Actions ------- Early in the week, the release team will be proposing stable/yoga branch creation for all deliverables that have not branched yet, using the latest available Yoga release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/yoga branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/yoga branch before releasing out of the stable/yoga branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for Zed development, though the focus should still be on finishing up Yoga until the final release. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final Yoga release. Finally, now is a good time to finalize release notes, if it is not done yet. In particular, consider adding any relevant "prelude" content. Release notes are targeted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the Yoga version of your project. Upcoming Deadlines & Dates -------------------------- Final RC deadline: March 24th, 2022 (R-1 week) Final Yoga release: March 30th, 2022 Next PTG: April 4 - 8, 2022 (virtual) Előd Illés irc: elodilles

3 2