This is the Synnefo Quick Installation guide.
It describes how to install the whole Synnefo stack on one (1) physical node, in less than 10 minutes. The installation uses the snf-deploy deployment tool and installs on a physical node that runs Debian Wheezy. After successful installation, you will have the following services running:
- Identity Management (Astakos)
- Object Storage Service (Pithos)
- Compute Service (Cyclades)
- Image Service (part of Cyclades)
- Network Service (part of Cyclades)
and a single unified Web UI to manage them all.
To install Synnefo the only thing you need is a Debian Wheezy Base System that has access to the public Internet.
First of all we need to install the snf-deploy tool. To do so please add the following line in your /etc/apt/sources.list file:
deb http://apt.dev.grnet.gr wheezy/
# curl https://dev.grnet.gr/files/apt-grnetdev.pub | apt-key add - # apt-get update # apt-get install snf-deploy
Now that you have snf-deploy successfully installed on your system, you can continue with configuring and installing Synnefo. Configuration files for snf-deploy can be found in /etc/snf-deploy, the defaults should work out of the box for most setups. If for some reason you encounter any problems, you should check there for network conflicts, etc.
To install the whole Synnefo stack run:
# snf-deploy synnefo --autoconf
This might take a while depending on the physical host you are running on, since it will download everything that is necessary, install and configure the whole stack.
If the following ends without errors, you have successfully installed Synnefo.
NOTE: All the passwords and secrets used during installation are hardcoded in /etc/snf-deploy/synnefo.conf. You can change them before starting the installation process. If you want snf-deploy create random passwords use the --pass-gen option. The generated passwords will be kept in the /var/lib/snf-deploy/snf_deploy_status file.
If you want to access the Synnefo installation from a remote machine:
Set your nameservers accordingly by adding the following line as your first nameserver in /etc/resolv.conf:
The <IP> is the public IP of the machine that you deployed Synnefo on, and want to access. Note that /etc/resolv.conf can be overwritten by other programs (Network Manager, dhclient) and you may therefore lose this line. Depending on your system, you may need to disable writes to /etc/resolv.conf or prepend the nameservers in the /etc/dhclient.conf.
Add the IP of your Synnefo installation in your /etc/hosts file:
<IP> synnefo.live <IP> accounts.synnefo.live <IP> compute.synnefo.live <IP> pithos.synnefo.live
If you’re using Windows the same settings can be applied on C:\WINDOWS\SYSTEM32\DRIVERS\ETC\HOSTS.
$ ssh -D localhost:9009 user@host
Now, you can either instruct your browser to tunnel all the traffic through the SOCKS proxy or even better install a plugin like Foxy Proxy to fine tune when to use the proxy or not.
In order to use the proxy globally in Firefox, go to Edit->Preferences->Advanced->Network->Settings and set SOCKS host to localhost and Port to 9009. Firefox by default doesn’t use the SOCKS proxy for domain name resolving. To enable this, type about:config in the URL bar and change network.proxy.socks_remote_dns to true.
For better control on which sites you view over the proxy, download FoxyProxy and set a URL_Pattern to whitelist the synnefo.live domain. To do this use the URL_Pattern *synnefo.live* and set FoxyProxy to run in the Use proxies based on their pre-defined patterns and priorities mode.
FoxyProxy is also available for Chrome through the Chrome Web Store, so a similar approach will work in Chrome also.
Internet Explorer doesn’t support SOCKS5 proxies.
Then open a browser and point it to:
If you want to access the installation from the same machine it runs on, you must connect graphically to the machine first. A simple way is to use SSH with X-forwarding:
$ ssh <user>@<hostname> -YC
where <user> is your username and <hostname> is the IP/hostname of your machine. Then, run iceweasel or chromium and in the address bar write:
The default <domain> is set to synnefo.live. A local BIND is already set up by snf-deploy to serve all FQDNs.
To be able to view all web pages make sure you have accepted all certificates for domains:
You should be able to: