Re: AWS US East (Ohio) Region now supported for Juju 2.x

2016-10-21 Thread Mark Shuttleworth
On 20/10/16 17:15, Aaron Bentley wrote: > To use it with 2.0.0, just run "juju update-clouds" once. You will see > the message: > Updated your list of public clouds with 1 cloud region added: > > added cloud region: > - aws/us-east-2 > > After that, the new region will work the same as

Re: lxd hook failed change-config

2016-10-21 Thread Adam Stokes
So it looks like a recent change to the LXD charm, see here: https://github.com/openstack/charm-lxd/commit/017246768e097c5fcd5283e23f19f075ff9f9d4e Chuck, are you aware of this issue? On Fri, Oct 21, 2016 at 10:19 AM Heather Lanigan wrote: > Adam, > > The entire container is not readonly. Jus

Re: lxd hook failed change-config

2016-10-21 Thread Adam Stokes
This looks like it's due to the way we deploy OpenStack with NovaLXD in all containers, this effectively breaks anyone wanting to do an all-in-one install on their system. On Fri, Oct 21, 2016 at 10:22 AM Adam Stokes wrote: > So it looks like a recent change to the LXD charm, see here: > > > htt

Re: lxd hook failed change-config

2016-10-21 Thread Heather Lanigan
Adam, The entire container is not readonly. Just /sys, the mount point for /dev/.lxc/sys. I choose another charm (neutron-api) to look at, /sys on that unit is readonly as well.Is that normal? What would be different in my config? My Xenial install is on a VM, but I’ve been running that

[Review Queue] IBM Platform RTM, LSF, Symphony, and Websphere Base

2016-10-21 Thread Kevin Monroe
Hi folks, Cory, Kostas, Pete, and myself had a look at the following this week: - IBM Platform RTM - https://bugs.launchpad.net/charms/+bug/1510216 - Minor issues with config (offered suggestions) and readme instructions (fixed) - Amulet test need

Re: lxd hook failed change-config

2016-10-21 Thread Chuck Short
Hi, I proposed a fix: https://review.openstack.org/#/c/389740/ chuck On Fri, Oct 21, 2016 at 10:27 AM, Adam Stokes wrote: > This looks like it's due to the way we deploy OpenStack with NovaLXD in > all containers, this effectively breaks anyone wanting to do an all-in-one > install on their s

Re: lxd hook failed change-config

2016-10-21 Thread Ryan Beisner
Hi All - we need a LP bug for this, please. The gerrit review will need to have its commit message updated with the lp bug info so that CI can do bug management on it. Then, once it lands in the charm's master, we can cherry-pick it for a stable backport to the stable charm. Thanks, Ryan On Fri,

Re: lxd hook failed change-config

2016-10-21 Thread Adam Stokes
Heather, A bug has been filed about this issue: https://bugs.launchpad.net/charm-lxd/+bug/1635659 I've asked that it get top priority in order to have this fixed pushed into the charmstore asap. I'll let you know once the updated charm is available for deployment again. Sorry for the inconvenien

Re: lxd hook failed change-config

2016-10-21 Thread Heather Lanigan
Update based on IRC conversation: I tried the fix. Turns out that (my) Xenial install doesn’t have the systemd-virt-detect command. -Heather > On Oct 21, 2016, at 10:54 AM, Chuck Short wrote: > > Hi, > > I proposed a fix: > > https://review.openstack.org/#/c/389740/ >

Re: lxd hook failed change-config

2016-10-21 Thread Heather Lanigan
The updated proposed fix is now working for me. -Heather > On Oct 21, 2016, at 12:42 PM, Heather Lanigan wrote: > > Update based on IRC conversation: I tried the fix. Turns out that (my) > Xenial install doesn’t have the systemd-virt-detect command. > > -Heather > >> On Oct 21, 2016, at