The newest version of Juju has been released, Juju 2.0 beta 4. One of the exciting new features is built-in support for the Juju GUI. Prior to this release one had to bootstrap Juju and then deploy the juju-gui charm or use a tool like juju-quickstart.
With the new release it has all been greatly simplified. Bootstrap an environment and you get a GUI running on the controller with no extra effort!
Once you’ve bootstrapped a controller use this command to see the GUI:
juju gui –show-credentials
With that command the GUI will connect to your current model and open a browser to it. You’ll need to login using the username and password printed in your terminal.
If you have a controller that has been running for a while and want to get the latest GUI changes, all you need to do is:
That command will download the latest GUI version and replace the one currently running on your controller.
If you want to see which versions are available run:
juju upgrade-gui –list
You can then upgrade or downgrade to one of the available versions by providing it to the upgrade-gui command, e.g.
juju upgrade-gui 2.1.2
You can even try a version of the GUI that has not yet been published in the streams by providing the path to a tarball on your local computer, e.g.
juju upgrade-gui /path/to/release.tar.bz2
In order to upgrade the GUI, you’ll have to have access rights to the controller. When an administrator upgrades the GUI, users will have to reload the open sessions in their browsers to see the changes.
If for some reason you don’t want to install the GUI into the controller, simply bootstrap your controller with the –no-gui flag:
juju bootstrap –no-gui
We think having the GUI built into controllers automatically will be very beneficial for most users. We’ve worked hard to provide an efficient user experience and hope the interface adds a visual dimension as you model and deploy your services.