Synnefo

are "node1.example.com" and "node2.example.com" and their public IPs are "203.0.113.1" and

"203.0.113.2" respectively. It is important that the two machines are under the same domain name.

In case you choose to follow a private installation you will need to

more information on how to do so.

General Prerequisites

Certificate Creation

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

trusted, the keys provided to Apache below should be signed with a certificate.

This certificate should be added to all nodes. In case you don't have signed keys you can create a self-signed certificate

and sign your keys with this. To do so on node1 run:

		# ./build-key-server node1.example.com

``/etc/openvpn/easy-rsa/2.0/keys`` directory. Copy these in ``/etc/ssl/certs/``

and ``/etc/ssl/private/`` respectively and use them in the apache2

configuration file below instead of the defaults.

Pithos data directory setup

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

called ``/srv/pithos`` visible by both nodes. We create and setup the ``data``

directory inside it:

Now edit ``/etc/exports`` and add the following line:

.. code-block:: console

   /srv/pithos/ 203.0.113.2(rw,no_root_squash,sync,subtree_check)

Once done, run:

There is a `"bug" in libevent 2.0.5 <http://sourceforge.net/p/levent/bugs/193/>`_

, where if you have multiple nameservers in your ``/etc/resolv.conf``, libevent

will round-robin against them. To avoid this, you must use a single nameserver

.. code-block:: console

   nameserver 203.0.113.1

Because of the aforementioned bug, you can't specify more than one DNS servers

``#resolv-file=`` to:

.. code-block:: console

   nameserver 8.8.8.8

and the ``interface`` you would like dnsmasq to listen to.

Finally, restart dnsmasq:

to inform the node about the new DNS server.

``/etc/resolv.conf``.

We are now ready with all general prerequisites for node2. Now that we have

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

To install Astakos, grab the package from our repository (make sure  you made

described previously), by running:

.. code-block:: console

Email delivery configuration

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

notify administrators with a notice that a new account has just been verified.

More specifically Astakos sends emails in the following cases

Kamaki

======

specific to Synnefo.

Kamaki Installation and Configuration

   # apt-get install kamaki

 `https://node1.example.com/astakos/ui/`

page, click on the orange ``Download your .kamakirc`` button and save the file

as ``.kamakirc`` in your home directory.

`Ganeti <http://code.google.com/p/ganeti/>`_ handles the low level VM management

for Cyclades, so Cyclades requires a working Ganeti installation at the backend.

the gory details. A successful Ganeti installation concludes with a working

:ref:`GANETI-MASTER <GANETI_NODES>` and a number of :ref:`GANETI-NODEs

<GANETI_NODES>`.

Ganeti requires FQDN. To properly configure your nodes please

see `this <http://docs.ganeti.org/ganeti/2.6/html/install.html#hostname-issues>`_.

explained above.

see `this <http://www.tldp.org/HOWTO/LVM-HOWTO/createvgs.html>`_.

Moreover, node1 and node2 must have the same dsa, rsa keys and authorised_keys

generate said keys, see `this <https://wiki.debian.org/SSH#Using_shared_keys>`_.

In the following sections, we assume that the public interface of all nodes is

create vlans, please see

`this <https://wiki.debian.org/NetworkConfiguration#Howto_use_vlan_.28dot1q.2C_802.1q.2C_trunk.29_.28Etch.2C_Lenny.29>`_.

respectively), as described `here <https://wiki.debian.org/BridgeNetworkConnections>`_.

Ganeti Installation and Initialization

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

Ganeti nodes:

.. code-block:: console

   # apt-get install qemu-kvm

the official Ganeti 2.10), we recommend using our Ganeti package version:

``2.8.2+snapshot1+b64v1+kvmopts1+extfix1+hotplug5+lockfix3+ippoolfix+rapifix+netxen-1~wheezy``

Let's briefly explain each patch:

    * hotplug: hotplug devices (NICs and Disks) (ganeti 2.10).

      base64, instead of 0/1.

    * ippoolfix: Ability to give an externally reserved IP to an instance (e.g.

      gateway IP)  (ganeti 2.10).

      capabilities.

    * extfix: Includes:

      * adds better arbitrary params support (modification, deletion).

      * cache, heads, cyls arbitrary params reach kvm command.

      arguments. (ganeti 2.9).

      instances. (ganeti 2.9).

    * lockfix2: Fixes for 2 locking issues:

        error (Patch waiting in ganeti-devel list).

        'XXXXXX' not found in set 'instance' (it may have been removed)].

    * snapshot: Add trivial 'snapshot' functionality that is unused by Synnefo

   # apt-get install snf-ganeti ganeti-htools ganeti-haskell

permanent you have to do the following :

.. code-block:: console

                    --default-iallocator hail \

                    --hypervisor-parameters kvm:kernel_path=,vnc_bind_address=0.0.0.0 \

                    --master-netdev eth0 ganeti.node1.example.com

    root@node1:~ # gnt-node add --no-ssh-key-check --master-capable=yes \

                    --vm-capable=yes node2.example.com

    root@node1:~ # gnt-cluster modify --disk-parameters=drbd:metavg=ganeti

To upload the file using kamaki, run:

.. code-block:: console

   # kamaki file upload debian_base-6.0-x86_64.diskdump pithos

Once the Image is uploaded successfully, download the Image's metadata file

Now, it is time to test our installation so far. So, we have Astakos and

Pithos installed, we have a working Ganeti installation, the snf-image

definition installed on all VM-capable nodes, a Debian Squeeze Image on

for this image.

To spawn a VM from a Pithos file, we need to know:

    2) The size of the file

If you uploaded the file with kamaki as described above, run:

.. code-block:: console

container and filename you used, when uploading the file.

The hashmap is the field ``x-object-hash``, while the size of the file is the

   should have the format ``pithosmap://<HashMap>/<size>``:

               * ``HashMap``: the map of the file

                 ``ls -l filename``

 * ``img_properties``: taken from the metadata file. Used only the two mandatory

needs of the system administrator.

In this section, we'll describe the simplest scenario, which will provide

the VMs.

.. _snf-network:

nfdhcpd

~~~~~~~

snf-network and information provided by Ganeti.

.. code-block:: console

   # /etc/init.d/nfdhcpd restart

traffic coming from the corresponding interfaces. To accomplish that run:

.. code-block:: console

In the following section, we'll guide you through a very basic network setup.

This assumes the following:

    * Node1 has access to the public network via eth0.

    * Node1 will become a NAT server for the VMs.

    * All nodes have ``br1/br2`` dedicated for the VMs' public/private traffic.

To setup the NAT server on node1, run:

.. code-block:: console

   # ip addr add 10.0.0.1/24 dev br1

   # iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

   # echo 1 > /proc/sys/net/ipv4/ip_forward

and append it to your ``/etc/rc.local``.

Testing the Public Networks

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

Finally, run on the GANETI-MASTER (node1):

.. code-block:: console

   # gnt-instance add -o snf-image+default --os-parameters \

                      img_passwd=my_vm_example_passw0rd,img_format=diskdump,img_id=debian_base-6.0-x86_64,img_properties='{"OSFAMILY":"linux"\,"ROOT_PARTITION":"1"}' \

                      -t plain --disk 0:size=2G --no-name-check --no-ip-check \

    * snf-network bridges the tap interface to ``br1`` and updates nfdhcpd state.

    * nfdhcpd serves 10.0.0.2 IP to the interface of ``testvm2``.

(connect to the VM using VNC as before).

Make sure everything works as expected, before proceeding with the Private

Private Networks Setup

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

``ebtables`` rules.

Testing the Private Networks

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

means that the instances will have a second NIC connected to the ``br1``.

.. code-block:: console

Cyclades supports different Public Networks on different Ganeti backends.

After connecting Cyclades with our Ganeti cluster, we need to setup a Public

Network for this Ganeti backend (`id = 1`). The basic setup is to bridge every

.. code-block:: console

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

For the purposes of the following example, we assume that the user has uploaded

he should have the appropriate `metadata file <http://cdn.synnefo.org/debian_base-6.0-x86_64.diskdump.meta>`_.

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

   $ kamaki image register "Debian Base" pithos:debian_base-6.0-x86_64 \

     --metafile debian_base-6.0-x86_64.diskdump.meta --public

Spawn a VM from the Cyclades Web UI

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

SSH or RDP (for windows machines).

Congratulations. You have successfully installed the whole Synnefo stack and