The lxd cloud works on Juju 2.0 beta1 out of the box. $ juju bootstrap mycontroller lxd
There is no need to edit any clouds.yaml. It Just Works. It seems the confusion comes from not seeing lxd in the output of juju list-clouds. list-clouds ostensibly shows available public clouds (aws, azure etc) and any private clouds (maas, openstack etc) added by the user. The lxd cloud is just built-in to Juju. But from a usability perspective, it's seems we should include lxd in the output of list-clouds. NOTE: the latest lxd 2.0.0 beta3 release recently added to the archives has an api change that is not compatible with Juju. You will need to ensure that you're still using the lxd 2.0.0 beta2 release to test with Juju. On 21/02/16 08:26, Jorge O. Castro wrote: > Awesome, a nice weekend present! > > I updated and LXD is not listed when I `juju list-clouds`. Rick and I > were guessing that maybe because the machine I am testing on is on > trusty that we exclude that cloud on purpose. If I was on a xenial > machine I would assume lxd would be available? > > What's an example clouds.yaml look like for a lxd local provider? I > tried manually adding a lxd cloud via `add-cloud` but I'm unsure of > what the formatting would look like for a local provider. > >> Development releases use the "devel" simple-streams. You must configure >> the `agent-stream` option in your environments.yaml to use the matching >> juju agents. > > I am confused, I no longer have an environments.yaml so is this > leftover from a previous release? > > Thanks! > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
