Juju development summary

[Ian Booth]

Hi folks

Here's a quick wrap up of what the Juju team has been doing lately.

A chunk of time has been spent planning what we want to work on next cycle
leading up to the 18.04 LTS. Issues/features required by the field take a high
priority, including (but not limited to):
- audit logging
- enhancements to bundle deployment
- support for Openstack with Cisco ACI
- containers inheriting properties from hosts
- space selection for controller and agent traffic

There's also other feature work planned such as providing goal state to charms
and other mechanisms to reduce message chatter and improve scalability; post
deploy management of spaces and bindings, crud for spaces and subnets etc; cloud
native functionality exposed to charms.

The main engineering focus has been polishing things for the imminent (late this
week/early next week) 2.3 beta 2 release. There's a number of great improvements
over beta 1 to look forward to, including:
- lease / leadership tracking immune to clock skew / bad ntp
- much better machine provisioning performance across the board (up to 40%
reduction in time when deploying a bundle with 16 machines on openstack)
- resolution of annoying issues like errors like "model not found" on controller
destruction
- cross model support for prometheus and nagio deployments
- lots of polish to various usability paper cuts

For those keen to try beta 2, we guarantee upgradeability from this release to
2.3.0 final. So give it a run and help provide feedback so we can make 2.3 as
awesome as possible.

We also pushed out a couple of 2.2.x point releases since 2.2.4 to fix a few
small but significant issues. We encourage everyone to upgrade to 2.2.6.


Quick links:
  Work pending: https://github.com/juju/juju/pulls
  Recent commits: https://github.com/juju/juju/commits/develop
  Recent 2.2 commits: https://github.com/juju/juju/commits/2.2