Thanks, Rick. We can definitely try out multiple environments locally.
I forgot to mention, Wayne did a great blog post
<http://waynewitzel.com/2015/11/05/juju-and-remote-lxd-host/> discussing
using the LXD provider on remote hosts.
On 11/09/2015 12:19 PM, Rick Harding wrote:
Thanks Katherine. That's looking great. One request, next demo I'd be
curious to see how easy it is to run multiple lxd environments
locally. I know it's been possible with lxc before with a bunch of
config. Ideally we'd just be able to create a new named section and
say it's lxd and boom, I can bootstrap the new one and have it
distinct from the first.
Keep up the great work!
On Mon, Nov 9, 2015 at 11:59 AM Katherine Cox-Buday
<[email protected]
<mailto:[email protected]>> wrote:
Hey all,
Moonstone spent last iteration tightening up the LXD provider. You
can see the latest results in our latest Demo Day
<https://www.youtube.com/watch?v=QyXLRDN0ERo>. It's a ~9 minute
video which demonstrates:
1. The format of the entry into environments.yaml.
2. LXD bootstrapping locally.
3. The fact that it's no longer necessary to tweak permissions of
the unix socket to utilize this.
4. Juju LXD coming back up when the host is rebooted.
We're also very happy to announce that this will land in the
upcoming 1.26-alpha2 milestone on 2015-11-17! If you'd like to
play with this in the meantime, feel free to build from our
feature branch <https://github.com/juju/juju/tree/lxd-provider>
and log bugs against the blueprint
<https://blueprints.launchpad.net/juju-core/+spec/charmer-experience-lxd-provider>.
Documentation and release notes will be forthcoming.
Thanks, and have fun!
-
Katherine
--
Juju mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
