Process to get layer approved

Hi all I'd like to get my juju-client layer approved as an official layer. What is the process to do this? If anyone would like to use this layer, please let me know! I'm open to feedback. Kind regards Merlijn

Re: Issue while deploying charm - Could not resolve 'archive.ubuntu.com'

Hello Suchitra, The error seems to indicate a problem not being able to find archive.ubuntu.com. This appears to be a DNS resolution problem. The DNS file can be found at /etc/resolv.conf on your system. I would check that your DNS sever can be reached by the system you are running Juju on.

Re: Process to get layer approved

Currently you have to ask a ~charmer and this list is a fine way to do that. We plan on lowering the barrier to modifying the index in the very near term. That said you have this layer as a nested directory in a repo. We currently only support linking to top level repos though if this sort of

Re: Process to get layer approved

Hi Benjamin Thanks for your reply! I've put the layer in its own repository . For the moment the functionality is very basic. I'll add more functionality like actions and some python wrappers around Juju functions but I think this is a good start and I'd

Re: local: nested lxc containers

For the time being you can add these entries to the lxc container defaults, which should be in `/etc/lxc/default.conf` and new containers launched will have those updated values. Going forward, we're working on a LXD provider for Juju - part of that work will enable nesting of containers by

Issue while deploying charm - Could not resolve 'archive.ubuntu.com'

Hi, I am facing this issue while deploying a charm in my local container. 2015-10-14 12:47:09 INFO install After this operation, 11.7 MB of additional disk space will be used. 2015-10-14 12:47:09 INFO install Err http://archive.ubuntu.com/ubuntu/ trusty-updates/main binutils amd64

local: nested lxc containers

Hi, I wrote a charm for an application I developed which deploys some lxc containers. I wanted to test it in my local environment (bootstrapped with juju-quickstart), but I couldn't find a way to configure juju to automatically create containers with specific settings---in my case, allowing for