juju-core 1.9.2
Milestone information
- Project:
- juju-core
- Series:
- 1.10
- Version:
- 1.9.2
- Released:
- Registrant:
- Dave Cheney
- 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 Dave Cheney, 1 Gustavo Niemeyer, 1 Roger Peppe, 2 William Reade
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- 2 Invalid, 5 Fix Released
Download files for this release
Release notes
juju-core 1.9.2
A new experimental release of Juju, juju-core 1.9.2, is now available for testing. This is second release of the Go port of Juju and should be considered experimental.
Getting Juju
juju-core 1.9.2 is available from the Gophers PPA
https:/
New and Notable
This release includes several improvements
juju-core now supports bootstrapping and deploying from clients running either Precise or Quantal. However, the client must be running amd64. 386 or arm clients are not supported.
juju-core now supports environments running Precise or Quantal.
Support has been added for EC2 ap-southeast-2 region.
In the hope of encouraging collaborators, initial README and CONTRIBUTING documentation is available in the source.
Known bugs and limitations
As this is an early release of Juju in Go there are a number of features which are still to be implemented. A non exhaustive list of known issues is as follows.
EC2 is the only supported provider.
Raring series environments are not supported.
Most types of relations are supported, but they are not displayed in juju status. #1073966
The ssl-hostname-
us-east-1 is the most reliable region to deploy into. Due to subtle differences in the EC2 regions, juju bootstrap may fail. The current workaround is to use us-east-1, retry your juju deploy command, or change your control bucket after destroying your previous environment. #1042107
The juju-core package currently cannot be installed in parallel with juju 0.5/0.6 due to conflicting ownership of /usr/bin/juju (and others). This may be mitigated in the future with alternatives.
destroy-service is not yet implemented. As a workaround you can remove all the units assigned to a service. This is issue #1027878.
terminate-machine is not yet implemented. #1073976
Constraints are not yet implemented. #1027873
Subordinate charms are not yet implemented.
We encourage everyone to subscribe the mailing list at juju-dev@
Dave Cheney
On behalf of the Juju team
https:/
Changelog
This release does not have a changelog.
0 blueprints and 7 bugs targeted
| Bug report | Importance | Assignee | Status | |||
|---|---|---|---|---|---|---|
| 1052836 | #1052836 | cmd/jujuc/server: FAIL: context_test.go:238: RunHookSuite.TestRunHook | 3 High | Roger Peppe | 3 Invalid | |
| 1067127 | #1067127 | juju remove-unit stops, but does not reclaim a machine | 1 Undecided | 3 Invalid | ||
| 1043557 | #1043557 | Mongo dependency should be known and fixed | 3 High | 10 Fix Released | ||
| 1046575 | #1046575 | Minor fixes in the mstate presence watching logic | 3 High | Gustavo Niemeyer | 10 Fix Released | |
| 1052387 | #1052387 | environs/ec2: FAIL: live_test.go:0: localServerSuite.TestBootstrap | 3 High | Dave Cheney | 10 Fix Released | |
| 1037068 | #1037068 | started unit agent should join relations | 1 Undecided | William Reade | 10 Fix Released | |
| 1037077 | #1037077 | unit agent must respond to unit lifecycle changes | 1 Undecided | William Reade | 10 Fix Released | |
