Here are the command-line tools StratusLab provides.

Instance management

• stratus-run-instance
• stratus-describe-instance
• stratus-kill-instance
• stratus-shutdown-instance
• stratus-run-cluster
• stratus-connect-instance
• stratus-create-image

Volume management

• stratus-describe-volumes
• stratus-create-volume
• stratus-attach-volume
• stratus-detach-volume
• stratus-delete-volume

Metadata management

• stratus-build-metadata
• stratus-upload-image
• stratus-sign-metadata
• stratus-validate-metadata
• stratus-upload-metadata
• stratus-deprecate-metadata

Other

• stratus-run-benchmark
• stratus-hash-password

These commands are available in the package/tarball stratuslab-cli-user. The above links provide descriptions of the utilities highlighting the main use-cases and describing main parameters. Please run the commands with -h/–help to get list of all supported parameters and their respective descriptions.

For working with user command-line tools one would need to posses the following credentials (requirement depends on use-case and utility used):

• X509 key/pair
• Globus/VOMS proxy
• PKCS12 certificate
• username/password of the account in StratusLab, Cloud frontend(s)

The configuration file contains definitions of different endpoints and credentials required for the user client. By default, user CLI utilities will search for the following file: $HOME/.stratuslab/stratuslab-user.cfg. This can be overwritten with -c/–config parameter. If the file is not found, a warning will be issued and required parameters will be searched in the following order: defaults, environment variables, command line options.

The configuration reference template file for RPM distribution is /etc/stratuslab/stratuslab-user.cfg.ref and for tar-ball is conf/stratuslab-user.cfg.ref.

User has to copy the file e.g. to the default location $HOME/.stratuslab/stratuslab-user.cfg and modify it accordingly. See stratuslab-user.cfg.ref for explanations of the variables. The variables that are commented out (eg p12_certificate) take their default values from the code.

The order of processing

1. defaults defined in the code 
2. configuration file
3. environment variable
4. command line parameter 

On example of MarketPlace Endpoint

1. http://appliances.stratuslab.eu/marketplace/metadata
2. marketplace_endpoint = http://appliances.stratuslab.eu/marketplace/metadata
3. STRATUSLAB_MARKETPLACE_ENDPOINT
4. --marketplace-endpoint

The variables in the configuration file correspond to the respective environment variables applying the following transformation STRATUSLAB_upper(<var in conf file>). I.e. apprepo_username → STRATUSLAB_APPREPO_USERNAME.

Installation, configuration and system test

• stratus-config
• stratus-install
• stratus-remote-install
• stratus-test

Utilities used in StratusLab transfer management scripts

– Image and image metadata

• stratus-policy-image
• stratus-manifest

– Persistent Disk Storage access

• stratus-storage
• stratus-storage-search
• stratus-storage-update
• stratus-storage-quarantine
• stratus-storage-delete
• stratus-download-image

– Other

• stratus-msg-publisher
• stratus-generate-p12

These commands are available in the package/tarball stratuslab-cli-sysadmin. For more details on manual installation/configuration see Manual Cloud Services Installation.