Hi Jonathan,
There's also Calico [1,2], which in its simplest form (and as currently
implemented):
- uses just IP routing (v4 and/or v6) to connect workloads (VMs /
containers / pods / bare metal)
- has a security model that works across workloads hosted in different
clouds, and so can specify
In regards to your last comment, that "it would be great for tenants
to be able to setup connections into AWS", HP CSA comes close to doing
that:
http://www8.hp.com/us/en/software-solutions/cloud-service-automation/
It's not *exactly* what you're looking for, you wouldn't be using the
OpenStack
On Mon, Oct 3, 2016 at 11:52 AM, Jonathan Proulx wrote:
>
> So my sense from responses so far:
>
> No one is doing unified SDN solutions across clouds and no one really
> wants to.
I do want to (but am not doing). When I worked at a public cloud based
on openstack we
Excerpts from Jonathan Proulx's message of 2016-10-03 13:52:42 -0400:
>
> So my sense from responses so far:
>
> No one is doing unified SDN solutions across clouds and no one really
> wants to.
>
> Consensus is just treat each network island like another remote DC and
> use normal VPN type
So my sense from responses so far:
No one is doing unified SDN solutions across clouds and no one really
wants to.
Consensus is just treat each network island like another remote DC and
use normal VPN type stuff to glue them together.
( nod to http://romana.io an interesting looking network
I think the best general way to view networking in cloud is WAN vs Cloud
Lan.
There's almost always an edge routing env for your cloud environments (
whether they be by region or by policy or by tim is an angry dude and you
don't touch his instances ).
Everything beyond that edge is a WAN
This can also be done with IPv4 address as well. Not quite the flexibility
that comes with v6, but workable for all but the very largest environments.
This is the approach that is embodied in the Romana (http://romana.io/) project
(I am part of this effort).
If you run all your OpenStack VMs on
Excerpts from Jonathan Proulx's message of 2016-10-03 11:16:03 -0400:
> On Sat, Oct 01, 2016 at 02:39:38PM -0700, Clint Byrum wrote:
>
> :I know it's hard to believe, but this world was foretold long ago and
> :what you want requires no special equipment or changes to OpenStack,
> :just
On Sat, Oct 01, 2016 at 02:39:38PM -0700, Clint Byrum wrote:
:I know it's hard to believe, but this world was foretold long ago and
:what you want requires no special equipment or changes to OpenStack,
:just will-power. You can achieve it now if you can use operating system
:versions published
Excerpts from Jonathan Proulx's message of 2016-09-30 10:15:26 -0400:
>
> Starting to think refactoring my SDN world (currently just neutron
> ml2/ovs inside OpenStack) in preparation for maybe finally lighting up
> that second Region I've been threatening for the past year...
>
> Networking is
On Fri, Sep 30, 2016 at 8:15 AM, Jonathan Proulx wrote:
>
> Starting to think refactoring my SDN world (currently just neutron
> ml2/ovs inside OpenStack) in preparation for maybe finally lighting up
> that second Region I've been threatening for the past year...
>
>
Starting to think refactoring my SDN world (currently just neutron
ml2/ovs inside OpenStack) in preparation for maybe finally lighting up
that second Region I've been threatening for the past year...
Networking is always the hardest design challeng. Has anyone seen my
unicorn? I dream of
12 matches
Mail list logo