juju-core 1.26-alpha1
Milestone information
- Project:
- juju-core
- Series:
- 1.26
- Version:
- 1.26-alpha1
- Released:
- Registrant:
- Curtis Hovey
- Release registered:
- Active:
- No. Drivers cannot target bugs and blueprints to this milestone.
Activities
- Assigned to you:
- No blueprints or bugs assigned to you.
- Assignees:
- 1 Anastasia, 1 Andrew McDermott, 15 Andrew Wilkins, 5 Casey Marshall, 8 Cheryl Jennings, 4 Dave Cheney, 1 Dimiter Naydenov, 1 Domas Monkus, 4 Eric Snow, 2 Horacio Durán, 6 Ian Booth, 1 James Tunnicliffe, 2 Jesse Meek, 3 Martin Packman, 1 Menno Finlay-Smits, 5 Michael Foord, 6 Tim Penhey, 1 Wayne Witzel III, 1 William Reade
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- 71 Fix Released
Download files for this release
Release notes
# juju-core 1.26-alpha1
A new development release of Juju, juju-core 1.26-alpha1, is now available.
This release replaces version 1.25.0.
## Getting Juju
juju-core 1.26-alpha1 is available for Wily and backported to earlier
series in the following PPA:
https:/
Windows, Centos, and OS X users will find installers at:
https:/
Development releases use the "devel" simple-streams. You must configure
the `agent-stream` option in your environments.yaml to use the matching
juju agents.
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.26-alpha1.
## Notable Changes
* Native support for charm bundles
* Unit agent improvements
* API login with macaroons
### Native support for charm bundles
The Juju 'deploy' command can now deploy a bundle. The Juju Quickstart
or Deployer plugins are not needed to deploy a bundle of charms. You can
deploy the mediawiki-single bundle like so:
juju deploy cs:bundle/
Local bundles can be deployed by passing the path to the bundle. For
example:
juju deploy ./openstack/
Local bundles can also be deployed from a local repository. Bundles
reside in the "bundle" subdirectory. For example, your local juju
repository might look like this:
juju-repo/
|
- trusty/
- bundle/
|
- openstack/
|
- bundle.yaml
and you can deploy the bundle like so:
export JUJU_REPOSITORY
juju deploy local:bundle/
### Unit agent improvements
We’ve made improvements to worker lifecycle management in the unit agent
in this release. The resource dependencies (API connections, locks,
etc.) shared among concurrent workers that comprise the agent are now
well-defined, modeled and coordinated by an engine, in a design inspired
by Erlang supervisor trees.
This improves the long-term testability of the unit agent, and should
improve the agent’s resilience to failure. This work also allows hook
contexts to execute concurrently, which supports features in development
targeting Ubuntu 16.04.
### API login with macaroons
Added an alternative API login method based on macaroons in support of a
new charm publishing workflow targeting Ubuntu 16.04.
## Known Issues
ARM-HF clients and agents are not available Precise, Trusty and Vivid.
Clients and agents are available for Wily.
## Resolved issues
* /var/lib/juju gone after 1.18->1.20 upgrade and manual edit of
agent.conf
Lp 1444912
* Panic: session already closed in presence watcher
Lp 1497241
* Leadership resolver still too noisy
Lp 1506353
* Maas with http_proxy, juju 1.24.6 -> 1.24.7, upgrade never
finishes
Lp 1509097
* "ignore-
Lp 1509292
* Raw go errors reported to users
Lp 1486254
Finally
We encourage everyone to subscribe the mailing list at
juju-dev@
Changelog
This release does not have a changelog.
