juju-core 2.0-beta6

# juju 2.0-beta6

A new development release of Juju, juju 2.0-beta6, is now available.
This release replaces version 2.0-beta5.

## Getting Juju

Juju 2.0-beta6 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-beta6

Upgrading environments to 2.0-beta6 is not supported.

## The complete release notes available on the Web

The release notes for Juju 2.0 beta6 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, …
        lxd lxd
        maas maas
        manual manual
        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 maas
  credential name: hmaas
  replace existing credential? [y/N]: y
  auth-type: oauth1
  maas-oauth:
credentials added for cloud maas

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.

## Notable Changes

This releases addresses stability and performance issues.

## Resolved issues

  * Juju rc1 loses agents during a lxd deploy
    Lp 1572237

  * Tools info mismatch on arch with lxd containers
    Lp 1572781

  * 'failed to ensure lxd image' creating lxd container
    Lp 1573149

  * Non-admin users unable to share models
    Lp 1573259

  * Only one user can create local users
    Lp 1573382

  * Maas provider bridge script deletes /etc/network/if-up.d/ntpdate
    during bootstrap
    Lp 1564397

  * Awaiting error resolution for "install" hook
    Lp 1566130

  * Model uuids shown in some "romulus" command output
    Lp 1571055

  * Panic in when bootstrapping maas 2.0
    Lp 1573659

  * [lxd provider] trusty container is used by default on xenial host
    Lp 1557747

  * Juju terms language confusing for locally-deployed charms
    Lp 1573148

Finally

We encourage everyone to subscribe the mailing list at
juju@lists.ubuntu.com, or join us on #juju on freenode.