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 c
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,
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,
ndich <*gustavo.rand...@gmail.com*
> >
> To:Mike Spreitzer/Watson/IBM@IBMUS
> Cc: "*openst...@lists.openstack.org*
> " <*openst...@lists.openstack.org*
> >, "
> *openstack-operators@lists.openstack.org*
> " <
> *openstack-operators@lists.openst
: "openst...@lists.openstack.org" ,
"openstack-operators@lists.openstack.org"
Date: 07/15/2016 01:44 PM
Subject: Re: [Openstack-operators] Reaching VXLAN tenant networks
from outside (without floating IPs)
Hi, this approach worked fine, except in the case when V
Gustavo Randich
> To:Mike Spreitzer/Watson/IBM@IBMUS
> Cc:"openst...@lists.openstack.org" ,
> "openstack-operators@lists.openstack.org" <
> openstack-operators@lists.openstack.org>
> Date:06/3
nstack.org" ,
"openstack-operators@lists.openstack.org"
Date: 06/30/2016 11:25 AM
Subject: Re: [Openstack-operators] Reaching VXLAN tenant networks
from outside (without floating IPs)
Mike, as far as I know those routers allow only outgoing traffic, i.e. VM
can see extern
On Wed, Jun 29, 2016 at 1:17 PM, Gustavo Randich
wrote:
> Hi operators...
>
> Transitioning from nova-network to Neutron (Mitaka), one of the key issues
> we are facing is how to reach VMs in VXLAN tenant networks without using
> precious floating IPs.
>
> Things that are outside Neutron in our ca
Maybe you can have something like :
https://bugs.launchpad.net/neutron/+bug/1175211
On Thu, Jun 30, 2016 at 8:54 PM, Gustavo Randich
wrote:
> Mike, as far as I know those routers allow only outgoing traffic, i.e. VM
> can see external networks, but those external networks cannot connect to VM
> i
Mike, as far as I know those routers allow only outgoing traffic, i.e. VM
can see external networks, but those external networks cannot connect to VM
if it doesn't have a FIP, am I right?
Thanks!
Gustavo
On Wed, Jun 29, 2016 at 7:24 PM, Mike Spreitzer wrote:
> Gustavo Randich wrote on 06/29/20
Gustavo Randich wrote on 06/29/2016 03:17:54
PM:
> Hi operators...
>
> Transitioning from nova-network to Neutron (Mitaka), one of the key
> issues we are facing is how to reach VMs in VXLAN tenant networks
> without using precious floating IPs.
>
> Things that are outside Neutron in our cas
Hi operators...
Transitioning from nova-network to Neutron (Mitaka), one of the key issues
we are facing is how to reach VMs in VXLAN tenant networks without using
precious floating IPs.
Things that are outside Neutron in our case are:
- in-house made application orchestrator: needs SSH access t
12 matches
Mail list logo
