Juju devel 1.19.2 is released

[Curtis Hovey-Canonical]

juju-core 1.19.2

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


Getting Juju

juju-core 1.19.2 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.2.

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.3*


New and Notable

* Status includes networks

* MAAS provider supports placement and add-machine

* The lxc-use-clone option makes lxc faster for non-local providers


Resolved issues

* Add support for utopic
  Lp 1314686

* Can't SSH with "juju ssh" command to EC2 instance.
  Lp 1313785

* lxc nested within kvm machines do not use lxc-clone

* LXCs nested within kvm machines do not use lxc-clone
  Lp 1315216

* Juju add-machine method Client.AddMachinesV2 is not implemented
  Lp 1317267

* Deploy --config assumes relative path if it starts with a tilde (~)
  Lp 1271819

* Juju doesn't check if 8021q module is present before modprobing it
  Lp 1316762

* Juju sync-tools destroys the environment when given an invalid source
  Lp 1316869

* LXC nested within kvm machines do not use lxc-clone
  Lp 1315216


Status includes networks

Juju supports multiple physical and virtual network interfaces with
the same MAC address on the same machine. The output of 'juju status'
will include information about networks when there is more than one. The
networks will be presented in this manner:
    machines: ...
    services: ...
    networks:
      net1:
        provider-id: foo
        cidr: 0.1.2.0/24
        vlan-tag: 42


MAAS provider supports placement and add-machine

You can specify which MAAS host to place the juju state-server on with
the '--to' option. To bootstrap on a host named 'fnord', run this:

    juju bootstrap --to fnord

The MAAS provider support the add-machine command now. You can provision
an existing host in the MAAS-based Juju environment. For example, you
can  add running machine named fnord like this:

    juju add-machine fnord


The lxc-use-clone option makes lxc faster for non-local providers

When 'lxc-use-clone' is set to true, the LXC provisioner will be
configured to use cloning regardless of provider type. This option
cannot be changed once it is set. You can set the option to true in
environments.yaml like this:

    lxc-use-clone: true

This speeds up LXC provisioning when using placement with any provider.
For example, deploying mysql to a new LXC container on machine 0 will
start faster:

    juju deploy --to lxc:0 mysql


Finally

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

-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui