If I understood you properly, I think you could have different ways to achieve it:
* Use an external device (switch) to bridge VLAN and VXLAN * Similar to the previous point, if you are using OVS as ML2 mech driver, on the networks nodes you could setup the same logic there (br-ex bridge) * Creating different L3 agents (one per VLXAN) and using "gateway_external_network_id" Anyway I have never tried VXLAN as external networks ... 2015-11-20 8:58 GMT+01:00 Amir Huskić <amir.hus...@gmail.com>: > Hello Jose, > > is it possible to do it also with vxlan instead vlan? I would like to > enable vxlan tunnel between tenants VMs (their external network) and > another LAN vxlan segment. > Thank you. > Regards, > Amir > > On Thu, Nov 19, 2015 at 12:38 PM, José Riguera López <jrigu...@gmail.com> > wrote: > >> >> You can, just tell neutron you want to have another external network. >> Lets say VLAN=300 is 192.168.66. <http://192.168.66.0/24>0/24 >> >> # Creating the external network type VLAN with VLAND ID == 300 >> # The name of the provider physical_network "ext" is mapped to a physical >> # device on the ML2 configuration file of each network node >> >> neutron net-create \ >> --provider:network_type vlan \ >> --provider:physical_network ext \ >> --router:external \ >> --provider:segmentation_id 300 \ >> ext_net_300 >> >> # Define the IP range for floating IPs available on that network, the >> gateway, >> # DNS nameservers and CIDR, and no DHCP (in this case) >> neutron subnet-create \ >> --allocation-pool start=192.168.66. <http://192.168.66.0/24>10,end=1 >> 92.168.66. <http://192.168.66.0/24>255 \ >> --ip-version 4 \ >> --gateway 192.168.88.1 \ >> --disable-dhcp \ >> --dns-nameserver 8.8.8.8 \ >> --name ext_net_300_subnet \ >> ext_net_300 192.168.66. <http://192.168.66.0/24>0/24 >> >> Then the users will see 2 (or more) floating ip pools ... >> >> Regards, >> >> >> >> 2015-11-19 11:18 GMT+01:00 Ray Sun <xiaoq...@gmail.com>: >> >>> I want to setup multiple external networks, but I don't know how to make >>> this works. >>> >>> Here's my user requirements: >>> There are two departments want to use my cloud, but as history problem, >>> they wants their VMs to use original IP range. DepA wants to use floating >>> ip in 192.168.66.0/24, DepB wants to use floating ip in 192.168.77.0/24. >>> >>> I can create multiple subnets in my external network. But I am not quite >>> sure if this can work in OpenStack. In my network environment, >>> 192.168.66.0/24 and 192.168.77.0/24 are two VLANs. >>> >>> >>> Anybody know how to implement this kind of scenarios? If this is not >>> possible, how can I design my architecture to meet the requirements. >>> >>> Thanks. >>> >>> Best Regards >>> -- Ray >>> >>> _______________________________________________ >>> 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 >>> >>> >> >> >> -- >> José Riguera López <jrigu...@gmail.com> >> >> _______________________________________________ >> 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 >> >> > -- José Riguera López <jrigu...@gmail.com>
_______________________________________________ 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
