Google Git
Sign in
apache / karaf-jclouds-cli / c2b1cd66194e2ce0f6c5ecff213d132d4679653c
commitc2b1cd66194e2ce0f6c5ecff213d132d4679653c[log] [tgz]
authorIoannis Canellos <iocanel@apache.org>Sat Jun 23 16:46:51 2012 +0300
committerIoannis Canellos <iocanel@apache.org>Sat Jun 23 16:46:51 2012 +0300
tree75b89567959d78d36a04938ceaeb03fd9152c272
parent207d47d27c9a47d38c18d18fd9627a6fd15a64a1 [diff]
Added cli for windows. Classpath is now build internally.
7 files changed
tree: 75b89567959d78d36a04938ceaeb03fd9152c272
  1. assembly/
  2. branding/
  3. runner/
  4. .gitignore
  5. pom.xml
  6. README.md
README.md

jclouds-cli

Jclouds CLI provides two types of command line interface:

  • An interactive shell.
  • A shell script.

Installation

To install the jclouds cli you just need to download the zip or the tarball and extract it to the folder of your choice.

Using the interactive shell

To start the interactive shell: ./bin/jclouds-cli

Using the CLI

To use the cli: ./bin/jclouds [category] [action] [options] [arguments].

  • Categories: node, group, image, location, hardware.
  • Actions: list, create, destroy, runscript.
  • Options: --provider, --identity, --credential --endpoint etc.

Some examples: To create 10 nodes on EC2 under group: myGroupName using Ubuntu 10.04

To list all nodes:

To destroy a node:

Leveraging environmental variables

Both in the interactive shell and cli modes, you may find repeating the provider information again and again not really friendly. You can completely skip those options by sepcifying them as environmental variables.

Supported variables:

  • JCLOUDS_PROVIDER
  • JCLOUDS_IDENTITY
  • JCLOUDS_CREDENTIAL