+.. code-block:: console
+
+ $ kamaki config set cloud.<cloud alias>.url <cloud-authentication-URL>
+ $ kamaki config set cloud.<cloud alias>.token myt0k3n==
+
+If only one cloud is configured, it is automatically considered the default.
+Otherwise, a default cloud should be specified:
+
+.. code-block:: console
+
+ $ kamaki config set default_cloud <cloud alias>
+
+Since version 0.14, Synnefo supports a single authentication URL for retrieving
+all API endpoints. This URL is retrieved from the Synnefo Web UI and should be
+set as the cloud URL for kamaki. All service-specific URLs are retrieved and
+handled automatically. Users of Synnefo clouds >=0.14 are advised against using
+any service-specific URLs.
+
+Migrating from kamaki 0.8.X to 0.9 or better
+--------------------------------------------
+
+This section refers to running installations of kamaki version <= 0.8.X. To
+check the current kamaki version:
+
+.. code-block:: console
+
+ $ kamaki -V
+
+Existing kamaki users should convert their configuration files to v9. To do
+that, kamaki 0.9 can inspect the configuration file and suggests a list of
+config file transformations, which are performed automatically after users'
+permission. This mechanism is invoked when an API-related kamaki command is
+fired. On example 2.1 we suggest using the `user authenticate` command to start
+the conversion mechanism for the configuration file.
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 2.1: Convert config file while authenticating user "exampleuser"
+
+ $ kamaki user authenticate
+ Config file format version >= 9.0 is required
+ Configuration file: "/home/exampleuser/.kamakirc"
+ but kamaki can fix this:
+ Calculating changes while preserving information
+ ... rescue global.token => cloud.default.token
+ ... rescue config.cli => global.config_cli
+ ... rescue history.file => global.history_file
+ ... DONE
+ The following information will NOT be preserved:
+ global.account =
+ global.data_log = on
+ user.account = exampleuser@example.com
+ user.url = https://accounts.okeanos.grnet.gr
+ compute.url = https://cyclades.okeanos.grnet.gr/api/v1.1
+ file.url = https://pithos.okeanos.grnet.gr/v1
+ image.url = https://cyclades.okeanos.grnet.gr/plankton
+
+ Kamaki is ready to convert the config file to version 9.0
+ Overwrite file /home/exampleuser/.kamakirc ? [Y, y]
+
+At this point, we should examine the kamaki output. Most options are renamed to
+match the latest configuration file version specifications.
+
+Lets take a look at the discarded options:
+
+* `global.account` and `user.account` are not used anymore.
+ The same is true for the synonyms `store.account` and `pithos.account`.
+ These options were used to explicitly set a user account or uuid to a
+ pithos call. In the latest Synnefo version (>= 0.14), these features are
+ meaningless and therefore omitted.
+
+* `global.data_log` option has never been a valid kamaki config option.
+ In this scenario, the user wanted to set the `log_data` option, but he or
+ she typed `data_log` instead. To fix this, the user should manually set the
+ correct option after the conversion is complete (Example 2.2).
+
+Users should press *y* when they are ready, which will cause the default config
+file to be modified so that it conforms with the latest version.
+
+.. code-block:: console
+ :emphasize-lines: 1
+
+ Example 2.2: Rescue misspelled log_data option
+
+ $ kamaki config set log_data on
+
+In order to convert more files, users may run kamaki with the -c option, which
+runs kamaki with a different configuration file (Example 2.3) and apply the
+steps described above.