Hi John,
What you are describing is a perfectly valid and common scenario. The
segmentation IDs don't really come out of thin air, though. They are defined as
a range of IDs in the ML2 or openvswitch agent configuration file depending on
the version of OpenStack. There could be a performance penalty with VXLAN over
VLAN, depending on your NIC and MTU size, and other caveats I won't go in to.
But, you gain some flexibility.
At some point, though, you will need at least one VLAN or untagged (flat)
network as your provider network. That will need to be trunked to the nodes
hosting the L3 agent(s), and possibly all nodes in the case of DVR.
James
From: John van Ommen
Sent: Wednesday, May 4, 2016 9:11 PM
To: openstack@lists.openstack.org
Subject: [Openstack] Multi-Node OpenStack with no VLANs
I am working on an OpenStack deployment where my customer's VLANs do
not appeared to be configured properly.
I am in a time crunch and I'm looking for a way to work around this.
Would it be possible to use VxLAN for my guest traffic, and basically
pick the subnets arbitrarily?
I am using OpenStack Kilo with KVM for my compute nodes, and I'm using
OVS for switching. It *seems* like I could pick the networks "out of
thin air" with VxLAN, and let OVS deal with the tags, instead of using
VLAN and have the customer's switches deal with the tags.
Will that work?
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
