Hi SAs,
Can someone confirm this bug please:
https://bugs.launchpad.net/juju-core/+bug/1398628
I am trying to deploy an LXC container using Juju 1.20.13 on MAAS provider
(1.7) and always get container failed to start.
Should be easy to confirm on the Orange Box with the latest stable Juju
Maybe, but not much information there or any workaround or MAAS bug link,
so not sure, maybe need some attention from the MAAS team then.
--
Best Wishes,
Darryl Weaver
Openstack Solutions Architect,
Canonical
Desk: +44 (0)207 630 2400 ext 507516
Mobile: +44 (0)7720088049
GPG FPR: EA3F 3805 9347
Hello all,
we are running an internal AWS like cloud and I would like to use Juju to
deploy services. Is there a way to configure a custom AWS like endpoint which
can be used in the environments,yaml?
Any help is much appreciated.
Thanks
Michael
--
Juju mailing list
Once the tests passed I promulgated the owncloud charm for trusty.
The charm's install hook is still pointing to upstream's 12.04 packages,
this should probably point to this instead:
http://download.opensuse.org/repositories/isv:/ownCloud:/community/xUbuntu_14.04/
--
Juju mailing list
We typically discourage querying cloud specific utils in charms as it makes
them far less portable. It would be much more preferred to have this
patched in Juju.
On Wed Nov 26 2014 at 10:10:35 PM Andrew Wilkins
andrew.wilk...@canonical.com wrote:
Hi Mike,
Sounds like you're hitting
I did reviews of four charm testing / red-to-green merge proposals:
* chef-server: +1
* thinkup: -1 (charm proof)
* couchbase: -1 (install hook failure)
* couchdb: -1 (install hook failure)
I submitted fixes for all of the failures, since they were relatively
small fixes.
On Thu, Dec 4, 2014 at 12:27 AM, Marco Ceppi ma...@ondina.co wrote:
We typically discourage querying cloud specific utils in charms as it
makes them far less portable. It would be much more preferred to have this
patched in Juju.
Sorry, I should have made this clear: this will be fixed in
