Tagged: juju Toggle Comment Threads | Keyboard Shortcuts

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

    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.

    cardgen

    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.

     

    ssh-key-import

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

    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

     
  • jeffpihach 6:51 am on March 19, 2016 Permalink | Reply
    Tags: juju, ,   

    Juju GUI 2.1.1 released 

    2.1.1

    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.

     
  • Francesco 12:39 pm on June 18, 2015 Permalink | Reply
    Tags: juju,   

    Juju Quickstart 2.2.0 

    We are happy to announce the 2.2.0 release of Juju Quickstart!

    Juju Quickstart helps both new and experienced users to quickly start Juju and the Juju GUI, whether they’ve never installed Juju or they have an existing Juju environment running.

    From the last update on this blog, we introduced several new features like support for the Google Compute Engine provider (which increases to 9 the number of supported providers) and updates to environments’ definitions, together with other minor improvements and bug fixes.
    Here are the release notes for version 2.2.0:

    • Add support for loading uncommitted bundles on the Juju GUI.
    • Allow configuring the Juju GUI so that it listens to a customized port.
    • On existing environments, automatically detect the port used by the GUI server.
    • Fix SSH agent handling when using uncommon shells.

    From the list above, there are two noteworthy changes we would like to highlight.

    Support for uncommitted bundles

    With the release of Juju GUI 1.4.0 it is now possible to import a bundle into the GUI canvas as a set of changes to be committed later. This way the bundle can be finely tuned and tweaked before actually committing the changes. For instance, you can modify scalability settings, machine placements, configuration options and constraints for each individual service, and even the resulting topology itself, so that the workload really fits your needs, and, only at that point, send the resulting changes to the Juju environment.

    This functionality is now available from the command line too, thanks to the new Juju Quickstart’s
    -u (or --uncommitted) flag.
    You can use it like the following:

    juju-quickstart -u openstack-base
    

    The command above will not automatically start the bundle deployment, but instead the provided bundle will be loaded in the GUI, waiting to be customized and then committed.

    For more about uncommitted bundles, have a look at this blog post.

    Customized Juju GUI ports

    The Juju GUI, by default, listens for HTTPS connections on port 443. It also redirects insecure requests (port 80) to port 443. Sometimes it can be useful to configure the GUI so that it listens to a different port. For instance, this is handy when you want to co-locate another web service on the same machine.
    Juju Quickstart now provides the ability to directly specify a customized port for the GUI, e.g.:

    juju-quickstart --gui-port 4242
    

    On subsequent Quickstart runs, the application will automatically detect that the GUI is listening to the customized port and react accordingly, by establishing WebSocket connections to that port, and by opening the browser to the right URL at the end of the execution.

    Installation

    The program is available on Ubuntu releases 12.04 LTS (precise), 14.04 LTS (trusty), 14.10 (utopic), 15.04 (vivid) and on OS X (10.7 and later). To install and start Juju Quickstart on Ubuntu, run these commands:

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

    On OS X, use Homebrew:

    brew install juju-quickstart
    juju-quickstart [-i]

    For more details, see juju-quickstart --help.

    Enjoy!

    quickstart-index

     
  • Francesco 2:06 pm on March 3, 2015 Permalink | Reply
    Tags: juju,   

    Juju Quickstart 2.0 

    The UI Engineering Team is proud to announce the 2.0 release of Juju Quickstart!

    The new release includes the following new features and fixes:

    • Update the way bundles are specified on the command line.
      The new simplified jujucharms.com syntax is used, e.g.

      juju-quickstart mediawiki-single

      User owned bundles can be deployed as follows:

      juju quickstart u/bigdata-dev/apache-analytics-sql

      The old bundle:mediawiki/single form is still supported but deprecated.

    • Add support for new Juju WebSocket API endpoints.
      Connect to a specific environment using its unique identifier when
      supported by the Juju version in use.
    • External Python API refactoring: implement the Juju reference model
      (charm and bundle URLs).
      Also improve support for bundles as first class entities.
      See models/references.py and models/bundles.py for details.
    • Retrieve bundles from the new charm store API v4.
    • Improve the testing infrastructure: exercise Quickstart with all the
      supported dependency versions.
      Also introduce functional tests against a real Juju environment.
      See the HACKING file for more details.

    This version introduces some backward incompatible changes:
    When deploying bundles, specifying a directory is no longer supported.
    Local files are still supported but must have a .yaml or .json extension.
    For more details, see juju-quickstart --help.

    Juju Quickstart helps both new and experienced users to quickly start Juju and the Juju GUI, whether they’ve never installed Juju or they have an existing Juju environment running.

    The program is available on Ubuntu releases 12.04 LTS (precise), 14.04 LTS (trusty), 14.10 (utopic), 15.04 (vivid) and on OS X (10.7 and later). To install and start Juju Quickstart on Ubuntu, run these commands:

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

    On OS X, use Homebrew:

    brew install juju-quickstart
    juju-quickstart [-i]

    For more details, have a look at this blog post.

    Enjoy!

    quickstart-index

     
  • Francesco 1:10 pm on January 14, 2015 Permalink | Reply
    Tags: juju,   

    Juju Quickstart 1.6.0 

    quickstart-index

    We are happy to announce the 1.6.0 release of Juju Quickstart!

    The new release includes the following new features and fixes:

    • Interactive session improvements: highlight active environments.
    • Ability to use Juju generated environments not listed in the environments.yaml file.
      With Juju Quickstart is now possible to manage imported environments (jenv files), even if they miss
      the corresponding entry in the environments.yaml file. It is possible to run Quickstart using
      those environments or just remove stale references.
    • Use the new charm store API to retrieve the most recent GUI charm revision.
    • With the upcoming Juju v1.21 supporting multiple users, Juju Quickstart has been changed not to assume “admin” to always be the user name to be used when connecting to the Juju API. For this reason, both the current user name and password are now displayed in the program’s output. It is also possible to connect to the environment, deploy bundles and log in into the Juju GUI using non-admin credentials.
    • Improve the way the environment’s provider type is retrieved.
    • Initial support for Ubuntu 15.04 (vivid). The Juju stable PPA (ppa:juju/stable) includes vivid packages.

    quickstart-jenv-detail-crop

    Juju Quickstart helps both new and experienced users to quickly start Juju and the Juju GUI, whether they’ve never installed Juju or they have an existing Juju environment running.

    The program is available on Ubuntu releases 12.04 LTS (precise), 14.04 LTS (trusty), 14.10 (utopic), 15.04 (vivid) and on OS X (10.7 and later). To install and start Juju Quickstart on Ubuntu, run these commands:

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

    On OS X, use Homebrew:

    brew install juju-quickstart
    juju-quickstart [-i]

    For more details, have a look at this blog post.

    Enjoy!

    quickstart-maas

    Automatically set up Juju and the GUI on MAAS with Juju Quickstart!

     

     

     
  • Francesco 2:30 pm on November 13, 2014 Permalink | Reply
    Tags: juju,   

    Juju Quickstart 1.5.0 

    The UI Engineering Team is proud to announce the 1.5.0 release of Juju Quickstart!
    Juju Quickstart helps both new and experienced users to quickly start Juju and the Juju GUI,
    whether they’ve never installed Juju or they have an existing Juju environment running.

    The new release includes the following new features:

    • Initial support for the manual provider type.
      Juju Quickstart can now be used to configure Juju, set up
      the Juju GUI and run an environment using manual provisioning.
    • Better integration with MAAS (Bare Metal):
      improved the way node addresses are retrieved, also handling the
      case where the MAAS DNS server is not being used on
      the local machine where Juju Quickstart is running.
      Also automatically detect a logged in MAAS API, so that
      it is possible to use the stored credentials to create and
      bootstrap a MAAS environment without user intervention.
    • Improve the way the application detects the Juju environment
      is already running. This results in a faster, more reliable and
      less expensive execution of Juju Quickstart when invoked
      on an already bootstrapped environment.
    • The interactive session environment editing view now
      shows required fields first, so that users can more
      quickly create/change their Juju environments’ definitions.
    • Interactive session no longer hides errors under certain
      circumstances.
    • Also note that, starting from this release, Juju Quickstart
      no longer supports Juju < 1.18
      .

    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]

    For more details, have a look at this blog post.

    Enjoy!

     
  • mitechie 5:37 pm on October 3, 2014 Permalink | Reply
    Tags: juju, ,   

    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.

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

    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! 🙂

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

    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.

    Enjoy!

     
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