Re: [Openstack-operators] Reaching VXLAN tenant networks from outside (without floating IPs)
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" 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 > wrote: > >> On 30 June 2016 at 05:17, Gustavo Randich >> 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@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Reaching VXLAN tenant networks from outside (without floating IPs)
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 wrote: > On 30 June 2016 at 05:17, Gustavo Randich > 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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [OSOps] Bi-Weekly Meeting - This coming Wednesday 7/20/2016
Everyone, The agenda is up for this week's OSOps meeting. You can find the agenda here: https://etherpad.openstack.org/p/osops-irc-meeting-20160720 I hope to have some ideas on how OSOps can help and how we can get more people to participate. The meeting will start at 1900 UTC in #openstack-meeting-4 Thanks --Joe ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
