[ANN] juju-core 1.9.8 has been released

[David Cheney]

[this will be cross posted to juju at lists.ubuntu.com shortly]

juju-core 1.9.8
===============

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

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

juju-core 1.9.8 is available from the Gophers PPA

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

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

* Juju client now supports OS X -- No binary packages are available, but

      go get launchpad.net/juju-core/cmd/juju

will download and compile from source providing Go is already installed.
* Experimental support for OpenStack Folsom -- Basic bootstrapping and 
status has been tested on Canonistack and HP Cloud.
* Juju client now generates a sample configuration if you ask it nicely 
-- “juju generate-config” will print a sample configuration to stdout. 
Use the ‘-w’ flag to write it to ~/.juju/environments.yaml. It will 
include (commented out) sections for all registered providers (ec2 and 
openstack), including reasonable defaults where possible (randomized 
names for default containers, admin keys, valid instance ids for known 
regions, etc).
* Raring series environments are now supported.

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

You can now use “juju generate-config -w” to write a sample bootstrap 
file.  Example:

      environments:
        openstack:
          type: openstack
          auth-url: https://keystoneurl:35357/v2.0/
          admin-secret: <random-hex-string>
          control-bucket: <unique-bucket-per-environment>
          default-image-id: <nova image id>
          auth-mode: userpass

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.8.
* terminate-machine is not yet implemented. #1073976
* Constraints are not yet implemented. #1027873

As an unstable release we do not yet guarantee a clean upgrade path of 
running environments from one 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