Submission of sme-1 for charm store

Hi, I’d like to respectively request that our new charm sme be considered for promulgation to the charm store. https://jujucharms.com/u/storage-made-easy/sme/xenial/1 Thanks, Steven Steven Sweeting. Director, Product Management Storage Made Easy | Twitter: Storage Made Easy | +1

Trouble adding IPv6 to installed Keystone charm.

Hey, all. Looking to enable IPv6 endpoints on our Newton cloud. "juju config keystone" shows this: prefer-ipv6: description: | If True enables IPv6 support. The charm will expect network interfaces to be configured with an IPv6 address. If set to False (default) IPv4

Re: Deploying a charm with t's & c's

Thanks chaps, I'll try elsewhere. Tom On 04/12/17 18:17, Rick Harding wrote: Thanks for this Tom, for some reason the controller in the region there isn't running 2.2.6, we're looking into it and will try to get it updated as soon as possible. On Mon, Dec 4, 2017 at 9:22 AM Tom Barber

Re: Deploying a charm with t's & c's

Thanks for this Tom, for some reason the controller in the region there isn't running 2.2.6, we're looking into it and will try to get it updated as soon as possible. On Mon, Dec 4, 2017 at 9:22 AM Tom Barber wrote: > mymodel jaasaws/us-east-1 2.2.2unsupported

Re: juju status ERROR current model controller devlocal not found

Hi Feng, did you get anywhere with this? It looks like you're running status on the controller itself. That's not a model to run status on. I'd check out what juju list-models shows and run juju status on those. I think what you need to do is to switch into the controller/model you want to status

Re: Deploying a charm with t's & c's

Hi Tom, This appears to be a problem with the 2.2.2 controller which has been fixed in later versions. If you try a different aws region you should get a more up to date controller and it should work as expected. e.g. $ juju add-model mymodel aws/eu-west-1 Hope this helps Matty On Mon, Dec 4,

Re: Juju bootstrap fails

Hi Deepa. When Juju boostrap it provisions a node and then uses an ssh connection to communicate with that provisioned node. It looks like your client machine isn't able to communicate with the newly provisioned MAAS node without the proxy config you've setup to help with it. I personally use a

juju status ERROR current model controller devlocal not found

Hi Juju, I had a localhost controller bootstrapped and deployed 8 machines (LXDs) to it. Host is a KVM vm of Ubuntu 16.04 amd64. Now for some strange reason, `juju status` reports error as if it lost its model? `list-controllers` showed the controller looks fine. `lxc list` shows all the

Re: Debug logs

Thanks Corey, Its pretty unfriendly in terms of usability, I currently have to find this thread every time I want to debug something. Maybe I'll stick it as a bash alias or something. I do remember the discussion about the noise, it does make sense, but being able to change the levels more

Re: Debug logs

It seems that the default logging level for models was reduced some time back. This makes the logs much less noisy and saves quite a bit of space, but it has the unfortunate side effect of making debugging charm failures from logs more difficult, as most failure messages only show up as stderr

Re: Deploying a charm with t's & c's

mymodel  jaas    aws/us-east-1 2.2.2    unsupported Tom On 04/12/17 14:08, Matthew Williams wrote: Hi Tom, What version of the controller are you using (show in juju status). Is this your own controller or are you using jimm? Thanks Matty On Mon, Dec 4, 2017 at 10:33 AM, Tom Barber

Re: Deploying a charm with t's & c's

Hi Tom, What version of the controller are you using (show in juju status). Is this your own controller or are you using jimm? Thanks Matty On Mon, Dec 4, 2017 at 10:33 AM, Tom Barber wrote: > Hi Casey > > https://asciinema.org/a/qXUZqY5WhCYFUA44l9OILeZWB As you'll see

Re: Deploying a charm with t's & c's

Hi Casey https://asciinema.org/a/qXUZqY5WhCYFUA44l9OILeZWB As you'll see here. #45 works for me also but #47 fails. I don't think we changed anything massively but clearly something in there is sad, the problem is that, the error thrown gives me no indication of where we've messed up. On a

Re: Getting the exposed ports

Hm, I wonder why the iptables charm is doing that. from charms.reactive.bus import State class states(StateList): connected = State('{relation_name}.connected') joined = State('{relation_name}.joined') departed = State('{relation_name}.departed') The internals of charms.reactive have