Updates from March, 2014 Toggle Comment Threads | Keyboard Shortcuts

  • mitechie 7:05 pm on March 28, 2014 Permalink | Reply

    Juju GUI team weekly update 

    Jeff suggests we look at a way of creating ‘saved state’ in the GUI to help us work on the new machine view features. Often, these require there to be an existing environment and a way to replicate our old rapi json environment states in the sandbox would be a welcome tool. Jeff is investigating what we can do to load such data from localStorage or other locations before the App processes. Thanks Jeff!

    Rick brings up that QA day has fallen by the wayside a bit. We should bring it back and make a good attempt to keep ahead of QA issues while we’re churning the code base so much for machine view. All agree this is good and Rick will poke people during their QA day to help remind folks.

  • Francesco 3:47 pm on March 25, 2014 Permalink | Reply
    Tags: ,   

    juju-quickstart 1.2.0 released 

    Juju Quickstart helps both new and experienced users quickly start Juju from Ubuntu.
    Release 1.2.0 is out, and includes the following new features/bug fixes:

    • Support for promulgated bundle URLs, e.g. “juju quickstart bundle:mediawiki/single”.
    • Bundles can be also specified via their jujucharms URLs.
    • Improved application help and installation instructions.
    • Updates to the dependency list and to Juju version handling.
    • SSH code reorganization.
    • Distribution files fixes.

    To install and start Juju Quickstart, run these commands:

    sudo add-apt-repository ppa:juju/stable
    sudo apt-get update && sudo apt-get install juju-quickstart
    juju-quickstart [-i]

    More details on juju-quickstart are available in this blog post.


  • mitechie 12:43 pm on March 17, 2014 Permalink | Reply  

    Video walkthrough of Juju Quickstart 

    Matthew Scott has done a great video walkthrough of the new Juju Quickstart tool. He demonstrates how to use it to configure your Juju environments, bootstrap them, and then deploy an awesome bundle into that environment. Check out how easy Juju Quickstart can make getting started with Juju and let us know what you think!

  • Madison Scott-Clary (Makyo) 3:34 pm on March 14, 2014 Permalink | Reply

    Weekly Retrospective – Week of March 10 

    Jeff – every js file has a test file associated with it. We could entertain the
    idea of creating more descriptive subdirectories, within each subdir have tests
    folder, those tests would be responsible for the module in there. Lots of tests
    touch too much. Decentralizing tests could help us write better tests with more
    coverage. Benji bring sup that it makes grepping for things harder, but not so
    much as to be a -1. Rick: switching over could be expensive, and build step
    would need to be modified to account for that – investigate work involved.

    Monkey patch before/after – Jeff – If you don’t provide before/after, they won’t
    be monkey patched. Be aware that there’s no default call if you don’t include
    an afterEach for cleanup. There should be a bug to have a base afterEach that
    runs cleanups, or at least warns about that.

    Dropping charm on service block – Jeff and Matt – if you drag something onto the
    canvas and drop it on the service block it acts like dropping a file in the
    browser, leads to download. Should we bubble? Can we do an invisible overlay?
    Apparently not, there’s an issue with it working only in chrome. Decided on
    canvas only. Lets file it as a bug – if we can fix it, verify, but if we
    can’t, can we at least reject the drop? Investigate.

    Add deps into modules-debug – Jeff – Our loader file doesn’t parse nested
    requires, explicitly add module into the use section which is for a sub
    dependency. Add requires into modules-debug list to avoid recursion.

  • mitechie 11:52 am on March 14, 2014 Permalink | Reply
    Tags: local, ,   

    Juju GUI 1.0.1 released 

    We’re pleased to announce the release of the Juju GUI 1.0.1. This is a small point release that provides the ability to upgrade services deployed with a local charm. It also allows Safari users to export their environment as a Bundle. This means the next release should include full Safari support.

    Please let us know what you think, feel free to file any bugs, and ask us any questions in #juju-gui on Freenode.

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