Juju Quickstart 2.0

The UI Engineering Team is proud to announce the 2.0 release of Juju Quickstart!

The new release includes the following new features and fixes:

  • Update the way bundles are specified on the command line.
    The new simplified jujucharms.com syntax is used, e.g.

    juju-quickstart mediawiki-single

    User owned bundles can be deployed as follows:

    juju quickstart u/bigdata-dev/apache-analytics-sql

    The old bundle:mediawiki/single form is still supported but deprecated.

  • Add support for new Juju WebSocket API endpoints.
    Connect to a specific environment using its unique identifier when
    supported by the Juju version in use.
  • External Python API refactoring: implement the Juju reference model
    (charm and bundle URLs).
    Also improve support for bundles as first class entities.
    See models/references.py and models/bundles.py for details.
  • Retrieve bundles from the new charm store API v4.
  • Improve the testing infrastructure: exercise Quickstart with all the
    supported dependency versions.
    Also introduce functional tests against a real Juju environment.
    See the HACKING file for more details.

This version introduces some backward incompatible changes:
When deploying bundles, specifying a directory is no longer supported.
Local files are still supported but must have a .yaml or .json extension.
For more details, see juju-quickstart --help.

Juju Quickstart helps both new and experienced users to quickly start Juju and the Juju GUI, whether they’ve never installed Juju or they have an existing Juju environment running.

The program is available on Ubuntu releases 12.04 LTS (precise), 14.04 LTS (trusty), 14.10 (utopic), 15.04 (vivid) and on OS X (10.7 and later). To install and start Juju Quickstart on Ubuntu, run these commands:

sudo add-apt-repository ppa:juju/stable
sudo apt-get update && sudo apt-get install juju-quickstart
juju-quickstart [-i]

On OS X, use Homebrew:

brew install juju-quickstart
juju-quickstart [-i]

For more details, have a look at this blog post.