Re: Charm stuck dying

I'm quite surprised to see an 'agent-state: stopped' and life: dead with an 'agent-status: ... executing'. If the agent really is dead, then there is nothing for the hooks to run on. Is this particular unit (nrpe/20) running on a machine that has other services running on it, or was it the last

Re: Faster LXD bootstraps and provisioning

> > ... > > +### tuple ### allow any 8000 0.0.0.0/0 any 0.0.0.0/0 in > +-A ufw-user-input -p tcp --dport 8000 -j ACCEPT > +-A ufw-user-input -p udp --dport 8000 -j ACCEPT > + > > If I'm reading this one correctly, it also means that anyone from *any* IP address (not restricted to your local

Re: Faster LXD bootstraps and provisioning

> > ... > > +### tuple ### allow any 8000 0.0.0.0/0 any 0.0.0.0/0 in > +-A ufw-user-input -p tcp --dport 8000 -j ACCEPT > +-A ufw-user-input -p udp --dport 8000 -j ACCEPT > + > > If I'm reading this one correctly, it also means that anyone from *any* IP address (not restricted to your local

Re: Faster LXD bootstraps and provisioning

My concern about your last configuration is that it appears to change your squid deb proxy into an open proxy by which anything can make a request to any website. At least that is my understanding of: http_access allow all (Its no longer a 'deb' proxy, its just a plain http proxy.) That may be

Re: Latest new about Juju master branch - upload-tools obsoleted

OK, I think I've got it now. On 16/08/16 15:19, Ian Booth wrote: On 16/08/16 12:58, Tim Penhey wrote: On 16/08/16 10:50, Ian Booth wrote: On 16/08/16 03:09, Nate Finch wrote: Ian, can you describe how Juju decides if it's running for a developer or an end user? I'm worried this could

Re: Latest new about Juju master branch - upload-tools obsoleted

On 16/08/16 12:58, Tim Penhey wrote: > > > On 16/08/16 10:50, Ian Booth wrote: >> >> On 16/08/16 03:09, Nate Finch wrote: >>> Ian, can you describe how Juju decides if it's running for a developer or >>> an end user? I'm worried this could trip people up who are both end users >>> and happen

Re: Deploying local code

Hi Alexander, Great to hear fellow kiwis interested. The dealing with artifacts is exactly the problem that resources were designed to fix. A charm defines the resources it needs and as the charm is deployed, it also has the resources fetched. Personally I've not used any charms yet that

Deploying local code

Hello everyone, I'm brand new to Juju, so first I'll say thanks for the exciting project, I really think that Juju takes the right approach to deployment. I will be using Juju to help software development companies build deployment automation for their own work. The first requirements I'm

Re: Latest new about Juju master branch - upload-tools obsoleted

On 16/08/16 03:09, Nate Finch wrote: > Ian, can you describe how Juju decides if it's running for a developer or > an end user? I'm worried this could trip people up who are both end users > and happen to have a juju development environment. > It's not so much Juju deciding - the use cases

Re: Faster LXD bootstraps and provisioning

Yes thanks for doing the work to share this menn0. It is much appreciated. I also needed to change the following in squid-deb-proxy (even though I added a bunch of domains to /etc/squid-deb-proxy/mirror-dstdomain.acl.d/10-default): --- a/squid-deb-proxy/squid-deb-proxy.conf +++

Re: Faster LXD bootstraps and provisioning

Yes thanks for doing the work to share this menn0. It is much appreciated. I also needed to change the following in squid-deb-proxy (even though I added a bunch of domains to /etc/squid-deb-proxy/mirror-dstdomain.acl.d/10-default): --- a/squid-deb-proxy/squid-deb-proxy.conf +++

Juju broken install. Charm in a dying state

Hi, I'm looking for some help with a charm stuck in a dying state. nrpe/20: workload-status: current: terminated since: 12 Aug 2016 10:57:55Z agent-status: current: executing message: running stop hook

nagios charm stuck dying

I have a charm stuck dying. Nothing I do seems to solve the issue. How can I delete or remove the stuck charm nagios: charm: cs:trusty/nagios-10 exposed: true life: dying service-status: current: unknown message: Waiting for agent initialization to finish

Re: Faster LXD bootstraps and provisioning

Thanks Rafael. Would you mind adding this to the wiki page? On 16 August 2016 at 02:31, Rafael Gonzalez wrote: > Hi Menno, > > Thanks for putting this together, great tips. I recently ran into an > issue which others could see as well. > > One may need to adjust

Re: Faster LXD bootstraps and provisioning

Good catch Casey. I've just updated the config in the gist to allow access to any mirror or PPA (in a cleaner way than in the blog article IMO). It seems to work well (apt-get download is nice way to test). On 16 August 2016 at 09:27, Casey Marshall wrote: >

Re: Faster LXD bootstraps and provisioning

Good catch Casey. I've just updated the config in the gist to allow access to any mirror or PPA (in a cleaner way than in the blog article IMO). It seems to work well (apt-get download is nice way to test). On 16 August 2016 at 09:27, Casey Marshall wrote: >

Re: Faster LXD bootstraps and provisioning

Menno, This is great and thanks for sharing! In case anyone else runs into this.. charms that install from PPAs will fail with this squid-deb-proxy setup. You'll need to allow archive mirrors for this to work. See https://1337.tips/ubuntu-cache-packages-using-squid-deb-proxy/ for an example. On

Re: Faster LXD bootstraps and provisioning

Menno, This is great and thanks for sharing! In case anyone else runs into this.. charms that install from PPAs will fail with this squid-deb-proxy setup. You'll need to allow archive mirrors for this to work. See https://1337.tips/ubuntu-cache-packages-using-squid-deb-proxy/ for an example. On

Fwd: breaking API change: controller vs model API connections

There is a PR that's soon to land [edit: just landed] that will change the Juju API so that controller-level RPC calls can no longer be executed on a model-specific connection. https://github.com/juju/juju/pull/5986 This is a breaking API change. The affected facades are the following:

breaking API change: controller vs model API connections

There is a PR that's soon to land that will change the Juju API so that controller-level RPC calls can no longer be executed on a model-specific connection. https://github.com/juju/juju/pull/5986 This is a breaking API change. The affected facades are the following: AllModelWatcher

Re: Latest new about Juju master branch - upload-tools obsoleted

Ian, can you describe how Juju decides if it's running for a developer or an end user? I'm worried this could trip people up who are both end users and happen to have a juju development environment. On Mon, Aug 15, 2016 at 11:29 AM Mark Shuttleworth wrote: > On 15/08/16 08:27,

Re: Latest new about Juju master branch - upload-tools obsoleted

On 15/08/16 08:27, Ian Booth wrote: > So if you pull master you'll no longer need to use upload-tools. > Juju will Do the Right Thing*, when you type: Thanks Ian, this is a lovely simplification. Mark -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at:

Charm stuck dying

Hi I have a charm that is stuck dying. It seem like the entry didn't get updated in juju. Is there a way to manually update the status or trigger the hooks nrpe/20: workload-status: current: terminated since: 12 Aug 2016 10:57:55Z agent-status:

Re: Faster LXD bootstraps and provisioning

Hi Menno, Thanks for putting this together, great tips. I recently ran into an issue which others could see as well. One may need to adjust the following for large bundle deployments on LXD. A bundle deployment fails with errors about "Too many files open." This will increase number of max

Re: Faster LXD bootstraps and provisioning

Hi Menno, Thanks for putting this together, great tips. I recently ran into an issue which others could see as well. One may need to adjust the following for large bundle deployments on LXD. A bundle deployment fails with errors about "Too many files open." This will increase number of max

Re: Error while installing Mariadb 5.5

Hi Rajith, What cloud are you installing to? Do the machines you installing on have full network access? The version of mariadb in the store fetches mariadb packages from a ppa provided by mariadb project. If you can't access that ppa from the machine you're installing on, then things will break.

[Review Queue] IBM IM, Pubphoto, Wordpress, Bip

Last week, Kostas, Pete, and I reviewed the following: - IBM Installation Manager - https://bugs.launchpad.net/charms/+bug/1575746 - Good example of a charm utilizing Resources and Terms. - Deployed with trusty and xenial and successfully exercised

Latest new about Juju master branch - upload-tools obsoleted

So if you pull master you'll no longer need to use upload-tools. Juju will Do the Right Thing*, when you type: $ juju bootstrap mycontroller aws|lxd|whatever or $ juju upgrade-juju *so long as your $GOPATH/bin is in your path (as a developer). 1. As a user, you bootstrap a controller using a

Re: DestroyModel, ModelInfo API deprecation

On Mon, Aug 15, 2016 at 2:13 PM Andrew Wilkins wrote: > Hi, > > We're making a handful of changes around model- and cloud-related APIs. > Some of these will be broken in beta16, and some will be deprecated then > and broken directly after. > > The first change is to

Re: DestroyModel, ModelInfo API deprecation

On Mon, Aug 15, 2016 at 2:13 PM Andrew Wilkins wrote: > Hi, > > We're making a handful of changes around model- and cloud-related APIs. > Some of these will be broken in beta16, and some will be deprecated then > and broken directly after. > > The first change is to

DestroyModel, ModelInfo API deprecation

Hi, We're making a handful of changes around model- and cloud-related APIs. Some of these will be broken in beta16, and some will be deprecated then and broken directly after. The first change is to ModelManager.DestroyModel. This method is now deprecated, and replaced with the pluralised

DestroyModel, ModelInfo API deprecation

Hi, We're making a handful of changes around model- and cloud-related APIs. Some of these will be broken in beta16, and some will be deprecated then and broken directly after. The first change is to ModelManager.DestroyModel. This method is now deprecated, and replaced with the pluralised