Tagged: jujucharms Toggle Comment Threads | Keyboard Shortcuts

  • jeffpihach 4:28 pm on August 4, 2017 Permalink | Reply
    Tags: , , , , jujucharms,   

    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.

    Screen Shot 2017-08-01 at 1.23.18 PM

    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.

    Screen Shot 2017-08-01 at 1.28.26 PM

    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.

    Screen Shot 2017-08-01 at 1.29.26 PM

    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

  • jeffpihach 5:40 pm on May 22, 2017 Permalink | Reply
    Tags: , , , , jujucharms,   

    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

  • bradcrittenden 8:57 pm on March 1, 2017 Permalink | Reply
    Tags: Beta, , jujucharms   

    Introducing JAAS – Juju as a Service 

    Recently on jujucharms.com we opened the public beta of JAAS — Juju as a Service. Let’s explore what JAAS is and how you can participate now in the beta.

    Models and Controllers

    First, a little background to put the changes we’ve introduced into context. Juju allows you to model your service-oriented architecture and manage the deployment to public clouds, OpenStack, local hardware, and containers. Using the GUI, which is installed with every deployment of Juju, you can visualise your model and configure the parts.

    To manage the deployments, Juju requires a controller, a management node that keeps track of all of the components in your deployed model, handles scaling, and all of the other magic Juju does. When you use the command-line command juju bootstrap you are simply creating a controller. If you’re using a public cloud, that controller is a resource you’re charged to use like any other machine. Bear in mind a highly available deployment will require multiple bootstrapped controllers, so your expense for those nodes will be tripled if you have three HA controllers.

    Although it doesn’t take a long time to bootstrap a new controller, it isn’t instantaneous. Further, each controller is an island to itself, any configuration you make to one controller is not reflected in the others. Identity management is one type of configuration that is beneficial to share across models.

    What JAAS introduces is a common controller that is always deployed that you can use to create your models — the things you actually care about. Since it is already running, and maintained by us, you can skip the juju bootstrap step and simply start by using juju add-model to begin your work.

    Public beta of JAAS

    For the public beta we have set up a controller for everyone to use. Every new model created at jujucharms.com/new is attached to the public controller.  You can also access it from the command-line, which will be explained later.

    So with the beta of JAAS we are providing:

    • anonymous user access to modelling in the GUI from jujucharms.com/new,
    • support for all three big clouds (AWS, Azure, and Google) through a single controller, available from a web browser or CLI,
    • identity management across all models,
    • user access management to models,
    • model sharing via URLs, and
    • everything else that Juju offers!

    Use of the controller during the beta period will be free of charge! Models you create will use your public cloud credentials and you’ll be charged for them but the use of the controller is free.

    Getting started

    To start modelling you don’t even have to be logged in. Just visit jujucharms.com/new and begin adding applications from the charm store to your model. When you’re done adding services, applying any custom configuration, and creating the relations between them you can download and save a bundle file or go ahead and deploy to a public cloud. To do the deployment you’ll need to provide your credentials for the cloud and your cloud provider will charge you for those instances you use. Once you’ve added your credentials to the controller they are securely stored for you and you can deploy future models using them.

    Currently we have controllers in two regions for each of the three supported public clouds and will add more as use increases. We provide HA controllers in the U.S. and in Europe for each cloud.


    Maintaining a production environment is a team effort so JAAS allows you to easily share access and management of your models with your project members. When you grant access to others they can see your model in the browser via jujucharms.com or by using Juju on the command line.

    With recent changes to the GUI models are individually addressable via a shareable URL. For instance if I had a model named wordpress it could be shared and seen by going to jujucharms.com/u/bac/wordpress.

    You can also see models shared with you by visiting your profile page at jujucharms.com/u/[your_user_name]. Here is the profile page of my colleague Jeff showing that I’ve shared my wordpress model with him. He’s also got another model shared by Uros.


    Sharing can be done via the command line with the juju grant command.

    juju grant hatch@external read wordpress

    Or in the GUI using the share button, seen below at the far right.


    That button brings up a dialog that looks like


    The user names must include a domain. Currently we use external (e.g. hatch@external) but that will change soon. So, for now, just append @external on the end of your collaborator’s Ubuntu SSO name. Use everyone@external to make a model publicly available.


    If you have a model shared with you as read-only you clearly cannot make changes to it. But given the URL scheme used you can request changes from the model owner. Suppose Jeff is viewing my wordpress model and wants to add an HA Proxy service. While viewing my model he can search for HA Proxy and the resulting URL in the context of my wordpress model is https://jujucharms.com/u/bac/wordpress/haproxy/40. Jeff could then email me that URL and request I add it to the model. When I go directly to that URL I would merely click the Add to canvas button and it would be done.

    JAAS controller registration

    Models you create on jujucharms.com are already created using the JAAS controller. In order to use that controller from the command line, you need to first register it. This is done with the command:

    $ juju register jimm.jujucharms.com


    Adding a model

    From the command line you add a model using juju add-model. But when working with the JAAS controller you’ve got to provide information about the cloud and region to use since the controller knows about three public clouds with two regions each.

    The following command will add a k8s model to the Google cloud using region us-east1 using the previously saved bac-gce credentials.

    $ juju add-model k8s google/us-east1 --credential bac-gce


    We have worked hard to bring JAAS to this point and it is very functional. This program is currently in a beta state. If you do encounter a bug please let us know by filing it at https://github.com/CanonicalLtd/jujucharms.com/issues. You can also reach the team in real-time in the #juju channel on Freenode IRC.

    Additional resources

    JAAS was introduced on the March 1, 2017, edition of the biweekly Juju Show live podcast. The recording can be found on YouTube.

  • mitechie 2:25 pm on December 19, 2014 Permalink | Reply
    Tags: jujucharms,   

    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!

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

    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 2:48 pm on July 26, 2013 Permalink | Reply
    Tags: , jujucharms   

    jujucharms.com update 

    Following up on yesterday’s announcement of Juju GUI 0.8.1, today we have a new release of jujucharms.com that includes those fixes.

    It also includes a number of redirects to be largely backwards compatible with existing links. For instance, links from pre-existing questions and from other sources should now work. Also, old links for charm authors and charm reviewers now redirect to the new location, away from http://jujucharms.com to http://manage.jujucharms.com. Examples include http://jujucharms.com/review-queue, http://jujucharms.com/interfaces, http://jujucharms.com/tools/proof-errors, http://jujucharms.com/recently-changed, and http://jujucharms.com/feed/charm-changes. Thank you to Curtis Hovey for arranging this fix!

    In the “two steps forward, one step back” department, unfortunately this release highlighted an issue in our caching directives to the browser . If you have visited jujucharms.com earlier this week, you will initially see some new, unattractive styling. This will naturally clear out of the browser cache in a day or so. To correct immediately, simply do a “hard reload” (shift-control-r) of the browser. We will deploy a fix as soon as possible.



  • garyposter 7:13 pm on July 22, 2013 Permalink | Reply
    Tags: , , jujucharms   

    jujucharms.com and Juju GUI 0.8.0 

    I’m very happy to let you know that we have released the Juju GUI 0.8.0, and that it is powering http://jujucharms.com.

    The GUI itself has a lot of incremental improvements and bugfixes in this release, and the UI is even more beautiful and usable. See the bottom of the post for changelog highlights, and see our installation details if you want to know how to use the GUI in your own Juju environment.

    However, our biggest news to my mind is that we now have a jujucharms.com that really encourages discovery and exploration. You can find charms; read more details about them; and experiment live to see how they interact within a mock Juju environment. You can even (hidden feature, for now!) use shift-D to export your experiments into a human readable format, and use that to turn your experiments into a real running system in your own Juju environment (see the Juju Deployer).

    Charmers, never fear: the features you need from the old site are still around, with some improvements. See http://manage.jujucharms.com/.

    Also, the old GUI demo site, uistage.jujucharms.com, will be retired soon, and redirect to jujucharms.com. Meanwhile, if you want to follow along with our progress on a commit-by-commit basis, you are welcome to join us over at http://comingsoon.jujucharms.com/. You may have to clear your cache regularly on that site, if you keep coming back: we are working through this code quickly. 🙂

    And in that vein, the thing I’m most proud of is being a part of the team that is making this! Big thanks and congratulations to UX (esp. Alejandra Obregon and Luca Paulina), Curtis Hovey’s Orange squad, and the Juju UI team.

    Bugfixes and new features are already in trunk, with more exciting things coming. Thanks for reading.


    0.8.0 changelog highlights:

    • Update charm browser styling.
    • Add provider test result data and links
    • Charm browser shows lifetime downloads and commit counts.
    • Update service block design.
    • Fix deployment issues encountered for some charms, e.g. Marco Ceppi’s discource charm.
    • Fix Juju deployer export.
    • More drag and drop deployment refinement and fixes.
    • Many other small bugfixes.
    • Incremental progress on service inspector behind the serviceInspector feature flag.
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