Tagged: juju Toggle Comment Threads | Keyboard Shortcuts

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

    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!

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

    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 .

    Enjoy!

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

    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!

     
  • garyposter 10:10 pm on November 7, 2013 Permalink | Reply
    Tags: , , , juju, ,   

    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?

  • bradcrittenden 3:28 pm on July 22, 2013 Permalink | Reply
    Tags: , juju,   

    Charm store moves, Juju GUI updated 

    Today the charm store moved to a new URL but the GUI had not been updated to reflect it. You may have seen a JSON parse URL when trying to deploy charms.

    This inconsistency has been resolved and the GUI (bzr revision 69) is now correct.

    Sorry for the inconvenience.

     
  • bradcrittenden 2:11 pm on April 9, 2013 Permalink | Reply
    Tags: ec2, juju, pissingawaymoney   

    Alerts for running EC2 instances 

    As a Juju developer I’m always creating and destroying EC2 environments. Sometimes I create more than I destroy which leads to a small hemorrhage of cash, which leads to a sinking feeling in the pit of my stomach when I discover what I’ve done.

    So I’m experimenting with this little cron-based reminder system. It may be simultaneously too annoying when I’m sitting in front of my computer and wholly ineffective if I’m away for long periods of time. Suggested improvements welcome.

    AWS_ACCESS_KEY=your key here
    AWS_SECRET_KEY=your secret here

    */5 * * * * /usr/bin/ec2-describe-instances -O $AWS_ACCESS_KEY -W $AWS_SECRET_KEY | grep INSTANCE && DISPLAY=:0.0 /usr/bin/notify-send –urgency=critical -i terminal -t 10000 “EC2 instances running”

     
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