Usage
=====
-Kamaki offers two command line interfaces: an one-command tool and an interactive shell. Both systems implement exactly the same command specifications. More details on the exact command specifications can be found in `Command Line Interfaces' section under 'Commands`. This guide covers the generic usage of both interfaces.
+Kamaki offers command line interfaces that implement specific command specifications. A detailed list of the command specifications can be found in `Commands <commands.html>`_ section. This guide covers the generic usage of both interfaces.
+
+What's more, kamaki offers a clients API that allows the development of external applications for synnefo. The clients API is listed in the `Clients lib <developers/code.html#the-clients-api>`_ section.
+
+Quick Setup
+-----------
+
+Kamaki interfaces rely on a list of configuration options. In the initial state, kamaki is configured to communicate with the Okeanos IaaS. A detailed guide for setting up kamaki can be found in the `Setup <setup.html>`_ section.
+
+It is essential for users to get a valid configuration token that works with for a synnefo-compliant Identity Manager service (okeanos.grnet.gr users go `here <https://accounts.okeanos.grnet.gr/im/>`_) and provide it to kamaki:
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 1.1: Set user token to myt0k3n==
+
+ $ kamaki set token myt0k3n==
+
+Shell vs one-command
+--------------------
+Kamaki users can access synnefo services through either the interactive shell or the one-command behaviors. In practice, both systems rely on the same command set implementations and API clients, with identical responses and error messages. Still, there are some differences.
+
+In favor of interactive shell behavior:
+
+* tab completion for commands (mostly on (X)nix OSs)
+* session history with "up" / "down" keys
+* shorter commands with command context switching
+* re-run old commands with /history
+
+In favor of one-command behavior:
+
+* can be used along with advanced shell features (pipelines, redirection, etc.)
+* can be used in shell scripts
+* prints debug and verbose messages if needed
+
+Run as shell
+^^^^^^^^^^^^
+To use kamaki as a shell, run:
+
+* without any parameters or arguments
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 2.2.1: Run kamaki shell
+
+ $ kamaki
+
+* with any kind of '-' prefixed arguments, except '-h', '--help'.
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 2.2.2: Run kamaki shell with custom configuration file
+
+ $ kamaki --config myconfig.file
+
+
+Run as one-command
+^^^^^^^^^^^^^^^^^^
+To use kamaki as an one-command tool, run:
+
+* with the '-h' or '--help' arguments (help for kamaki one-command)
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 2.3.1: Kamaki help
+
+ $kamaki -h
+
+* with one or more command parameters:
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 2.3.2: List VMs managed by user
+
+ $ kamaki server list
One-command interface
---------------------
+Using help
+^^^^^^^^^^
+
+Kamaki help is used to list available commands with description, syntax and corresponding optional arguments.
+
+To see the command groups, use -h or --help like in example 1.3.1. In the same way, help information for command groups and commands is printed. In the following examples, the help messages of kamaki, of a command group (server) and of a command in that group (list) are shown.
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 3.1.1: kamaki help shows available parameters and command groups
+
+
+ $ kamaki -h
+ usage: kamaki <cmd_group> [<cmd_subbroup> ...] <cmd>
+ [-s] [-V] [-i] [--config CONFIG] [-o OPTIONS] [-h]
+
+ optional arguments:
+ -v, --verbose More info at response
+ -s, --silent Do not output anything
+ -V, --version Print current version
+ -d, --debug Include debug output
+ -i, --include Include protocol headers in the output
+ --config CONFIG Path to configuration file
+ -o OPTIONS, --options OPTIONS
+ Override a config value
+ -h, --help Show help message
+
+ Options:
+ - - - -
+ astakos: Astakos API commands
+ config : Configuration commands
+ flavor : Compute/Cyclades API flavor commands
+ history: Command history
+ image : Compute/Cyclades or Plankton API image commands
+ network: Compute/Cyclades API network commands
+ server : Compute/Cyclades API server commands
+ store : Pithos+ storage commands
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 3.1.2: Cyclades help contains all first-level commands of Cyclades command group
+
+
+ $ kamaki server -h
+ usage: kamaki server <...> [-v] [-s] [-V] [-d] [-i] [--config CONFIG]
+ [-o OPTIONS] [-h]
+
+ optional arguments:
+ -v, --verbose More info at response
+ -s, --silent Do not output anything
+ -V, --version Print current version
+ -d, --debug Include debug output
+ -i, --include Include protocol headers in the output
+ --config CONFIG Path to configuration file
+ -o OPTIONS, --options OPTIONS
+ Override a config value
+ -h, --help Show help message
+
+ Options:
+ - - - -
+ addmeta : Add server metadata
+ addr : List a server's nic address
+ console : Get a VNC console
+ create : Create a server
+ delete : Delete a server
+ delmeta : Delete server metadata
+ firewall: Set the server's firewall profile
+ info : Get server details
+ list : List servers
+ meta : Get a server's metadata
+ reboot : Reboot a server
+ rename : Update a server's name
+ setmeta : Update server's metadata
+ shutdown: Shutdown a server
+ start : Start a server
+ stats : Get server statistics
+ wait : Wait for server to finish [BUILD, STOPPED, REBOOT, ACTIVE]
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 3.1.3: Help for command "server list" with syntax, description and available user options
+
+
+ $ kamaki server list -h
+ usage: kamaki server list [-V] [-i] [--config CONFIG] [-h] [-l]
+
+ List servers
+
+ optional arguments:
+ -v, --verbose More info at response
+ -s, --silent Do not output anything
+ -V, --version Print current version
+ -d, --debug Include debug output
+ -i, --include Include protocol headers in the output
+ --config CONFIG Path to configuration file
+ -o OPTIONS, --options OPTIONS
+ Override a config value
+ -h, --help Show help message
+ -l show detailed output
+
+.. _using-history-ref:
+
+Using history
+^^^^^^^^^^^^^
+
+Kamaki command history is stored in a file at user home (".kamaki.history" by default). To set a custom history file path users must set the history.file config option (see `available config options <setup.html#editing-options>`_).
+
+Every syntactically correct command is appended at the end of that file. In order to see how to use history, use the kamaki help system:
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 3.2.1: Available history options
+
+
+ $ kamaki history -h
+ Options:
+ - - - -
+ clean: Clean up history (permanent)
+ run : Run previously executed command(s)
+ show : Show intersession command history
+
+The following example showcases how to use history in kamaki
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 3.2.2: Clean up everything, run a kamaki command, show full and filtered history
+
+
+ $ kamaki history clean
+ $ kamaki server list
+ ...
+ $ kamaki history show
+ 1. kamaki server list
+ 2. kamaki history show
+ $ kamaki history show --match server
+ 1. kamaki server list
+ 3. kamaki history show --match server
+
+Debug
+^^^^^
+
+In case of errors, kamaki in debug mode shows useful debug information, like the stack trace. Kamaki in debug mode cancels suppression of warning messages.
+
+To run kamaki in debug mode use the -d or --debug option (can be combined with any other parameters or options)
+
+Verbose and Include
+"""""""""""""""""""
+
+Most kamaki commands are translated into http requests. Kamaki clients API translated the semantics to REST and handles the response. Users who need to have access to these commands can use the verbose mode that presents the HTTP Request details as well as the full server response.
+
+To run kamaki in verbose mode use the -v or --verbose option
+
+Be default, kamaki in verbose mode prints down only the headers and the address information, thus hiding the data body of the request or response. To see the data body, the -i option can be used.
+
+One-command features
+^^^^^^^^^^^^^^^^^^^^
+
+Kamaki commands can be used along with advanced shell features.
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 3.4.1: Print username for token us3rt0k3n== using grep
+
+
+ $ kamaki astakos authenticate -o token=us3rt0k3n== | grep userame
+ userame : user@synnefo.org
+
+The -o argument can be used to temporarily override various (set or unset) options. In one command, all -o option sets are forgotten just after the command has been completed, and the previous settings are restored (a.k.a. the configuration file is not modified).
+
+The astakos-authenticate command in example 3.4.1 runs with an explicitly provided token, which temporarily overrides the token provided in the configuration file.
+
Interactive shell
-----------------
+
+Command Contexts
+^^^^^^^^^^^^^^^^
+
+The kamaki interactive shell implements the notion of command contexts. Each command group is also a context where the users can **enter** by typing the group name. If the context switch is successful, the kamaki shell prompt changes to present the new context ("store" in example 4.1.1).
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 4.1.1: Enter store commands context / group
+
+
+ $ kamaki
+ [kamaki]: store
+ [store]:
+
+Type **exit** (alternatively **ctrl-D** in (X)nix systems or **ctrl-Z** in Windows) to exit a context and return to the context of origin. If already at the top context (kamaki), an exit is equivalent to exiting the program.
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 4.1.2: Exit store context and then exit kamaki
+
+ [store]: exit
+ [kamaki]: exit
+ $
+
+A user might **browse** through different contexts during one session.
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 4.1.3: Execute list command in different contexts
+
+ $ kamaki
+ [kamaki]: config
+ [config]: list
+ ... (configuration options listing) ...
+ [config]: exit
+ [kamaki]: store
+ [store]: list
+ ... (storage containers listing) ...
+ [store]: exit
+ [kamaki]: server
+ [server]: list
+ ... (VMs listing) ...
+ [server]: exit
+ [kamaki]:
+
+Users have the option to avoid switching between contexts: all commands can run from the **top context**. As a result, examples 4.1.3 and 4.1.4 are equivalent.
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 4.1.4: Execute different "list" commands from top context
+
+
+ [kamaki]: config list
+ ... (configuration options listing) ...
+ [kamaki]: store list
+ ... (storage container listing) ...
+ [kamaki]: server list
+ ... (VMs listing) ...
+ [kamaki]:
+
+Using Help
+^^^^^^^^^^
+
+There are two help mechanisms: a context-level and a command-level.
+
+**Context-level help** lists the available commands in a context and can also offer a short description for each command.
+
+Context-level help syntax::
+
+ * Show available commands in current context *
+ [context]: help
+ [context]: ?
+
+ * Show help for command cmd *
+ [context]: help cmd
+ [context]: ?cmd
+
+The context-level help results change from context to context
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 4.2.1: Get available commands, pick a context and get help there as well
+
+
+ [kamaki]: help
+
+ kamaki commands:
+ ================
+ astakos config flavor history image network server store
+
+ interactive shell commands:
+ ===========================
+ exit help shell
+
+ [kamaki]: ?config
+ Configuration commands (config -h for more options)
+
+ [kamaki]: config
+
+ [config]: ?
+
+ config commands:
+ ================
+ delete get list set
+
+ interactive shell commands:
+ ===========================
+ exit help shell
+
+ [config]: help set
+ Set a configuration option (set -h for more options)
+
+In context-level, there is a distinction between kamaki-commands and interactive shell commands. The former are available in one-command mode and are related to the cloud client setup and use, while the later are context-shell functions.
+
+**Command-level help** prints the syntax, arguments and description of a specific (terminal) command
+
+Command-level help syntax::
+
+ * Get help for command cmd1 cmd2 ... cmdN *
+ [context]: cmd1 cmd2 ... cmdN -h
+ <syntax>
+
+ <description>
+
+ <arguments and possible extensions>
+
+Command-level help mechanism is exactly the same as the one used in one-command mode. For example, it is invoked by using the -h or --help parameter at any point.
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 4.2.2: Get command-level help for config and config-set
+
+
+ [kamaki]: config --help
+ config: Configuration commands
+ delete: Delete a configuration option (and use the default value)
+ get : Show a configuration option
+ list : List configuration options
+ set : Set a configuration option
+
+ [kamaki]: config
+
+ [config]: set -h
+ usage: set <option> <value> [-v] [-d] [-h] [-i] [--config CONFIG] [-s]
+
+ Set a configuration option
+
+ optional arguments:
+ -v, --verbose More info at response
+ -d, --debug Include debug output
+ -h, --help Show help message
+ -i, --include Include protocol headers in the output
+ --config CONFIG Path to configuration file
+ -s, --silent Do not output anything
+
+There are many ways of producing a help message, as shown in example 4.2.3
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 4.2.3: Equivalent calls of command-level help for config-set
+
+
+ [config]: set -h
+ [config]: set --help
+ [kamaki]: config set -h
+ [kamaki]: config set --help
+ [store]: /config set -h
+ [server]: /config set --help
+
+.. _accessing-top-level-commands-ref:
+
+Accessing top-level commands
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+When working in a context, it is often useful to access other contexts or top-level commands. Kamaki offers access to top-level commands by using the / prefix, as shown bellow::
+
+ * access a command "anothercontext cmd1 cmd2 ... cmdN"
+ [context]: /anothercontext cmd1 cmd2 ... cmdN
+
+An example (4.3.1) that showcases how top-level access improves user experience is the creation of a VM. A VM is created with the command server-create. This command is called with three parameters:
+
+* the name of the new VM
+* the flavor id
+* the image id
+
+It is often the case that a user who works in the context command, needs to create a new VM, but hasn't selected a flavor or an image id, or cannot recall the id of that flavor or image. Therefore, it is necessary to list all available flavors (flavor-list) or images (image-list). Both commands belong to different contexts.
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 4.3.1: Create a VM from server context
+
+ [server]: create -h
+ create <name> <flavor id> <image id> ...
+ ...
+
+ [server]: /flavor list
+ ...
+ 43 AFLAVOR
+ SNF:disk_template: drbd
+ cpu : 4
+ disk : 10
+ ram : 2048
+
+ [server]: /image list
+ 1580deb4-edb3-7a246c4c0528 (Ubuntu Desktop)
+ 18a82962-43eb-8f8880af89d7 (Windows 7)
+ 531aa018-9a40-a4bfe6a0caff (Windows XP)
+ 6aa6eafd-dccb-67fe2bdde87e (Debian Desktop)
+
+ [server]: create 'my debian' 43 6aa6eafd-dccb-67fe2bdde87e
+ ...
+
+An other example (4.3.2) showcases how to acquire and modify configuration settings from a different context. In this scenario, the user token expires at server side while the user is working. When that happens, the system responds with an *(401) UNAUTHORIZED* message. The user can acquire a new token (valid for the astakos identity manager of preference) which has to be set to kamaki.
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 4.3.2: Set a new token from store context
+
+
+ [store]: list
+ (401) UNAUTHORIZED Access denied
+
+ [store]: /astakos authenticate
+ (401) UNAUTHORIZED Invalid X-Auth-Token
+
+ [store]: /config get token
+ my3xp1r3dt0k3n==
+
+ [store]: /config set token myfr35ht0k3n==
+
+ [store]: /config get token
+ myfr35ht0k3n==
+
+ [store]: list
+ 1. pithos (10MB, 2 objects)
+ 2. trash (0B, 0 objects)
+
+.. note:: The error messages on this example where shortened for clarity. Actual kamaki error messages are more helpful and descriptive.
+
+The following example compares some equivalent calls that run *astakos-authenticate* after a *store-list* 401 failure.
+
+.. code-block:: console
+ :emphasize-lines: 1,3,10,17,26
+
+ Example 4.3.3: Equivalent astakos-authenticate calls after a store-list 401 failure
+
+ * without kamaki interactive shell *
+ $ kamaki store list
+ (401) UNAUTHORIZED Access denied
+ $ kamaki astakos authenticate
+ ...
+ $
+
+ * from top-level context *
+ [kamaki]: store list
+ (401) UNAUTHORIZED Access denied
+ [kamaki]: astakos authenticate
+ ...
+ [kamaki]
+
+ * maximum typing *
+ [store]: list
+ (401) UNAUTHORIZED Access denied
+ [store]: exit
+ [kamaki]: astakos
+ [astakos]: authenticate
+ ...
+ [astakos]:
+
+ * minimum typing *
+ [store]: list
+ (401) UNAUTHORIZED Access denied
+ [store]: /astakos authenticate
+ ...
+ [store]:
+
+.. hint:: To exit kamaki shell while in a context, try */exit*
+
+Using config
+^^^^^^^^^^^^
+
+The configuration mechanism of kamaki is detailed at the `setup section <setup.html>`_ and it is common for both interaction modes. In specific, the configuration mechanism is implemented as a command group, namely *config*. Using the config commands is as straightforward as any other kamaki commands.
+
+It is often useful to set, delete or update a value. This can be managed either inside the config context or from any command context by using the / prefix.
+
+.. Note:: config updates in kamaki shell persist even after the session is over.
+
+All setting changes affect the physical kamaki config file. The config file is created automatically at callers' home firectory the first time a config option is set, and lives there as *.kamakirc* . It can be edited with any text editor or managed with kamaki config commands.
+
+In example 4.4.1 the user is going to work with only one storage container. The store commands use the container:path syntax, but if the user sets a container name as default, the container name can be omitted. This is possible by setting a *store.container* setting.
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 4.4.1: Set default storage container
+
+
+ [store]: list
+ 1. mycontainer (32MB, 2 objects)
+ 2. pithos (0B, 0 objects)
+ 3. trash (2MB, 1 objects)
+
+ [store]: list mycontainer
+ 1. D mydir/
+ 2. 20M mydir/rndm_local.file
+
+ [store]: /config set store.container mycontainer
+
+ [store]: list
+ 1. D mydir/
+ 2. 20M mydir/rndm_local.file
+
+After a while, the user needs to work with multiple containers, therefore a default container is no longer needed. The *store.container* setting can be deleted, as shown in example 4.4.2 .
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 4.4.2: Delete a setting option
+
+
+ [store]: /config delete store.container
+
+ [store]: list
+ 1. mycontainer (32MB, 2 objects)
+ 2. pithos (0B, 0 objects)
+ 3. trash (2MB, 1 objects)
+
+Using history
+^^^^^^^^^^^^^
+
+There are two history modes: session and permanent. Session history keeps record of all actions in a kamaki shell session, while permanent history appends all commands to an accessible history file.
+
+Session history is only available in interactive shell mode. Users can iterate through past commands in the same session with the *up* and *down* keys. Session history is not stored, although syntactically correct commands are recorded through the permanent history mechanism
+
+Permanent history is implemented as a command group and is common to both the one-command and shell interfaces. In specific, every syntactically correct command is appended in a history file (configured as *history.file* in settings, see `setup section <setup.html>`_ for details). Commands executed in one-command mode are mixed with the ones run in kamaki shell (also see :ref:`using-history-ref` section on this guide).
+
+Scripting
+^^^^^^^^^
+
+The history-run feature allows the sequential run of previous command executions in kamaki shell.
+
+The following sequence copies and downloads a file from *mycontainer1* , uploads it to *mycontainer2* , then undo the proccess and repeats it with history-run
+
+.. code-block:: console
+ :emphasize-lines: 1,12,19,32
+
+ * Download mycontainer1:myfile and upload it to mycontainer2:myfile
+ [kamaki]: store
+ [store]: copy mycontainer1:somefile mycontainer1:myfile
+ [store]: download mycontainer1:myfile mylocalfile
+ Download completed
+ [store]: upload mylocalfile mycontainer2:myfile
+ Upload completed
+
+ * undo the process *
+ [store]: !rm mylocalfile
+ [store]: delete mycontainer1:myfile
+ [store]: delete mycontainer2:myfile
+
+ * check history entries *
+ [store]: exit
+ [kamaki]: history
+ [history]: show
+ 1. store
+ 2. store copy mycontainer1:somefile mycontainer1:myfile
+ 3. store download mycontainer1:myfile mylocalfile
+ 4. store upload mylocalfile mycontainer2:myfile
+ 5. store delete mycontainer1:myfile
+ 6. store delete mycontainer2:myfile
+ 7. history
+ 8. history show
+
+ *repeat the process *
+ [history]: run 2-4
+ <store copy mycontainer1:somefile mycontainer1:myfile>
+ <store download mycontainer1:myfile mylocalfile>
+ Download completed
+ <store upload mylocalfile mycontainer2:myfile>
+ Upload completed
+
+For powerfull scripting, users are advised to take advantage of their os shell scripting capabilities and combine them with kamaki one-command. Still, the history-run functionality might prove handy in many occasions.
+
+Tab completion
+^^^^^^^^^^^^^^
+
+Kamaki shell features tab completion for the first level of command terms of the current context. Tab completion pool changes dynamically when the context is switched. Currently, tab completion is not supported when / is used (see :ref:`accessing-top-level-commands-ref` ).
+
+OS Shell integration
+^^^^^^^^^^^^^^^^^^^^
+
+Kamaki shell features the ability to execute OS-shell commands from any context. This can be achieved by typing *!* or *shell*::
+
+ [kamaki_context]: !<OS shell command>
+ ... OS shell command output ...
+
+ [kamaki_context]: shell <OS shell command>
+ ... OS shell command output ...
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 4.7.1: Run unix-style shell commands from kamaki shell
+
+
+ [kamaki]: !ls -al
+ total 16
+ drwxrwxr-x 2 username username 4096 Nov 27 16:47 .
+ drwxrwxr-x 7 username username 4096 Nov 27 16:47 ..
+ -rw-rw-r-- 1 username username 8063 Jun 28 14:48 kamaki-logo.png
+
+ [kamaki]: shell cp kamaki-logo.png logo-copy.png
+
+ [kamaki]: shell ls -al
+ total 24
+ drwxrwxr-x 2 username username 4096 Nov 27 16:47 .
+ drwxrwxr-x 7 username username 4096 Nov 27 16:47 ..
+ -rw-rw-r-- 1 username username 8063 Jun 28 14:48 kamaki-logo.png
+ -rw-rw-r-- 1 username username 8063 Jun 28 14:48 logo-copy.png
+
+
+Kamaki shell commits command strings to the outside shell and prints the results, without interacting with it. After a command is finished, kamaki shell returns to its initial state, which involves the current directory, as show in example 4.8.2 .
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 4.8.2: Attempt (and fail) to change working directory
+
+
+ [kamaki]: !pwd
+ /home/username
+
+ [kamaki]: !cd ..
+
+ [kamaki]: shell pwd
+ /home/username
projects / kamaki / blobdiff