Re: Implement aws style user-data

Hi Drew, Juju uses cloud-init currently when provisioning machines today. We've recently added a bootstrap configuration option to allow for cloud-init yaml to be passed through. Details can be found in an old bug: https://bugs.launchpad.net/juju/+bug/1535891 I need to get this added to the doc

Re: juju bug (?) when allocating floating ips to machines

Hi Patrizio, Judging by the code in develop, we do not check the tenant_id when choosing a FIP. There is an attempt to ensure the FIP is in the provided external network, if specified. So that may be another work around. Please file a bug. I'm wondering if there are more places the provider sh

We are excited to announce the release of Juju 2.2.2!

This release fixes some bugs that missed the cut for 2.2.1. Notable inclusions are: * juju debug-log will no longer stop prematurely * missing credentials will no longer stop upgrades * reduced log spam in many places * added datastore selector for vSphere provider * agents will no longer fals

A new release of Juju, 2.2-beta4 and conjure-up are here!

# Juju 2.2-beta4 Release Notes We are delighted to announce the release of Juju and conjure-up 2.2-beta4! In this release, Juju greatly improves memory and storage consumption, works on KVM containers, and improves network modelling. conjure-up now supports Juju as a Service (JAAS), provides a Mac

Re: How to add openstack cloud to juju 2.1.2-xenial

owto-privatecloud down to the juju > > > boostrap > > > command of: > > > > > > juju bootstrap acauits --config image-metadata-url=http://10.20.9.1 > > > 39:8 > > > 0/swift/v1 > > > > > > and it

Re: How to add openstack cloud to juju 2.1.2-xenial

Here is a link on generating the image metadata: https://jujucharms.com/docs/stable/howto-privatecloud -Heather > On Apr 11, 2017, at 10:20 PM, Daniel Bidwell wrote: > > I am making progress. My openstack cloud has been added now. > >

Re: lxd hook failed change-config

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 > &

Re: lxd hook failed change-config

commit/017246768e097c5fcd5283e23f19f075ff9f9d4e > > <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 <mailto:hmlani...@gmail.com>

Re: lxd hook failed change-config

d deployment today and one of the upstream maintainers > ran through the same deployment and didn't run into any issues. > > > On Thu, Oct 20, 2016, 10:02 PM Heather Lanigan <mailto:hmlani...@gmail.com>> wrote: > > I used conjure-up to deploy openstack-novalxd o

lxd hook failed change-config

I used conjure-up to deploy openstack-novalxd on a Xenial system. Before deploying, the operating system was updated. LXD init was setup with dir, not xfs. All but one of the charms has a status of “unit is ready" The lxd/0 subordinate charm has a status of: hook failed: "config-changed”.