juju-core 1.23.1

Milestone information

Project:
juju-core
Series:
1.23
Version:
1.23.1
Released:
 
Registrant:
Curtis Hovey
Release registered:
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
1 Dimiter Naydenov, 1 Martin Packman
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
2 Fix Released

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon juju-setup-1.23.1-signed.exe (md5, sig) Signed Windows installer for the juju client 5
last downloaded 261 weeks ago
download icon juju-1.23.1-osx.tar.gz (md5, sig) OS X juju commands tarball 2
last downloaded 261 weeks ago
download icon juju-setup-1.23.1.exe (md5, sig) Windows installer for the juju client 16
last downloaded 261 weeks ago
download icon juju-core_1.23.1.tar.gz (md5, sig) Juju-core release 24
last downloaded 261 weeks ago
Total downloads: 47

Release notes 

# juju-core 1.23.1

A new proposed stable release of Juju, juju-core 1.23.1, is now available.
This release may replace version 1.23.0 on Thursday April 23.

## Getting Juju

juju-core 1.23.1 is available for vivid and backported to earlier
series in the following PPA:

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

Windows and OS X users will find installers at:

    https://launchpad.net/juju-core/+milestone/1.23.1

Proposed releases use the "proposed" simple-streams. You must configure
the `agent-stream` option in your environments.yaml to use the matching
juju agents.

## Notable Changes since 1.23.0

### Experimental: Addressable LXC Containers and KVM Instances on AWS and MAAS

The Juju AWS and MAAS providers now support starting LXC containers. The
MAAS providers also supports networking on KVM. Containers and Virtual
Machines will be given statically allocated private IP addresses from
the same subnet as their host machine. For example on MAAS you can now:

    juju deploy wordpress --to lxc:0
    juju add-unit mysql --to kvm:1

This experimental feature can be enabled when the environment is
bootstrapped like so:

    JUJU_DEV_FEATURE_FLAGS="address-allocation" juju bootstrap

These two units can now talk directly on the private subnet.

## Resolved issues

  * Addressable containers cannot resolve non-fqdn in maas
    Lp 1445063

  * Vivid bootstrap and destroy-environment intermittently fails
    Lp 1446662

Finally

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

Changelog 

This release does not have a changelog.

0 blueprints and 2 bugs targeted

Bug report Importance Assignee Status
1445063 #1445063 addressable containers cannot resolve non-FQDN in maas 2 Critical Dimiter Naydenov  10 Fix Released
1446662 #1446662 Vivid bootstrap and destroy-environment intermittently fails 2 Critical Martin Packman  10 Fix Released
This milestone contains Public information
Everyone can see this information.