Re: Juju 2.0-rc3 is here!

[Mark Shuttleworth]

On 07/10/16 13:59, Curtis Hovey-Canonical wrote:
> Tell the juju controller to use devel streams. Eg, to upgrade my own
> deployment, I I set the streams to devel, then upgrade the controller
> than the hosted model. 

Guys, there should be no devel streams in 2.0.

One stream, with all releases, *tagged* so you don't upgrade to a beta
unless you are already on one.

Mark

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Juju 2.0-rc3 is here!

[Mark Shuttleworth]

On 07/10/16 13:59, Curtis Hovey-Canonical wrote:
> Tell the juju controller to use devel streams. Eg, to upgrade my own
> deployment, I I set the streams to devel, then upgrade the controller
> than the hosted model. 

Guys, there should be no devel streams in 2.0.

One stream, with all releases, *tagged* so you don't upgrade to a beta
unless you are already on one.

Mark

-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Juju 2.0-rc3 is here!

[Mark Shuttleworth]

On 07/10/16 11:49, Adam Israel wrote:
> One potential way to display the information, using existing
> whitespace so we're not changing the overall layout.
>
> http://pastebin.ubuntu.com/23290044/

Yeah, I like that, Though I would do it as:

Unit (*leader)  Workload  ...

If we're touching that code, could we convert tables to Capital Case
Headers please?

Mark

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Juju 2.0-rc3 is here!

[Mark Shuttleworth]

On 07/10/16 11:49, Adam Israel wrote:
> One potential way to display the information, using existing
> whitespace so we're not changing the overall layout.
>
> http://pastebin.ubuntu.com/23290044/

Yeah, I like that, Though I would do it as:

Unit (*leader)  Workload  ...

If we're touching that code, could we convert tables to Capital Case
Headers please?

Mark

-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Juju 2.0-rc3 is here!

[Matt Rae]

Thanks Curtis! following your steps and setting the agent-stream=devel, I
was able to upgrade the controller and default models to rc3

Matt

On Fri, Oct 7, 2016 at 1:59 PM, Curtis Hovey-Canonical  wrote:

> Hi Matt,
>
> You, and several of us, are victims of '"upload-tools strikes back"
> cannot upgrade with streams'
> https://bugs.launchpad.net/juju/+bug/1631529
>
> On Fri, Oct 7, 2016 at 1:51 PM, Matt Rae  wrote:
> > Hi, I'm testing an upgrade between juju 2.0 rc2 and rc3.
> >
> > Should 'juju upgrade-juju -m default' upgrade to rc3?
> >
> > So far I'm seeing 'no upgrades available'
> >
> > $ juju model-config agent-version
> > 2.0-rc2
> > $ juju --version
> > 2.0-rc3-xenial-amd64
> > $ juju upgrade-juju
> > no upgrades available
> > $ juju upgrade-juju --agent-version 2.0-rc3
> > ERROR no matching tools available
>
> Do you see this:
> $ juju model-config -m controller agent-stream
> released
>
> ^ No, the juju client selected devel streams without telling the controller
>
> WORK AROUND
>
> Tell the juju controller to use devel streams. Eg, to upgrade my own
> deployment, I I set the streams to devel, then upgrade the controller
> than the hosted model.
>
> $ juju model-config -m controller agent-stream=devel
> $ juju upgrade-juju -m controller
> started upgrade to 2.0-rc3
> $ juju upgrade-juju -m default
> started upgrade to 2.0-rc3
>
> When 2.0.0 is released, switch the streams to released.
> $ juju model-config -m controller agent-stream=released
>
> Then upgrade as normal.
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Juju 2.0-rc3 is here!

[Curtis Hovey-Canonical]

Hi Matt,

You, and several of us, are victims of '"upload-tools strikes back"
cannot upgrade with streams'
https://bugs.launchpad.net/juju/+bug/1631529

On Fri, Oct 7, 2016 at 1:51 PM, Matt Rae  wrote:
> Hi, I'm testing an upgrade between juju 2.0 rc2 and rc3.
>
> Should 'juju upgrade-juju -m default' upgrade to rc3?
>
> So far I'm seeing 'no upgrades available'
>
> $ juju model-config agent-version
> 2.0-rc2
> $ juju --version
> 2.0-rc3-xenial-amd64
> $ juju upgrade-juju
> no upgrades available
> $ juju upgrade-juju --agent-version 2.0-rc3
> ERROR no matching tools available

Do you see this:
$ juju model-config -m controller agent-stream
released

^ No, the juju client selected devel streams without telling the controller

WORK AROUND

Tell the juju controller to use devel streams. Eg, to upgrade my own
deployment, I I set the streams to devel, then upgrade the controller
than the hosted model.

$ juju model-config -m controller agent-stream=devel
$ juju upgrade-juju -m controller
started upgrade to 2.0-rc3
$ juju upgrade-juju -m default
started upgrade to 2.0-rc3

When 2.0.0 is released, switch the streams to released.
$ juju model-config -m controller agent-stream=released

Then upgrade as normal.

-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Juju 2.0-rc3 is here!

[Curtis Hovey-Canonical]

Hi Matt,

You, and several of us, are victims of '"upload-tools strikes back"
cannot upgrade with streams'
https://bugs.launchpad.net/juju/+bug/1631529

On Fri, Oct 7, 2016 at 1:51 PM, Matt Rae  wrote:
> Hi, I'm testing an upgrade between juju 2.0 rc2 and rc3.
>
> Should 'juju upgrade-juju -m default' upgrade to rc3?
>
> So far I'm seeing 'no upgrades available'
>
> $ juju model-config agent-version
> 2.0-rc2
> $ juju --version
> 2.0-rc3-xenial-amd64
> $ juju upgrade-juju
> no upgrades available
> $ juju upgrade-juju --agent-version 2.0-rc3
> ERROR no matching tools available

Do you see this:
$ juju model-config -m controller agent-stream
released

^ No, the juju client selected devel streams without telling the controller

WORK AROUND

Tell the juju controller to use devel streams. Eg, to upgrade my own
deployment, I I set the streams to devel, then upgrade the controller
than the hosted model.

$ juju model-config -m controller agent-stream=devel
$ juju upgrade-juju -m controller
started upgrade to 2.0-rc3
$ juju upgrade-juju -m default
started upgrade to 2.0-rc3

When 2.0.0 is released, switch the streams to released.
$ juju model-config -m controller agent-stream=released

Then upgrade as normal.

-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui

-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Juju 2.0-rc3 is here!

[Adam Israel]

One potential way to display the information, using existing whitespace so
we're not changing the overall layout.

http://pastebin.ubuntu.com/23290044/


On Fri, Oct 7, 2016 at 10:52 AM Adam Israel 
wrote:

> That's a great piece of information to relay to the user. Is there a way
> we can better communicate what it represents in the tabular status output?
>
> On Fri, Oct 7, 2016 at 10:08 AM Mark Shuttleworth  wrote:
>
> On 07/10/16 09:58, Adam Israel wrote:
> > It looks like rc3 introduced a minor change in the status output. Each
> > unit has an asterisk next to its name, i.e., mariadb/0* (full output
> > in pastebin). What is the asterisk meant to represent?
> >
> > http://pastebin.ubuntu.com/23289710/
>
> I believe thats leadership election in the application.
>
> --
> Adam Israel, Software Engineer
> Canonical // Cloud DevOps // Juju // Ecosystem
>
-- 
Adam Israel, Software Engineer
Canonical // Cloud DevOps // Juju // Ecosystem
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Juju 2.0-rc3 is here!

[Adam Israel]

One potential way to display the information, using existing whitespace so
we're not changing the overall layout.

http://pastebin.ubuntu.com/23290044/


On Fri, Oct 7, 2016 at 10:52 AM Adam Israel 
wrote:

> That's a great piece of information to relay to the user. Is there a way
> we can better communicate what it represents in the tabular status output?
>
> On Fri, Oct 7, 2016 at 10:08 AM Mark Shuttleworth  wrote:
>
> On 07/10/16 09:58, Adam Israel wrote:
> > It looks like rc3 introduced a minor change in the status output. Each
> > unit has an asterisk next to its name, i.e., mariadb/0* (full output
> > in pastebin). What is the asterisk meant to represent?
> >
> > http://pastebin.ubuntu.com/23289710/
>
> I believe thats leadership election in the application.
>
> --
> Adam Israel, Software Engineer
> Canonical // Cloud DevOps // Juju // Ecosystem
>
-- 
Adam Israel, Software Engineer
Canonical // Cloud DevOps // Juju // Ecosystem
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Juju 2.0-rc3 is here!

[Curtis Hovey-Canonical]

> A new development release of Juju, 2.0-rc3, is here!
...
> ## How do I get it?

You can now install the Juju 2.0-rc3 snap.

snap install juju --beta --devmode

^ This is the 2.0-rc3. Juju requires requires confinement: devmode,
which restricts our RCs and stables to the beta channel :(

-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui

-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Juju 2.0-rc3 is here!

[Matt Rae]

Hi, I'm testing an upgrade between juju 2.0 rc2 and rc3.

Should 'juju upgrade-juju -m default' upgrade to rc3?

So far I'm seeing 'no upgrades available'

$ juju model-config agent-version
2.0-rc2
$ juju --version
2.0-rc3-xenial-amd64
$ juju upgrade-juju
no upgrades available
$ juju upgrade-juju --agent-version 2.0-rc3
ERROR no matching tools available

Matt



On Fri, Oct 7, 2016 at 10:07 AM, Christian Muirhead <
christian.muirh...@canonical.com> wrote:

> It indicates that that unit is the leader for the application. It's a bit
> academic in the status you pasted, since each application only has one
> unit, but I can see it being useful if you had scaled out a bit.
>
> Cheers,
> Christian
>
> On Fri, Oct 7, 2016 at 5:59 PM Adam Israel <adam.isr...@canonical.com>
> wrote:
>
>> It looks like rc3 introduced a minor change in the status output. Each
>> unit has an asterisk next to its name, i.e., mariadb/0* (full output in
>> pastebin). What is the asterisk meant to represent?
>>
>> http://pastebin.ubuntu.com/23289710/
>>
>> On Thu, Oct 6, 2016 at 5:28 PM Andrew Wilkins <
>> andrew.wilk...@canonical.com> wrote:
>>
>> On Fri, Oct 7, 2016 at 6:15 AM Curtis Hovey-Canonical <
>> cur...@canonical.com> wrote:
>>
>> A new development release of Juju, 2.0-rc3, is here!
>>
>>
>> ## What's new?
>>
>> * For an AWS VPC account juju will create a t2.medium for controller
>>   instances by default now. Non-controller instances are unchanged for
>>   now, and remain m3.medium by default. Controller instance root disk
>>   now defaults to 32GiB, but can be overridden with constraints.
>> * Shorten the hostnames we apply to instances created by the OpenStack
>>   provider.
>> Example old hostname:
>> juju-fd943864-df2e-4da1-8e7d-5116a87d4e7c-machine-14
>>
>> Example new hostname:
>> Juju-df7591-controller-0
>> * Added support for LXD 2.3 apis
>> * New update-credential command
>> * Added --model-default option to the bootstrap
>> * LXD containers now have proper hostnames set
>>
>>
>> Also, support for the aws/ap-south-1 region has been added.
>>
>> Adam Stokes just found a bug related to this, which prevented him from
>> being able to destroy his rc2 controller with an rc3 client. I'll fix this
>> for 2.0, but in the mean time I recommend you destroy your controller
>> before upgrading the client.
>>
>> If you do upgrade the client, then you will need to modify
>> ~/.local/share/juju/bootstrap-config.yaml, fixing the endpoint cached in
>> there. You can find the correct value by running "juju show-cloud aws", and
>> picking out the value associated with the region you bootstrapped.
>>
>> Cheers,
>> Andrew
>>
>>
>> ## How do I get it?
>>
>> If you are running Ubuntu, you can get it from the juju devel ppa:
>>
>> sudo add-apt-repository ppa:juju/devel
>> sudo apt-get update; sudo apt-get install juju-2.0
>>
>> Windows, Centos, and MacOS users can get a corresponding installer at:
>>
>> https://launchpad.net/juju/+milestone/2.0-rc3
>>
>>
>> ## Feedback Appreciated!
>>
>> We encourage everyone to subscribe the mailing list at
>> juju@lists.ubuntu.com and join us on #juju on freenode. We would love to
>> hear
>> your feedback and usage of juju.
>>
>>
>> ## Anything else?
>>
>> You can read more information about what's in this release by viewing the
>> release notes here:
>>
>> https://jujucharms.com/docs/devel/temp-release-notes
>>
>>
>> --
>> Curtis Hovey
>> Canonical Cloud Development and Operations
>> http://launchpad.net/~sinzui
>>
>> --
>> Juju-dev mailing list
>> juju-...@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/
>> mailman/listinfo/juju-dev
>>
>> --
>> Juju-dev mailing list
>> juju-...@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/
>> mailman/listinfo/juju-dev
>>
>> --
>> Adam Israel, Software Engineer
>> Canonical // Cloud DevOps // Juju // Ecosystem
>> --
>> Juju-dev mailing list
>> juju-...@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/
>> mailman/listinfo/juju-dev
>>
>
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju-dev
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Juju 2.0-rc3 is here!

[Adam Israel]

That's a great piece of information to relay to the user. Is there a way we
can better communicate what it represents in the tabular status output?

On Fri, Oct 7, 2016 at 10:08 AM Mark Shuttleworth  wrote:

> On 07/10/16 09:58, Adam Israel wrote:
> > It looks like rc3 introduced a minor change in the status output. Each
> > unit has an asterisk next to its name, i.e., mariadb/0* (full output
> > in pastebin). What is the asterisk meant to represent?
> >
> > http://pastebin.ubuntu.com/23289710/
>
> I believe thats leadership election in the application.
>
-- 
Adam Israel, Software Engineer
Canonical // Cloud DevOps // Juju // Ecosystem
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Juju 2.0-rc3 is here!

[Matt Rae]

Hi, I'm testing an upgrade between juju 2.0 rc2 and rc3.

Should 'juju upgrade-juju -m default' upgrade to rc3?

So far I'm seeing 'no upgrades available'

$ juju model-config agent-version
2.0-rc2
$ juju --version
2.0-rc3-xenial-amd64
$ juju upgrade-juju
no upgrades available
$ juju upgrade-juju --agent-version 2.0-rc3
ERROR no matching tools available

Matt



On Fri, Oct 7, 2016 at 10:07 AM, Christian Muirhead <
christian.muirh...@canonical.com> wrote:

> It indicates that that unit is the leader for the application. It's a bit
> academic in the status you pasted, since each application only has one
> unit, but I can see it being useful if you had scaled out a bit.
>
> Cheers,
> Christian
>
> On Fri, Oct 7, 2016 at 5:59 PM Adam Israel <adam.isr...@canonical.com>
> wrote:
>
>> It looks like rc3 introduced a minor change in the status output. Each
>> unit has an asterisk next to its name, i.e., mariadb/0* (full output in
>> pastebin). What is the asterisk meant to represent?
>>
>> http://pastebin.ubuntu.com/23289710/
>>
>> On Thu, Oct 6, 2016 at 5:28 PM Andrew Wilkins <
>> andrew.wilk...@canonical.com> wrote:
>>
>> On Fri, Oct 7, 2016 at 6:15 AM Curtis Hovey-Canonical <
>> cur...@canonical.com> wrote:
>>
>> A new development release of Juju, 2.0-rc3, is here!
>>
>>
>> ## What's new?
>>
>> * For an AWS VPC account juju will create a t2.medium for controller
>>   instances by default now. Non-controller instances are unchanged for
>>   now, and remain m3.medium by default. Controller instance root disk
>>   now defaults to 32GiB, but can be overridden with constraints.
>> * Shorten the hostnames we apply to instances created by the OpenStack
>>   provider.
>> Example old hostname:
>> juju-fd943864-df2e-4da1-8e7d-5116a87d4e7c-machine-14
>>
>> Example new hostname:
>> Juju-df7591-controller-0
>> * Added support for LXD 2.3 apis
>> * New update-credential command
>> * Added --model-default option to the bootstrap
>> * LXD containers now have proper hostnames set
>>
>>
>> Also, support for the aws/ap-south-1 region has been added.
>>
>> Adam Stokes just found a bug related to this, which prevented him from
>> being able to destroy his rc2 controller with an rc3 client. I'll fix this
>> for 2.0, but in the mean time I recommend you destroy your controller
>> before upgrading the client.
>>
>> If you do upgrade the client, then you will need to modify
>> ~/.local/share/juju/bootstrap-config.yaml, fixing the endpoint cached in
>> there. You can find the correct value by running "juju show-cloud aws", and
>> picking out the value associated with the region you bootstrapped.
>>
>> Cheers,
>> Andrew
>>
>>
>> ## How do I get it?
>>
>> If you are running Ubuntu, you can get it from the juju devel ppa:
>>
>> sudo add-apt-repository ppa:juju/devel
>> sudo apt-get update; sudo apt-get install juju-2.0
>>
>> Windows, Centos, and MacOS users can get a corresponding installer at:
>>
>> https://launchpad.net/juju/+milestone/2.0-rc3
>>
>>
>> ## Feedback Appreciated!
>>
>> We encourage everyone to subscribe the mailing list at
>> j...@lists.ubuntu.com and join us on #juju on freenode. We would love to
>> hear
>> your feedback and usage of juju.
>>
>>
>> ## Anything else?
>>
>> You can read more information about what's in this release by viewing the
>> release notes here:
>>
>> https://jujucharms.com/docs/devel/temp-release-notes
>>
>>
>> --
>> Curtis Hovey
>> Canonical Cloud Development and Operations
>> http://launchpad.net/~sinzui
>>
>> --
>> Juju-dev mailing list
>> Juju-dev@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/
>> mailman/listinfo/juju-dev
>>
>> --
>> Juju-dev mailing list
>> Juju-dev@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/
>> mailman/listinfo/juju-dev
>>
>> --
>> Adam Israel, Software Engineer
>> Canonical // Cloud DevOps // Juju // Ecosystem
>> --
>> Juju-dev mailing list
>> Juju-dev@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/
>> mailman/listinfo/juju-dev
>>
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju-dev
>
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Juju 2.0-rc3 is here!

[Mark Shuttleworth]

On 07/10/16 09:58, Adam Israel wrote:
> It looks like rc3 introduced a minor change in the status output. Each
> unit has an asterisk next to its name, i.e., mariadb/0* (full output
> in pastebin). What is the asterisk meant to represent?
>
> http://pastebin.ubuntu.com/23289710/

I believe thats leadership election in the application.

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Juju 2.0-rc3 is here!

[Mark Shuttleworth]

On 07/10/16 09:58, Adam Israel wrote:
> It looks like rc3 introduced a minor change in the status output. Each
> unit has an asterisk next to its name, i.e., mariadb/0* (full output
> in pastebin). What is the asterisk meant to represent?
>
> http://pastebin.ubuntu.com/23289710/

I believe thats leadership election in the application.

-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Juju 2.0-rc3 is here!

[Christian Muirhead]

It indicates that that unit is the leader for the application. It's a bit
academic in the status you pasted, since each application only has one
unit, but I can see it being useful if you had scaled out a bit.

Cheers,
Christian

On Fri, Oct 7, 2016 at 5:59 PM Adam Israel <adam.isr...@canonical.com>
wrote:

> It looks like rc3 introduced a minor change in the status output. Each
> unit has an asterisk next to its name, i.e., mariadb/0* (full output in
> pastebin). What is the asterisk meant to represent?
>
> http://pastebin.ubuntu.com/23289710/
>
> On Thu, Oct 6, 2016 at 5:28 PM Andrew Wilkins <
> andrew.wilk...@canonical.com> wrote:
>
> On Fri, Oct 7, 2016 at 6:15 AM Curtis Hovey-Canonical <
> cur...@canonical.com> wrote:
>
> A new development release of Juju, 2.0-rc3, is here!
>
>
> ## What's new?
>
> * For an AWS VPC account juju will create a t2.medium for controller
>   instances by default now. Non-controller instances are unchanged for
>   now, and remain m3.medium by default. Controller instance root disk
>   now defaults to 32GiB, but can be overridden with constraints.
> * Shorten the hostnames we apply to instances created by the OpenStack
>   provider.
> Example old hostname:
> juju-fd943864-df2e-4da1-8e7d-5116a87d4e7c-machine-14
>
> Example new hostname:
> Juju-df7591-controller-0
> * Added support for LXD 2.3 apis
> * New update-credential command
> * Added --model-default option to the bootstrap
> * LXD containers now have proper hostnames set
>
>
> Also, support for the aws/ap-south-1 region has been added.
>
> Adam Stokes just found a bug related to this, which prevented him from
> being able to destroy his rc2 controller with an rc3 client. I'll fix this
> for 2.0, but in the mean time I recommend you destroy your controller
> before upgrading the client.
>
> If you do upgrade the client, then you will need to modify
> ~/.local/share/juju/bootstrap-config.yaml, fixing the endpoint cached in
> there. You can find the correct value by running "juju show-cloud aws", and
> picking out the value associated with the region you bootstrapped.
>
> Cheers,
> Andrew
>
>
> ## How do I get it?
>
> If you are running Ubuntu, you can get it from the juju devel ppa:
>
> sudo add-apt-repository ppa:juju/devel
> sudo apt-get update; sudo apt-get install juju-2.0
>
> Windows, Centos, and MacOS users can get a corresponding installer at:
>
> https://launchpad.net/juju/+milestone/2.0-rc3
>
>
> ## Feedback Appreciated!
>
> We encourage everyone to subscribe the mailing list at
> juju@lists.ubuntu.com and join us on #juju on freenode. We would love to
> hear
> your feedback and usage of juju.
>
>
> ## Anything else?
>
> You can read more information about what's in this release by viewing the
> release notes here:
>
> https://jujucharms.com/docs/devel/temp-release-notes
>
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
> --
> Adam Israel, Software Engineer
> Canonical // Cloud DevOps // Juju // Ecosystem
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Juju 2.0-rc3 is here!

[Christian Muirhead]

It indicates that that unit is the leader for the application. It's a bit
academic in the status you pasted, since each application only has one
unit, but I can see it being useful if you had scaled out a bit.

Cheers,
Christian

On Fri, Oct 7, 2016 at 5:59 PM Adam Israel <adam.isr...@canonical.com>
wrote:

> It looks like rc3 introduced a minor change in the status output. Each
> unit has an asterisk next to its name, i.e., mariadb/0* (full output in
> pastebin). What is the asterisk meant to represent?
>
> http://pastebin.ubuntu.com/23289710/
>
> On Thu, Oct 6, 2016 at 5:28 PM Andrew Wilkins <
> andrew.wilk...@canonical.com> wrote:
>
> On Fri, Oct 7, 2016 at 6:15 AM Curtis Hovey-Canonical <
> cur...@canonical.com> wrote:
>
> A new development release of Juju, 2.0-rc3, is here!
>
>
> ## What's new?
>
> * For an AWS VPC account juju will create a t2.medium for controller
>   instances by default now. Non-controller instances are unchanged for
>   now, and remain m3.medium by default. Controller instance root disk
>   now defaults to 32GiB, but can be overridden with constraints.
> * Shorten the hostnames we apply to instances created by the OpenStack
>   provider.
> Example old hostname:
> juju-fd943864-df2e-4da1-8e7d-5116a87d4e7c-machine-14
>
> Example new hostname:
> Juju-df7591-controller-0
> * Added support for LXD 2.3 apis
> * New update-credential command
> * Added --model-default option to the bootstrap
> * LXD containers now have proper hostnames set
>
>
> Also, support for the aws/ap-south-1 region has been added.
>
> Adam Stokes just found a bug related to this, which prevented him from
> being able to destroy his rc2 controller with an rc3 client. I'll fix this
> for 2.0, but in the mean time I recommend you destroy your controller
> before upgrading the client.
>
> If you do upgrade the client, then you will need to modify
> ~/.local/share/juju/bootstrap-config.yaml, fixing the endpoint cached in
> there. You can find the correct value by running "juju show-cloud aws", and
> picking out the value associated with the region you bootstrapped.
>
> Cheers,
> Andrew
>
>
> ## How do I get it?
>
> If you are running Ubuntu, you can get it from the juju devel ppa:
>
> sudo add-apt-repository ppa:juju/devel
> sudo apt-get update; sudo apt-get install juju-2.0
>
> Windows, Centos, and MacOS users can get a corresponding installer at:
>
> https://launchpad.net/juju/+milestone/2.0-rc3
>
>
> ## Feedback Appreciated!
>
> We encourage everyone to subscribe the mailing list at
> j...@lists.ubuntu.com and join us on #juju on freenode. We would love to
> hear
> your feedback and usage of juju.
>
>
> ## Anything else?
>
> You can read more information about what's in this release by viewing the
> release notes here:
>
> https://jujucharms.com/docs/devel/temp-release-notes
>
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
> --
> Adam Israel, Software Engineer
> Canonical // Cloud DevOps // Juju // Ecosystem
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Juju 2.0-rc3 is here!

[Adam Israel]

It looks like rc3 introduced a minor change in the status output. Each unit
has an asterisk next to its name, i.e., mariadb/0* (full output in
pastebin). What is the asterisk meant to represent?

http://pastebin.ubuntu.com/23289710/

On Thu, Oct 6, 2016 at 5:28 PM Andrew Wilkins <andrew.wilk...@canonical.com>
wrote:

> On Fri, Oct 7, 2016 at 6:15 AM Curtis Hovey-Canonical <
> cur...@canonical.com> wrote:
>
> A new development release of Juju, 2.0-rc3, is here!
>
>
> ## What's new?
>
> * For an AWS VPC account juju will create a t2.medium for controller
>   instances by default now. Non-controller instances are unchanged for
>   now, and remain m3.medium by default. Controller instance root disk
>   now defaults to 32GiB, but can be overridden with constraints.
> * Shorten the hostnames we apply to instances created by the OpenStack
>   provider.
> Example old hostname:
> juju-fd943864-df2e-4da1-8e7d-5116a87d4e7c-machine-14
>
> Example new hostname:
> Juju-df7591-controller-0
> * Added support for LXD 2.3 apis
> * New update-credential command
> * Added --model-default option to the bootstrap
> * LXD containers now have proper hostnames set
>
>
> Also, support for the aws/ap-south-1 region has been added.
>
> Adam Stokes just found a bug related to this, which prevented him from
> being able to destroy his rc2 controller with an rc3 client. I'll fix this
> for 2.0, but in the mean time I recommend you destroy your controller
> before upgrading the client.
>
> If you do upgrade the client, then you will need to modify
> ~/.local/share/juju/bootstrap-config.yaml, fixing the endpoint cached in
> there. You can find the correct value by running "juju show-cloud aws", and
> picking out the value associated with the region you bootstrapped.
>
> Cheers,
> Andrew
>
>
> ## How do I get it?
>
> If you are running Ubuntu, you can get it from the juju devel ppa:
>
> sudo add-apt-repository ppa:juju/devel
> sudo apt-get update; sudo apt-get install juju-2.0
>
> Windows, Centos, and MacOS users can get a corresponding installer at:
>
> https://launchpad.net/juju/+milestone/2.0-rc3
>
>
> ## Feedback Appreciated!
>
> We encourage everyone to subscribe the mailing list at
> juju@lists.ubuntu.com and join us on #juju on freenode. We would love to
> hear
> your feedback and usage of juju.
>
>
> ## Anything else?
>
> You can read more information about what's in this release by viewing the
> release notes here:
>
> https://jujucharms.com/docs/devel/temp-release-notes
>
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-- 
Adam Israel, Software Engineer
Canonical // Cloud DevOps // Juju // Ecosystem
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Juju 2.0-rc3 is here!

[Adam Israel]

It looks like rc3 introduced a minor change in the status output. Each unit
has an asterisk next to its name, i.e., mariadb/0* (full output in
pastebin). What is the asterisk meant to represent?

http://pastebin.ubuntu.com/23289710/

On Thu, Oct 6, 2016 at 5:28 PM Andrew Wilkins <andrew.wilk...@canonical.com>
wrote:

> On Fri, Oct 7, 2016 at 6:15 AM Curtis Hovey-Canonical <
> cur...@canonical.com> wrote:
>
> A new development release of Juju, 2.0-rc3, is here!
>
>
> ## What's new?
>
> * For an AWS VPC account juju will create a t2.medium for controller
>   instances by default now. Non-controller instances are unchanged for
>   now, and remain m3.medium by default. Controller instance root disk
>   now defaults to 32GiB, but can be overridden with constraints.
> * Shorten the hostnames we apply to instances created by the OpenStack
>   provider.
> Example old hostname:
> juju-fd943864-df2e-4da1-8e7d-5116a87d4e7c-machine-14
>
> Example new hostname:
> Juju-df7591-controller-0
> * Added support for LXD 2.3 apis
> * New update-credential command
> * Added --model-default option to the bootstrap
> * LXD containers now have proper hostnames set
>
>
> Also, support for the aws/ap-south-1 region has been added.
>
> Adam Stokes just found a bug related to this, which prevented him from
> being able to destroy his rc2 controller with an rc3 client. I'll fix this
> for 2.0, but in the mean time I recommend you destroy your controller
> before upgrading the client.
>
> If you do upgrade the client, then you will need to modify
> ~/.local/share/juju/bootstrap-config.yaml, fixing the endpoint cached in
> there. You can find the correct value by running "juju show-cloud aws", and
> picking out the value associated with the region you bootstrapped.
>
> Cheers,
> Andrew
>
>
> ## How do I get it?
>
> If you are running Ubuntu, you can get it from the juju devel ppa:
>
> sudo add-apt-repository ppa:juju/devel
> sudo apt-get update; sudo apt-get install juju-2.0
>
> Windows, Centos, and MacOS users can get a corresponding installer at:
>
> https://launchpad.net/juju/+milestone/2.0-rc3
>
>
> ## Feedback Appreciated!
>
> We encourage everyone to subscribe the mailing list at
> j...@lists.ubuntu.com and join us on #juju on freenode. We would love to
> hear
> your feedback and usage of juju.
>
>
> ## Anything else?
>
> You can read more information about what's in this release by viewing the
> release notes here:
>
> https://jujucharms.com/docs/devel/temp-release-notes
>
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-- 
Adam Israel, Software Engineer
Canonical // Cloud DevOps // Juju // Ecosystem
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Juju 2.0-rc3 is here!

[Andrew Wilkins]

On Fri, Oct 7, 2016 at 6:15 AM Curtis Hovey-Canonical <cur...@canonical.com>
wrote:

> A new development release of Juju, 2.0-rc3, is here!
>
>
> ## What's new?
>
> * For an AWS VPC account juju will create a t2.medium for controller
>   instances by default now. Non-controller instances are unchanged for
>   now, and remain m3.medium by default. Controller instance root disk
>   now defaults to 32GiB, but can be overridden with constraints.
> * Shorten the hostnames we apply to instances created by the OpenStack
>   provider.
> Example old hostname:
> juju-fd943864-df2e-4da1-8e7d-5116a87d4e7c-machine-14
>
> Example new hostname:
> Juju-df7591-controller-0
> * Added support for LXD 2.3 apis
> * New update-credential command
> * Added --model-default option to the bootstrap
> * LXD containers now have proper hostnames set
>

Also, support for the aws/ap-south-1 region has been added.

Adam Stokes just found a bug related to this, which prevented him from
being able to destroy his rc2 controller with an rc3 client. I'll fix this
for 2.0, but in the mean time I recommend you destroy your controller
before upgrading the client.

If you do upgrade the client, then you will need to modify
~/.local/share/juju/bootstrap-config.yaml, fixing the endpoint cached in
there. You can find the correct value by running "juju show-cloud aws", and
picking out the value associated with the region you bootstrapped.

Cheers,
Andrew


> ## How do I get it?
>
> If you are running Ubuntu, you can get it from the juju devel ppa:
>
> sudo add-apt-repository ppa:juju/devel
> sudo apt-get update; sudo apt-get install juju-2.0
>
> Windows, Centos, and MacOS users can get a corresponding installer at:
>
> https://launchpad.net/juju/+milestone/2.0-rc3
>
>
> ## Feedback Appreciated!
>
> We encourage everyone to subscribe the mailing list at
> juju@lists.ubuntu.com and join us on #juju on freenode. We would love to
> hear
> your feedback and usage of juju.
>
>
> ## Anything else?
>
> You can read more information about what's in this release by viewing the
> release notes here:
>
> https://jujucharms.com/docs/devel/temp-release-notes
>
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Juju 2.0-rc3 is here!

[Andrew Wilkins]

On Fri, Oct 7, 2016 at 6:15 AM Curtis Hovey-Canonical <cur...@canonical.com>
wrote:

> A new development release of Juju, 2.0-rc3, is here!
>
>
> ## What's new?
>
> * For an AWS VPC account juju will create a t2.medium for controller
>   instances by default now. Non-controller instances are unchanged for
>   now, and remain m3.medium by default. Controller instance root disk
>   now defaults to 32GiB, but can be overridden with constraints.
> * Shorten the hostnames we apply to instances created by the OpenStack
>   provider.
> Example old hostname:
> juju-fd943864-df2e-4da1-8e7d-5116a87d4e7c-machine-14
>
> Example new hostname:
> Juju-df7591-controller-0
> * Added support for LXD 2.3 apis
> * New update-credential command
> * Added --model-default option to the bootstrap
> * LXD containers now have proper hostnames set
>

Also, support for the aws/ap-south-1 region has been added.

Adam Stokes just found a bug related to this, which prevented him from
being able to destroy his rc2 controller with an rc3 client. I'll fix this
for 2.0, but in the mean time I recommend you destroy your controller
before upgrading the client.

If you do upgrade the client, then you will need to modify
~/.local/share/juju/bootstrap-config.yaml, fixing the endpoint cached in
there. You can find the correct value by running "juju show-cloud aws", and
picking out the value associated with the region you bootstrapped.

Cheers,
Andrew


> ## How do I get it?
>
> If you are running Ubuntu, you can get it from the juju devel ppa:
>
> sudo add-apt-repository ppa:juju/devel
> sudo apt-get update; sudo apt-get install juju-2.0
>
> Windows, Centos, and MacOS users can get a corresponding installer at:
>
> https://launchpad.net/juju/+milestone/2.0-rc3
>
>
> ## Feedback Appreciated!
>
> We encourage everyone to subscribe the mailing list at
> j...@lists.ubuntu.com and join us on #juju on freenode. We would love to
> hear
> your feedback and usage of juju.
>
>
> ## Anything else?
>
> You can read more information about what's in this release by viewing the
> release notes here:
>
> https://jujucharms.com/docs/devel/temp-release-notes
>
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Juju 2.0-rc3 is here!

[Curtis Hovey-Canonical]

A new development release of Juju, 2.0-rc3, is here!


## What's new?

* For an AWS VPC account juju will create a t2.medium for controller
  instances by default now. Non-controller instances are unchanged for
  now, and remain m3.medium by default. Controller instance root disk
  now defaults to 32GiB, but can be overridden with constraints.
* Shorten the hostnames we apply to instances created by the OpenStack
  provider.
Example old hostname:
juju-fd943864-df2e-4da1-8e7d-5116a87d4e7c-machine-14

Example new hostname:
Juju-df7591-controller-0
* Added support for LXD 2.3 apis
* New update-credential command
* Added --model-default option to the bootstrap
* LXD containers now have proper hostnames set


## How do I get it?

If you are running Ubuntu, you can get it from the juju devel ppa:

sudo add-apt-repository ppa:juju/devel
sudo apt-get update; sudo apt-get install juju-2.0

Windows, Centos, and MacOS users can get a corresponding installer at:

https://launchpad.net/juju/+milestone/2.0-rc3


## Feedback Appreciated!

We encourage everyone to subscribe the mailing list at
juju@lists.ubuntu.com and join us on #juju on freenode. We would love to hear
your feedback and usage of juju.


## Anything else?

You can read more information about what's in this release by viewing the
release notes here:

https://jujucharms.com/docs/devel/temp-release-notes


-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju