On Wed, Mar 4, 2015 at 10:12 AM, Adam Collard
adam.coll...@canonical.com wrote:
Why not stick to the UNIX principle and compose a pipeline?
That would also do the trick, as long as it's something that can
capture what's going on in one snippet.
--
Jorge Castro
Canonical Ltd.
On Wed, Mar 4, 2015 at 8:44 AM, Martin Packman
martin.pack...@canonical.com wrote:
On 04/03/2015, Andrew Wilkins andrew.wilk...@canonical.com wrote:
Curtis and I have talked about also doing a ppc64 test run as part of
the gating job, that gets us the map ordering stuff as a newer go
would,
Hi,
May I add two tips that can help
1. When you use the python template, the charmhelpers package download
and use is done for you, but it then prevents your script to be run
with as a simple python script since usually
/usr/local/lib/python2.7/dist-packages is not a default.
*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I've asked Jake to file a bug for this issue, as it will be easier to
track it and collect all the information in one place.
In the mean time I'll be analyzing the possible cause for this.
Cheers,
Dimiter
On 4.03.2015 17:13, Jake Kugel wrote:
On 4 March 2015 at 13:45, Jorge O. Castro jo...@ubuntu.com wrote:
Hi everyone,
Sometimes people deploy things like a complex bundle on a cloud and it
doesn't work. Having to wrangle the person to find out which units
broke, juju sshing in and manually digging around logs and refiring
off
There is a bug about us defaulting to uploading the user's private id_rsa
ssh key to joyent as a part of bootstrapping a new server. This is
obviously a bad thing. bug:
https://bugs.launchpad.net/juju-core/+bug/1415671
However, the proposed solution (generate our own key and use that) doesn't
Developers using Windows can't download and hack on charms. There's really
not need to create symlinks in hooks directories, you can achieve the same
affect by stubbing hooks which import your hooks.py file and invoke the
methods that are wrapped with the Hook decorator.
Again, best practice, not
Since I haven't been able to find a listserv specifically for MAAS and
this listserv is close to the subject and seems to provide good
answers...
I have a MAAS server that was last installed December 18, 2014 to test
building an OpenStack cloud. When I first built it, it would discover,
Greetings Halimaton,
I see you ran across my tutorial on exposing LXC containers on your
network. There are a few things here that can cause the problem you are
seeing about Containers failing to start.
The networking on the local provider if faux DHCP, and doesn't seem to
check for collisions,
On 4 March 2015 at 17:23, Eric Snow eric.s...@canonical.com wrote:
On Wed, Mar 4, 2015 at 10:04 AM, Nate Finch nate.fi...@canonical.com wrote:
My suggested solution is that we do what we do for all the rest of the
providers, which is to make the user give us authentication credentials in
the
Thanks again, opened following bug:
https://bugs.launchpad.net/juju-core/+bug/1428345
Jake
From: Dimiter Naydenov dimiter.nayde...@canonical.com
To: juju@lists.ubuntu.com
Date: 03/04/2015 10:39 AM
Subject:Re: unit-get and ipv6 addresses
Sent by:
mumble-server:
Mostly cosmetic changes. +1
https://code.launchpad.net/~lazypower/charms/precise/mumble-server/metadata_cleanup/+merge/246058
python-moinmoin:
These merge proposals fix issues in both the precise and trusty version
of this charm, including refactored tests. +1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the +1's Adam. I've taken action on the listed MP's based
on your review and pushed them upstream.
All the best
On 03/04/2015 05:07 PM, Adam Israel wrote:
mumble-server:
Mostly cosmetic changes. +1
On 04/03/15 19:05, Andrew Wilkins wrote:
The bugs were fixed in this branch: https://github.com/juju/juju/pull/1738
- invalid printf-style formatting will cause go vet to fail
My bad. I had deleted the pre-push hook script some time ago when go vet
failed continuously, and I hadn't reinstated
On Thu, Mar 5, 2015 at 1:04 AM, Nate Finch nate.fi...@canonical.com wrote:
There is a bug about us defaulting to uploading the user's private id_rsa
ssh key to joyent as a part of bootstrapping a new server. This is
obviously a bad thing. bug:
On Thu, Mar 5, 2015 at 10:24 AM, Tim Penhey tim.pen...@canonical.com
wrote:
On 04/03/15 19:05, Andrew Wilkins wrote:
The bugs were fixed in this branch:
https://github.com/juju/juju/pull/1738
- invalid printf-style formatting will cause go vet to fail
My bad. I had deleted the pre-push
One option is to run the test suite with go 1.3 and just make sure that
juju compiles with all the other compilers (1.2, gccgo, etc). That gives us
a fast precommit check, which won't catch everything, but should catch most
1.2 compat bugs. And leave the full test suite runs as CI tests.
John
=:-
Hello,
I got a similar issue and solved it by disabling IPv6 under main host so
lxc containers could communicate through IPv4 and access to external world.
I haven't yet understand the issue but it sounds like if the main host
is IPv6 enabled, then system tries to communicat through IPv6 even
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015-03-04 08:53 AM, Dimiter Naydenov wrote:
If it's about catching map ordering issues, let's use go 1.3+ as
an extra step, rather than gccgo, which is buggy and slow and
randomly segfaults. It's likely we'll slow down merge gating
On Wed, Mar 4, 2015 at 1:05 AM, Andrew Wilkins
andrew.wilk...@canonical.com wrote:
The bot is currently running (I think) Go 1.2. I'm running 1.4, Ian's
running 1.3, and I'm sure Dave's running tip ;) Go 1.3+ made map iteration
less deterministic, so these sorts of bugs are much more likely to
On 04/03/2015, Andrew Wilkins andrew.wilk...@canonical.com wrote:
Hi all,
Ian asked me to mail the list about a couple of bugs that managed to get
past the bot; first so that we can all be mindful of these sorts of bugs,
and second to highlight the fact that they could have been caught by the
Hi everyone,
Sometimes people deploy things like a complex bundle on a cloud and it
doesn't work. Having to wrangle the person to find out which units
broke, juju sshing in and manually digging around logs and refiring
off hooks, etc. is time consuming.
Marco and I thought something like `juju
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4.03.2015 15:44, Martin Packman wrote:
On 04/03/2015, Andrew Wilkins andrew.wilk...@canonical.com
wrote:
Hi all,
Ian asked me to mail the list about a couple of bugs that managed
to get past the bot; first so that we can all be mindful of
Why not stick to the UNIX principle and compose a pipeline?
With https://bugs.launchpad.net/juju-core/+bug/1390585 fixed it could be as
simple as juju debug-log --no-stream --replay | pastebinit
On 4 March 2015 at 13:45, Jorge O. Castro jo...@ubuntu.com wrote:
Hi everyone,
Sometimes people
24 matches
Mail list logo
