| commit | 8ab4409c0773800ef2063049ef8e7cd785131d68 | [log] [tgz] |
|---|---|---|
| author | Adrian Cole <adrian@jclouds.org> | Mon Jul 02 12:40:01 2012 -0700 |
| committer | Adrian Cole <adrian@jclouds.org> | Mon Jul 02 12:40:01 2012 -0700 |
| tree | 864930ff33b3d2529ddafb50fd80ff098cf76cb6 | |
| parent | b1f1e34c65153a3783de6770d956a8637cb62963 [diff] | |
| parent | a2a866cbc7c8b1722368f86fcb5e798618659a0e [diff] |
Merge pull request #2 from abayer/master Fix sshj spam
Jclouds CLI provides two types of command line interface:
To install the jclouds cli you just need to download the zip or the tarball and extract it to the folder of your choice.
To start the interactive shell: ./bin/jclouds-cli
The are two ways of configuring a provider or api, when using the interactive mode:
All commands support the following options that you can use: --provider (use this for apis too), --identity, --credential --endpoint.
For example, in a fresh installation you can simple:
If you want to avoid passing the same options all the time, you can configure the provider or the api once and reuse it. To configure the provider or the api:
For compute providers & apis:
For blobstore providers or apis:
These commands, will create a new configuration with the filename specified as an argument. Each configuration will be assigned a new unique id, which you can use if you need to edit or delete the config in the future.
Once the service is configured, you can verify the service installation using:
To use the cli: ./bin/jclouds [category] [action] [options] [arguments].
Some examples: To create 10 nodes on EC2 under group: myGroupName using Ubuntu 10.04
To list all nodes:
To destroy a node:
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: