Issue with (some) layered charms in network-restricted envs

I'd like to raise awareness of the following issue open against charm-tools: https://github.com/juju/charm-tools/issues/117 It affects deploying charms in network-restricted environments, depending on whether any of the Python libraries they depend on in their wheelhouse use a feature called

Re: Issue with (some) layered charms in network-restricted envs

Not sure if this would help, but, I recently came across this https://github.com/pantsbuild/pex. Would something like this help for keeping charms self contained? On Tue, Mar 1, 2016, 4:45 PM Cory Johns wrote: > I'd like to raise awareness of the following issue open

Re: Resyndicating your post

More than happy to Samuel. There's a bigger thank you to the guys who helped me over the weekend figure out how to get Juju Trunk running with LXD instead of telling me to shut up and wait for the next beta/stable release! ;) So thanks to John, Serge, Rick H for the help, and to Jorge for writing

Re: Logging into the API on Juju 2.0

Went ahead and filed a bug here: https://bugs.launchpad.net/juju-core/+bug/1551743 On Tue, Mar 1, 2016 at 8:40 AM, Rick Harding wrote: > Thank Adam. That's good feedback. With tabular output the default now we > should be more verbose on the yaml output and display

Re: Logging into the API on Juju 2.0

One of the problems using `juju list-controllers --format yaml` versus reading the controllers.yaml file directly is the information is different. Specifically I need the UUID in order to build the URL used when accessing Juju's API.  adam@deadpool:conjure  juju list-controllers --format

Re: Logging into the API on Juju 2.0

Thank Adam. That's good feedback. With tabular output the default now we should be more verbose on the yaml output and display the uuids and other data. On Tue, Mar 1, 2016, 8:37 AM Adam Stokes wrote: > One of the problems using `juju list-controllers --format yaml`

Re: Logging into the API on Juju 2.0

Awesome, appreciate it. On Tue, Mar 1, 2016, 8:48 AM Adam Stokes wrote: > Went ahead and filed a bug here: > https://bugs.launchpad.net/juju-core/+bug/1551743 > > On Tue, Mar 1, 2016 at 8:40 AM, Rick Harding > wrote: > >> Thank Adam.

Re: Bitnami wordpress charm development

Hi Samuel! Well! It's a good idea! But since I'm to new in shell scripting I don't think I could handle such thing. On the other hand I think I could create a template charm that, with minimal effort, the community would be able to use it on another bitnami stacks. Since stack commands should be

Re: Bitnami wordpress charm development

Ney, If you want, I am available on IRC to discuss the idea. It's definitely doable, specially with config-get parameters, and it would be great to have it! You can find us on #juju on irc.freenode.net. My nick is `jose` in there. On 03/01/2016 12:23 PM, Ney Moura wrote: Hi Samuel! Well!

Re: LXD Bootstrap

Okay we're back. Here is the /proc/mount stuff: http://paste.ubuntu.com/15260347/ http://paste.ubuntu.com/15260350/ You can see a bit of a diff after the remount, hope it helps! Tom -- Director Meteorite.bi - Saiku Analytics Founder Tel: +44(0)5603641316 (Thanks to the Saiku

Re: LXD Bootstrap

On Mon, Feb 29, 2016 at 5:35 PM, Serge E. Hallyn wrote: > Hi Casey, > > I haven't reproduced that here in VMs. If you can reproduce this at will > (by > rebooting the host) could you file a bug against the kernel ( > pad.lv/u/linux) ? > Saw it again after booting up my laptop

Re: Extra Network Bindings for Charms

Just to confirm the implementation to support the extra bindings has started and should be available for early testing tomorrow, in the maas-spaces2 feature branch. Cheers, Dimiter On 1.03.2016 11:24, John Meinel wrote: > As we discussed how the Juju network model was going to map network >

Extra Network Bindings for Charms

As we discussed how the Juju network model was going to map network spaces into IP addresses for charms, the Openstack charmers noted that it wasn't sufficient to just provide networking configuration for existing relations. There were several places where the Openstack charms needed a way to