I'd like to propose that we adopt a "minimum footprint by default"
guidance for charmers, with a convention for how you might say "in this
case, assume you're the dominant workload" or "feel free to use XYZ
resources".
By this I mean that a charm deployed with default config would adopt a
lowest-
-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
>
> https://code.launchpad.net/~l
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
https://code.laun
Thanks again, opened following bug:
https://bugs.launchpad.net/juju-core/+bug/1428345
Jake
From: Dimiter Naydenov
To: juju@lists.ubuntu.com
Date: 03/04/2015 10:39 AM
Subject:Re: unit-get and ipv6 addresses
Sent by:juju-boun...@lists.ubuntu.com
-BEGIN PGP SIGNED
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,
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,
commissio
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
On Tue, Mar 3, 2015 at 4:38 PM, Vahric Muhtaryan
wrote:
> Hello All ,
>
> I'm quite new Juju but like it and preparing to introduce it to our
> customers for they can use it as a PaaS solution with our cloud offerings
> Not understand or learn full functionality of Docker but like juju it can
> d
On 2 March 2015 at 17:46, Marco Ceppi wrote:
> # Charm Authors
>
> - Avoid symlinks in charm
/me blinks
I assume you don't mean symlinks in hooks/ dir?
Anything documenting why this is a bad idea?
--
Simon
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https:
On 4 March 2015 at 13:45, Jorge O. Castro 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 hooks, etc. is
-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 Wed, Mar 4, 2015 at 10:12 AM, Adam Collard
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.
http://juju.ubuntu.com/ - Automate your Clou
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.
* Defaul
Hi,
we also got around it by disabling IPv6 on our hosts.
I had tried sending additional logs Dimiter requested but the email was
too large for mailing list server. For lack of better idea on how to deal
with large attachments I had sent Dimiter logs directly (sorry Dimiter).
Maybe pastebin n
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 wrote:
> Hi everyone,
>
> Sometimes people deploy things
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 pa
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
17 matches
Mail list logo
