Updates from April, 2014 Toggle Comment Threads | Keyboard Shortcuts

  • Francesco 10:33 pm on April 30, 2014 Permalink | Reply
    Tags: ,   

    juju-quickstart 1.3.2 released 

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

    • Ability to deploy the Juju GUI trusty charm on trusty environments.
    • Support for the Joyent provider.
    • Make control-bucket optional.
    • Improve Urwid unicode support.

    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.

    Enjoy!

     
    • juan caballero 2:18 am on May 3, 2014 Permalink | Reply

      hi i notice that there is no juju-quickstart for maas. for us metal users. is there going to be a maas option like ec2,local,azure..

      • Rick Harding 9:11 pm on October 5, 2014 Permalink | Reply

        Just to follow up, quickstart 1.4.4 is out and has maas support built in. It’s available via pypi and the juju stable ppa, and we’re working to get it updated for the utopic release.

    • Francesco 9:20 am on May 6, 2014 Permalink | Reply

      Hi Juan,
      yes MAAS support is definitely in our TODO list.
      Hopefully we will be able to work on that over the next weeks.

      • Ricky 2:23 pm on August 14, 2014 Permalink | Reply

        Totally second the MAAS juju-quickstart request! 🙂

  • mitechie 6:49 pm on April 18, 2014 Permalink | Reply
    Tags:   

    Juju GUI weekly retrospective. 

    This week’s retrospective includes a couple of discussions.

    We’ve been creating feature flags across the work we’ve been doing beyond the initial two documented and shared with others to help follow along our progress. This hurts in two ways. First, others can’t follow along with out progress as they don’t know what flags to use. Second, it hurts ourselves as we don’t see the different chunks of code working and interacting together. This could lead to more time required to bring tasks together as we drop flags and release features. The end result is that we love feature flags, but we need to keep the limited as much as possible.

    Secondly, deployments are good and everyone should be able to do one. It’s not something that should be limited to one or two folks as deployments are sometimes required at odd times due to critical situations. We all agree that everyone should try to do a deploy and Matt stepped up to be the first to try a deploy next week.

     
  • mitechie 8:40 pm on April 9, 2014 Permalink | Reply
    Tags: ,   

    Juju GUI 1.0.2 released: Safari users rejoice! 

    The Juju GUI team is proud to release 1.0.2. This release sees the addition of Safari to our stable of supported browsers. This release also brings along a series of bug fixes, some important updates for how local charms are upgraded and displayed into GUI, and a few performance improvements. See the full change log for every detail.

    I want to give a big thanks to the GUI team for the awesome work that’s gone into this release. We’ve got some exciting stuff on deck and already can’t wait to get the next release out the door.

     
  • mitechie 4:13 pm on April 4, 2014 Permalink | Reply
    Tags:   

    Juju GUI team weekly update 

    Matt brought up an interesting point that while fetching the values for HTML node attributes, browsers can return different things. In one case, Firefox returns null while Chrome returned “”. The value was getting a .split() called on the result which worked in one browser and failed in another.

    Watch out folks.

     
c
Compose new post
j
Next post/Next comment
k
Previous post/Previous comment
r
Reply
e
Edit
o
Show/Hide comments
t
Go to top
l
Go to login
h
Show/Hide help
shift + esc
Cancel