Overlay network for Juju LXC containers?

[Andrew McDermott]

Hi Patrik,

There is no current solution for Digital Ocean.

On AWS a container gets an IP address on the lxcbr0 network. We then add
iptable rules that make the container visible on the hosts network - the
host can see the container, the container can see the host.

On MAAS (for 16.04) we create a bridge per NIC and the container, depending
on how many interfaces are configured, will get an address on each subnet.
Please note that all of this is currently work in progress and is only
available on a feature branch (maas-spaces).

AWS and MAAS do not use the fan.

We are currently working on Juju's network model to make it easier to do
what you are asking for. My colleague Dimiter Naydenov has been blogging
about this recently:


https://insights.ubuntu.com/2015/11/08/deploying-openstack-on-maas-1-9-with-juju/

So for DO we don't have any transparent Juju solution for you, but we are
actively developing the capabilities of Juju's networking model.

HTH

On 6 January 2016 at 17:29, Patrik Karisch <patrik.karisch at gmail.com> wrote:

> Hi,
>
> I'm wondering what Juju does to make services deployed into LXC containers
> on different machines reachable within the whole environment? Does it use
> Fan or something?
>
> Currently I'm trying Juju on Digital Ocean, where a machine has only one
> private IP and can't get more. I don't have the budget to run every service
> in a new machine, so they must reside in containers on a limited bunch of
> machines.
>
> Best regards
> Patrik
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>


-- 
Andrew McDermott <andrew.mcdermott at canonical.com>
Juju Core Sapphire team <http://juju.ubuntu.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20160107/38de05c5/attachment.html>