Upcoming CLI change for beta15

Hi folks, We've just landed a change that will be part of beta15 which changes how you refer to models owned by other users. Model names may be reused by different users, e.g. alex and billie can each have a model called "foo". Until beta15, there is no way for either alex or billie to refer to

Re: Let's talk retries

On 9 August 2016 at 12:22, Katherine Cox-Buday < katherine.cox-bu...@canonical.com> wrote: > > To implement this, I do something like this: > > args := retry.CallArgs{ > Func: func() error { > // Body of my loop > }, > BackoffFunc: func(delay time.Duration, attempt int)

Let's talk retries

Hey All, We currently have 3 ways we're performing retries in Juju: 1. Archaic, custom, intra-package retry code. 2. github.com/juju/utils::{Countdown,BackoffTimer} 3. github.com/juju/retry (current best practice) I have just touched some code which fits #1, and when I was attempting to

Re: Juju and snappy implementation spike - feedback please

On Mon, Aug 8, 2016 at 11:49 AM, John Meinel wrote: > If we are installing in '--devmode' don't we have access to the unfiltered > $HOME directory if we look for it? And we could ask for an interface which > is to JUJU_HOME that would give us access to just

Re: 2.0 as default on main repos?

Matt... Yes.. I did that.. so far mine install 2.0 beta 12. I thought 13 is latest. thanks. On Mon, Aug 8, 2016 at 2:34 PM, Matt Bruzek wrote: > Hi Steve, > > If you have not installed any of the older packages the commands are > simple: > > sudo

Re: 2.0 as default on main repos?

Hi Steve, If you have not installed any of the older packages the commands are simple: sudo add-apt-repository ppa:juju/develsudo apt updatesudo apt install juju As always, please refer to the documentation when it comes to installation instructions:

Re: 2.0 as default on main repos?

Hi Steve, If you have not installed any of the older packages the commands are simple: sudo add-apt-repository ppa:juju/develsudo apt updatesudo apt install juju As always, please refer to the documentation when it comes to installation instructions:

Re: 2.0 as default on main repos?

I'm newbi what is command to install latest beta version of Juju on ubuntu? thx On Mon, Aug 8, 2016 at 12:23 PM, Rick Harding wrote: > Thanks for the feedback Jose. Merlijn also brought up a similar note and I > replied on the main juju list to help explain the

Re: 2.0 as default on main repos?

Thanks for the feedback Jose. Merlijn also brought up a similar note and I replied on the main juju list to help explain the current pain window we're working through. Rather than copy/paste you can see it here: https://lists.ubuntu.com/archives/juju/2016-August/007679.html Please let me know if

Re: 2.0 as default on main repos?

Thanks for the feedback Jose. Merlijn also brought up a similar note and I replied on the main juju list to help explain the current pain window we're working through. Rather than copy/paste you can see it here: https://lists.ubuntu.com/archives/juju/2016-August/007679.html Please let me know if

Re: The move to 2.0 gives the wrong impression to new users

Merlijn, nothing at all to apologize for. It's not nitpicking and is a very true pain point right now. Originally we had planned to have Juju 2.0 out in Xenial and the default. Xenial is due to be supported for five years and so there were calls we needed to make to set us up for success looking

Re: Juju and snappy implementation spike - feedback please

If we are installing in '--devmode' don't we have access to the unfiltered $HOME directory if we look for it? And we could ask for an interface which is to JUJU_HOME that would give us access to just $HOME/.local/share/juju We could then copy that information into the normal 'home' directory of

Re: 2.0 as default on main repos?

Hey Matt, Thanks for the link. If anyone reading has a way to help get it fixed, please do so. This is a horrible bug that causes inconsistencies, and until 2.0 is released it should not be in main. On Mon, Aug 8, 2016, 09:22 Matt Bruzek wrote: > Hello José, > >

Re: 2.0 as default on main repos?

Hello José, I ran into this problem myself and filed a bug with the packaging. https://bugs.launchpad.net/juju-release-tools/+bug/1609437 While I still think this is a bug, I did find a work around which I put in the bug for other people having this same problem. Hope that helps! - Matt

Re: 2.0 as default on main repos?

Hello José, I ran into this problem myself and filed a bug with the packaging. https://bugs.launchpad.net/juju-release-tools/+bug/1609437 While I still think this is a bug, I did find a work around which I put in the bug for other people having this same problem. Hope that helps! - Matt

Re: How to register Mr.Smiths, em, agents to IdM

Well that clears that up :) Thanks! On Mon, Aug 8, 2016 at 8:10 AM Uros Jovanovic wrote: > Hi Charles, all, > > This was sent to a wrong "j-tab" recipient. Sorry for spamming the list. > > > On Monday, 8 August 2016, Charles Butler >

Re: How to register Mr.Smiths, em, agents to IdM

Hi Charles, all, This was sent to a wrong "j-tab" recipient. Sorry for spamming the list. On Monday, 8 August 2016, Charles Butler wrote: > Greetings Uros, > > I don't mean to be daft, but what is this? At first glance, it looks like > adding a user to a

Juju and snappy implementation spike - feedback please

Hi folks The below refers to work in a branch, not committed to master. TL:DR; I've made some changes to Juju so that a custom build can be easily snapped and shared. The snap is still required to be run in devmode until new interfaces are done. TL;DR2; The way upload-tools works has been

Re: How to register Mr.Smiths, em, agents to IdM

Greetings Uros, I don't mean to be daft, but what is this? At first glance, it looks like adding a user to a controller? But it feels like there's some missing help text around this, as to what it's doing, and when I would want to do this. Also don't we have commands already to add a user to a

Re: Hung up post 2.0 upgrade? juju-unregister to the rescue!

On Mon, Aug 8, 2016 at 9:50 AM, Charles Butler wrote: > Greetings! > > I was in #juju riffing with some juju users, and it became apparent that > there is a not-so-well-known feature of juju in the 2.0+ series. > > As 2.0 is not marked as stable, every new release

Re: Hung up post 2.0 upgrade? juju-unregister to the rescue!

Adding heat to https://bugs.launchpad.net/juju-core/+bug/1607303 welcomed. On Mon, 8 Aug 2016 at 13:50 Charles Butler wrote: > Greetings! > > I was in #juju riffing with some juju users, and it became apparent that > there is a not-so-well-known feature of juju in

Hung up post 2.0 upgrade? juju-unregister to the rescue!

Greetings! I was in #juju riffing with some juju users, and it became apparent that there is a not-so-well-known feature of juju in the 2.0+ series. As 2.0 is not marked as stable, every new release is treated like an island. Sometimes it may be compatible with what you have deployed (eg beta-12

The move to 2.0 gives the wrong impression to new users

Hi all I think that the way the move to Juju 2.0 is being handled gives the wrong impression to (new) users. Some examples: - The docs default to Juju 2.0 but show a big red warning banner that 2.0 isn't ready for production. A user reading the warning banner might think "This isn't

Re: juju @ conjure-up on Power8 , Free Trial on SoftLayer

Thanks John & Adam, I think u already mention to me in the IRC that conjure-up will not work n require xenial only. But I just want to used juju 1.0 and lxc to deploy the charms. 1st bootstrap working but when I want to deploy juju-gui charms, "juju status --format=tabular" showing error On

Re: juju @ conjure-up on Power8 , Free Trial on SoftLayer

Conjure-up is Juju 2.0, MAAS 2.0, and Xenial only. You will need to use the previous openstack-installer if on trusty. Also if KVM is not supported on power you'll need to use a different virt-type for nova-compute. On Mon, Aug 8, 2016, 6:23 AM John Meinel wrote: > I

Re: juju @ conjure-up on Power8 , Free Trial on SoftLayer

I don't know if conjure-up supports Juju 1.0. In 1.0 the setting was in environments.yaml as 'default-series'. So something like: environments: power8: type: ? default-series: trusty My memory is a bit hazy there, but that's roughly what I remember. John =:-> On Mon, Aug 8, 2016 at

Re: juju @ conjure-up on Power8 , Free Trial on SoftLayer

Thanks John for the advise. fenris@bigsoftware:~$ juju --version 1.25.5-trusty-ppc64el fenris@bigsoftware:~$ juju bootstrap --bootstrap-series=trusty error: flag provided but not defined: --bootstrap-series On Mon, Aug 8, 2016 at 1:59 PM, John Meinel wrote: > You need

Re: juju @ conjure-up on Power8 , Free Trial on SoftLayer

You need Xenial if you want to use MAAS 2.0, but Juju can deploy to Trusty just fine. I'm not sure about kvm_intel, but you can do "juju bootstrap --bootstrap-series=trusty" to get a Trusty Controller, and then 'juju deploy --series trusty APP" to select a Trusty series there as well. John =:->