Logging changes coming with juju 1.15

Hi All, Last night I was pointed at a bug where one of the main problems was poor communication on my part as to changes, so here is the comprehensive details. For a long time (all of juju-core up to now), all the machine agents logged everything at debug. Logging at the debug level is used prim

Re: juju-local bootstrap: connection refused

On 25/10/13 01:17, Peter Waller wrote: > Hi All, > > I'm on Ubuntu 12.04.3 with the juju stable repository and trying to > experiment with juju locally. I can't seem to get past the bootstrap though. > > I've followed the instructions here: > > https://juju.ubuntu.com/docs/config-local.html > >

Re: Troubleshooting the local provider docs now available.

On 05/11/13 09:16, Jorge O. Castro wrote: > Hi everyone, > > We've started to collect best practice for troubleshooting the local provider: > > https://juju.ubuntu.com/docs/troubleshooting-local.html > > These docs are NOT yet indexed on the main table of contents on the > side, I wanted to give

Re: juju-local

On 04/11/13 22:55, Stuart Bishop wrote: > On Mon, Nov 4, 2013 at 11:40 AM, Yasmany Cubela Medina > wrote: >> Im trying to configure juju-local on my virtual-box machine to test some >> environments, learn, play and then make some desition to deploy to my cloud. >> >> I follow the docs on juju page

Re: docker hype and juju's future

On 21/11/13 21:43, Ramez Hanna wrote: > I am sure it is on the roadmap to containerize services on the juju > deployed services Containerisation is simple, but networking is hard. We have lxc containers working in juju now, but they are currently only addressable in MAAS. We have some work outsta

Windows clients and PuTTY

Hi folks, I watch the Ask Ubuntu questions around Juju, and saw one yesterday that I think we need to get better docs around. The user was saying he couldn't edit the files on the machines that Juju started. This had me going "huh?". I should have twigged immediately at the use of Filezilla, bu

Re: Vagrant boxes with Juju now available

On 07/12/13 07:46, Daniele Stroppa wrote: > John, David, > > the reason why I'm destroying the service and re-deploy it's because I'm > testing/debugging my charm's hooks, specifically the install hook in > this case. > > My understanding is that 'juju upgrade-charm' will trigger the > upgrade-c

Re: Fwd: How to make juju aware of IP address changes?

On 07/12/13 05:04, roger peppe wrote: > I think that there are a few things that could help here, > most important points first: > > - We should limit agent restarting in some way (exponential backoff or > retry limits or both) I think this is a key one. If the agent is repeatedly failing, we sh

Re: juju nuke

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/01/14 09:49, Casey Marshall wrote: > When I'm debugging a charm, I'll often deploy, debug, destroy & > redeploy that charm until I get it right. In my OpenStack > environment, each time I deploy a service, by default it provisions > a new machine

Re: JuJu, LXC, OpenStack charm problem w/Nova & Quantum

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18/03/14 05:35, Matt Rae wrote: > On Mon, Mar 17, 2014 at 7:04 AM, James Page > It would be interesting to know what are the blockers for this to >> work. Using the local provider has been very convenient and it >> would be nice to be able to deploy

Re: Juju stable 1.18.0 is released

Wow... that is a lot of changes in the 1.18 release. Sometimes as a developer you forget how much has been done. Cheers, Tim On 06/04/14 06:21, Curtis Hovey-Canonical wrote: > juju-core 1.18.0 > > A new stable release of Juju, juju-core 1.18.0, is now available. > This release replaces 1.16.6.

Re: Questions about the integration of the Outscale cloud provider into juju-core

k being done this cycle to switch from using storage > from the Provider to instead using our own internal storage. I > don't know that the work will be done for another few months, > though. I believe Tim Penhey is going to be leading up that work > as

The PostgreSQL charm, AWS and robustness

Hi folks, I'm writing not as a canonical core developer, but as a user who is occasionally stupid :-) I have a new project that I'm wanting to deploy and it is a django project backed with a postgresql database. Pretty simple really. I want to manage my deployment with Juju, but I want to manag

Re: The PostgreSQL charm, AWS and robustness

On 30/05/14 01:28, Patrick Hetu wrote: > I have a new project that I'm wanting to deploy and it is a django > project backed with a postgresql database. Pretty simple really. > > > If you plan to use the python-django charm be sure to use this branch: > > > https://code.launchpad.net/

Having trouble with the block-storage-broker and ec2

Hi folks, I'm attempting to get postgresql working on EC2 with the new block-storage-broker so the postgresql database can be stored on a persistent s3 device. https://manage.jujucharms.com/charms/precise/block-storage-broker I copied the basis of the bundle below from the docs above, however I'

Re: Having trouble with the block-storage-broker and ec2

On 07/06/14 00:29, Andreas Hasenack wrote: > On Fri, Jun 6, 2014 at 7:39 AM, Tim Penhey <mailto:tim.pen...@canonical.com>> wrote: > > options: > provider: ec2 > key: >

Re: Having trouble with the block-storage-broker and ec2

On 15/08/14 15:27, Charles Butler wrote: > Thread Necromancy, > > > Have we had any movement on this Tim? If not I'd like to file a bug to > move the BSP off of the euca2ools and instead use either the AWS SDK or > write API client wrappers for this. I've not done anything, but I'd agree that th

Re: Juju is still too hard

On 22/09/14 03:29, Michael Schwartz wrote: > > Guys, > > I hate to break this to you, but deploying and managing Juju is still > too hard and too unreliable. > > I hear this in the market, and my own experience confirms it. The two > times I tried, once on my local system, once on Azure, it didn

Re: Gluu Server Juju Charm

On 24/09/14 16:20, Michael Schwartz wrote: > Juju team, > > Thanks to Charles and José, I was able to get my local deployment of > Juju running, and later I was successful getting the Gluu Server and > Gluu OpenDJ charms installed, which is great progress. Good to hear. Tim -- Juju mailing li

Re: Juju devel 1.21-alpha2 is available

On 24/10/14 13:37, Curtis Hovey-Canonical wrote: > A new development release of Juju, juju-core 1.21-alpha2, is now > available. This release replaces 1.21-alpha1. > Multiple-user Support > > Juju now supports multiple people connecting to the environment with > their own identity and credentials.

Re: python-django charm questions

On 03/12/14 06:38, Simon Davy wrote: > On 2 December 2014 at 17:04, sheila miguez wrote: >> * Why is django_extra_settings used in config_changed but not during >> install? > > I expect that's a bug. The config_changed hook is called after the install hook when first installing. Tim -- Juju m

Re: feedback about juju after using it for a few months

On 18/12/14 11:24, Caio Begotti wrote: > Folks, I just wanted to share my experience with Juju during the last > few months using it for real at work. I know it's pretty long but stay > with me as I wanted to see if some of these points are bugs, design > decisions or if we could simply to talk abo

Re: Upcoming change in 1.24: tags in EC2

On 22/05/15 17:26, Andrew Wilkins wrote: > Hi all, > > Just a small announcement, in case anyone cares. In the EC2 provider, > from 1.24, we will start tagging instances and volumes with their > Juju-internal names and the Juju environment UUID. Instances, for > example, will have a name of "machi

problems working with bundletester

Hi folks, tl;dr: lots of problems with bundletester, ping me on IRC I have been spending several hours today trying to get bundletester working properly, and a clean environment from which to run it. Based on a clean trusty install, pip install bundletester fails. The build failed due to missin

Messaging to new users

I have been wondering for a while how we message to new users. I raise this because I see quite a few messages on stack overflow that go something like this: "I'm really new to Juju and I'm trying to set up MaaS." I feel that if we are getting to this, we are doing something wrong. Perhaps we

Re: Which JUJU_DEV_FEATURE_FLAG were used?

On 23/09/15 05:18, Andreas Hasenack wrote: > Hi, > > given an existing juju environment, is there a way to tell which > JUJU_DEV_FEATURE_FLAGs were used to bootstrap it? > > I'm using 1.24.6 The second line of logging in every agent lists the feature flags that the agent is using. As the agent

Re: ERROR cannot read info: lock timeout exceeded

On 26/09/15 22:02, Mark Shuttleworth wrote: > On 25/09/15 15:43, Tim Van Steenburgh wrote: >> >>> Generating separate JUJU_HOMEs will insulate your from bug >>> https://bugs.launchpad.net/juju-core/+bug/1467331 >> >> Thanks, I'm going to try this approach and see what happens. Although, it >> seems

Re: ERROR cannot read info: lock timeout exceeded

The code does just hold the lock for the duration of the read or write. Since it is possible to have multiple environments sharing a server, and the server data, the access to that data is synchronized. There *shouldn't* be a case where the lock is held but not released. The lock file itself sho

Re: ERROR cannot read info: lock timeout exceeded

ect > the lock and look for a process with the same PID as in the lock file > and if it doesn't exist break it automatically. This assumes all local > access, (so sharing $HOME over NFS is risky). > > John > =:-> > > > On Mon, Sep 28, 2015 at 12:42 AM, Tim Penhe

Re: ERROR cannot read info: lock timeout exceeded

I added a low-hanging fruit tech-debt card to the board. https://bugs.launchpad.net/juju-core/+bug/1500613 Tim On 29/09/15 09:50, Tim Penhey wrote: > The lock isn't there to guard against the same process, but other processes. > > I think a safer approach would be to look at th

Re: Juju 2.0~ Local LXD provider workflows are awesome!

On 04/02/16 02:23, Mark Shuttleworth wrote: > On 03/02/16 12:09, James Page wrote: >> juju create-model midonet-review >> juju switch midonet-review > > Thanks for the feedback James, it's great to see these bits coming > together so nicely :) > > Should we automatically switch to a new model

Re: Use of Jujucharms to launch non-opensource code

IANAL either, but if you are just using Juju and public charms to deploy a commercial project or product, then I think that is fine. Like deploying a private django app (which is what I do). This is just using the tools for what they were designed for. However, if you are modifying Juju source, an

Re: Logging into the API on Juju 2.0

On 01/03/16 03:48, Adam Stokes wrote: > Is there a way to list all models for a specific controller? Yes. > https://godoc.org/github.com/juju/juju/api/controller > and https://godoc.org/github.com/juju/juju/api/modelmanager seem to do > the same thing wrt listing models. This also only does it fo

Re: Logging into the API on Juju 2.0

te: > > > > On 01/03/16 11:25, Adam Stokes wrote: > > On Mon, Feb 29, 2016 at 7:24 PM, Tim Penhey > mailto:tim.pen...@canonical.com>> > > wrote: > > > >> On 01/03/16 03:48, Adam Stokes wrote: > >&

Re: Juju 2.0-beta9 ETA

Hi folks, Due to a change I landed without fully thinking through the implications, the reverting of said change has pushed us out a day. I was trying to add consistency to the wire-protocol that Juju uses by changing the serialisation names. Thinking that we were still in the "we don't need

Breaking API change landing for 2.0-beta10

Hi folks, This impacts all people calling the Juju API directly. If you use the juju client, you *should* be fine. Taking advantage of our time in "beta", we are adding consistency to the wire-protocol used by the juju client to talk to the juju apiserver. In general this means that all the

Re: Juju Secrets

On 25/07/16 06:32, James Beedy wrote: Proposed Solution: Juju Secrets To give Juju a combative edge on the privacy pinwheel of secrets distribution in the realm of bleeding edge devops tooling, behold my hypothetical proposed solution: |juju secrets|. Juju secrets could be used like so: |juju

Re: BDX <-> Juju

This sounds AMAZING!!! Great to hear Juju making a real difference. Thanks for sharing. Tim On 02/08/16 16:38, James Beedy wrote: Team, As some of you may know, I have taken on a new position as DevOps Engineer for a creative company -> CreativeDrive . CreativeDrive

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 use

Re: Feedback wanted: Changes to the Ubuntu Charm

Marco, This is awesome. I use the ubuntu charm all the time for testing, and seeing the workload version and workload status being set is pretty cool. I had hoped that seeing the "unknown" status would apply gentle pressure to get people to set a workload status. Winning!!! Tim On 15/09/1

Re: Increasing the size of VERSION in tabular status output

Yesterday we changed the limit to 15 from 7. Tim On 20/09/16 04:41, Rick Harding wrote: The primary trouble is that we really want to enforce a limit so that there's room for the arbitrary text at the end of the same line. I think we could try 10. I do think we need that hard cutoff. If you nee

Re: Proposal: display-name for charm metadata

+1 for optional 'display-name' field that doesn't have the naming restrictions of 'name' -1 for case insensitivity use as part of this work. Tim On 25/09/16 05:02, Marco Ceppi wrote: On Sat, Sep 24, 2016 at 11:34 AM Alex Kavanagh mailto:alex.kavan...@canonical.com>> wrote: Why not allow

Re: List plugins installed?

If we do that, then we can make the plug-in also install a metadata file that explains help and usage, so you don't call the script to do that. It makes it easy to list plug-ins, because you are searching a known location, and not the entire path. Only show plug-ins that have the appropriate m

Re: List plugins installed?

On Thu, Sep 29, 2016, 6:07 PM Tim Penhey mailto:tim.pen...@canonical.com>> wrote: If we do that, then we can make the plug-in also install a metadata file that explains help and usage, so you don't call the script to do that. It makes it easy to list plug-ins, because you

Re: Juju 2.0 is here!

I concur. You only have to use 1.25 for a short while again to see how far Juju has come. Be proud of your work, celebrate the release. Go team! Tim On 14/10/16 17:50, Mark Shuttleworth wrote: Congrats everyone, this is a release to be proud of. Multi-user multi-model, great CLI, it's a joy

Re: A (Very) Minimal Charm

Make sure you also run on LXD with a decent delay to the APT archive. That is what makes my local testing slow. Tim On 15/12/16 13:34, Marco Ceppi wrote: So, I wanted to circle back around to this thread. I think a lot of good feedback has come from this, and we're looking into making the reac

Re: Juju Snap Changes

Thanks Nicholas, Sounds awesome. Tim On 01/03/17 08:52, Nicholas Skaggs wrote: Those of you subscribed to a snap channel may have noticed some nice changes that happened with 2.1 release. The juju snap package now utilizes classic mode, and all channels (including stable) are now active. You s

Re: Constraints for Additional Units

On 17/03/17 14:23, James Beedy wrote: Currently, if I scale the units of my application, the new units do not have the same constraints as the previously deployed units. Well, I certainly think they should be carrying over the constraints as the constraints are set on the application, not the

PROPOSAL: stop recording 'executing update-status hook'

Hi folks, Currently juju will update the status of any hook execution for any unit to show that it is busy doing things. This was all well and good until we do things based on time. Every five minutes (or so) each unit will have the update-status hook executed to allow the unit to set or upd

Re: django charm broken or am I just doing it wrong?

05/17 04:15, John Meinel wrote: I believe Tim Penhey makes active use of the python-django charm, but it's possible he uses it in a different fashion. John =:-> On May 21, 2017 14:25, "Erik Lönroth" <mailto:erik.lonr...@gmail.com>> wrote: Hello! I'm tr

Re: PROPOSAL: stop recording 'executing update-status hook'

On 19/05/17 19:21, roger peppe wrote: On 19 May 2017 at 03:13, Tim Penhey wrote: Hi folks, Currently juju will update the status of any hook execution for any unit to show that it is busy doing things. This was all well and good until we do things based on time. Every five minutes (or so

Re: PROPOSAL: stop recording 'executing update-status hook'

On 20/05/17 19:48, Merlijn Sebrechts wrote: On May 20, 2017 09:05, "John Meinel" > wrote: I would actually prefer if it shows up in 'juju status' but that we suppress it from 'juju status-log' by default. This is still very strange behavior. Why should th

Re: We are excited to announce the release of Juju 2.2.1!

Yes indeed. Congratulations to the whole team. Tim On 23/06/17 23:35, Ante Karamatić wrote: > Congrats! > > Excellent release and some of our high profile users are already on > 2.2.1 as of now. The fact that one can just upgrade big > environments like that, while drinking coffee, speaks

Re: Upgrading juju2

On 13/06/17 04:25, Mario Splivalo wrote: > Hi, ladies and lads! > > I am verifying the juju upgrade procedure and I ran into some > ‘misunderstandings’ which I’m hoping could be clarified out here. > > I am running juju 2.0.0 and the plan is to upgrade it to the latest 2.1 > version, which is cur

Re: LXD bootstrap inside KVM failed

Yep, that is pretty strange. Why was bind running? Tim On 03/08/17 07:45, fengxia wrote: > For anyone, the solution is rather strange: > > $ sudo service stop bind9 > > $ sudo lxd start > > Reference: https://github.com/lxc/lxd/issues/2046 > > > On 08/02/2017 03:33 PM, fengxia wrote: >> Hi J

Re: We are excited to announce the release of Juju 2.2.3!

We are still getting the docs updated. https://jujucharms.com/docs/2.2/charms-bundles#setting-charm-configurations-options-in-a-bundle has a note about the include-file:// and include-base64:// items. We still seem to be missing details about --bundle-config. Tim On 08/09/17 22:41, Sandor Zeest

Juju 2.3 release train starting

Hi folks, We are gearing up to release Juju 2.3. Juju 2.3 brings two headline features: * Cross model relations - the ability to relate applications in different models * Persistent storage - storage can outlive the unit or model it was created for. The team will be releasing 2.3-beta1 tomorrow

Re: How to open port with juju when no application is instlaled?

I think you might be able to use: juju run postgresql/0 'open-port 80' Tim On 24/11/17 06:54, Akshat Jiwan Sharma wrote: > Hi, > > I've used juju to deploy postgres on aws. On the same machine I've > installed an nginx server manually (i.e without juju) that listens on > ports 80 and 443. I w

Re: Debug logs

What is the logging level for the model? The output from the hooks are logged at debug level. Tim On 26/11/17 13:25, Tom Barber wrote: > Maybe its just me, I dunno. > > Has the amount of detail in debug-logs decreased? > > I'm  not seeing failure causes for example: > > 2017-11-26 00:11:18 IN

Re: Juju 2.3-rc2 is here!

Hi Merlijn, You should be able to go: juju upgrade-juju -m controller That should do the trick. If the client version is different you may want to specify the agent version: juju upgrade-juju -m controller --agent-version 2.3-rc2 Tim On 07/12/17 06:26, Merlijn Sebrechts wrote: > Is there a

Beware 2.2.7 release

Hi folks, Last night we were alerted to a fundamental issue with the 2.2.7 agent only release. There was a weird race condition that was only observable on larger models which would cause a model to be non-responsive to controller generated events, like config updates, actions, juju run etc. We

Re: juju 2.3.3 failing to bootstrap localhost

How did you login to the container? It sounds like you may be missing SSH logins? Tim On 22/02/18 14:32, fengxia wrote: > Verified by login to the container. I could `apt update`, `apt install > htop`. > > At juju bootstrap terminal, I picked up this error message: > > 01:27:52 DEBUG juju.provi

Re: More juju upgrade-juju failings

Hi Daniel, The issue here is that you are upgrading the default model, not the controller model itself. I think we could make the error messaging more clear, and also have the command also check the controller version before showing a lot of baffling output. What you need to do is upgrade the co

Intro to Juju webinar in about 13 hours

Hi folks, I'm going to be presenting an Introduction to Juju on the BrightTALK platform tomorrow morning (my time). https://www.brighttalk.com/webcast/6793/298241 It is a high level introduction, nothing too technical, and ideal for someone that has no understanding of Juju wondering whether or

We are pulling he 2.3.6 agents

Hey people, We have field reports where a 2.3.6 upgrade interacted badly with some charm settings causing Juju to get itself into a stuck, somewhat corrupt state. We are still evaluating how to fix this for stuck systems. The symptom is the 2.3.6 upgrade fails and gets stuck. The agents are bein

Re: EC2 availability zones and bundles

I don't believe this is possible with bundles at the moment. The only placement directives that is currently supported in bundles are: new lxd:new lxd: kvm:new kvm: I *think* that is it. Tim On 16/06/18 05:57, George Kraft wrote: > Hey folks, > > Is there a way to assign units or

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

ows connection to the WWW, why doesn’t Juju, it > seems both reasonable and logical? I guess thats my expectation, > considering the containers need to apt-get etc. > > Juju is 2.3.7 > > Tom > > > On 26 June 2018 at 21:57:21, Tim Penhey (tim.pen...@canonical.com >

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 > <mailto:tim.pen...@can

Re: Aggregate all bundle.yaml | API endpoint

On 14/07/18 17:23, Ilias Tsoumas wrote: > Hello Mark, > > For the sake of clarification, let's try to explain my thoughts. I want > to understand if I can use juju's bundles as directed (acyclic) graphs. > Is there the information about direction? If no, do you propose to use > the bundles as undi

Moving conversations to discourse and closing this list.

Hi all, Juju is moving with the times and moving to have a central place for conversations, questions, and soon, documentation. We are using Discourse [1] and it can be found here: https://discourse.jujucharms.com/ Discourse offers a very nice interface for conversations, and has a bot walk y