On Fri, Nov 27, 2015 at 9:37 AM Aaron Bentley <aaron.bent...@canonical.com> wrote:
> # juju-core 1.26-alpha2 > This is probably the most anticipated release of the year. Looking forward to trying out all the new features! > ### LXD Provider > > The new LXD provider is the best way to use Juju locally. > > The state-server is no longer your host machine; it is now a LXC > container. This keeps your host machine clean and allows you to utilize > your local environment more like a traditional Juju environment. Because > of this, you can test things like Juju high-availability without needing > to utilize a cloud provider. > > The previous local provider remains functional for backwards > compatibility. > > #### Requirements > > - Running Wily (LXD is installed by default) > > For the LXD provider, I have the latest LXD installed on trusty, will that work or is it hard-coded to wily+ ? > - Import the LXD cloud-images that you intend to deploy and register > an alias: > > lxd-images import ubuntu trusty --alias ubuntu-trusty > lxd-images import ubuntu wily --alias ubuntu-wily > > or register an alias for your existing cloud-images > > lxc image alias create ubuntu-trusty <fingerprint> > lxc image alias create ubuntu-wily <fingerprint> > > - For alpha2, you must specify the "--upload-tools" flag when > bootstrapping the environment that will use trusty cloud-images. > This is because most of Juju's charms are for Trusty, and the > agent-tools for Trusty don't yet have LXD support compiled in. > > juju bootstrap --upload-tools > > "--upload-tools" is not required for deploying a wily state-server and > wily services. >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
