Synnefo

   $ kamaki config list

.. code-block:: console

   $ kamaki config set file.url https://pithos.example.com/v1

   $ kamaki config set user.url https://accounts.example.com

   $ kamaki config set token ...

have been written for advanced operations wherever needed, and minor changes

for things that were missing or change frequently.

| Cyclades/Compute Service -> OpenStack Compute API

| Cyclades/Network Service -> OpenStack Compute/Network API (not Quantum yet)

| Pithos/Storage Service -> OpenStack Object Store API

| Astakos/Identity Service -> Proprietary, moving to OpenStack Keystone API

Below, we will describe all Synnefo APIs with conjuction to the OpenStack APIs.

    Identity API <astakos-api-guide>

.. toctree::

    :maxdepth: 2

details.

.. toctree::

   :maxdepth: 2

   Object Storage Service (codename: pithos) <pithos>

   Compute Service (codename: cyclades) <cyclades>

   Network Service (part of Cyclades) <networks>

   Volume Storage Service (codename: archipelago) <archipelago>

.. image:: images/synnefo-overview.png

.. _plankton:

Introduction

============

Let's see below:

.. image:: images/synnefo-clonepath.png

The figure shows a sailor bundling his physical machine with the

    * Identity Management (Astakos)

    * Object Storage Service (Pithos+)

    * Compute Service (Cyclades)

and a single unified Web UI to manage them all.

Installation of Synnefo / Introduction

======================================

For the rest of the documentation we will refer to the first physical node as

"node1" and the second as "node2". We will also assume that their domain names

=====================

These are the general synnefo prerequisites, that you need on node1 and node2

To be able to download all synnefo components you need to add the following

lines in your ``/etc/apt/sources.list`` file:

please continue with the rest of the guide.

Besides Astakos and Pithos+, you will also need a number of additional working

prerequisites, before you start the Cyclades installation.

More about Ganeti's RAPI users `here.

<http://docs.ganeti.org/ganeti/2.5/html/rapi.html#introduction>`_

This section describes the installation of Cyclades. Cyclades is Synnefo's

.. code-block:: console

   # apt-get install snf-cyclades-app memcached python-memcache

Since version 0.13, Synnefo uses the VMAPI in order to prevent sensitive data

needed by 'snf-image' to be stored in Ganeti configuration (e.g. VM password).

request. Synnefo uses `memcached <http://memcached.org/>`_ as a

`Django <https://www.djangoproject.com/>`_ cache backend.

Conf files

----------

   BACKEND_DB_CONNECTION = 'postgresql://synnefo:example_passw0rd@node1.example.com:5432/snf_pithos'

   BACKEND_BLOCK_PATH = '/srv/pithos/data/'

denotes the Pithos+ database (where the Image files are stored). So we set that

to point to our Pithos+ database. ``BACKEND_BLOCK_PATH`` denotes the actual

Pithos+ data location.

   CHUID="nobody:www-data"

Database Initialization

-----------------------

   node1 # snf-manage reconcile-resources-cyclades --fix

If all the above return successfully, then you have finished with the Cyclades

Let's test our installation now.

Cyclades Web UI

---------------

Cyclades Images

---------------

 * Upload an Image file to Pithos+

 * Spawn a new VM from that Image from the Cyclades Web UI

We will use the `kamaki <http://www.synnefo.org/docs/kamaki/latest/index.html>`_

   $ kamaki config set user.url "https://node1.example.com"

   $ kamaki config set compute.url "https://node1.example.com/api/v1.1"

   $ kamaki config set file.url "https://node2.example.com/v1"

   $ kamaki config set token USER_TOKEN

Alternatively check if the new container and file appear on the Pithos+ Web UI.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

For the purposes of the following example, we assume that the user UUID is

``u53r-un1qu3-1d``.

Once the Image file has been successfully uploaded on Pithos+ then we register

.. code-block:: console

This command registers the Pithos+ file

``pithos://u53r-un1qu3-1d/images/debian_base-6.0-7-x86_64.diskdump`` as an

be able to spawn VMs from it and is of type ``diskdump``. The first two

properties (``OSFAMILY`` and ``ROOT_PARTITION``) are mandatory. All the rest

properties are optional, but recommended, so that the Images appear nicely on

inside the ``20-snf-cyclades-app-ui.conf`` configuration file.

``OSFAMILY`` and ``ROOT_PARTITION`` are mandatory because they will be passed

:ref:`previous section <ganeti-with-pithos-images>`). All other properties are

used to show information on the Cyclades UI.

 * Identity Management (Astakos)

 * Object Storage Service (Pithos+)

 * Compute Service (Cyclades)

and a single unified Web UI to manage them all.

    # kamaki config set astakos.url "https://accounts.example.com"

    # kamaki config set compute.url "https://cyclades.example.com/api/v1.1"

    # kamaki config set store.enable on

    # kamaki config set store.pithos_extensions on

    # kamaki config set store.url "https://pithos.example.com/v1"

   # kamaki store create images

   # kamaki store upload --container images /tmp/debian_base.diskdump debian_base.diskdump

.. code-block:: console

 * Identity Management (Astakos)

 * Object Storage Service (Pithos+)

 * Compute Service (Cyclades)

and a single unified Web UI to manage them all.