[ANN] juju-core 1.9.11 has been released

[David Cheney]

juju-core 1.9.11
================

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

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

juju-core 1.9.11 is available from the Gophers PPA

https://code.launchpad.net/~gophers/+archive/go

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

* HP Cloud is now supported by the OpenStack provider and ready for 
testing. See notes below.
* The help offered by the juju cli commands has been greatly improved.
* An issue was detected after the 1.9.10 release version was cut and 
thus there is no public 1.9.10 release. 1.9.11 supersedes 1.9.10.

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

* The OpenStack specific use-floating-ip configuration variable now 
defaults to false. This behaviour is a change from the 1.9.9 release and 
now matches the Juju 0.6 default.

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.

* Most types of relations are supported, but are not displayed in juju 
status. #1073966
* The juju-core package currently cannot be installed in parallel with 
juju 0.5/0.6 due to conflicting ownership of /usr/bin/juju (and others). 
This may be mitigated in the future with alternatives. The current 
workaround is to remove the juju 0.5/0.6 package before installing 
juju-core 1.9.11.
* 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 HP Cloud
-------------------

Support for HP Cloud is currently experimental.  As such, no public 
tools are available when deploying to HP Cloud. To deploy to HP Cloud 
please follow these steps

1. Compile juju-core from source. Please consult the README file in the 
source for instructions for building juju-core from source. If you 
choose to build juju-core from source, to avoid confusion, you should 
not install juju-core from PPA.
2. Set default-image-id in your environments.yaml to a string value of 
one of the Ubuntu images in your storage region.
3. When bootstrapping, use the --upload-tools flag to compile the tools 
from your local checkout source and push them to your private control 
bucket.

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 2.0.

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