Re: Juju 2.0-beta16 is here!

[Andrew Wilkins]

On Fri, Aug 26, 2016 at 4:05 AM Nicholas Skaggs <
nicholas.ska...@canonical.com> wrote:

> A new development release of Juju, 2.0-beta16, is here!
>
> ## 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 update; sudo apt install juju-2.0
>
> Or install it from the snap store
>
> snap install juju --beta --devmode
>
> Windows, Centos, and OS X users can get a corresponding installer at:
>
> https://launchpad.net/juju/+milestone/2.0-beta16
>
> ## What's new?
>
> This release fixed 61 bugs and added some new and expanded features. Some
> of the notable changes include:
>
> * Juju rejects LXD 2.1 https://bugs.launchpad.net/bugs/1614559
> * debug-log usability changes
>  - only tails by default when running in a terminal
> --no-tail can be used to not tail from a terminal
> --tail can be used for force tailing when not on a terminal
>  - time output now defaults to local time (--utc flag added to show times
> in utc)
>  - filename and line number no longer shown by default (--location flag
> added to include location in the output)
>  - dates no longer shown by default (--date flag added to include dates in
> output)
> --ms flag added to show timestamps to millisecond precision
>  - severity levels and location now shown in color in the terminal
> --color option to force ansi color codes to pass to 'less -R'
> * controllers models, and users commands now show current controller and
> model respectively using color as well as the asterix
> * removal of smart formatter for CLI commands. Where 'smart' used to be
> the default, now it is 'yaml'.
> * controllers, models, and users commands now print the access level users
> have against each model/controller
> * juju whoami command prints the current controller/model/logged in user
> details
> * fix for LXD image aliases so that the images auto update (when
> bootstrapping a new LXD cloud, images will be downloaded again the first
> time, even if existing ones exist)
> * Expanded controller and model permissions.
>
> Also, juju-2 has moved on launchpad to launchpad.net/juju.
> launchpad.net/juju-core will continue to be utilized for juju-1
> milestones and bug tracking.
>
>
> ## 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?
>

There is something else I had meant to email the list about yesterday, but
slipped my mind. The manual provider's "bootstrap-user" model config
attribute has been removed. Instead, you can now do:

juju bootstrap controller-name manual/user@host

And in your clouds.yaml, you can include "user@" in the endpoint for
manual-type clouds.

Cheers,
Andrew

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
>
> --
> 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-beta16 is here!

[Jeff Pihach]

Juju GUI 2.1.10, has also been added to simplestreams and will be installed
with any new controllers.

To upgrade an existing controller:

juju upgrade-gui

Due to a minor incompatibility between the latest GUI release and Juju 2.0
beta 16 the ability to create and switch models from the GUI has been
disabled. This issue is being resolved and will work as expected in the
upcoming release.

If you have any questions feel free to reach out to us on #juju on freenode
or open an issue https://github.com/juju/juju-gui
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Juju 2.0-beta16 is here!

[Nicholas Skaggs]

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

## 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 update; sudo apt install juju-2.0

Or install it from the snap store

snap install juju --beta --devmode

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

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

## What's new?

This release fixed 61 bugs and added some new and expanded features. Some
of the notable changes include:

* Juju rejects LXD 2.1 https://bugs.launchpad.net/bugs/1614559
* debug-log usability changes
 - only tails by default when running in a terminal
--no-tail can be used to not tail from a terminal
--tail can be used for force tailing when not on a terminal
 - time output now defaults to local time (--utc flag added to show times
in utc)
 - filename and line number no longer shown by default (--location flag
added to include location in the output)
 - dates no longer shown by default (--date flag added to include dates in
output)
--ms flag added to show timestamps to millisecond precision
 - severity levels and location now shown in color in the terminal
--color option to force ansi color codes to pass to 'less -R'
* controllers models, and users commands now show current controller and
model respectively using color as well as the asterix
* removal of smart formatter for CLI commands. Where 'smart' used to be the
default, now it is 'yaml'.
* controllers, models, and users commands now print the access level users
have against each model/controller
* juju whoami command prints the current controller/model/logged in user
details
* fix for LXD image aliases so that the images auto update (when
bootstrapping a new LXD cloud, images will be downloaded again the first
time, even if existing ones exist)
* Expanded controller and model permissions.

Also, juju-2 has moved on launchpad to launchpad.net/juju.
launchpad.net/juju-core will continue to be utilized for juju-1 milestones
and bug tracking.


## 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
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Juju 2.0-beta16 is here!

[Nicholas Skaggs]

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

## 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 update; sudo apt install juju-2.0

Or install it from the snap store

snap install juju --beta --devmode

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

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

## What's new?

This release fixed 61 bugs and added some new and expanded features. Some
of the notable changes include:

* Juju rejects LXD 2.1 https://bugs.launchpad.net/bugs/1614559
* debug-log usability changes
 - only tails by default when running in a terminal
--no-tail can be used to not tail from a terminal
--tail can be used for force tailing when not on a terminal
 - time output now defaults to local time (--utc flag added to show times
in utc)
 - filename and line number no longer shown by default (--location flag
added to include location in the output)
 - dates no longer shown by default (--date flag added to include dates in
output)
--ms flag added to show timestamps to millisecond precision
 - severity levels and location now shown in color in the terminal
--color option to force ansi color codes to pass to 'less -R'
* controllers models, and users commands now show current controller and
model respectively using color as well as the asterix
* removal of smart formatter for CLI commands. Where 'smart' used to be the
default, now it is 'yaml'.
* controllers, models, and users commands now print the access level users
have against each model/controller
* juju whoami command prints the current controller/model/logged in user
details
* fix for LXD image aliases so that the images auto update (when
bootstrapping a new LXD cloud, images will be downloaded again the first
time, even if existing ones exist)
* Expanded controller and model permissions.

Also, juju-2 has moved on launchpad to launchpad.net/juju.
launchpad.net/juju-core will continue to be utilized for juju-1 milestones
and bug tracking.


## 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
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

maas 1.9.4 commissioning fails

[Daniel Bidwell]

I have maas 1.9.4 on trusty.  My server has been enlisted, does wake on
lan, and commissions.  It pxe boots and runs the cloud-init stuff,
updates the maas server with its CPUs, memory, and disks, etc, but
changes its status to commissioning failed.  Where do I find the logs
as to why it has failed? I don't see anything helpful on the maas
server in /var/log/maas.

From watching the console as it runs through everything it looks ok,
what I can see as it flies by.  Then it powers itself down.
-- 
Daniel Bidwell 


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

maas 1.9.4 commissioning fails

[Daniel Bidwell]

I have maas 1.9.4 on trusty.  My server has been enlisted, does wake on
lan, and commissions.  It pxe boots and runs the cloud-init stuff,
updates the maas server with its CPUs, memory, and disks, etc, but
changes its status to commissioning failed.  Where do I find the logs
as to why it has failed? I don't see anything helpful on the maas
server in /var/log/maas.

From watching the console as it runs through everything it looks ok,
what I can see as it flies by.  Then it powers itself down.
-- 
Daniel Bidwell 


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