Updates from jeffpihach Toggle Comment Threads | Keyboard Shortcuts

  • jeffpihach 6:01 pm on April 2, 2015 Permalink | Reply  

    Juju GUI 1.3.5 "Cutting Ties" Release 

    Introducing a faster, more responsive GUI thanks to the new Charmstore v4 API. We have finished porting all API calls in the GUI to the new version of the Charmstore API which provides a considerable boost in responsiveness.

    For those who have their own tools relying on the old Charmstore API we will be keeping it around for a while but it is a good idea to start working on porting over to v4. You can find the documentation for the new Charmstore API here: https://github.com/juju/charmstore/blob/v4/docs/API.md

    Screenshot from 2015-04-02 11:04:45

    Changes in this release:

    • Completed converting all API calls to the new Charmstore v4 API.
    • (FIX) Charms which were duplicates of promulgated charms weren’t shown.
    • Add React JSX compilation support to the Makefile.

    To upgrade an existing deployment:

    juju upgrade-charm juju-gui
    juju set juju-gui “juju-gui-source=1.3.5″

    If you run into any bugs from this transition please file them here:https://bugs.launchpad.net/juju-gui

  • jeffpihach 9:00 pm on March 19, 2015 Permalink | Reply  

    Juju GUI 1.3.4 “Not so sticky” Release 

    Here comes another bug fix release for the Juju GUI which contains fixes for bugs reported by you since the last release.

    Screenshot from 2015-03-19 15:26:09

    In this release you’ll find the following updates:

    • (FIX) Service icons on the canvas no longer bounce back to their original
      positions when being repositioned.
    • (FIX) Bundle deploys no longer fail with invalid name error.
    • Removed the Features tab from the charm details pane.
    • Updated a number of api calls to the new v4 api.
    • Updated sysdeps makefile target for easier development.

    To upgrade an existing deployment:

    juju upgrade-charm juju-gui
    juju set juju-gui “juju-gui-source=1.3.3″

    As we move forward on updating the api calls to the new v4 api if you run into any bugs please file them here: https://bugs.launchpad.net/juju-gui

  • jeffpihach 7:47 pm on November 27, 2014 Permalink | Reply  

    Juju GUI 1.3.1 Maintenance Release 

    Following quickly on the heals of the 1.3.0 release which included the new Added Services bar we are putting out a maintenance release which includes a few fixes like:

    • Modifying the visibility of a service using the Added Services bar now animates the service icons on the canvas.
    • UI tweaks for the Inspector, Canvas, and Machine View.
    • (FIX) Change Version option now includes the most recent release version.
    • (FIX) Charm configuration options with null default values are now respected when being deployed or when exporting bundle configurations.

    For those who usually upgrade their charms via the GUI this release will be especially interesting because it fixes an issue where the most recent charm release wouldn’t always show up in the Change Version section of the service’s inspector. You will want to upgrade your existing GUI instance using the CLI for this release to make sure you get the most recent version. Every other release can then be upgraded as usual via the Change Version section of the service inspector. If you aren’t familiar with the Juju CLI the command is:

    juju upgrade-charm juju-gui

    Thanks to everyone who tried out the previous release and submitted bugs and feature requests. We always love to hear your feedback and continue to squash bugs as they pop up. If you have any questions or comments you can find us in #juju-gui and #juju on irc.freenode.net or bugs can be filed on launchpad.

  • jeffpihach 11:08 am on November 18, 2014 Permalink | Reply  

    Juju GUI 1.3.0 Released – Now with Added Services view 

    The Added Services side bar has now been released. This view allows you to highlight and fade services so that you can focus on a smaller segment of your complex environment. Highlighted and faded services will also modify the visibility of machines in the machine view respective to the options selected. To access the added services bar simply click the ‘Added Services’ button at the top of the charm browser then click the light bulb or eye icon to highlight or fade the respective service.


    We have now added a new port configuration option to the Juju GUI charm. This highly requested feature allows you to specify a custom port for the Juju GUI to run on allowing you to run the GUI on a machine or container which already has a service running on port 80 or 443.

    Plus 9 other pull requests including bug fixes and enhancements which you can read more about in the changelog.

    We would love to hear what you think of the new features we have been adding over the past couple months, including the new Added Services bar. If you have any questions or comments you can find us in #juju-gui and #juju on irc.freenode.net or bugs can be filed on launchpad.

  • jeffpihach 8:22 pm on November 19, 2013 Permalink | Reply  

    A Juju Charm designed to fail 

    If you have ever wanted a charm which would fail predictably for testing and development purposes in Juju or the Juju GUI? Wait no more, I bring you the first cut of ‘failtester’. A Charm whose only purpose is to fail predictably depending on the configuration settings passed into it. It can be found on launchpad or jujuCharms.com.

    Additional details can be found on the original post on my blog

  • jeffpihach 7:43 pm on July 3, 2013 Permalink | Reply  

    Juju GUI v0.7.1 Released! 

    As of a few minutes ago the 0.7.1 version of the Juju GUI was released. It brings with it over 1000 unit tests, performance, memory and stability improvements, along with:

    • Added drag and drop deployment from charm browser.
    • Export environment to Juju deployer YAML format from keyboard shortcut (shift-d).
    • Databinding and conflict resolution finalized (feature-flagged).
    • Start of new service inspector development (feature-flagged).
    • Added relations to Go sandbox (Go sandbox still in progress).

    You can download it from Juju GUI on Launchpad.

  • jeffpihach 10:28 pm on June 13, 2013 Permalink | Reply  

    TypeError: JSON.stringify cannot serialize cyclic structures.

    While running the Juju GUI test suite, if you run into the above error from phantomjs look through your commits for console logs which are attempting to dump complex objects or instances which might contain references to itself.

    An common use case could be a log of a Y.Node instance hanging around ie) console.log(Y.one(‘.foo’));

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