juju-br0

[Merlijn Sebrechts]

This Charm
<https://github.com/galgalesh/tengu-charms/tree/master/charms/trusty/lxc-networking>
is a horrible hack that creates the lxcbr0 interface on a host and bridges
it to the given network. You can use this to crudely change networking of
lxc containers by first deploying the charm to the host itself and then
deploying charms to lxc containers. In the future I'll also be looking into
changing default routes on the lxc container. Let me know if you can use
this. I could put it in its own repository, put it in the Charm store and
accept pull requests if there is interest for it.

@Andrew: I'm using lxc containers in the manual provider and manage their
networks using the above Charm. I'm very interested in more "official"
support for this.

2015-12-02 8:48 GMT+01:00 Andrew McDermott <andrew.mcdermott at canonical.com>:

> The short answer is not at the moment. However, we were discussing this
> only yesterday (by chance!) and we plan to create a bridge per NIC.
>
> On 2 December 2015 at 00:38, Pshem Kowalczyk <pshem.k at gmail.com> wrote:
>
>> Hi,
>>
>> Currently all my LXC containers are joined to juju-br0, which also
>> contains first physical interface (in my case eth0). Is there a way to
>> deploy those LXC with more complicated networking setup (for example
>> bridging with eth1, or having access to multiple bridges)? If so - how can
>> that be achieved?
>>
>> kind regards
>> Pshem
>>
>>
>> --
>> 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>
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20151202/0c6dede4/attachment.html>