juju-core 1.17.4 is released

[Curtis Hovey-Canonical]

juju-core 1.17.4

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


Getting Juju

juju-core 1.17.4 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.4.

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 backup and restore state-server (bootstrap node) plugins


Resolved issues

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

* Juju 1.18 needs to support all CLI against a 1.16 server
  Lp 1253619

* Provide remove-* aliases for destroy-service and destroy-machine
  Lp 1261628

* Juju status incompatible in 1.17.0 against 1.16
  Lp 1266734

* Loading state on bootstrap ignores ssl-hostname-verification setting
  Lp 1268913

* Juju internal use of rsyslog should use ssl/tls for aggregation
  Lp 1281071

* Juju 1.17.2 doesn't pass command line options to ssh
  Lp 1281577

* rsyslog upgrade step doesn't set LogDir
  Lp 1284020

* Juju scp should accept multiple targets and pass extra args to scp
  Lp 1283412


Known Issues

* The juju-mongodb package breaks 1.17.4 trusty client bootstrap
  Bootstrapping environments in AWS, HP Cloud, and Azure fail when
  juju-mongodb is installed on the local machine.
  Lp 1286279


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

Juju will use juju-mongodb on the state-server (bootstrap node) when it is
already installed. You can install juju-mongodb on your local host to
boostrap a local environment, or on the bootstrap-host before bootstrapping
a manual environment (née null provider).

Machines with juju-mongodb installed cannot bootstrap environments with other
providers such as ec2, openstack, and azure. Do not install juju-mongodb on
any machine that needs to bootstrap non-local, non-manual environments. In the
future, juju will  always try to install juju-mongodb on the state-server, but
will fallback to mongodb-server if it is not available.


Juju backup and restore state-server (bootstrap node) plugins

Juju provides backup and restore plugins to recover the juju
state-server in case of failure. The juju-backup plugin creates a
tarball of the state-server’s configuration, keys, and environment data.

    $ juju switch my-env
    $ juju-backup

The juju-restore plugin creates a new juju bootstrap instance using a
backup file. It updates the existing instances in the environment to
recognise the new state-server. The plugin ensures the state-server is
not running before it create the replacement. As with the normal
bootstrap command, you can pass --constraints to setup the new
state-server.

    $ juju switch my-env
    $ juju-restore juju-backup-2014-02-21.tgz

You can learn more details by running “juju-restore --help”.


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