Web GUI for Juju
This charm makes it easy to deploy a Juju GUI into an existing environment.
The Juju GUI supports recent releases of the Chrome, Chromium and Firefox web
The Juju GUI runs the Juju Charm Store on
jujucharms.com. From there, you can browse charms,
try the GUI, and build an example environment to export for use elsewhere.
A staging server is also available,
running the latest and greatest version.
Deploying the Juju GUI is accomplished using Juju itself.
You need a configured and bootstrapped Juju environment: see the Juju docs
about getting started,
and then run the usual bootstrap command.
Next, you simply need to deploy the charm and expose it. (See also "Deploying
with Jitsu" below, for another option.)
juju deploy juju-gui
juju expose juju-gui
Finally, you need to identify the GUI's URL. It can take a few minutes for the
GUI to be built and to start; this command will let you see when it is ready
to go by giving you regular status updates:
watch juju status
Eventually, at the end of the status you will see something that looks like
That means you can go to the public-address in my browser via HTTPS
(https://ec2-www-xxx-yyy-zzz.compute-1.amazonaws.com/ in this example), and
start configuring the rest of Juju with the GUI. You should see a similar
web address. Accessing the GUI via HTTP will redirect to using HTTPS.
By default, the deployment uses self-signed certificates. The browser will ask
you to accept a security exception once.
You will see a login form with the username fixed to "user-admin" (for juju-
core) or "admin" (for pyjuju). The password is the same as your Juju
environment's admin-secret, found in ~/.juju/environments.yaml.
When using the default options the charm uses the network connection only for
installing Deb packages from the default Ubuntu repositories. For this reason
the charm can be deployed behind a firewall in the usual way:
juju deploy juju-gui
There are situations and customizations in which the charm needs to connect to
If, for any reason, you need to use the legacy server, it is still possible to
deploy behind a firewall configuring the charm to pull the GUI release from a
location you specify.
For both Juju Core and PyJuju, you must simply do the following steps. Note
that PyJuju must do these steps, plus another set described further below.
The config variable juju-gui-source allows a url: prefix which understands
both http:// and file:// protocols. We will use this to load a local copy
of the GUI source.
Set the config variable to that location using a command such as
juju set juju-gui juju-gui-source=url:...
where the ellipsis after the url: is your http:// or file:// URI. This
may also be done during the deploy step using --config.
If you had already tried to deploy the GUI and received an install error due
to not being able to retrieve the source, you may also need to retry the unit
with the following command (using the unit the GUI is deployed on):
juju resolved --retry juju-gui/0
These steps are sufficient for Juju Core. If you are using PyJuju, you need to
do another set of steps in addition.
Use bzr to branch lp:~hazmat/juju/rapi-rollup locally ("bzr branch
lp:~hazmat/juju/rapi-rollup") and copy the branch to the gui service machine.
Use "juju set juju-gui juju-api-branch=PATH_TO_LOCAL_BZR_BRANCH" (where the
path is not a file:// URI).
Retry as described in the step 3 above (juju resolved --retry juju-gui/0).
When a new version of Juju GUI is released, the charm is updated to include the
new release in the local releases repository. Assuming the new version is
1.0.1, after upgrading the charm, it is possible to also upgrade to the newer
Juju GUI release by running the following:
juju set juju-gui-source=1.0.1
In this case the new version will be found in the local repository and
therefore the charm will not attempt to connect to Launchpad.
The instructions above cause you to use a separate machine to work with the
GUI. If you'd like to reduce your machine footprint (and perhaps your costs),
you can colocate the GUI with the Juju bootstrap node.
This approach might change in the future (possibly with the Juju shipped with
Ubuntu 13.10), so be warned.
The instructions differ depending on the Juju implementation.
Replace "juju deploy cs:precise/juju-gui" from the previous
instructions with this:
juju deploy --force-machine 0 cs:precise/juju-gui
Colocation support is not included by default in the pyjuju implementation; to
activate it, you will need to install Jitsu:
sudo apt-get install juju-jitsu
and then replace "juju deploy cs:precise/juju-gui" from the previous
instructions with this:
jitsu deploy-to 0 cs:precise/juju-gui
If you run into problems with the charm, please feel free to contact us on the
Juju mailing list, or on
Freenode's IRC network on #juju. We're not always around (working hours in
Europe and North America are your best bets), but if you send us a mail or
ping "jujugui" we will eventually get back to you.
If you want to help develop the charm, please see the charm's HACKING.md.