Juju 2.0-rc3 is here!

Christian Muirhead christian.muirhead at canonical.com
Fri Oct 7 17:07:27 UTC 2016


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.israel at 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.wilkins at canonical.com> wrote:
>
> On Fri, Oct 7, 2016 at 6:15 AM Curtis Hovey-Canonical <
> curtis at 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 at 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 at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
> --
> Juju-dev mailing list
> Juju-dev at 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 at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20161007/6e2641a3/attachment.html>


More information about the Juju mailing list