Juju 1.17.6 is released.

[Curtis Hovey-Canonical]

juju-core 1.17.6

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


Getting Juju

juju-core 1.17.6 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.17.6.

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


New and Notable

* Juju now supports juju-mongodb, a mongodb tuned for juju’s needs

* Juju now has support for proxies

* Juju local provider can use clone for faster LXC


Resolved issues

* Juju uses tools for the wrong architecture when unable to find correct
  tools
  Lp 1227722

* Call to relation-get failing with 'permission denied'
  Lp 1239681

* Network interface br0 not brought up by cloud-init script with
  MAAS provider
  Lp 1271144

* Juju bootstrap --upload-tools does not honor the arch of the machine
  being created
  Lp 1282869

* Filesystem mount from lxc template causes filesystem permission
  breakages
  Lp 1293549

* Juju userdata should not restart networking
  Lp 1248283

* Juju deploy -n 15 gets rate limited in EC2
  Lp 1277397

* Juju bootstrap does not select tools with respect to constraints
  Lp 1282870

* Juju 1.17.5 tries to execute non-existent hooks
  1293310


Juju now supports juju-mongodb, a mongodb tuned for juju’s needs

The Juju state-server (bootstrap node) prefers juju-mongodb and it will
use it when it is available. The package is available in Ubuntu Trusty,
the new db will be used when a Trusty environment is bootstrapped.

The juju-local package on Trusty will include juju-mongodb when
mongodb-server is not already installed. Upgrades of the juju-local
package will continue to use mongodb-server to preserve continuity with
existing local environments. Trusty users can install juju-mongodb to
bootstrap new lxc and kvm environments with it.


Juju now has support for proxies

Proxies can now be configured for the providers in the environments.yaml
file, or added to an existing environment using ‘juju set-env’

The configuration values are:
    http-proxy, https-proxy, ftp-proxy, no-proxy
The values that are set for these proxies are exported in all hook
execution contexts, and also available in the shell through ‘juju ssh’
or ‘juju run’.

There are three additional proxy values specific for apt:
    apt-http-proxy, apt-https-proxy, apt-ftp-proxy
These are set to be the same as the non-apt proxy values, but can be
overridden independently. For example, having squid-deb-proxy running
on a laptop, you can specify the apt-http-proxy to use it for the
containers by doing:
    apt-http-proxy: http://10.0.3.1:8000
The IP address here is the address on the host machine’s network-bridge
as seen from the machines on the bridge.

Note: there is a known limitation here (bug 1295372), once you have set
a value, there is no way to remove it.


Juju local provider can use clone for faster LXC

The local provider gains the ability to use lxc-clone to create the
containers used as machines. This ability is controlled through a
configuration value on the provider:
    lxc-clone
This value defaults to ‘true’ for Trusty and above, and ‘false’ before
that. You can try to use lxc-clone on earlier releases, but it is not a
supported value. It may well work.

The local provider is btrfs aware. If your LXC directory is on a btrfs
filesystem, the clones use snapshots and are much faster to create and
take up much less space. There is also support for using aufs as a
backing-store for the LXC clones, but there are some situations where
aufs doesn’t entirely behave as intuitively as one might expect, so this
must be turned on explicitly.
    lxc-clone-aufs: true

When using clone, the first machine to be created will create a
‘template’ machine that is used as the basis for the clones. This will
be called ‘juju-<series>-template’, so for a precise image, the name is
‘juju-precise-template’. You should not modify or start this image
while a local provider environment is running, as you cannot clone a
running lxc machine. Some work is in progress, to be delivered as a
plugin, that will provide additional functionality to create these
template images independently of an environment, and helper functions to
keep it up to date (i.e. running apt-get update/upgrade inside the
container).


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