# Juju 2.0-beta5

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


## Getting Juju

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

Upgrading environments to 2.0-beta5 is not supported.


## The complete release notes available on the Web

The release notes for Juju 2.0 beta5 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.


## What's New in Beta5

* Support for local charm repositories removed.
  * All local charms must now be deployed using the path to the charm
    instead of a local URL.
  * Bundles support specifying local charms using the path to the charm.

* Notable Bug Fixes:
  * GridFS namespace breaks charm and tools deduping across models
    Lp 1569054
  * Unable to download local: charm due to hash mismatch in
    multi-model deployment
    Lp 1541482
  * Destroyed models still show up in list-models
    Lp 1534627


## Notable Changes

This releases addresses stability and performance issues.

### Improved Local Charm Deployment

Local charms can be deployed directly from their source directory
without  having to set up a pre-determined local repository file
structure. This  feature makes it more convenient to hack on a charm and
just deploy it, and  it also necessary to develop local charms
supporting multi series.

Assuming a local charm exists in directory /home/user/charms/mycharm:

    juju deploy ~/charms/mycharm

will deploy the charm using the default series.

    juju deploy ~/charms/mycharm --series trusty

will deploy the charm using trusty.

Note that it is no longer necessary to define a JUJU_REPOSITORY nor
locate  the charms in a directory named after a series. Any directory
structure can  be used, including simply pulling the charm source from a
VCS, hacking on  the code, and deploying directly from the local repo.

Bundles are also supported. You can now do something like this:

    series: xenial
    services:
        wordpress:
            charm: ./wordpress
            num_units: 1
            series: trusty
        mysql:
            charm: ./mysql
            num_units: 1
    relations:
        - ["wordpress:db", "mysql:server"]


Note the series attributes. These are required if the charm does not
yet define any default series in metadata or you want to use a series
different to the default. Either the bundle default series will be
used ("xenial" for the mysql service above) or the service specific
one will be ("trusty" for the wordpress service above).


## Resolved issues

  * Newly created lxd container has zero network devices
    Lp 1564395

  * Cloud-init cannot always use private ip address to fetch tools
    (ec2 provider)
    Lp 1566431

  * Address allocation feature flag still enabled for maas provider in
    juju 2.0
    Lp 1568925

  * Gridfs namespace breaks charm and tools deduping across models
    Lp 1569054

  * Storage-get crashes on xenial (aws)
    Lp 1569490

  * Apiserver: digest sha header is incorrectly formed
    Lp 1503992

  * Destroyed models still show up in list-models
    Lp 1534627

  * Unable to download local: charm due to hash mismatch in multi-
    model deployment
    Lp 1541482

  * Help text for juju remove-relation needs improving
    Lp 1555694

  * Ensure availability uses wrong constraints
    Lp 1561315

  * 'juju help glossary' and 'juju help topics' are deprecated
    Lp 1564017

  * Disallow upgrading with --upload-tools for hosted models
    Lp 1567170

  * List resources will not work correctly
    Lp 1569386

  * Juju lxd bridge detection fallback is not reliable
    Lp 1570473

  * Manpage still refers to 1.x config for 2.0
    Lp 1570654

  * Can't deploy multiseries charms in bundles
    Lp 1571254

  * "juju register" stores password on disk
    Lp 1571476

  * Juju login should only ask for password once
    Lp 1571478

  * "juju change-user-password --generate" is unhelpful
    Lp 1571901

  * Help text for juju import-ssh-key needs improving
    Lp 1554700

  * Help text for juju list-ssh-keys needs improving
    Lp 1554705

  * Help text for juju add-ssh-key needs improving
    Lp 1557380

  * Help text for juju remove ssh key needs improving
    Lp 1558078

  * Help text for juju set-constraints needs improving
    Lp 1563932

  * Help text for juju get-constraints needs improving
    Lp 1563939

  * Help text for juju set-config needs improving
    Lp 1563942

  * Help text for juju debug-log needs improving
    Lp 1563950

  * Help text for juju scp needs improving
    Lp 1563956

  * Help text for juju get-config needs improving
    Lp 1564515

  * Help text for juju remove-credential needs improving
    Lp 1566332

  * Help text for juju add-credential needs improving
    Lp 1566362

  * Help text for juju upgrade-juju needs improving
    Lp 1566367

  * Help text for juju ssh needs improving
    Lp 1566369

  * Help text for juju list-shares needs improving
    Lp 1567719

  * Help text for juju set-default-credential needs improving
    Lp 1567721

  * Help text for juju list-credentials needs improving
    Lp 1567722

  * Help text for juju add-cloud needs improving
    Lp 1567724

  * Help text for juju disable-user needs improving
    Lp 1567726

  * Help text for juju enable-user needs improving
    Lp 1567728

  * Help text for juju unexpose needs improving
    Lp 1567730

  * Help text for juju expose needs improving
    Lp 1567732

  * Help text for juju set-default-region needs improving
    Lp 1567734

  * Help text for juju add-unit needs improving
    Lp 1567925

  * Help text for juju bootstrap needs improving
    Lp 1568848

  * Help text for juju needs improving
    Lp 1568862

  * Help text for juju grant needs improving
    Lp 1569652

  * Help text for juju revoke needs improving
    Lp 1569654

  * Help text for juju show-controller needs improving
    Lp 1569914

  * Help text for juju list-machines needs improving
    Lp 1569948

  * Unhelpful error message shown when metered deployment fails
    Lp 1571054


Finally

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


-- 
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

Reply via email to