[FFE] Update juju-quickstart to support MAAS as a configurable provider

Bug #1359944 reported by Richard Harding
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-quickstart (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

We have the goal this cycle of updating juju-quickstart to be able to build the environments.yaml block for MAAS as it can for local, ec2, hpcloud, etc. This work is not yet complete, but we'd like to request an exception to get it in.

There is little risk that adding another provider will create issues for juju-quickstart users. We already support five providers and so this new one should not require any deep changes to the way quickstart operates.

The changes required are

- The first time you launch quickstart you'd see a new item in the new provider list, MAAS.
- Selecting that needs to populate a form UI for entering all the provider specific information required by MAAS.
- Saving that form updates your environments.yaml with the new provider block as it does for the others.
- We do not currently believe that adding this provider will require fundamental changes in the way juju-quickstart works once the provider is available.

We'll be looking to complete this work before the end of September and have the final juju-quickstart release ready one month before the release of Utopic.

Revision history for this message
Francesco Banconi (frankban) wrote :

The changes has been made and released on PyPI (version 1.4.4): https://pypi.python.org/pypi/juju-quickstart/1.4.4

Quickstart now supports creating and managing MAAS environments: this allows MAAS users to quickly configure and bootstrap an environment on MAAS, including the Juju GUI deployed on the bootstrap node, with automatic login and bundle deployment support. This completes the quickstart offer in terms of supported providers: we need MAAS to be a first class provider along with ec2, amazon, hp cloud and all the other provider types supported by quickstart.

This did not require any change in the list of dependencies.
The feature is properly tested (both unit tests and live tests in a real MAAS controller).

Here is the changelog since 1.4.2:

juju-quickstart (1.4.4) trusty; urgency=low

  * Support creating and using MAAS (Metal As A Service) environments.

 -- Francesco Banconi <email address hidden> Wed, 01 Oct 2014 15:38:32 +0000

juju-quickstart (1.4.3) trusty; urgency=low

  * Support for overriding the Juju executable with the JUJU env var.
  * Add support for Ubuntu 14.10 (utopic).
  * Base dependencies update.

 -- Francesco Banconi <email address hidden> Thu, 11 Sep 2014 11:57:47 +0000

We opened bug 1359938 in order to handle version 1.4.3.
I am available for any help or clarification.

Revision history for this message
Francesco Banconi (frankban) wrote :

Please also note that juju-quickstart is in unverse.

Revision history for this message
Robie Basak (racb) wrote :

Upload blocked by bug 1374335. juju-quickstart 1.4.4 needs python-websocket >= 0.18 and python-jujuclient >= 0.18.4.

Revision history for this message
Scott Kitterman (kitterman) wrote :

$ rmadison juju-quickstart
 juju-quickstart | 1.3.1-0ubuntu1 | trusty/universe | source, all
 juju-quickstart | 1.3.1-0ubuntu1.1 | trusty-updates/universe | source, all
 juju-quickstart | 1.4.2-0ubuntu1 | utopic/universe | source, all
 juju-quickstart | 1.6.0-0ubuntu1 | vivid/universe | source, all

Changed in juju-quickstart (Ubuntu):
status: New → 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.