Mark, Thanks for the reply! Just to make sure I'm picking up what you are laying down, are you implying that Juju will soon support host <-> host container networking by supplying its own provider agnostic network fabric?
~James > On Aug 23, 2016, at 4:29 AM, Mark Shuttleworth <[email protected]> wrote: > > > LXC/LXD should work everywhere, but *networking* to those containers is > tricky. There is a dedicated team working on that problem, and we expect to > ahve the ability to make and use LXC containers universally, soon. > > The remaining constraint will be that some charms try to modify their guest > kernel, and that of course will be prevented in a container. > > Mark > >> On 22/08/16 22:03, James Beedy wrote: >> Team, >> >> Question: What providers can Juju deploy LXD to? >> >> Answer: All of them. >> >> Question: What providers support Juju deployed LXD (juju deploy >> <application> --to lxd:0)? >> >> Answer: MAAS >> >> >> Problem: Juju can deploy LXD to all of the providers, but Juju can >> **REALLY** only provision LXD on MAAS. I get the impression that Juju is >> broken when I deploy applications to lxd on any provider other than MAAS. >> >> Proposed Solution: Disable `juju deploy <application> --to lxd:0` on >> providers which it is not supported. >> >> >> Thoughts? >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
