Re: Aggregate all bundle.yaml | API endpoint

Hello Merlijn and all, I developed a python script which fetching all the bundle.yml. Here is the repo: https://github.com/itsoum/BundlesFetcher Merlijn special thanks for the help about the API. Now, there rise a new "problem". As I had mentioned in the first-post above I fetch bundles for the r

Charm series in API URL

Hello all, I’ve been part of a small project with Spicule Ltd recently involving extraction of Charm deployment data from the Juju Charm API. Why is it so that the only way to get the deployment data showing for Charms that are only deployable on one series, is by leaving the series section of

Re: Charm series in API URL

Hi Tim, The statistics are based on the name of the charm itself. Once upon a time all charms contained the series in their name. Using your example above cs:~bigdata-charmers/trusty/hadoop-plugin-5 ( https://jujucharms.com/u/bigdata-charmers/hadoop-plugin/trusty/5) is a different charm from cs:~b

Re: Aggregate all bundle.yaml | API endpoint

The format is - - : - : Where application-name is the name of the _instance_ of the charm (as defined in the applications section of bundle.yaml) and endpoint-name is the name of the endpoint (requires/provides from metadata.yaml) that is used to connect the two nodes. Endpoint-name is optiona

LXD on Manual incorrect resolv.conf

Hi folks, I’m trying to do a manual cloud with LXD containers within it. When I manually launch and LXD container I get nameserver 10.61.251.1 search lxd If juju launches a container it gets: nameserver 127.0.0.1 search ovh.net lxd Which doesn’t connect to the interwebs and makes Juju sad. Wh

Re: LXD on Manual incorrect resolv.conf

Hi Tom, What is your expectation on how the containers are getting their IP addresses? Also, which version of Juju? Tim On 27/06/18 08:29, Tom Barber wrote: > Hi folks, > > I’m trying to do a manual cloud with LXD containers within it. > > When I manually launch and LXD container I get  > >

Re: LXD on Manual incorrect resolv.conf

I don’t have any expectation other than connectivity to the internet would be nice because otherwise it makes juju quite hard :) But irrespective of my expectations, if standalone LXD containers get a resolv.conf that allows connection to the WWW, why doesn’t Juju, it seems both reasonable and log

Re: LXD on Manual incorrect resolv.conf

I guess I should have been more clear with respect to the IP addresses. Clearly the container isn't being set up correctly if it can't reach out and we should look into that. When a container is started there are several options for how it gets an IP address. The various default behaviours are di

Re: LXD on Manual incorrect resolv.conf

Ah right, apologies, the IP address is provided by the LXD default bridge. On 26 June 2018 at 22:31:12, Tim Penhey (tim.pen...@canonical.com) wrote: I guess I should have been more clear with respect to the IP addresses. Clearly the container isn't being set up correctly if it can't reach out a

Re: LXD on Manual incorrect resolv.conf

Am I right in assuming that you are bringing up bionic containers? On 27/06/18 10:09, Tom Barber wrote: > Ah right, apologies, the IP address is provided by the LXD default bridge. > > > On 26 June 2018 at 22:31:12, Tim Penhey (tim.pen...@canonical.com > ) wrote: