Updates from Francesco Toggle Comment Threads | Keyboard Shortcuts

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

    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

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

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

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

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

    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!

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

    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.

    Enjoy!

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

    Juju Quickstart 1.0 Released 

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

    ppa:juju/stable

    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:
    https://bugs.launchpad.net/juju-quickstart/+bugs

    Many thanks!

     
  • Francesco 11:18 am on April 17, 2013 Permalink | Reply  

    The –fake-series argument of “juju bootstrap” is no longer required in latest juju-core trunk.
    AFAIK that behavior is now enabled by default when you use –upload-tools.

     
  • Francesco 10:10 am on April 12, 2013 Permalink | Reply  

    Didn’t know this. Having source maps activated in Chromium, it is possible to create breakpoints in the source files (i.e. everything under /juju-ui/assets/source/)! This ability to automatically map breakpoints in the sources to specific locations in the compressed js helped me a lot during the JujuGUI/juju-core debugging and QA sessions.

     
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