[ANN] juju-core 1.9.14 has been released

[David Cheney]

juju-core 1.9.14
================

A new release of Juju, juju-core 1.9.14, is now available for testing.

Getting Juju
------------

The location of the PPA has changed, please note the new location.

juju-core 1.9.14 is available from the Juju development PPA

https://launchpad.net/~juju/+archive/devel

New and Notable
---------------

 * Juju now supports Metal as a Service (maas) provided environments.

 * juju upgrade-charm command is now available and compatible with
Python juju.
 * juju deploy now supports setting basic constraints on EC2 (Openstack
and MaaS provider support in progress), so you can write:

    juju deploy --constraints "cpu=8 mem=32G" mysql

   and get an appropriate machine.
 * juju set-environment / get-environment to permit updating SSH keys
and other environment settings on live environments in a clean way.
 * juju status now displays basic relation information.
Juju-core now deploys charms on the specified series, or fails cleanly.
 * juju deploy and juju add-unit now take an experimental switch
"--force-machine" with to juju deploy and juju add-unit` which takes a
machine ID, and forces a unit to be deployed to a specific machine.
This enables co-location of unrelated services on an existing machine,
but requires the administrator to manually assure that the two services
are actually co-installable.
 * For Raring and above, the mongodb dependency is now part of the core
distribution. for Quantal and Precise, the mongodb dependency is sourced
from a PPA. This will be updated shortly once mongodb has been backported.
 * juju status is more compatible with Python juju: relations, machine
agent-state and errors are displayed properly.
 * juju-core now has an API for watching all events in the system,
useful for tools like the Juju-GUI to be able to track the current state
of the environment.
 * The juju-core logging system has been updated, and the volume of log
messages has been reduced to a readable level.
 * Tool distribution in private clouds now supported.
 * The logic to find compatible tools has been rewritten and tool
discovery should be much more reliable.
 * The juju-core package now includes a basic man page.
 * Machine reuse has been disabled -- thus preventing old-unremoved
service cruft from potentially polluting a new service.

Configuration changes
---------------------

 * none

Known bugs and limitations
--------------------------

As this is an early release of Juju in Go there are a number of features
which are still to be implemented. A non exhaustive list of known issues
is as follows.

 * Constraints are not yet implemented. #1027873
 * The Openstack provider only supports the userpass authentication
scheme. The keypass authentication scheme is not supported.  #1135335

Testing on Canonistack and HP Cloud
-----------------------------------

A publicly readable bucket has been created for holding the Juju tools
on Canonistack. To use it, put this in your ~/.juju/environments.yaml
(all on one line):

    public-bucket-url:
https://swift.canonistack.canonical.com/v1/AUTH_526ad877f3e3464589dc1145dfeaac60

For HP Cloud the public bucket is available at:

    public-bucket-url:
https://region-a.geo-1.objects.hpcloudsvc.com/v1/60502529753910


As an unstable release we do not yet guarantee a clean upgrade path of
running environments from on 1.9.x version to another.  However,
live-upgrades may work now, and will be a supported feature of 1.10.

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

Dave Cheney
On behalf of the Juju team
https://launchpad.net/juju-core