Open Stack

Hi,


If you would have both VLAN and VxLAN types of provider networks, it is possible to accomplish that.


First of all, you need to provide the right configuration in the file of "openvswitch_agent.ini" and "ml2_conf.ini". Then with two NICs (ports), connect them to the different bridges (one for VLAN (br-vlan) and the other for VxLAN (br-tun)), respectively. At this stage, you should have two types of provider networks, one for VLAN and the other for VxLAN.


Br,
Chao
 
------------------ Original ------------------
From:  "John van Ommen"<john.vanommen at gmail.com>;
Date:  Fri, Feb 26, 2016 03:46 AM
To:  "Neil Jerram"<Neil.Jerram at metaswitch.com>; 
Cc:  "openstack at lists.openstack.org"<openstack at lists.openstack.org>; 
Subject:  Re: [Openstack] One Interface with VLAN and one with VxLAN

 
I want to have VLAN provider networks for some customers.

I currently have my cloud configured for VxLAN, and I'm not able to create a VLAN provider network.





On Thu, Feb 25, 2016 at 11:24 AM, Neil Jerram <Neil.Jerram at metaswitch.com> wrote:
On 25/02/16 19:08, John van Ommen wrote:
 > Is it possible to have one interface configured with VLAN and another
 > with VxLAN?
 
 Do you mean for tenant networks, or for provider networks?
 
 I believe it's possible for provider networks, but not for tenant. [1]
 
 [1]
 http://lists.openstack.org/pipermail/openstack-dev/2016-January/084744.html
 
 > I'm in a situation where I have some customers who want to do VxLAN, but
 > I also have some legacy customers that need VLAN.
 
 Out of interest, why do the legacy customers need VLAN specifically?
 
 > To complicate matters further, my compute nodes are in vCenter. I
 > understand that KVM can do VxLAN and VLAN using DVR. My vCenter compute
 > nodes are plugged into a OVSVapp virtual switch.
 
 I'm afraid I have no idea about this dimension!
 
 Regards,
         Neil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160226/181c628b/attachment.html>