Comment 3 for bug 1364946

Revision history for this message
Martin Hilton (martin-hilton) wrote :

Incidently if you then continue with the already set up, and bootstrapped environement then it completes

$ juju-quickstart -e hpcloud Downloads/bundles.yaml
juju quickstart v1.4.2
contents loaded for bundle envExport (services: 2)
bootstrapping the hpcloud environment (type: openstack)
reusing the already bootstrapped hpcloud environment
retrieving the environment status
retrieving the Juju API address
connecting to wss://15.126.225.8:17070
bootstrap node series: trusty
charm URL: cs:trusty/juju-gui-6
service juju-gui already deployed
exposing service juju-gui
requesting new unit deployment
juju-gui/0 deployment request accepted
juju-gui/0 placed on 15.126.225.8
juju-gui/0 deployment is pending
machine 0 is started
juju-gui/0 is installed
juju-gui/0 is ready on machine 0

Juju GUI URL:
password:

connecting to the Juju GUI server
requesting a deployment of the envExport bundle with the following services:
  mariadb, wordpress
bundle deployment request accepted
use the GUI to check the bundle deployment progress
done!

Run "juju quickstart -e hpcloud" again if you want
to reopen and log in to the GUI browser later.
Run "juju quickstart -i" if you want to manage
or bootstrap your Juju environments using the
interactive session.
Run "juju destroy-environment hpcloud [-y]"
to destroy the environment you just bootstrapped.