On Sun, Feb 21, 2016 at 7:28 AM Ian Booth <ian.bo...@canonical.com> wrote:
> To specify a different LXD host: > > $ juju bootstrap mycontroller lxd/<remotehost> > > For now, just localhost (the default) has been fully tested and is > guaranteed to > work with this beta1. > The lxd/<host> format has not been implemented yet. That will come later, along with support for remote lxd, which AFAIK does not exist in the provider. There's no need to edit any clouds.yaml file for the LXD cloud. It's meant > to be > really easy to use! > > > On 21/02/16 09:21, Marco Ceppi wrote: > > Won't the user be able to create different LXD clouds by specifying a > > remote LXD host though? > > > > On Sun, Feb 21, 2016, 12:19 AM Ian Booth <ian.bo...@canonical.com> > wrote: > > > >> 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 > >> > > > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
