[Openstack-operators] Reaching VXLAN tenant networks from outside (without floating IPs)

Erik McCormick emccormick at cirrusseven.com
Tue Jul 19 01:47:42 UTC 2016


I've recently gone through provisioning Midonet (open source version) with
the intent of tying their vxlan gateway in with my Cumulus switches. This
approach should be usable with pretty much any vxlan-capable switch. If
you're open to straying from the well travelled OVS/LB path, you may want
to consider checking it out

-Erik

On Jul 18, 2016 8:51 PM, "Gustavo Randich" <gustavo.randich at gmail.com>
wrote:

> Right Blair, we've considered provider vlans, but we wanted to leverage
> the low cost of private IPs (from a hardware switch perspective), taking
> into account that we'll have thousands of VMs not needing external access.
>
> On Sunday, 17 July 2016, Blair Bethwaite <blair.bethwaite at gmail.com>
> wrote:
>
>> On 30 June 2016 at 05:17, Gustavo Randich <gustavo.randich at gmail.com>
>> wrote:
>> >
>> > - other?
>>
>> FWIW, the other approach that might be suitable (depending on your
>> project/tenant isolation requirements) is simply using a flat provider
>> network (or networks, i.e., VLAN per project) within your existing
>> managed private address space, then you have no requirement for a
>> Neutron router. This model seems a lot easier to visualise when
>> starting out with Neutron and can side-step a lot of integration
>> problems.
>>
>> --
>> Cheers,
>> ~Blairo
>>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160718/d484a51a/attachment.html>


More information about the OpenStack-operators mailing list