Juju devel 2.0-beta7 is released
Curtis Hovey-Canonical
curtis at canonical.com
Sat May 14 00:08:05 UTC 2016
# Juju 2.0-beta7
A new development release of Juju, juju 2.0-beta7, is now available.
This release replaces version 2.0-beta6.
## Getting Juju
Juju 2.0-beta7 is available for Xenial and backported to earlier
series in the following PPA:
https://launchpad.net/~juju/+archive/devel
Windows, Centos, and OS X users will find installers at:
https://launchpad.net/juju-core/+milestone/2.0-beta7
Upgrading environments to 2.0-beta7 is not supported.
## The complete release notes available on the Web
The release notes for Juju 2.0 beta7 are very long. They are too large
to post to a list. The complete release notes are published at
https://jujucharms.com/docs/devel/temp-release-notes
## Getting started with Juju 2.0
Juju 2.0 allows you to get started creating models without modifying any
definition files. Just provide your credentials and go! (*Note: to
fully understand the new bootstrap experience please see the "New
Bootstrap and Cloud Management Experience" section below)
* LXD provider (requires lxd 2.0.0~rc9 or later):
The LXD provider requires no credentials, so you can create a
controller by just specifying its name:
juju bootstrap <controller name> lxd
Note that the lxdbr0 bridge needs to be properly configured for the lxd
provider to work, for details see:
http://insights.ubuntu.com/2016/04/07/lxd-networking-lxdbr0-explained/
* Public Clouds:
Known public clouds can be listed with juju list-clouds:
juju list-clouds
CLOUD TYPE REGIONS
aws ec2 us-east-1, us-west-1, us-west-2, ...
aws-china ec2 cn-north-1
aws-gov ec2 us-gov-west-1
azure azure japanwest, centralindia, eastus2, ...
azure-china azure chinaeast, chinanorth
cloudsigma cloudsigma mia, sjc, wdc, zrh, hnl
google gce us-east1, us-central1, ...
joyent joyent us-east-1, us-east-2, us-east-3, …
localhost lxd localhost
rackspace rackspace lon, syd, hkg, dfw, ord, iad
Add your credentials using either:
juju add-credential <cloud>
or
juju add-credential <cloud> -f creds.yaml
or
juju autoload-credentials
When specifying just the cloud, juju add-credential will allow a new
credential to be added interactively. You will be prompted type the
required credential attributes. Example:
juju add-credential aws
credential name: aws-creds
replace existing credential? [y/N]: y
auth-type: access-key
access-key: ABC123ABC123ABC123AB
secret-key:
credentials added for cloud aws
The new credentials.yaml file at: ~/.local/share/juju/credentials.yaml
The autoload tool will search for existing credentials for AWS,
OpenStack/Rackspace, and Google clouds. You will then be prompted for
which ones you'd like to save.
If you have an existing credential.yaml file, you can also import a
named credential, eg for MAAS
cat credentials.yaml
credentials:
maas:
my-credentials:
auth-type: oauth1
maas-oauth: <mass-oauth-key>
or, for AWS
cat credentials.yaml
credentials:
aws:
default-credential: my-credentials
my-credentials:
auth-type: access-key
access-key: <key>
secret-key: <secret>
Bootstrap using your default credentials:
juju bootstrap <controller name> <cloud>[/region]
Examples:
juju bootstrap aws-controller aws
juju bootstrap mass-controller maas/192.168.0.1
In the MAAS example above, you specify the host address of the MAAS
controller. So to use Juju on MAAS out of the box, you set up a
credentials file (either interactively, or based on the example above)
and then bootstrap. This avoids the need for any cloud configuration.
But it's also possible to set up a named MAAS cloud definition as
explained later.
More details on the new bootstrap experience, including defining private
clouds can be found in the New Bootstrap and Cloud Management Experience
section.
## What's New in Beta7
* Support for MAAS 2
* The create-model command has been renamed to add-model
## Resolved issues
* Juju does not support ec2 with no default vpc
Lp 1321442
* Juju restore-backup does not complete properly
Lp 1569467
* Juju still vulnerable to cve-2013-2566, cve-2015-2808
Lp 1571457
* Boot resource 2.0 schema check failed: kflavor: expected string,
got nothing
Lp 1575768
* Filesystem 2.0 schema check failed: mount_point: expected string,
got nothing
Lp 1575808
* 'juju create-backup' fails first on a mongodump dependency then
auth failure
Lp 1576270
* --sslpemkeypassword parameter must be passed with = on yakkety
Lp 1581284
* Charm get endpoint is not authenticated
Lp 1499338
* [joyent] 4k ssh key can not be used: "cannot create credentials:
an error occurred while parsing the key: asn1: structure error:
length too large"
Lp 1543283
* Add maas 2.0 support in juju 2.0
Lp 1564577
* Payload commands don't work
Lp 1567518
* Multiple interfaces lead to stalled charm download over wrong api
endpoint
Lp 1574607
* Azure multi model dns failure
Lp 1576376
* Unblock panic: invalid memory address or nil pointer dereference
Lp 1578373
* Cannot deploy windows nano
Lp 1579127
* Help text for juju list-users needs improving
Lp 1557143
* Lxd, maas and manual do not make sense in list-clouds
Lp 1564054
* Juju help status missing controller syntax
Lp 1572746
* Add-cloud method not documented by "juju help"
Lp 1575332
* Juju switch returns confusing error message
Lp 1575760
Finally
We encourage everyone to subscribe the mailing list at
juju at lists.ubuntu.com, or join us on #juju on freenode.
--
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui
More information about the Juju
mailing list