lxd provider in master

Hi all, I noticed that the lxd provider was now in master and attempted to use it to help debug an HA problem. In environments.yaml file I added a very simple clause: lxd: type: lxd But when I try to bootstrap, I get the following: $ juju bootstrap --debug 2015-11-23 03:26:14 INFO

Re: lxd provider in master

On 23/11/15 16:59, Andrew Wilkins wrote: > On Mon, Nov 23, 2015 at 11:50 AM Tim Penhey There appears to be no feature flag for the lxd provider, so what am I > missing? > > > Have you added yourself to the lxd group? ("newgrp lxd") Yes, I've had lxd

Re: [Ecosystem-engineering] The future of Charm Helpers

I am very much in favor of this move forward. I’ve recently worked on converting the charm-benchmark package to charms.benchmark; I see where having cleaner namespaces make will make every charm author’s life easier. That said, I know that transitioning to this new model is an epic undertaking,

Re: lxd provider in master

On Mon, Nov 23, 2015 at 11:50 AM Tim Penhey wrote: > Hi all, > > I noticed that the lxd provider was now in master and attempted to use > it to help debug an HA problem. > > In environments.yaml file I added a very simple clause: > >lxd: > type: lxd > > But

Re: juju deploy failure on nova

Hi Cathy, These messages are used to indicate why the service is not a fully functional service.. As you point out, the software packages for the base charm service has been installed at this point in time, but needs additional relations in order to make the service a fully functioning service.