Juju devel 1.21-beta1 is released

[Curtis Hovey-Canonical]

juju-core 1.21-beta1

A new development release of Juju, juju-core 1.21-beta1, is now available.
This release replaces 1.21-alpha2.


Getting Juju

juju-core 1.21-beta1 is available for utopic and backported to earlier
series in the following PPA:

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

The devel packages in this archive use the devel simple-streams.
You must configure the 'agent-stream' option in your
environments.yaml to use the matching juju agents.

    agent-stream: 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.21-beta1.


Notable Changes

 * Manage the agent versions that Juju uses with agent-stream
 * NUMA support
 * Charms can inspect the opened ports
 * More mirrors for faster bootstraps


Manage the agent versions that Juju uses with agent-stream

The 'agent-stream' config option selects the versions of juju that
an environment can deploy and upgrade to. The default behaviour
of juju is to select agents from the "released" stream. These are
the most stable versions of juju. You can set 'agent-stream' to
select "devel" streams now to test the unstable versions of juju.

    agent-stream: devel

In a few weeks, we will add "proposed", which will allow you to
evaluate the next stable version of juju before it is the default
version.

The 'tools-metadata-url' or 'agent-metadata-url' does not need
to be set to get "devel" or "proposed". You can remove it from
environments.yaml if you have set it. 'agent-metadata-url' is
only needed to select a private stream for a private cloud.

If you have an existing test environment using 'tools-metadata-url'
or 'agent-metadata-url', you can still upgrade to 1.21-beta1.
After you upgrade, you can update the environment to use the
devel streams at the default stream location

    juju set-env agent-metadata-url=https://streams.canonical.com/juju/tools
    juju set-env agent-stream=devel

Subsequent upgrades will "just work".


NUMA support

Juju can be tuned to take advantage of NUMA machines. If your
state-server will be on a machine with NUMA support, you can set
'set-numa-control-policy' to true in environments.yaml like this.

    set-numa-control-policy: true

The default value is false.


Charms can inspect the opened ports

Your charm hooks can call the new 'open-ports' shell command to get
a listing of the open ports on the unit.


More mirrors for faster bootstraps

Juju agents are mirrored in the certified public clouds (AWS, Azure,
HP Cloud, and Joyent) to make bootstraps fast. You don't need to
do anything to use them, they just work when we add and update them.

We added mirrors to Joyent. We registered the new regions recently added
to AWS, Azure, and HP Cloud.


Resolved issues

* Juju doesn't retry hard enough when destroying maas environments
  Lp 1384001

* 1.21 alpha 2 broke watch api, no longer reports all services
  Lp 1386143

* Set-env fails to honour deprecated attributes
  Lp 1387953

* Juju debug-log is broken
  Lp 1388688

* Bad apt proxy config file in deployed nodes
  Lp 1309207

* Tools tarballs need to be stored in a directory named after their
  stream
  Lp 1384979

* Juju deploy hangs for a long time and then fails
  Lp 1386405

* Cmd/juju: add help on placement directives (zones, maas host name)
  Lp 1387421

* Juju scp help text is unclear on how to pass additional arguments
  Lp 1387640

* Juju set-env/get-env work with arbitrary strings
  Lp 1304126

* Cannot set user for juju scp
  Lp 1387766

* Status --errors only to show only things with errors
  Lp 1309260

* Provider/azure: boilerplate uses <> inconsistently around values
  that require replacing
  Lp 1381289

* Juju set should give feedback that the value is already set
  Lp 1384622

* Stable juju cannot bootstrap because it selects the devel stanza in
  index.json
  Lp 1389807

* No safe way to publish a stream and preserve existing streams
  Lp 1390250

* Logs are not logrotated
  Lp 1078213

* Juju db should use numactl when running mongo on multi-socket nodes
  Lp 1350337

* Juju status panic if state conn is shutdown || closing.
  Lp 1361316

* Container failed to start with lxc-clone-aufs=true
  Lp 1364939

* No defined 'state-servers' on environment file after bootstrap,
  works after run 'juju status'
  Lp 1370149

* Juju add-unit --to <non-existing-machine> fails too late, leaving
  unit unassigned
  Lp 1384732

* Services are no longer filtered when running juju status
  Lp 1385456

* Ec2 says     agent-state-info: 'cannot run instances: no default
  subnet for availability zone:       ''us-east-1e''. (invalidinput)'
  Lp 1388860

* Provider/ec2: try alternative az on insufficientinstancecapacity
  error
  Lp 1389037

* Provider should test and verify credentials as first operation
  before bootstrap
  Lp 1362072

* Non subordinate container scoped relations broken
  Lp 1382751

* --debug dumps sensitive information to terminal
  Lp 1289038


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