Tagged: juju-gui Toggle Comment Threads | Keyboard Shortcuts

  • jeffpihach 6:51 am on March 19, 2016 Permalink | Reply
    Tags: , juju-gui,   

    Juju GUI 2.1.1 released 


    As a quick follow up to the Juju GUI 2.1.0 release we’ve got a patch release for the Juju GUI making sure that we keep the Juju GUI interactions transparent when working with either Juju or the Juju 2 beta. Along with this release we’ve added a few additional bug and usability fixes:

    • If you have uncommitted changes we now warn you when switching models so you don’t lose your changes accidentally. We will be working towards persisting this data in the future.
    • Disable container and machine creation buttons until we’ve collected enough information to successfully create the machine.
    • Added language and content direction flags so that the input fields work better for users using rtl languages.

    To upgrade an existing deployment:

    juju upgrade-charm juju-gui

    To deploy this release into your model:

    juju deploy juju-gui

    If you find any issues or have any feedback for the Juju GUI we’d love to hear it. Please let us know in our github repository https://github.com/juju/juju-gui/issues and we’ll be sure to get back to you.

  • bradcrittenden 7:02 pm on December 23, 2015 Permalink | Reply
    Tags: juju-gui,   

    Juju GUI 2.0 Beta released 

    We are really happy to announce availability of the new and shiny beta version of Juju GUI 2.0 with completely redesigned and rewritten user interface and improved user experience. The new GUI introduces:

    • redesigned canvas, relation management and charm handling with the new inspector,
    • improved integration with the charm store, unifying the web experience at jujucharms.com,
    • new machine view with drag’n’drop functionality – allocating units has never been easier,
    • creation and switching between models within a controller, and
    • new bundle deploys.

    Not much has stayed the same, so it’s best if you give the new GUI a try yourself.

    We’re aware of the small details that need polish before we close the beta, but we’d like to make the 2.0 release rock solid and therefore would appreciate as much feedback from you as possible. Should you discover a bug, use the GitHub issue tracker to file a report. Please provide as much information as possible, e.g. the cloud provider, the output of ‘juju version’, steps made, errors from the browser console, etc.

    Machine view Model Empty canvas Store

    The major changes for this release are:

    GUI with controllers and models

    If you would like to test the GUI against a Juju controller, the JES feature flag needs to be enabled before bootstrapping. This will enable you to create, list and manage models directly from the GUI.

    juju bootstrap

    Deploying the Juju GUI 2.0 beta

    Juju 1.25 or older

    The charm is available via the charmstore URL cs:~yellow/trusty/juju-gui and at https://jujucharms.com/u/yellow/juju-gui on the web. Just do the usual:

    juju deploy cs:~yellow/juju-gui

    Juju master (1.26 alphas)

    Recent Juju builds support a new publishing mechanism and can properly parse URLs with the development channel. If you’re using recent Juju builds, bootstrap a controller on a cloud of your choice and use the development version of the promulgated Juju GUI charm located at cs:development/juju-gui or https://jujucharms.com/development/juju-gui on the web. You can deploy the development version of the charm with:

    juju deploy cs:development/juju-gui

    You should see a response similar to:

    Added charm “cs:development/trusty/juju-gui-42” to the environment.
    Deploying charm “cs:development/trusty/juju-gui-42” with the charm series “trusty”.


    We hope you find the new GUI easier to use and find the layout to be more intuitive. Enjoy using it and let us know what you think!

  • mitechie 5:37 pm on October 3, 2014 Permalink | Reply
    Tags: , juju-gui,   

    Juju GUI triple release week! 1.2.2 out the door. 

    The last 8 days have been crazy for the team. We released machine view which is a great amount of work from the team.

    Earlier this week we followed that up with a bug fix release. A charm bug and an issue in the search are now fixed up.

    Finally, we’ve released a 1.2.2 today. It adds a UI for custom settings. You can find them by hitting loading up the shortcuts UI with the ‘?’ key. We also moved the service expose/unexpose into the list of changes that can be ‘uncomitted’ and fixed a couple of bugs along the way.

    View the full changelog here

    If you’ve not yet checked out the new Juju GUI, stop by our recent screencasts showing off the new machine view.

  • garyposter 6:42 pm on November 14, 2013 Permalink | Reply
    Tags: , juju-gui, ,   

    jujucharms.com update and Juju GUI 0.13.0 release (mostly bugfix) 

    The jujucharms.com site has been updated with the 0.13.0 Juju GUI release.  In addition to basic bundles available, bigger demonstration ones like this one or this one can show off some of what we can do.

    Also, yes, that’s a new Juju GUI release.  0.13.0 is out the door.  It’s primarily a bugfix release.  Here’s the breakdown.

    • Added help and feedback menu to top right, replacing feedback link on side.
    • (FIX) The inspector tries to get out of your way when you are making a relation.
    • (CLEANUP) Bundle deployment instructions for using quickstart and juju deployer were clarified and brought up to date.
    • (FIX) Fix bundle visualization so that it does not occasionally clip.
    • (CHARM FIX) Charm now honors bundle deployment positioning.
    • (FIX) Services without positioning are less likely to be automatically positioned on top of themselves.
    • (FIX) Make sandbox bundle deployment positioning more reliable.
    • (CLEANUP) Remove remaining old unused notifications code.


  • garyposter 10:10 pm on November 7, 2013 Permalink | Reply
    Tags: , , , , juju-gui,   

    Juju GUI 0.12.0: Bundles (beta)! 

    browsebundle Today we made a huge release for us: Juju GUI 0.12.0.  In arguably the biggest single new feature of the GUI since its release, the GUI now supports importing, exporting, browsing and deploying “bundles”. Bundles are collections of charms and their relations. You can export bundles using the export icon at the top of the GUI (an arrow pointing up out of a box) or shift-d. You can import them using the import icon (an arrow pointing into the box), by dragging yaml files from your computer and dropping then onto the environment, or by deploying bundles found in the store.

    (More …)

    • Robert Keating 4:49 pm on March 10, 2014 Permalink | Reply

      I am trying to import my current Prod environment (which has MaaS tags), and it fails with an ‘unsupported tags’ error. Do you have an update on this?

  • garyposter 9:49 pm on September 18, 2013 Permalink | Reply
    Tags: , juju-gui   

    Juju GUI 0.10.0: A big release 

    We’re very happy to announce the release of Juju GUI 0.10.0.  It has a big change that we are very excited about: the new service inspector.

    InspectorThe inspector lets you look at services and units while still keeping an eye on the bigger context.  It also gives you a more dynamic view than ever before on a changing environment.  Changes to services and units are visible immediately in the inspector.  If you are editing  a value, the inspector can even help you identify conflicts between your choices and a concurrent change from the environment.  You can quickly view the details of the service’s charm, or a unit’s status.  And it is designed to let us bring you even more features in the future.

    If you’d like to take a quick look now, https://jujucharms.com/ can give you a preview.  Once you are ready to use it in your own environment, follow the simple deployment instructions and give it a try.

    We hope you enjoy the new release.  More great things are coming soon.

  • garyposter 1:14 am on July 26, 2013 Permalink | Reply
    Tags: , juju-gui   

    Juju GUI 0.8.1 

    We released Juju GUI 0.8.1 this evening. It fixes a number of bugs.

    • Subordinate charms are now handled correctly in juju core.
    • Fixed bug causing settings page to not scroll.
    • Fixed bug causing the initial loading spinner to spin forever in Firefox with cookies or sessionStorage disabled.
    • Fixed another bug causing the initial loading spinner to spin forever intermittently, rarely.

    We plan to roll these out to jujucharms.com tomorrow morning, US.

    0.8.1 also includes some big progress on upcoming features (search autocomplete, new inspector) but these are hidden behind feature flags. We’ll describe those separately.

  • Madison Scott-Clary (Makyo) 2:19 am on July 23, 2013 Permalink | Reply
    Tags: , juju-gui, OpenStack   

    Deploying OpenStack with Juju and the GUI 

    A small video tutorial on how to deploy OpenStack with Juju using the GUI

  • garyposter 7:13 pm on July 22, 2013 Permalink | Reply
    Tags: , juju-gui,   

    jujucharms.com and Juju GUI 0.8.0 

    I’m very happy to let you know that we have released the Juju GUI 0.8.0, and that it is powering http://jujucharms.com.

    The GUI itself has a lot of incremental improvements and bugfixes in this release, and the UI is even more beautiful and usable. See the bottom of the post for changelog highlights, and see our installation details if you want to know how to use the GUI in your own Juju environment.

    However, our biggest news to my mind is that we now have a jujucharms.com that really encourages discovery and exploration. You can find charms; read more details about them; and experiment live to see how they interact within a mock Juju environment. You can even (hidden feature, for now!) use shift-D to export your experiments into a human readable format, and use that to turn your experiments into a real running system in your own Juju environment (see the Juju Deployer).

    Charmers, never fear: the features you need from the old site are still around, with some improvements. See http://manage.jujucharms.com/.

    Also, the old GUI demo site, uistage.jujucharms.com, will be retired soon, and redirect to jujucharms.com. Meanwhile, if you want to follow along with our progress on a commit-by-commit basis, you are welcome to join us over at http://comingsoon.jujucharms.com/. You may have to clear your cache regularly on that site, if you keep coming back: we are working through this code quickly. 🙂

    And in that vein, the thing I’m most proud of is being a part of the team that is making this! Big thanks and congratulations to UX (esp. Alejandra Obregon and Luca Paulina), Curtis Hovey’s Orange squad, and the Juju UI team.

    Bugfixes and new features are already in trunk, with more exciting things coming. Thanks for reading.


    0.8.0 changelog highlights:

    • Update charm browser styling.
    • Add provider test result data and links
    • Charm browser shows lifetime downloads and commit counts.
    • Update service block design.
    • Fix deployment issues encountered for some charms, e.g. Marco Ceppi’s discource charm.
    • Fix Juju deployer export.
    • More drag and drop deployment refinement and fixes.
    • Many other small bugfixes.
    • Incremental progress on service inspector behind the serviceInspector feature flag.
  • Francesco 10:42 am on April 4, 2013 Permalink | Reply
    Tags: , juju-gui   

    Debugging Juju GUI / juju-core connection 

    The GUI communicates with the juju-core API backend using a secure WebSocket connection. Several operations are performed as the user starts a GUI session:

    • the GUI connects and authenticates to the API server;
    • the GUI subscribes to the juju-core “mega watcher” and starts listening for all state changes;
    • the GUI reacts to those changes (a.k.a. delta stream) updating its internal database;
    • when the user modifies the environment, the GUI makes the corresponding API calls, and waits for responses coming from juju-core.

    Debugging those interactions is not straightforward, but some tools, described below, can simplify the process.

    A precise environment

    juju-core is released more or less every two weeks. Most of the time we need to bootstrap the environment using juju-core trunk, so that we can test the GUI against the newer changes in the API layer, e.g.:

    go install -v launchpad.net/juju-core/...
    $GOPATH/bin/juju bootstrap --upload-tools

    The –upload-tools flag uploads the local juju-core binaries to the environment node. At this point, the best way to set up the GUI and connect it to the bootstrap node is deploying the Juju GUI charm. Here comes the first problem: the Juju GUI charm, at the time of this writing, only works on precise. What if your juju-core development environment is on quantal? The quantal tools are installed in the bootstrap node, but in practice they cannot be reused in other nodes. As a consequence, as far as I know, when starting the agent on the charm machine, juju-core installs the latest precise tools it finds in the cache. If juju-core was recently released this could just work, but often happens that some changes in juju-core trunk break the compatibility between the uploaded quantal tools and the precise ones taken from the cache. In this case, one solution is bootstrapping a precise environment.
    In essence we need to compile and upload tools from precise: there can be many ways to do that, I ended up using a precise LXC container (which can seem convoluted but actually works and is fast enough to set up).

    Create an LXC template in /etc/lxc/local.conf containing the following lines:


    Create a precise LXC, binding your home directory:

    sudo lxc-create -t ubuntu -n juju-precise -f /etc/lxc/local.conf -- \
    -r precise -a `dpkg-architecture -qDEB_HOST_ARCH` -b $USER

    Start the container:

    sudo lxc-start -n juju-precise -d

    SSH into the container and install some required packages (from now on, all operations are intended to be run inside the LXC container).

    sudo apt-get update && sudo apt-get upgrade
    sudo apt-get install language-pack-en
    sudo apt-get install bzr bzrtools build-essential python-software-properties

    Add the Gophers PPA to package sources:

    sudo apt-add-repository ppa:gophers/go && sudo apt-get update

    Install golang, taking version 1.0.3 from the Gophers PPA

    sudo apt-get install golang-stable

    At this point, since your home directory is shared between the host and the container, you should already have the GOPATH environment variable set up.
    We need to rebuild juju-core from precise, and therefore we need to delete the existing quantal binaries. I guess there are better ways to do this, but this is what I came up with:

    rm -rf $GOPATH/pkg/linux_amd64
    go install -v launchpad.net/juju-core/... launchpad.net/goamz/... \

    Time to bootstrap the new precise environment, and deploy the Juju GUI charm into it:

    $GOPATH/bin/juju bootstrap --upload-tools
    $GOPATH/bin/juju deploy cs:~juju-gui/precise/juju-gui
    $GOPATH/bin/juju expose juju-gui
    $GOPATH/bin/juju status


    The first step is exposing the GUI branch we want to debug, e.g.:

    $GOPATH/bin/juju set juju-gui juju-gui-source=lp:juju-gui

    The easiest way to check the API logs is to use the debug-log command, recently reintroduced in juju-core (hooray!):

    $GOPATH/bin/juju debug-log

    Trying to log in from the GUI you will see something like:

    domU-12-31-39-0C-24-F7:2013/04/04 09:44:28 DEBUG JUJU:jujud:machine api: <- {"Request": "Login", "Params": {"Password": "passwd", "AuthTag": "user-admin"}, "Type": "Admin", "RequestId": 0}
    domU-12-31-39-0C-24-F7:2013/04/04 09:44:28 DEBUG JUJU:jujud:machine api: -> {"RequestId":0,"Response":{}}

    The debug-log includes delta events. Anyway, you can also use the short Python script in http://pastebin.ubuntu.com/5676102/: it connects to the bootstrap node address (passed as first argument), authenticates to the API server, and subscribes to the mega watcher, printing to stdout (using a more readable formatting) new events as they arrive.

    • Francesco 3:26 pm on April 8, 2013 Permalink | Reply

      Update: I have not tried, but a recent juju-core change should allow for deploying a precise charm on an environment bootstrapped from quantal with –upload-tools.

      juju bootstrap –upload-tools –fake-series precise

    • garyposter 3:35 pm on April 9, 2013 Permalink | Reply

      Even if you just want to play around, you’ll want to do the first line of the “Debugging” section in Francesco’s blog post, until we make a go-compatible release.

    • Matthew Scott (Makyo) 4:16 pm on May 2, 2013 Permalink | Reply

      Since testing is unhappy on raring, this might be pertinent again.

Compose new post
Next post/Next comment
Previous post/Previous comment
Show/Hide comments
Go to top
Go to login
Show/Hide help
shift + esc