[FFe] juju-core 1.16 for Ubuntu 13.10

Bug #1219879 reported by James Page
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
juju-core (Ubuntu)
Fix Released
High
Unassigned

Bug Description

juju-core 1.16.0 stable release is due by the 3rd October and includes the following features over the version already in the archive:

* MAAS Tag support
* Get juju tools and cloud configuration data from a central well know location
* support for --ssl-hostname-verification: false
* API only communication with the state server for all non-state-server agents (not CLI, and not removing direct mongo access for agents at earlier versions)
* manual provisioning, bootstrap and null provider -- ability to create nodes and even bootstrap a full environment using pre-existing machines and SSH.
* Support for the VPC by default changes on EC2
* Improved hook error reporting
* Early failure when we know up front that lxc containers can't get addresses

Possible additional features.

* KVM container support
* Split out ~/.juju/environments/<env>.yaml (related to the endpoint caching feature above)
* CLI tool caches endpoint addresses locally for faster connect time

Approval is sought from the release team to upgrade to this new version upon release.

James Page (james-page)
summary: - [FFe] juju-core to 1.14.0 stable release for Ubuntu 13.10
+ [FFe] juju-core past 1.14.0 stable release for Ubuntu 13.10
James Page (james-page)
summary: - [FFe] juju-core past 1.14.0 stable release for Ubuntu 13.10
+ [FFe] juju-core 1.16 for Ubuntu 13.10
James Page (james-page)
description: updated
Mark Ramm (mark-ramm)
description: updated
James Page (james-page)
description: updated
Changed in juju-core (Ubuntu):
importance: Undecided → High
Revision history for this message
Antonio Rosales (arosales) wrote :

https://launchpad.net/juju-core/+milestone/1.16.0 is also tracking bugs for the 1.16 release targetted for Oct 3.

-thanks,
Antonio

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in juju-core (Ubuntu):
status: New → Confirmed
Revision history for this message
Tim Penhey (thumper) wrote :

1.16 will also fix the local provider, which is broken on saucy with 1.14 due to changes in upstart and lxc.

Revision history for this message
Antonio Rosales (arosales) wrote :

Note 1.15.1 milestone:
  https://launchpad.net/juju-core/+milestone/1.15.1
has the targeted bugs.

-thanks,
Antonio

Mark Ramm (mark-ramm)
description: updated
Revision history for this message
James Page (james-page) wrote :

For reference I've tested:

juju bootstrap and deploy with the local provider on Saucy
juju juju-upgrade, and juju bootstrap and deploy with the openstack provider
juju juju-upgrade with the maas provider

All completed successfully.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package juju-core - 1.16.0-0ubuntu1

---------------
juju-core (1.16.0-0ubuntu1) saucy; urgency=low

  * New upstream stable release (LP: #1219879).
 -- James Page <email address hidden> Thu, 10 Oct 2013 18:07:45 +0100

Changed in juju-core (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.