On Tue, Oct 29, 2013 at 7:38 PM, Andreas Hasenack andr...@canonical.com wrote:
When the first unit of the app comes up, it creates a random password and
uses the DB admin user to create an unprivileged DB user with that password.
Do you know why the client service needs to create the user,
Hi,
$ dpkg-query -W juju-core
juju-core 1.16.2-0ubuntu1~ubuntu13.04.1~juju1
but
$ juju version
1.17.0-raring-amd64
$ apt-cache policy juju-core
juju-core:
Installed: 1.16.2-0ubuntu1~ubuntu13.04.1~juju1
Candidate: 1.16.2-0ubuntu1~ubuntu13.04.1~juju1
Version table:
***
It's not the first time that the inactive bit there creates
confusion. One idea would be to rename charmers to be more
descriptive, rather than having a negative team (a team that does NOT
do something). For example:
~charmers = all charmers
~charm-reviewers = only those who review; this team is
On 11/03/2013 05:00 PM, Sidnei da Silva wrote:
To be clear, this *specific* change (the rename of a config.yaml argument)
is a revert of r31 of the charm in the charm store.
Also in this specific case, nagios_check_http_params is the config key
used in several of the other charms and would be
Okay, so taking in Sidnei's feedback I've merged this request as it's
reverting back to a previous state. The example not withstanding I'm
curious on how we should handle such changes in the future.
Thanks, Marco
On Mon, Nov 4, 2013 at 10:53 AM, David Ames david.a...@canonical.comwrote:
On
Hi everyone,
We've started to collect best practice for troubleshooting the local provider:
https://juju.ubuntu.com/docs/troubleshooting-local.html
These docs are NOT yet indexed on the main table of contents on the
side, I wanted to give you guys a couple of days to toss in any
techniques you
On 05/11/13 09:16, Jorge O. Castro wrote:
Hi everyone,
We've started to collect best practice for troubleshooting the local provider:
https://juju.ubuntu.com/docs/troubleshooting-local.html
These docs are NOT yet indexed on the main table of contents on the
side, I wanted to give you
On 04/11/13 22:55, Stuart Bishop wrote:
On Mon, Nov 4, 2013 at 11:40 AM, Yasmany Cubela Medina
yasman...@gmail.com wrote:
Im trying to configure juju-local on my virtual-box machine to test some
environments, learn, play and then make some desition to deploy to my cloud.
I follow the docs on
Hello everyone!
I'm happy to announce charm-tools 1.1.2 has been released! This release
succeeds 1.1.1, which was released a few hours. This announcements contains
the fixes for both 1.1.1 and 1.1.2. This release implements two patches to
improve proofing functionality for bundles and charms.
#
On Mon, Nov 4, 2013 at 12:04 PM, John Arbash Meinel
j...@arbash-meinel.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2013-11-04 17:52, roger peppe wrote:
There's no point in salting the agent passwords, and we can't
easily change things to salt the user passwords until none of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/11/13 00:45, John Arbash Meinel wrote:
https://blueprints.launchpad.net/juju-core/+spec/t-cloud-juju-cli-api
I also went through the photo I took of our big bit of paper
and marked done those that were (although sync-tools seemed to be
a
Hi Curtis,
The local provider was broken again with an update to cgroups-lite. This
then triggered an apparmor protection mechanism from the host machine,
and left apt in an incomplete state.
The symptoms are that install hooks fail to run for units.
Tracked in bug
I have landed the change. If this causes problems, we can add a flag
private-cloud datasources to prevent fallback.
We'll need to document this in the release notes. I have created a new bug
so this gets a mention in 1.17.0:
https://bugs.launchpad.net/juju-core/+bug/1247730
Cheers,
Andrew
On
13 matches
Mail list logo
