JAAS & Juju update: Juju GUI 2.8.0

JAAS has seen 2 minor and 6 patch updates in the last nine weeks. Let’s talk about what’s new as of the 2.8.0 release.

Direct Deploy

Direct Deploy gets your solutions deployed easier and faster. The feature allows you to create Juju cards which will add the specified bundle or charm to a new model and then open directly into the deployment flow. At this point they simply need to complete the deployment flow and will have a deployed solution without having to manually add or modify the model pre-deploy.

To create a card simply visit https://jujucharms.com/community/cards and enter the charm or bundle id that you’d like to embed. A card will be generated for you which you can embed in your own website or blog.

Check out the release video of Direct Deploy in action and check back for a follow-up post with details about how you can create your own Direct Deploy card.

Import & Add SSH Keys

Users often need the ability to SSH into one or more of the Juju provisioned machines to access generated content, logs, or results of Juju actions. In the deployment flow we now allow you to import public SSH keys directly from GitHub or add them manually. These keys will then be propagated to all of the machines in your model making sure you can ssh directly to them.

 

Define and Modify Machine Constraints

One of the benefits to cloud computing is your ability to tailor the machine hardware to your needs. With the updates to the Machine View, you can now specify a number of constraints for the machines that you’d like Juju to request from your cloud provider. These constraints are now editable pre-deploy in the machine view and shown in the Deployment Flow. These might include 16G of ram or 4 CPU cores.

Model Changes List

After modeling a complex environment you’ll often want to review the actions that Juju will perform before hitting the deploy button. Now in the Deployment Flow we’ve merged the two change log lists into a single list which groups the changes by application and splits out the machine information into their own lists to make it much easier for you to review.

Users on JAAS are already running the latest GUI and have these features available today!

If you’ve bootstrapped your own controller you can upgrade to the latest Juju GUI with:

    juju upgrade-gui

We welcome any feedback you may have. You can chat with us in #juju on irc.freenode.net or you can file issues at: https://github.com/juju/juju-gui/issues

Juju & JAAS Beta updates: Juju GUI 2.6.0

With the public beta release of Juju As A Service (JAAS) on jujucharms.com we’ve been working hard to implement solutions in the Juju GUI to resolve a number of outstanding feature requests from our users. Let’s walk through some highlights.

Updated Search Results

We now make it a lot easier to find applications and solutions by others in the community by including those results in the default search results. Simply perform a search, click the community button to see what others in the community have made available.

Deploying private content from the GUI

While developing new charms and bundles, it’s nice to keep them private, we now allow you to easily deploy private charms and bundles from your user profile page.

New Account Page

For those of you with multiple credentials across multiple clouds we’ve added a new account page which allows you to easily manage them in one location. The account page can be accessed from the user dropdown in the top right. Credentials can be added and removed from here as well as in the deployment flow as usual.

Terms and Conditions Support

When installing software it’s common to see a terms and conditions dialogue before you’re able to continue. We’ve now made it extremely easy to view and agree to terms and conditions while deploying charms and bundles. When deploying a charm that requires a term agreement the terms will be presented in the deployment flow prior to being allowed to deploy.

For those on JAAS you’re already running the latest GUI.

If you’ve bootstrapped your own controller you can upgrade to the latest Juju GUI with:

    juju upgrade-gui

We welcome any feedback you may have. You can chat with us in #juju on irc.freenode.net or you can file issues at: https://github.com/juju/juju-gui/issues

Juju GUI 2.1.1 released

As a quick follow up to the Juju GUI 2.1.0 release we’ve got a patch release for the Juju GUI making sure that we keep the Juju GUI interactions transparent when working with either Juju or the Juju 2 beta. Along with this release we’ve added a few additional bug and usability fixes:

• If you have uncommitted changes we now warn you when switching models so you don’t lose your changes accidentally. We will be working towards persisting this data in the future.
• Disable container and machine creation buttons until we’ve collected enough information to successfully create the machine.
• Added language and content direction flags so that the input fields work better for users using rtl languages.

To upgrade an existing deployment:

juju upgrade-charm juju-gui

To deploy this release into your model:

juju deploy juju-gui

If you find any issues or have any feedback for the Juju GUI we’d love to hear it. Please let us know in our github repository https://github.com/juju/juju-gui/issues and we’ll be sure to get back to you.

Juju GUI 2.0 Beta released

We are really happy to announce availability of the new and shiny beta version of Juju GUI 2.0 with completely redesigned and rewritten user interface and improved user experience. The new GUI introduces:

• redesigned canvas, relation management and charm handling with the new inspector,
• improved integration with the charm store, unifying the web experience at jujucharms.com,
• new machine view with drag’n’drop functionality – allocating units has never been easier,
• creation and switching between models within a controller, and
• new bundle deploys.

Not much has stayed the same, so it’s best if you give the new GUI a try yourself.

We’re aware of the small details that need polish before we close the beta, but we’d like to make the 2.0 release rock solid and therefore would appreciate as much feedback from you as possible. Should you discover a bug, use the GitHub issue tracker to file a report. Please provide as much information as possible, e.g. the cloud provider, the output of ‘juju version’, steps made, errors from the browser console, etc.

The major changes for this release are:

GUI with controllers and models

If you would like to test the GUI against a Juju controller, the JES feature flag needs to be enabled before bootstrapping. This will enable you to create, list and manage models directly from the GUI.

export JUJU_DEV_FEATURE_FLAGS=jes
juju bootstrap

Deploying the Juju GUI 2.0 beta

Juju 1.25 or older

The charm is available via the charmstore URL cs:~yellow/trusty/juju-gui and at https://jujucharms.com/u/yellow/juju-gui on the web. Just do the usual:

juju deploy cs:~yellow/juju-gui

Juju master (1.26 alphas)

Recent Juju builds support a new publishing mechanism and can properly parse URLs with the development channel. If you’re using recent Juju builds, bootstrap a controller on a cloud of your choice and use the development version of the promulgated Juju GUI charm located at cs:development/juju-gui or https://jujucharms.com/development/juju-gui on the web. You can deploy the development version of the charm with:

juju deploy cs:development/juju-gui

You should see a response similar to:

Added charm “cs:development/trusty/juju-gui-42” to the environment.
Deploying charm “cs:development/trusty/juju-gui-42” with the charm series “trusty”.

 

We hope you find the new GUI easier to use and find the layout to be more intuitive. Enjoy using it and let us know what you think!

New jujucharms.com release, Holiday Edition!

With the holiday’s approaching the team squeezed one one last update to https://jujucharms.com before everyone takes a well deserved break with friends and family. This release is a small bit of polish. Changes include:

• Update many views and static file serving to have proper cache headers so browsers will cache/speed things up.
• Shrink the sizes of many of the large static assets to shrink up the page load hits.
• Lazy load charm icons on the /solutions page and search results to help make for a better loading experience.
• Update to now include bundle download stats as well as fixing the bug in the stats on the older versions of charms.
• Along with a handful of small bug fixes since our release last week.

As always, please try it out and let us know about any issues or suggestions you have at: https://github.com/CanonicalLtd/jujucharms.com/issues

The Juju UI Engineering team wants to wish everyone a Happy Holidays and we’ll have another suite of updates ready for you all to enjoy next year!

Juju GUI triple release week! 1.2.2 out the door.

The last 8 days have been crazy for the team. We released machine view which is a great amount of work from the team.

Earlier this week we followed that up with a bug fix release. A charm bug and an issue in the search are now fixed up.

Finally, we’ve released a 1.2.2 today. It adds a UI for custom settings. You can find them by hitting loading up the shortcuts UI with the ‘?’ key. We also moved the service expose/unexpose into the list of changes that can be ‘uncomitted’ and fixed a couple of bugs along the way.

View the full changelog here

If you’ve not yet checked out the new Juju GUI, stop by our recent screencasts showing off the new machine view.

Juju GUI 1.1.0 released: where art thou inspector?

The Juju UI Engineering team is proud to announce the release of Juju GUI 1.1.0. The big change in this release is the move of the floating inspector from floating on the right side to working in the sidebar on the left. There’s a lot of updates under the hood and big chunk of progress on the upcoming machine view behind the feature flag /:flags:/mv.

You can see the full list of changes and bug fixes in the Changelog.

You can upgrade existing GUI charms for both Trusty and Precise. If you find any issues make sure to let us know by filing a bug at https://bugs.launchpad.net/juju-gui

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.

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.

Juju GUI 1.0 released!

Drag and drop the ghost.zip file.

Today we released the Juju GUI 1.0. It brings together several lines of work and we’re proud of what the GUI has grown into. Here’s looking forward to 2.0.

The update to 1.0 brings:

Local charm deploys are now supported. Drag-n-drop a zip file of your charm onto the canvas to deploy it. This requires the in development version of Juju 1.17.3.

New relation line visualization. Multiple relations are now grouped into a single line. The line color helps indicate relation health and a popup is available to interact with the relations.

Remove the bws prefixes from the tabs in the details view. Note this changes urls to specific tabs. The old urls are respected but are deprecated. Please update your bookmarks.

Notifier users when the window size is too small to work with effectively.

Auto open and close the browser when interacting with the inspector.

Safari has been added to CI and the test suite. Local charm support is still be be completed in the next release. At that point it will become an officially supported browser.

(FIX) allow use of local web fonts to enable better offline support.