This is a lot cleaner and nicer! It would be nice to upstream it!
On Fri, Nov 13, 2015 at 2:11 PM, Ethan J. Jackson
wrote:
> Hi All,
>
> Melvin made a much better version of this which he's uploaded here:
> https://github.com/NetSys/ovs-containers
>
> In particular, it creates a container per da
Hi All,
Melvin made a much better version of this which he's uploaded here:
https://github.com/NetSys/ovs-containers
In particular, it creates a container per daemon, and greatly simplifies
boot using a docker script. Any interest in upstreaming this? I'd be
happy to submit a patch.
Ethan
On
Agreed on all points. This was somewhat of an MVP to get us going, but it
definitely could be improved.
Another thing we should probably do is pre-create an empty ovsdb rather
than doing it with ovsdb-tool on boot.
Anyways, this works well enough from us, so we may improve it but it's
unlikely i
Thanks Ethan for the initiative.
A few comments:
1. Is there any reason you guys chose to keep ovsdb-server and
ovs-vswitchd into separate containers?
I think having atleast the ovsdb-server and ovs-vswitchd together in
the same container may make things easy.
2. You can also run your containers
hi ethan.
sure it should work.
Just some thoughts from the isolation perspective.
On Wed, Nov 11, 2015 at 10:19 AM, Ethan J. Jackson
wrote:
> Well, since OVS is in upstream linux, all you really need are ovsdb-server
> and ovs-vswitchd to get up and running. It can go ahead and connect t
Well, since OVS is in upstream linux, all you really need are ovsdb-server
and ovs-vswitchd to get up and running. It can go ahead and connect to the
kernel module that's already there and forward packets. At least this has
worked for us with CoreOS without any additional modification.
Getting
thanks ethan!
seems we've put the ovsdb-server and ovs-vswitchd (user-face) part into a
container, which are basically userspace apps.
But it still requires host support on the datapath module.
more interesting is to put the whole ovs, including the datapath into
container.
there's some userspace o
Hi everyone,
We're doing a project here at Berkeley which requires OVS/Docker
integration on CoreOS. Melvin Walls (an undergrad working with me here)
did the heavy lifting to get that setup, so I thought I'd forward it to the
list in case there's interest.
The first (and most important) step, is
