Updates from November, 2013 Toggle Comment Threads | Keyboard Shortcuts

  • 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

  • garyposter 4:31 pm on November 15, 2013 Permalink | Reply


    Jeff: We have been using anchors even for links that are not supposed to change the URL.  This causes problems with PJAX and is annoying to work around.  Suggested resolution, after discussion: anchor tags should only be used for content that has an href and intends to change the URL.  We should use classed & styled button tags for other in-line controls.

    Gary: why buttons (rather than, say, spans)? Jeff: Because they allow you to support tab and focus support. Gary: But the semantics of an anchor are sometimes correct, right?  If the text is in-line?  Jeff: they are only right if they are a link; otherwise they are a control–e.g., a button.

    Everyone: OK!

  • garyposter 2:54 pm on November 15, 2013 Permalink | Reply  

    Developer docs for releases are on http://juju-gui.readthedocs.org/ (and in the source code under the docs directory).

  • garyposter 2:40 pm on November 15, 2013 Permalink | Reply

    Jorge Castro made a great blog post about bundles.


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

    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 4:57 pm on November 8, 2013 Permalink | Reply

    feature flag notes 

    Benji suggests these feature flag rules

    • Check negative featureflags, not positive feature: in other words the new behavior should be in the main path so you can simply rip out the old path when you are ready.
      • Rick mentions that this will not work out sometimes.
      • Resolution: we prefer this, but it doesn’t always make sense.
      • Benji: if you have a flag check that includes another condition, don’t do it.  Benji can lint this!
    • Check feature flags as few times as possible
      • Lint this?  Rick mentions that this might be unpleasant in some cases. We do not pursue.

    We also liked the effect of old soon-to-be-deletable class subclassing new class, the way charmworld does in; and we liked copying the old tests so we can delete them.  Duplication is OK for tests that will go away.

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

    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:08 pm on November 7, 2013 Permalink | Reply
    Tags: ,   

    Juju Quickstart Plugin: alpha but useful 

    The GUI team has a tool in alpha that we think is useful now. It is an opinionated way to start a great Juju experience quickly. We’re looking for users and feedback from early releases.

    What does it do now?

    If you run the plugin from the commandline, it will bootstrap an environment, install the GUI in the quickest [1] and most efficient [2] way available, and open a web browser to let you see the GUI.

    It also can be used in the same single command to deploy GUI environment exports that do not use local charms, and to deploy the very-soon-to-be-announced charm store bundles.

    We have one known bug: quickstart fails if the bootstrap node is not running Precise (which usually means that default-series is not set to precise in the environment). We will be explicitly setting the bootstrap node to Precise (or eventually Trusty) in the future.

    What will it do?

    Within a couple of weeks, we’ll have the following functionality. This will be added incrementally.

    When you run “juju-quickstart”, it will first install the ppa:juju/stable and Juju itself, if necessary; then, if necessary, it will guide you through (on the commandline) setting up credentials for a variety of supported clouds, as desired; then it will bootstrap a Juju instance, and install the GUI in the most quick and efficient way available; and finally it will open a webbrowser for you, showing the GUI and logging you in automatically. The bundle functionality described above will also be enhanced.

    Moreover, it will always recognize when you already have progress. For instance, if you have Juju installed and credentials configured, it will then start to bootstrap. If you have already bootstrapped but not installed the GUI, it will install the GUI and log you in. If you have installed the GUI on a bootstrapped environment, it will simply open your browser and log you in.

    How can I get it?

    sudo add-apt-repository ppa:juju-gui/quickstart-beta
    sudo apt-get update
    sudo apt-get install juju-quickstart

    Assuming you have Juju (juju-core) installed, now you can run “juju quickstart –help“ and learn what features are available today.

    Once we are through alpha and beta phases, we plan to move the plugin to ppa:juju/stable, and then pursue main inclusion in Trusty.

    Please give us feedback on the juju@lists.ubuntu.com list, on the juju-gui@lists.ubuntu.com list, or by filing a bug.

    Thanks, and enjoy!

    [1] On EC2, installing the GUI via the quickstart plugin adds less than a minute to bootstrapping. Installing it over the API is the quickest way right now because it does not download the charm to your local system and upload it to the environment, so that’s what we use.

    [2] We install the GUI on the Juju state server, so it doesn’t add additional machines to your deployment, or additional time to wait for a new machine to spin up.

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