December 2021 - openstack-discuss

[neutron] Routing fake "floating IPs" of VMs running inside VMs of an OpenStack
by Thomas Goirand 17 Dec '21

17 Dec '21

Hi, I've been designing a CI for OCI [1] to make it more robust and easier to contribute. After a week and a half, I've been able to make OCI deploy itself in an OpenStack itself. OCI itself pops with a public IP I can reach from the outside, and it setups OpenStack inside OpenStack VMs on a flat, private subnet (currently 192.168.100.0/24). This works pretty well, I have a fully working setup, and the deployment is completely automated. This even works without admin credentials, so all one needs, is a non-privileged account in any OpenStack. However, at this point, I'd like to setup the network for VMs inside the VMs. And that's where it becomes tricky. The VM that runs tempest will need to reach the floating IPs of the VMs inside the VMs that are running nova-compute, in order to do ssh tests. How can I do that? Is this even possible? Cheers, Thomas Goirand (zigo) [1] https://salsa.debian.org/openstack-team/debian/openstack-cluster-installer

2 1

[neutron][ovn] VLAN Ranges
by Ammad Syed 17 Dec '21

17 Dec '21

Hi, I am using neutron xena release with OVN. I have currently defined the vlan range "network_vlan_ranges = vlannet1:3500:3600" in ml2_conf.ini. I have set bridge mapping via ovs with the below command. ovs-vsctl set open . external-ids:ovn-bridge-mappings=vlannet1:br-vlan Now I have to add a new vlan range. Can anyone confirm the syntax of ml2_conf.ini and bridge mapping. network_vlan_ranges = vlannet1:3500:3600,vlannet2:300:400 ovs-vsctl set open . external-ids:ovn-bridge-mappings=vlannet1:br-vlan,vlannet2:br-vlan Need to confirm the correct way to add new vlan range if the server is currently live ? Can we use the same bridge with two different mapping i.e vlannet1 and vlannet2 ? Ammad

2 3

[blazar] Next IRC meeting cancelled
by Pierre Riteau 17 Dec '21

17 Dec '21

Hello, As decided during yesterday's meeting, we are cancelling the Blazar IRC meeting scheduled for December 30. The next meeting will be on January 13. Merry Christmas and Happy New Year! Best wishes, Pierre Riteau (priteau)

1 0

[horizon] Cancelling next two weekly meetings
by vishal manchanda 17 Dec '21

17 Dec '21

Hello Team, As agreed, during the last weekly meeting, we are canceling our weekly meeting on 22nd and 29th December. The next weekly meeting will be on 5th December. Happy holidays and happy new year in advance! Thanks & Regards, Vishal Manchanda

1 0

[charms] review abandonment policy
by James Page 17 Dec '21

17 Dec '21

Hi Charms Contributors As part of this cycles work to put in more proactive general maintenance of the Gerrit review queue for the OpenStack Charms projects we have introduced an abandonment policy for reviews: https://docs.openstack.org/charm-guide/latest/community/rotas.html#abandonm… Pruning the set of open reviews on a regular basis against this policy will help reviewers focus on active reviews. We'll start doing this in January - you can follow the blocked/failing links in the charm-guide policy section to see which reviews will be abandoned at any given point in time. Cheers James

1 0

[neutron] missing dhcp ports after reboot and neutron-ovs-cleanup
by Kamil Madáč 16 Dec '21

16 Dec '21

Hello We have deployed Victoria release with kolla-ansible (openvswitch neutron driver), and after the reboot of control nodes we are experiencing issues with dhcp on some networks. I found out that there were missing dhcp tap interfaces in br-int openvswitch. After restart of dhcp agetn and openvswitch agent, interface was added to br-int and dhcp works again in that network. I found bug from 2016 (https://bugs.launchpad.net/kolla/+bug/1617188), that there is a script neutron-ovs-cleanup (it is in each neutron docker container), which should be run after reboot of dhcp/L3 nodes otherwise issues with dhcp/metadata/l3 functionalities could arise. I do not see mentioned this in kolla documentation, bug is quite old and expired, so I would like to ask, is that still valid and should it be run manually after each reboot of dhcp/L3 node? If yes, what is best what how to achieve it when docker starts all container automatically after reboot. Should I stop neutron containers, run neutron-ovs-cleanup and start them again? Kamil Madáč Slovensko IT a.s.

2 1

[neutron] No more meetings in 2021 :-)
by Lajos Katona 16 Dec '21

16 Dec '21

Hi Neutrinos! Due to the holiday season let's cancel the next 2 Team and Drivers meeting. See you all in January, and have great Holidays! Lajos Katona (lajoskatona)

1 0

[nova] instance device_metadata
by Arnaud Morin 16 Dec '21

16 Dec '21

Hey all, How is filled the device_metadata in instance_extra db? It's empty for my instances. It's supposed to be accessible then through metadata api, and contains at least network and block device info, but it's empty here. Thanks for any hint!

1 1

[manila] No IRC meeting on 30th Dec 2021
by Goutham Pacha Ravi 16 Dec '21

16 Dec '21

Hi Zorillas, As we discussed during our meeting today [1], we'll have our last IRC meeting for 2021 next week (23rd Dec 2021 at 1500 UTC) in OFTC's #openstack-meeting-alt. We'll skip the meeting on 30th Dec 2021 due to the year end holidays. As always, please feel free to add to the meeting agenda here: https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting Thanks, Goutham Pacha Ravi [1] https://meetings.opendev.org/meetings/manila/2021/manila.2021-12-16-15.01.l…

1 0

[all][tc][policy] Canceling policy popup team next meeting
by Ghanshyam Mann 16 Dec '21

16 Dec '21

Hello Everyone, Due to holiday weeks, we are cancelling the policy pop-up next meeting scheduled for 30th Dec. We will continue this biweekly meeting from 13th Jan. https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… -gmann

1 0