Revision fa479dc3 docs/setup.rst

b/docs/setup.rst
1 1
Setup
2 2
=====
3 3

  
4
Kamaki is easy to install from source or as a package. Some ui features are optional and can be install separately. Kamaki behavior can be configured in the kamaki config file.
4
Kamaki is easy to install from source or as a package. Some advanced or ui features
5
are optional and can be installed separately. Kamaki behavior can be configured in
6
the kamaki config file.
5 7

  
6 8
Quick Setup
7 9
-----------
8 10

  
9
Kamaki interfaces rely on a list of configuration options. Be default, they are configured to communicate with the `Okeanos IaaS <http://okeanos.grnet.gr>`_.
11
Existing kamaki users should consult the
12
`migration guide <#migrating-from-kamaki-0-8-x-to-0-9>`_ first.
10 13

  
11
.. note:: It is essential for users to get a configuration token (okeanos.grnet.gr users go `here <https://accounts.okeanos.grnet.gr/im/>`_) and provide it to kamaki:
14
Kamaki has to be configured to use a specific Synnefo deployment.
12 15

  
16
Since Synnefo version 0.14, each deployment offers a single authentication
17
url, which has to be set as the default url for kamaki (Example 1.1).
18

  
19
.. code-block:: console
20
    :emphasize-lines: 1, 2
21

  
22
    Example 1.1: Set https://astakos.example.com/astakos/identity/v2.0/ as the
23
    default single authentication url 
24
    
25
    $ kamaki config set remote.default.url https://astakos.example.com/astakos/identity/v2.0/
26

  
27
Kamaki also needs a user authentication token (Example 1.2).
28

  
29
.. code-block:: console
30
    :emphasize-lines: 1
31

  
32
    Example 1.2: Set user token to myt0k3n==
33

  
34
    $ kamaki config set remote.default.token myt0k3n==
35

  
36
Migrating from kamaki 0.8.X to 0.9
37
----------------------------------
38

  
39
This section refers to running installations of kamaki version <= 0.8.X
40
To check the current kamaki version:
41

  
42
.. code-block:: console
43

  
44
    $ kamaki -V
45

  
46
Existing kamaki users should convert their configuration files to v3. To do
47
that, kamaki 0.9 inspects the configuration file and suggests a list of config
48
file transformations, which are performed automatically on user permission.
49
This mechanism is invoked when the first API-releated kamaki command is fired.
50
We suggest the command of the example 2.1.
51

  
52
.. code-block:: console
53
    :emphasize-lines: 1
54

  
55
    Example 2.1: Try to authenticate user but convert config file instead
56

  
57
    $ kamaki user authenticate
58
    Config file format version >= 3.0 is required
59
    Configuration file "/home/exampleuser/.kamakirc" format is not up to date
60
    but kamaki can fix this:
61
    Calculating changes while preserving information
62
    ... rescue global.token => remote.default.token
63
    ... rescue config.cli => global.config_cli
64
    ... rescue history.file => global.history_file
65
    ... DONE
66
    The following information will NOT be preserved:
67
        global.account = 
68
        global.data_log = on
69
        user.account = exampleuser@example.com
70
        user.url = https://accounts.okeanos.grnet.gr
71
        compute.url = https://cyclades.okeanos.grnet.gr/api/v1.1
72
        file.url = https://pithos.okeanos.grnet.gr/v1
73
        image.url = https://cyclades.okeanos.grnet.gr/plankton
74

  
75
    Kamaki is ready to convert the config file to version 3.0
76
    Overwrite file /home/exampleuser/.kamakirc ? [Y, y]
77

  
78
At this point, we should examine the kamaki output. Most options are renamed to
79
be accessible by the new kamaki.
80

  
81
Let's take a look at the discarded options:
82

  
83
* global.account and user.account are not used anymore. The same is true for
84
    store.account and pithos.account which were ways to explicitly set a user
85
    account name to a pithos call. After the latest Synnefo evolutions, these
86
    features are meaningless and therefore omitted.
87

  
88
* global.data_log option has never been a valid kamaki config option. In this
89
    example, the user accidentally mixed the terms "log_data" (which is a valid
90
    kamaki config option) with "data_log". To fix this, the user should set the
91
    correct option after the conversion is complete (Example 2.2)
92

  
93
Users should press *y* when they are ready. Kamaki has now modified the default
94
config file to conform with kamaki config file v3. Now users should rescue
95
unrescued information (if any).
96

  
97
.. code-block:: console
98
    :emphasize-lines: 1
99

  
100
    Example 2.2: Rescue misspelled log_data option
101

  
102
    $ kamaki config set log_data on
103

  
104
In order to convert more files, users may run kamaki with the -c option
105
(Example 2.3) and apply the steps described above.
13 106

  
14 107
.. code-block:: console
15 108
    :emphasize-lines: 1
16 109

  
17
    Example 1.1: Set user token to myt0k3n==
110
    Example 2.3: Use kamaki to update a configuration file called ".myfilerc"
18 111

  
19
    $ kamaki config set token myt0k3n==
112
    $ kamaki -c .myfilerc user authenticate
20 113

  
21 114
Optional features
22 115
-----------------
23 116

  
24
For installing any or all of the following, consult the `kamaki installation guide <installation.html#install-ansicolors>`_
117
For installing any or all of the following, consult the
118
`kamaki installation guide <installation.html#install-ansicolors>`_
25 119

  
26 120
* ansicolors
27 121
    * Make command line / console user interface responses prettier with text formating (colors, bold, etc.)

Also available in: Unified diff