Hello,
I got juju bootstrap error.
I used Ubuntu 14.04 LTS.
How to fix this?
Thanks!
root@maas:/home/ceph# juju bootstrap --show-log
2014-05-12 12:21:06 INFO juju.cmd supercommand.go:297 running
juju-1.18.1-trusty-amd64 [gc]
2014-05-12 12:21:06 INFO juju.environs open.go:177 environment info
Hi,
I am running a clean MaaS with juju 1.18.x in a separate network within our
school LAN. I have tried to include a schema of it here:
(Best viewed in a monospace font)
___ MaaS Controller (192.168.3.1/24)
School LAN (10.0.0.0/20) __/
Sebastian,
Glad to see your submission has made it this far! This is exciting news for
the Drupal users in the community. What specific questions do you have in
relation to charm scaling? We can schedule a charm school to cover best
practices when building a charm's architecture for scale, but
Hi!
I just noticed that I now have specify the arch constraint if I want amd64
instances. Without it, I get i386 instances. juju help constraints still
tells me that amd64 is supposed to be the default.
I am using juju 1.18.2 on EC2, precise on the instances, trusty on my
workstation.
Has this
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1304407
It should be fixed in 1.18.3.
John
=:-
On Mon, May 12, 2014 at 9:36 PM, Henning Eggers henn...@keeeb.com wrote:
Hi!
I just noticed that I now have specify the arch constraint if I want amd64
instances. Without it, I get i386
Why isn't the default tweaked by --upload-tools itself then? We
should be optimizing these options for users, rather than for
developers, and it sounds sensible to assume that the vast majority of
users do want to deploy on amd64 rather than i386 or arm.
On Mon, May 12, 2014 at 2:53 PM, Nate
Ah, thank you! I searched for a matching bug but I guess I used the wrong
search terms. ;-)
Cheers,
Henning
Am 12.05.2014 19:50, schrieb John Meinel:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1304407
It should be fixed in 1.18.3.
John
=:-
On Mon, May 12, 2014 at 9:36 PM,
On Tue, May 13, 2014 at 4:14 AM, Joey STANFORD j...@canonical.com wrote:
Hi Juju'ers,
I'm curious to know if there is any reliable mechanism to detect a
cowboyed change inside a juju environment and then report them.
A non-juju synonym of what I'm trying to accomplish would be with puppet
I actually think this isn't about someone doing juju set-env but someone
just ssh'ing into the machine and changing things with a text editor.
Joey is the type of guy to be very concerned about people making changes
out of band that we wouldn't know about even if we had audit logging.
(Which we
The builds for Juju devel and stable were broken by external packages.
http://juju-ci.vapour.ws:8080/job/build-revision/
Fetching http://labix.org/v2/mgo/txn?go-get=1
import labix.org/v2/mgo/txn: http/https fetch: Get
http://labix.org/v2/mgo/txn?go-get=1: dial tcp 69.163.203.213:80:
juju-qa-bot has will be doing mass/automated bug changes for us now.
You can filter those bug emails out since they will be usually be a
case of bugs changing to Fix Committed or Fix Released. I am also
tasking to bot to create the pool of Medium bugs tat we will actively
retriage.
On Fri, May 9,
I don't want to have this bikeshed - I vote for people to use their
best judgement and permit anything which fits through gofmt.
On Tue, May 13, 2014 at 3:37 PM, John Meinel j...@arbash-meinel.com wrote:
In the risk of running a bikeshedding paint-fest, I'm curious what the
best-recommended
12 matches
Mail list logo
