Re: juju devel 2.0-beta1 is available for testing

2016-02-20 Thread Mark Shuttleworth
On 21/02/16 00:18, Ian Booth wrote: > 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

Re: juju devel 2.0-beta1 is available for testing

2016-02-20 Thread Mark Shuttleworth
On 21/02/16 03:57, Andrew Wilkins wrote: > The lxd/ format has not been implemented yet. That will come later, > along with support for remote lxd, which AFAIK does not exist in the > provider. I'm not sure it will be appropriate to do that way now that we have made the assumption of a single

Re: juju devel 2.0-beta1 is available for testing

2016-02-20 Thread Ian Booth
To specify a different LXD host: $ juju bootstrap mycontroller lxd/ For now, just localhost (the default) has been fully tested and is guaranteed to work with this beta1. 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,

Re: juju devel 2.0-beta1 is available for testing

2016-02-20 Thread Marco Ceppi
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 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

Re: juju devel 2.0-beta1 is available for testing

2016-02-20 Thread Ian Booth
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

Re: juju devel 2.0-beta1 is available for testing

2016-02-20 Thread Rick Harding
I tested this on xenial and it's not there. I've filed a bug for it. https://bugs.launchpad.net/juju-core/+bug/1547966 To get it going I first created a lxd.yaml file with the config for the lxd 'cloud'. clouds: lxd: type: lxd Then I added that with juju add-cloud lxd lxd.yaml

Re: juju devel 2.0-beta1 is available for testing

2016-02-20 Thread Jorge O. Castro
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

juju devel 2.0-beta1 is available for testing

2016-02-20 Thread Curtis Hovey-Canonical
# juju-core 2.0-beta1 A new development release of Juju, juju-core 2.0-beta1, is now available. This release replaces version 2.0-alpha2. ## Getting Juju juju-core 2.0-beta1 is available for Xenial and backported to earlier series in the following PPA:

Re: Migration of OpenStack Charm development to OpenStack git/gerrit

2016-02-20 Thread Antoni Segura Puimedon
On Fri, Feb 19, 2016 at 3:03 PM, James Page wrote: > Hi All > > > As you may or may not be aware, the OpenStack team have been working towards > migration of the development process around the OpenStack charms to the > OpenStack project. > > > This means we will be moving

Re: @when('config.changed')

2016-02-20 Thread Antoni Segura Puimedon
On Fri, Feb 19, 2016 at 6:30 PM, Charles Butler wrote: > I like the idea of an @after() decorator. > > I've run into some cases where having @after would be a boon, such as > cycling for docker extensions (setting up network, storage, et-al) that > would benefit from