Synnefo

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

"4.3.2.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

set up a private dns server, using dnsmasq for example. See node1 below for more.

		* apache (http server)

		* public certificate

		* gunicorn (WSGI http server)

		* postgresql (database)

		* rabbitmq (message queue)

		* ntp (NTP daemon)

		* gevent

		* dns server

Certificate Creation

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

Node1 will host Cyclades. Cyclades should communicate with the other snf tools over a trusted connection.

In order for the connection to be 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

.. code-block:: console

		# aptitude install openvpn

		# mkdir /etc/openvpn/easy-rsa

		# cp -ai /usr/share/doc/openvpn/examples/easy-rsa/2.0/ /etc/openvpn/easy-rsa

		# cd /etc/openvpn/easy-rsa/2.0

		# vim vars

In vars you can set your own parameters such as KEY_COUNTRY

.. code-block:: console

	# . ./vars

	# ./clean-all

Now you can create the certificate

.. code-block:: console 

		# ./build-ca

The previous will create a ``ca.crt`` file. Copy this file under

``/usr/local/share/ca-certificates/`` directory and run :

.. code-block:: console

		# update-ca-certificates

to update the records. You will have to do the following on node2 as well.

Now you can create the keys and sign them with the certificate

.. code-block:: console

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

This will create a .pem and a .key file in your current folder. Copy these in

``/etc/ssl/certs/`` and ``/etc/ssl/private/`` respectively and 

use them in the apache2 configuration file below instead of the defaults.

DNS server setup

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

If your machines are not under the same domain nameyou have to set up a dns server.

In order to set up a dns server using dnsmasq do the following

.. code-block:: console

				# apt-get install dnsmasq

Then edit you ``/etc/hosts/`` as follows

.. code-block:: console

		4.3.2.1     node1.example.com

		4.3.2.2     node2.example.com

Finally edit the ``/etc/dnsmasq.conf`` file and specify the ``listen-address`` and

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

Also add the following in your ``/etc/resolv.conf`` file 

.. code-block:: console

		nameserver 4.3.2.1

    * certificates

    * dns setup

Acquire certificate

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

Copy the certificate you created before on node1 (`ca.crt`) under the directory

``/usr/local/share/ca-certificate``

and run:

.. code-block:: console

		# update-ca-certificates

to update the records.

DNS Setup

~~~~~~~~~

Add the following line in ``/etc/resolv.conf`` file

.. code-block:: console

		nameserver 4.3.2.1

to inform the node about the new dns server.

deliver messages, is shown below. Alter the following example to meet your 

smtp server characteristics. Notice that the smtp server is needed for a proper

installation

    # /etc/synnefo/00-snf-common-admins.conf

Notice that in this installation astakos and cyclades are in node1 and pithos is in node2

not familiar with Ganeti. 

Unfortunately, the current stable version of the stock Ganeti (v2.6.2) doesn't

GRNET provided packages until stable 2.7 is out. These packages will also install

the proper version of Ganeti. To do so:

Ganeti will make use of drbd. To enable this and make the configuration pemanent 

you have to do the following :

.. code-block:: console

		# rmmod -f drbd && modprobe drbd minor_count=255 usermode_helper=/bin/true	

		# echo 'drbd minor_count=255 usermode_helper=/bin/true' >> /etc/modules

say it's ``ganeti.node1.example.com``). This IP is needed to communicate with 

the Ganeti cluster. Make sure node1 and node2 have same dsa,rsa keys and authorised_keys 

for password-less root ssh between each other. If not then skip passing --no-ssh-init but be 

aware that it will replace /root/.ssh/* related files and you might lose access to master node. 

Also, Ganeti will need a volume to host your VMs' disks. So, make sure there is an lvm volume 

group named ``ganeti``. Finally, setup a bridge interface on the host machines (e.g: br0). This  

will be needed for the network configuration afterwards.

.. warning:: 

		snf-image uses ``curl`` for handling URLs. This means that it will

		not  work out of the box if you try to use URLs served by servers which do

		not have a valid certificate. In case you haven't followed the guide's

		directions about the certificates,in order to circumvent this you should edit the file

		``/etc/default/snf-image``. Change ``#CURL="curl"`` to ``CURL="curl -k"`` on every node.

               * ``UUID``: the username found in Cyclades Web UI under API access

If the above returns successfully, connect to the new VM through VNC as before and run:

   CLOUDBAR_MENU_URL = 'https://node1.example.com/astakos/ui/get_menu'

                           pithos://u53r-un1qu3-1d/images/debian_base-6.0-11-x86_64.diskdump \

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