Open Stack

Felipe;

A lot of this will depend on how you have Neutron configured.  We use OpenVSwitch.  For OpenVSwitch you want a completely unconfigured interface, for VLANs.

If you haven't looked at Server World's tutorial for OpenStack, I would suggest you do so.  They can be found here:
https://www.server-world.info/en/note?os=Ubuntu_20.04&p=openstack_xena2&f=6
https://www.server-world.info/en/note?os=CentOS_Stream_8&p=openstack_xena2&f=6

Pay particular attention to the names br-eth1 and physnet1, and where and how they are used.  You are likely going to need to reference the "Configure Neutron #2" page from the tutorial to understand the whole configuration, as these assume #1 and #2 have been completed (#1 walks through how to setup the support services).

The tutorials are for VXLAN, but are modifiable to be VLAN.

In particular;
[ml2_type_vxlan]
vni_ranges = 1:1000

becomes:
[ml2_type_vlan]
network_vlan_ranges = physnet1:1:1000

For you, I believe that last line would be:
network_vlan_ranges = physnet1:684:684

What I can't help you with is how this interacts with PackStack.

Thank you,

Dominic L. Hilsbos, MBA
Vice President – Information Technology
Perform Air International Inc.
DHilsbos at PerformAir.com
www.PerformAir.com



From: Felipe Mogollon [mailto:fmogollon at vicomtech.org] 
Sent: Wednesday, February 2, 2022 12:44 AM
To: Dominic Hilsbos
Subject: Re: Openstack VLAN provider Network

Do you mean to remove only ip address from VLAN's eth configuration or removing all VLAN's eth configuration?

Thanks

Felipe

On Wed, Feb 2, 2022 at 12:21 AM <DHilsbos at performair.com> wrote:
Felipe;

I had significant problems with this as well, when I was first setting up our cluster.

The first thing to recognize is that the network type is from the stand point of the host (more specifically from the network services host, and the neutron compute hosts), not the network itself.  Your VLAN network is actually a physical network (from the standpoint of the host), because it is bound to a physical interface.

If you want to actually use it as a vlan type; a) remove the IP address(es) from the interface(s) of the network and compute host(s), and b) properly configure ml2, or an equivalent plugin.

Thank you,

Dominic L. Hilsbos, MBA
Vice President – Information Technology
Perform Air International Inc.
DHilsbos at PerformAir.com
www.PerformAir.com


From: Felipe Mogollon [mailto:fmogollon at vicomtech.org] 
Sent: Tuesday, February 1, 2022 7:49 AM
To: openstack-discuss
Subject: Openstack VLAN provider Network

I have deployed an OpenStack Victoria using packstack in a Centos 8 Stream machine.
I have 3 NIC interfaces that are configured in the following way
eno1 -> VLAN 684 10.15.0.0/16 
eno2 -> local network 192.168.235.0/24
eno3 -> local network 192.168.15.0/24
VLAN and local networks are working fine outside Openstack.
I have deployed Openstack using packstack and local networks work fine and I can deploy instances inside openstack that get floating ips from those ranges without problem and I can ping to them.
The problem is with VLAN network, I can deploy instances and I get floating ips from VLAN network range but I can't ping them.
My packstack answer file is https://pastebin.com/GEqspMWu
I have created VLAN network using following commands:
neutron net-create vlan_network --provider:network_type vlan --provider:physical_network vlan  --router:external=True --shared --provider:segmentation_id=684

neutron subnet-create --name vlan_subnet --enable_dhcp=False --allocation-pool=start=10.15.11.103,end=10.15.11.113 --gateway=10.15.11.1 vlan_network 10.15.11.0/24
Any ideas?


-- 


Juan Felipe Mogollón Rodríguez
Researcher | Investigador

fmogollon at vicomtech.org
+[34] 943 30 92 30
Digital Media

  

member of: 

La información que contiene este mensaje y sus adjuntos son confidenciales y están dirigidos exclusivamente a sus destinatarios. Si recibe este mensaje por error, se ruega nos lo comunique y proceda a su borrado.

The information contained in this electronic message is intended only for the personal and confidential use of the recipients designated in the original message. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer.