juju-core 1.19.1

juju-core 1.19.1

A new development release of Juju, juju-core 1.19.1, is now available.

Getting Juju

juju-core 1.19.1 is available for trusty and backported to earlier
series in the following PPA:
    https://launchpad.net/~juju/+archive/devel

Upgrading from stable releases to development releases is not
supported. You can upgrade test environments to development releases
to test new features and fixes, but it is not advised to upgrade
production environments to 1.19.1.

If you are using a development release of juju-core, and find you need
to go back to a stable release, you can find it in the juju stable PPA:
    https://launchpad.net/~juju/+archive/stable

If you have multiple sources of juju-core, you can select the version
you want using apt:
    sudo apt-get install juju-core=1.18.1*

New and Notable

* High Availability

* Support for Multiple NICs with the Same MAC

* Constraints Support instance-type

Resolved issues

* Git usage can trigger disk space/memory issues for charms with blobs
  Lp 1232304

* Juju upgrade-charm fails because of git
  Lp 1297559

* .pyc files caused upgrade-charm to fail with merge conflicts
  Lp 1191028

* Juju backup command fails against trusty bootstrap node
  Lp 1305780

* mongodb-server installed instead of juju-mongodb on trusty
  Lp 1310719

* MAAS provider cannot provision named instance
  Lp 1237709

* Manual provider specify bash as shell for ubuntu user
  Lp 1303195

* Stale lock causes local provider unit to be stuck pending
  Lp 1302935

* Local provider fails to provision precise instances from a trusty host
  Lp 1306537

* Local provider machines do not boot without default-series
  Lp 1309805

* The juju-local package doesn't state that lxc 1.0.0+ is required
  Lp 1311909

* Juju client is not using the floating ip to connect to the state
  server
  Lp 1308767

* Juju bootstrap defaults to i386
  Lp 1304407

* Juju crash during bootstrap on arm64
  Lp 1298085

* juju status panic() when unable to parse .jenv
  Lp 1312136

* Juju authorised-keys should have an authorized-keys alias
  Lp 1312537

High Availability

The juju state-server (bootstrap node) can be placed into high
availability mode. Juju will automatically recover when one or more the
state-servers fail. You can use the 'ensure-availability' command to
create the additional state-servers:

    juju ensure-availability

The 'ensure-availability' command create's 3 state servers by default,
but you may use the '-n' option to specify a larger number. The number
of state servers must be odd. The command supports the '--series' and
'--constraints' options like the 'bootstrap' command. You can learn more
details by running 'juju ensure-availability --help'

Support Multiple NICs with the Same MAC

Juju now supports multiple physical and virtual network interfaces with
the same MAC address on the same machine. Juju takes care of this
automatically, there is nothing you need to do.

Caution, network settings are not upgraded from 1.19.0 to 1.19.1. If you
used juju 1.19.0 to deploy an environment with specified networks, you
must redeploy your environment instead of upgrading to 1.19.1.

Constraints Support instance-type

You can specify 'instance-type' with the '--constraints' option to
select a specific image defined by the cloud provider. The
'instance-type' constraint can be used with Azure, EC2, HP Cloud, and
all OpenStack-based clouds. For example, when creating an EC2
environment, you can specify 'm1.small':

    juju bootstrap --constraints instance-type=m1.small

Constraints are validated by all providers to ensure values conflicts
and unsupported options are rejected. Previously, juju would reconcile
such problems and select an image, possibly one that didn't meet the
needs of the service.

Finally

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