juju-core 1.19.4

This is an unstable micro release.

Milestone information

Project:
juju-core
Series:
1.20
Version:
1.19.4
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:
17 Andrew Wilkins, 3 Curtis Hovey, 3 Dave Cheney, 1 Dimiter Naydenov, 1 Domas Monkus, 1 Eric Snow, 1 Horacio Durán, 10 Ian Booth, 1 Jimmie Butler, 3 John A Meinel, 1 Jorge Niedbalski, 1 Matthew Williams, 1 Menno Finlay-Smits, 3 Michael Foord, 1 Tim Penhey, 4 Wayne Witzel III
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
54 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.19.4.exe (md5, sig) Windows installer for the juju client 35
last downloaded 69 weeks ago
download icon juju-core_1.19.4.tar.gz (md5, sig) Juju-core release 113
last downloaded 69 weeks ago
Total downloads: 148

Release notes 

juju-core 1.19.4

A new development release of Juju, juju-core 1.19.4, is now available.

Getting Juju

juju-core 1.19.4 is available for trusty and backported to earlier
series in the following PPA:
    https://launchpad.net/~juju/+archive/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.19.4.

If you are using a development release of juju-core, and find you need
to go back to a stable release, you can find it in the juju stable PPA:
    https://launchpad.net/~juju/+archive/stable

If you have multiple sources of juju-core, you can select the version
you want using apt:
    sudo apt-get install juju-core=1.18.4*

New and Notable

* Availability zone placement

* Network constraints and deploy argument for MasS

* Server side API Versioning

Resolved issues

* Images are not found if endpoint and region are inherited from
  the top level in simplestreams metadata
  Lp 1329805

* Replicaset initiation fails when mongo is on a big, slow disk
  Lp 1327940

* Missing @ syntax for reading config setting from file content
  Lp 1216967

* Upgrading 1.18 to 1.19 breaks agent.conf
  Lp 1333682

* Juju upgrade-juju needs a dry run mode
  Lp 1272544

* Juju debug-hooks should display a start message
  Lp 1270856

* Can't determine which relation is in error from status
  Lp 1194481

* local charm deployment fails with symlinks
  Lp 1330919

* The root-disk constraint is broken on ec2
  Lp 1324729

* Creating a local environment stops the syslog (1.19.3)
  Lp 1332358

* Can't destroy MAAS environment with LXCs
  Lp 1325830

* Default bootstrap timeout is too low for MAAS environments
  Lp 1314665

* Azure destroy-environment does not complete
  Lp 1324910

* Azure bootstrap dies with xml schema validation error
  Lp 1259947

* Azure provider stat output does not show machine hardware info
  Lp 1215177

* Bootstrapping azure causes memory to fill
  Lp 1250007

* Floating IPs are not recycled in OpenStack Havana
  Lp 1247500

Availability zone placement

Juju supports explicit placement of machines to availability zones
(AZs), and implicit spread units across the available zones.

When bootstrapping or adding a machine, you can specify the availability
zone explicitly as a placement directive. e.g.

    juju bootstrap --to zone=us-east-1b
    juju add-machine zone=us-east-1c

If you don't specify a zone explicitly, Juju will automatically and
uniformly distribute units across the available zones within the region.
Assuming the charm and the charm's service are well written, you can
rest assured that IaaS downtime will not affect your application.
Commands you already use will ensure your services are always available.
e.g.

    juju deploy -n 10 <service>

When adding machines without an AZ explicitly specified, or when adding
units to a service, the ec2 and openstack providers will now
automatically spread instances across all available AZs in the region.
The spread is based on density of instance "distribution groups".

State servers compose a distribution group: when running "juju
ensure-availability", state servers will be spread across AZs. Each
deployed service (e.g. mysql, redis, whatever) composes a separate
distribution group; the AZ spread of one service does not affect the AZ
spread of another service.

Amazon's EC2 and OpenStack Havana-based clouds and newer are supported.
This includes HP Cloud. Older versions of OpenStack are not supported.
Azure uses an inverted concept of availability sets, and Juju announced
support for this in 1.19.0

Network constraints and deploy argument for MasS

You can specify which networks to include or exclude as a constraint to
the deploy command. The constraint is used to select a machine to deploy
the service's units too. The value of "networks=" is a comma-delimited
list of juju network names (provided by MaaS). Excluded networks are
prefixed with a "^". For example, this command specify the service
requires the "logging" and "storage" networks and conflicts with the
"db" and "dmz" networks.

    juju deploy mongodb --constraints networks=logging,storage,^db,^dmz

The network constraint does not enable the network for the service. It
only defines what machine to pick.

Use the "deploy" command's "--networks" argument to specify
service-specific network requirements. The "--networks" argument takes a
comma-delimited list of juju-specific network names. Juju will enable
the networks on the machines that host service units.

Juju networking support is still experimental and under development,
currently only supported with the MaaS provider.

The "--exclude-network" argument was removed from the deploy command as
it is superseded by the constraint option.

There are plans to add support for network constraint and argument with
Amazon EC2, Azure, and OpenStack Havana-based clouds like HP Cloud, in
the next several releases.

Server Side API Versioning

The Juju API server now has support for a Version field in requests that
are made. For this release, there are no RPC calls that require anything
other than "version=0" which is the default when no Version is supplied.
This should have limited impact on existing CLI or API users, since it
allows us to maintain exact compatibility with existing requests. New
features and APIs should be exposed under versioned requests.

For details on the internals (for people writing API clients), see:
    https://docs.google.com/document/d/1fPOSUu7Dc_23pil1HGNTSpdFRhkMHGxe4o6jBghZZ1A/edit?usp=sharing

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 54 bugs targeted

Bug report Importance Assignee Status
1247500 #1247500 Floating IPs are not recycled in OpenStack Havana 2 Critical Ian Booth  10 Fix Released
1328905 #1328905 hpcloud: index file has no data for cloud 2 Critical Ian Booth  10 Fix Released
1329123 #1329123 status outage during upgrades in joyent, Juju is broken 2 Critical Ian Booth  10 Fix Released
1329544 #1329544 HA performance degradation 2 Critical Ian Booth  10 Fix Released
1330162 #1330162 provider/openstack: everything is broken if AZs aren't supported 2 Critical Andrew Wilkins  10 Fix Released
1330163 #1330163 provider/ec2: availability zones may be reported "available" and yet unusable 2 Critical Andrew Wilkins  10 Fix Released
1330919 #1330919 local charm deployment fails with symlinks 2 Critical Ian Booth  10 Fix Released
1331744 #1331744 panic: reflect: Call of unexported method ppc64el/gccgo unit tests 2 Critical John A Meinel  10 Fix Released
1332110 #1332110 restore fails on hp and aws 2 Critical Horacio Durán  10 Fix Released
1332365 #1332365 trusty EC2: cannot initiate replica set 2 Critical   10 Fix Released
1333098 #1333098 API panic running test suite 2 Critical John A Meinel  10 Fix Released
1333357 #1333357 apiserver/networker go1: internal compiler error: in comparison 2 Critical Dave Cheney  10 Fix Released
1333682 #1333682 upgrading 1.18 to 1.19 breaks agent.conf 2 Critical Ian Booth  10 Fix Released
1183831 #1183831 unable to specify availability zone 3 High Andrew Wilkins  10 Fix Released
1194481 #1194481 Can't determine which relation is in error from status 3 High Menno Finlay-Smits  10 Fix Released
1250007 #1250007 Bootstrapping azure causes memory to fill 3 High Andrew Wilkins  10 Fix Released
1252759 #1252759 destroy-environment hangs forever 3 High Andrew Wilkins  10 Fix Released
1259350 #1259350 juju bootstrap fails in Azure (BadRequest - The affinity group name is empty or was not specified.) 3 High Andrew Wilkins  10 Fix Released
1259947 #1259947 Azure bootstrap dies with xml schema validation error 3 High Andrew Wilkins  10 Fix Released
1270856 #1270856 Juju debug-hooks should display a start message 3 High Domas Monkus  10 Fix Released
1272544 #1272544 juju upgrade-juju needs a dry run mode 3 High Matthew Williams  10 Fix Released
1307736 #1307736 ensure-availability can add more state servers while ones it just started haven't come up yet 3 High Wayne Witzel III  10 Fix Released
1310268 #1310268 rsyslog should accumulate on all state machines 3 High Wayne Witzel III  10 Fix Released
1310449 #1310449 rsyslog worker should have its own watcher 3 High Wayne Witzel III  10 Fix Released
1312121 #1312121 juju ensure-availability immediately after bootstrap considers machine-0 as not available 3 High Wayne Witzel III  10 Fix Released
1314665 #1314665 default bootstrap timeout is too low for MAAS environments 3 High Jorge Niedbalski  10 Fix Released
1323160 #1323160 repliaset test failure - closed explicitly 3 High Ian Booth  10 Fix Released
1323263 #1323263 remove --exclude-network from deploy 3 High Dimiter Naydenov  10 Fix Released
1323774 #1323774 win installer broken by bad version 3 High Curtis Hovey  10 Fix Released
1323898 #1323898 failed test: storageSuite.TestWriteFailure 3 High Andrew Wilkins  10 Fix Released
1323937 #1323937 panic setting up 1.18.1 to upgrade to 1.20-beta1 3 High Tim Penhey  10 Fix Released
1324255 #1324255 Precice local provider cannot boostrap 3 High Michael Foord  10 Fix Released
1324729 #1324729 root-disk constraint broken on ec2 3 High Ian Booth  10 Fix Released
1324910 #1324910 azure destroy-environment does not complete 3 High Andrew Wilkins  10 Fix Released
1325072 #1325072 unit tests fail on utopic 3 High Ian Booth  10 Fix Released
1325074 #1325074 Juju version cannot be set to 1.19.4 3 High Curtis Hovey  10 Fix Released
1325707 #1325707 ppc unittests broken by "bytes" package 3 High Dave Cheney  10 Fix Released
1325830 #1325830 Can't destroy MAAS environment with LXCs 3 High Andrew Wilkins  10 Fix Released
1326506 #1326506 Juju upgrade of precise local env timeouts 3 High Michael Foord  10 Fix Released
1327940 #1327940 replicaset initiation fails when mongo is on a big, slow disk 3 High Andrew Wilkins  10 Fix Released
1328716 #1328716 CONTRIBUTING should be cleaned up a bit 3 High Eric Snow  10 Fix Released
1329805 #1329805 juju search for image does not find item if endpoint and region are inherited from the top level 3 High Ian Booth  10 Fix Released
1332358 #1332358 creating a local environment stops the syslog (1.19.3) 3 High Michael Foord  10 Fix Released
1242468 #1242468 Boilerplate for HP Cloud missing several keys 4 Medium   10 Fix Released
1283244 #1283244 500 errors on azure intermittent, stop machine deployment 4 Medium Andrew Wilkins  10 Fix Released
1289815 #1289815 machine address updater should only send transaction if delta 4 Medium Andrew Wilkins  10 Fix Released
1293697 #1293697 state/api/provisioner: TestWatchContainersAcceptsSupportedContainers fails intermittently 4 Medium Andrew Wilkins  10 Fix Released
1319694 #1319694 Client API is a bit special 4 Medium John A Meinel  10 Fix Released
1324599 #1324599 juju/azure doesn't cleanup its private containers 4 Medium Andrew Wilkins  10 Fix Released
1215177 #1215177 Azure provider stat output does not show machine hardware info (ie cpu, mem) 5 Low Andrew Wilkins  10 Fix Released
1299171 #1299171 local provider doles out install requirements piecemeal 5 Low Curtis Hovey  10 Fix Released
1301369 #1301369 azure provider TestStopInstancesWithLimitedConcurrency 5 Low Andrew Wilkins  10 Fix Released
1312940 #1312940 Update to use gosshnew from go.crypto 5 Low Dave Cheney  10 Fix Released
1321236 #1321236 Client.AddMachines returns machine Ids instead of Tags 5 Low Jimmie Butler  10 Fix Released
This milestone contains Public information
Everyone can see this information.