Tagged: generalinterest Toggle Comment Threads | Keyboard Shortcuts

  • Francesco 9:18 am on February 20, 2014 Permalink | Reply
    Tags: generalinterest, ,   

    juju-quickstart 1.1.0 released 

    Juju Quickstart helps both new and experienced users quickly start Juju from Ubuntu.
    Release 1.1.0 is out, including the following new features:

    • Support for newer juju-core versions.
    • Get admin-secret from juju-generated jenv file.
    • Use existing ssh-agent if possible.
    • Minor fixes to code and documentation.

    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.


  • garyposter 9:11 pm on January 21, 2014 Permalink | Reply
    Tags: generalinterest, ,   

    Juju Quickstart 1.0: Try it out! 

    Following on from Francesco’s 1.0 announcement, I wanted to reiterate our goals for the project.

    Juju Quickstart helps both new and experienced users quickly start Juju from Ubuntu. Francesco Banconi led the project, and he and the GUI team did a great job with it.

    Juju Quickstart is a command-line tool that quickly starts Juju and the GUI, whether you’ve never installed Juju or you have an existing Juju environment running. Features include the following.

    • New users are guided, as needed, to install Juju, set up SSH keys, and configure it for first use.
    • Juju environments can be created and managed from a command line interactive session.
    • The Juju GUI is automatically installed, adding no additional machines (installing on an existing state server when possible).
    • Bundles can be deployed, from local files, HTTP(S) URLs or the charm store, so that a complete topology of services can be set up in one simple command.
    • Quickstart ends by opening the browser and automatically logging the user into the GUI, to observe and manage the environment visually.
    • Users with a running Juju environment can run the quickstart command again to simply re-open the GUI without having to find the proper URL and password.

    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]

    Run “juju-quickstart -h” for a list of all the available options.

    Once Juju has been installed, the command can also be run as a juju plugin, without the hyphen (“juju quickstart”).

    While the project is currently Ubuntu-only, Mac support could be added relatively quickly. Windows support will take more time. As noted previously, juju-quickstart does not yet work on Trusty but the related issues will be addressed soon.

    File bugs at https://bugs.launchpad.net/juju-quickstart .


  • Francesco 3:47 pm on January 21, 2014 Permalink | Reply
    Tags: generalinterest, ,   

    Juju Quickstart 1.0 Released 

    The new 1.0 release of juju quickstart is available on the “juju stable packages” PPA:


    You can do the following to get everything installed and create/start an environment with the GUI running and ready:

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

    The change log includes the following new features and bug fixes:

    • Environments management support: allow for creating/editing Juju environments.
    • Improve SSH keys handling.
    • Unicode refactoring.
    • Improve machine errors handling.

    The trusty package is also available, but must be considered experimental and right now it does not seem to be in a usable state.

    A list of the problems we encountered using quickstart in trusty follows:

    • juju currently is not able to bootstrap an ec2 environment in trusty:
    juju-quickstart: error: WARNING no tools available, attempting to retrieve from https://streams.canonical.com/juju
    ERROR bootstrap failed: cannot find bootstrap tools: XML syntax error on line 9…

    Bootstrapping with –upload-tools and then relaunching quickstart works well. This seems to be a juju-core problem: once solved, it will no longer affect quickstart.

    • There are also problems with trusty and LXC containers. Each time I tried to bootstrap a local environment I experienced machine errors due to missing symlinks or similar issues. Also in this case, fixing the problem should not require additional quickstart work.

    That said, juju qucikstart is ready to be installed and tested, and with this release we think we achieved the goals we set for 1.0.
    We appreciate any feedback; bugs can be filed here:

    Many thanks!

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

    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: , generalinterest, , , ,   

    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: generalinterest,   

    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.

  • garyposter 9:31 pm on October 18, 2013 Permalink | Reply
    Tags: generalinterest   

    0.11.0 Juju GUI Release 

    As of last night, the 0.11.0 release is out (but not yet at jujucharms.com).  This one has some nice new features, a lot of good bugfixes, and a ton of work towards some almost-ready-to-release features.  Please give it a try and let us know how it goes.

    • The inspector (and the GUI, for the first time) supports upgrading or downgrading a service’s charm.
    • The masthead’s UX is improved, notably giving a bit more room for the rest of the application.
    • Relations now display the names of both endpoints in the environment.
    • The GUI distribution is now about 1/9 the size it was before, speeding up deployment.
    • Recommended charms (and bundles) are now marked with a red triangle, per results from UX tests.
    • (FIX, CLEANUP) Service coordinates were being stored in three places, leading to confusion and bugs. This code was refactored, introducing many fixes to our service positioning behavior.
    • (FIX) If the charm browser were fully open to show charm details, and the browser was minimized and then reopened, the details page would be blank.
    • (FIX) The Go implementation of the sandbox always lost the first delta from the AllWatcher’s Next method.
    • (FIX) Bundle export should not include the number of units for subordinates.
    • (FIX) Inspector scale up input was disabled forever after value change.
    • (FIX) Charm details link was not working correctly from inspector.
    • (FIX) Unit details did not display exposed URL links properly.
    • (FIX) Position annotations are once again included in exports.
    • (FIX) New units added to the canvas no longer overlap old ones.
    • (FIX) The charm “code” tab in the charm browser now sorts filenames by directory and name, to make it easier to find a particular file. It also excludes the svg files from the list, since the rendering was less than valuable.
    • (CHARM FIX) This is actually a fix in the charm, but it is an important one that is worth calling out. In some environments, the GUI would break, not allowing proper inspection, export, or other basic behavior. This turned out to be because the new server had an issue with non-ascii values in some cases.
    • Behind the “charmworldv3” flag, bundle support is ready for demonstration, including browsing and deploying, in the sandbox and in a live environment. Tweaks, bug fixes, and some approved bundles should take us the rest of the way soon. This comprised a very large portion of the work behind this release.
    • Behind the “onboard” flag, the GUI has work to show helpful onboarding for new users.
  • garyposter 11:10 pm on October 1, 2013 Permalink | Reply
    Tags: generalinterest   

    Juju GUI 0.10.1 Released 

    Today we released Juju GUI 0.10.1.  This includes many fixes, listed below, as extracted from the changelog.

    • Add icon for exporting a bundle.
    • (FIX) The GUI was unusable when cookies were turned off in your browser.
    • (CLEANUP) Use service model in ghost inspector, rather than charm model. This is a nice cleanup and also enables a true environment-wide “save” button in the future.
    • (FIX) The GUI was unable to deploy charms without config options.
    • (FIX) Remove unit button did not work in Juju Core.
    • (FIX) The inspector’s unit view did not update when the unit’s values changed. Now everything except for the relations updates. Relations have other issues that, in part, need in-progress changes in Juju Core to work.
    • (FIX) Changing settings did not work in Juju Core.
    • (FIX) Removed broken and largely unnecessary “All Notifications” link. More, better changes will come there soon.
    • (CLEANUP) As part of bundle work, clean up some browser templates for general improvements and for better re-use.
    • (FIX) After saving a service config, old, unchanged values would seem to disappear, and then reappear a few seconds later.
    • (CLEANUP) Remove the serviceInspector flag code and some of the now-irrelevant old view code.
    • (FIX) if a service is destroyed in the command line, the inspector should close when the service disappears.
    • (FIX) subordinate charms should not show constraints and should not seem to allow control of scaling.
    • (FIX) destroying a service would hide it too soon, causing surprises if the destruction failed. It now disappears when it is destroyed.
    • Behind upgradeCharm feature flag, complete implementation of support for upgrading a charm in the GUI. This will be released in 0.11, very soon.
    • Behind charmworldv3 feature flag, add more support for bundles (model, search results, featured list, initial token, better sandbox support, etc.).

    We have not yet deployed this to jujucharms.com.

  • garyposter 9:49 pm on September 18, 2013 Permalink | Reply
    Tags: generalinterest,   

    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 3:08 am on August 3, 2013 Permalink | Reply
    Tags: generalinterest   

    Juju GUI 0.8.2 and another jujucharms.com update 

    Today, we made a GUI release of 0.8.2 and another jujucharms.com update. Unfortunately, I don’t have a lot of time to describe a release that has a lot of fixes that will make people happy. For a quick summary, though, here are five highlights in my mind.

    • We stomped on a lot of different link issues in the charm browser (like these two).
    • Charm upgrades deal with browser caches better now. This is coming to jujucharms.com soon, though we did make this release much smoother in that regard.
    • We fixed the bug that made it impossible to destroy a service from the detail page.
    • More legacy URLs are fixed.
    • We made a lot of other small improvements, like showing when a charm is a subordinate.

    Meanwhile some other changes were also made behind the scenes for upcoming features, which we will talk about soon.

    We hope you enjoy it!

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