Hey Beedy, Since nobody tells you anything, this works on most clouds so long as your units show up in the same subnet. The fan is mathematically calculated, so it won't really work well on the default VPC in say AWS.
But if you're deploying into a VPC, and your container network bridge is provided by the fan, you get functional cross host networking out of the box. (FYI, if you install the docker.io package, it comes pre-configured with the fan from xenial forward... possibly wily?) All the best, Charles On Tue, Aug 23, 2016 at 8:45 AM James Beedy <[email protected]> wrote: > What!? This is awesome! No one ever tells me these things. Thanks for > looping me in, Tom! > > On Aug 23, 2016, at 6:25 AM, Tom Barber <[email protected]> wrote: > > Possibly something like... https://wiki.ubuntu.com/FanNetworking ? :) > > -------------- > > Director Meteorite.bi - Saiku Analytics Founder > Tel: +44(0)5603641316 > > (Thanks to the Saiku community we reached our Kickstart > <http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/> > goal, but you can always help by sponsoring the project > <http://www.meteorite.bi/products/saiku/sponsorship>) > > On 23 August 2016 at 14:23, James Beedy <[email protected]> wrote: > >> 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 >> >> > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > -- Juju Charmer Canonical Group Ltd. Ubuntu - Linux for human beings | www.ubuntu.com Juju - The fastest way to model your service | www.jujucharms.com
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
