EPN2020-RI
EUROPLANET2020 Research Infrastructure
H2020-INFRAIA-2014-2015
Grant agreement no: 654208
Document: WP6-task2-001-v01
EPN-TAP Installation for VESPA Data Provider Tutorial
Date: 2015/11/21
Start date of project: 01 September 2015
Duration: 48 Months
Responsible WP Leader: OBSPARIS / Stéphane Erard
Project co-funded by the European Union's Horizon 2020 research and innovation programme | ||
Dissemination level | ||
PU | Public | |
PP | Restricted to other programme participants (including the Commission Service) | |
RE | Restricted to a group specified by the consortium (including the Commission Services) | |
CO | Confidential, only for members of the consortium (excluding the Commission Services) |
Project Number | 654208 |
Project Title | EPN2020 - RI |
Project Duration | 48 months: 01 September 2015 – 30 August 2019 |
Document Number | WP11-task2-001-v01 |
Delivery date | 2015.11.21 |
Title of Document | |
Contributing Work package (s) | WP11 |
Dissemination level | PU |
Author (s) | Baptiste Cecconi, Pierre Le Sidaner, Stéphane Erard, Renaud Savalle, Markus Deimletner, Paul Sladen |
Abstract: |
Document history (to be deleted before submission to Commission) | ||||
Date | Version | Editor | Change | Status |
21 Nov 2015 | 0.1 | First issue (imported from internal MS-Word document) |
| |
| ||||
| ||||
|
Table of Contents
1. Introduction
This document presents the full installation procedure to set up data distribution server with an EPN-TAP service. We propose here to set up three service interfaces on the same physical server (and the same public IP address): a standard web server (Apache) to serve data files, a tool to have access statistics (using AWStats), and a DaCHS server to provide the Virtual Observatory (VO) interfaces (including a TAP service). The webserver front end will give access to data, usage statistics and a TAP interface. The various endpoints will be:
http://yourservername.domain.name/data/ Data repository
http://yourservername.domain.name/stat/ Access Statistic interface
http://vo.yourservername.domain.name/ DaCHS server interface
Section 2 describes the Debian distribution installation. Section 3 describes the installation of DaCHS and its configuration. Section 4 describes the installation and configuration of AWStat. Section 5 describes the configuration of the Apache server and of DNS.
Debian Stable (Jessie) Installation
DaCHS (Data Center Helper Suite) must be installed on a fresh Debian Stable distribution. The current installation image for this distribution is available here: https://www.debian.org/distrib/netinst#smallcd. In this example, we used the following ISO image: debian-8.2.0-amd64-netinst.iso
. The installation demonstration is done on a Virtual Box guest computer. This virtual machine is emulating an AMD 64bits processor based system. On boot the Debian installation ISO image is mounted and the system boots from it. On the first screen (Fig. 2.1), select "Install". The next screen are used to configure the system:
- Language used for the installation process, and for the system, once installed (Fig. 2.2): Select "
English
" - Location of the installation (Fig. 2.3): Select your country.
- Locale used for the installation (Fig. 2.4): Select "
en-US.UTF-8
" - Keyboard map: Select your keyboard map.
- Hostname for this computer (Fig. 2.5): Type the hostname (here "
dachs
") - Domain name for this computer (Fig. 2.6): Type the domain name (here "
obspm.fr
") - Root password (Fig. 2.7): Enter root password (pick a password, which is not easy to guess and don't forget it!)
- Main user (Fig. 2.8): Enter Full Name, user name and password.
- Disk configuration (Fig. 2.9): Select "
Use entire disk
" - Select Disk to partition (Fig. 2.10): Select the main disk (there should be only one).
- Partition Scheme (Fig. 2.11): Select "
All files in one partition
" - Confirmation of partition set up (Fig. 2.12): Select "
Finish partioning and write changes to disk
" - Configuration of package manager (Fig. 2.13): Select a mirror close to your place.
- Proxy configuration (Fig. 2.14): if needed enter the proxy information to go on internet.
- Configuring popularity-contest (Fig. 2.15): This is up to you (here "
No
" is selected) - Software selection (Fig. 2.16): Select a minimal set of package, namely "
web server
", "ssh server
", "standard system utilities
". Note that no desktop environment is selected here. As a server, only shell access is necessary. - Installation of GRUB boot loader, part 1 (Fig. 2.17): Select "
yes
" - Installation of GRUB boot loader, part 2 (Fig. 2.18): Select the newly created partition.
- Installation completion (Fig. 2.19): Select "
continue
" to finish installation and reboot. - Reboot (Fig. 2.20).
Fig. 2.1
Fig. 2.2
Fig. 2.3
Fig. 2.4
Fig. 2.5
Fig. 2.6
Fig. 2.7
Fig. 2.8
Fig. 2.9
Fig. 2.10
Fig. 2.11
Fig. 2.12
Fig. 2.13
Fig. 2.14
Fig. 2.15
Fig. 2.16
Fig. 2.17
Fig. 2.18
Fig. 2.19
Fig. 2.20
DaCHS Installation and Configuration
There are several ways to install DaCHS as presented by his author in [1]. For DaCHs installation you need an Debian Stable distribution, at this time Jessie (see Section 2).
Install DaCHS framework
On the server, log with the regular user created during installation (either on the computer itself, or remotely with ssh). The first thing is to install and set up the sudo command, which allows a user to issue commands with root rights. Use the su command to log as root, and type the root password.
user@yourservername:~$ su Password:
Install the sudo package:
root@yourservername:/home/user# apt-get install sudo Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: sudo 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 850 kB of archives. After this operation, 2,694 kB of additional disk space will be used. Get:1 http://ftp.fr.debian.org/debian/ jessie/main sudo amd64 1.8.10p3-1+deb8u2 [850 kB] Fetched 850 kB in 0s (1,110 kB/s) Selecting previously unselected package sudo. (Reading database ... 33745 files and directories currently installed.) Preparing to unpack .../sudo_1.8.10p3-1+deb8u2_amd64.deb ... Unpacking sudo (1.8.10p3-1+deb8u2) ... Processing triggers for systemd (215-17+deb8u2) ... Processing triggers for man-db (2.7.0.2-5) ... Setting up sudo (1.8.10p3-1+deb8u2) ... Processing triggers for systemd (215-17+deb8u2) ... Set up rights for your regular user to use the sudo command: root@yourservername:/home/user# adduser "user" sudo Adding user `user' to group `sudo' ... Adding user user to group sudo Done.
You have now the log out from your root shell and your regular user shell. Once you log back in with the regular user, you will be able to use the sudo command.
The repository source list must be updated to include DaCHS packages.Edit the file /etc/apt/sources.list with your preferred command line editor, for instance, you can use the pico editor (useful short cuts: ^O to save, ^X to quit):
user@yourservername:~$ sudo pico /etc/apt/sources.list
Add the following lines at the end of file (see Fig. 3.1):
# DaCHS repository deb http://vo.ari.uni-heidelberg.de/debian stable main deb-src http://vo.ari.uni-heidelberg.de/debian stable main
user@yourservername:~$ wget -qO - http://docs.g-vo.org/archive-key.asc | sudo apt-key add -
user@yourservername:~$ sudo apt-get update user@yourservername:~$ sudo apt-get upgrade
user@yourservername:~$ sudo apt-get install gavodachs-server
Basic DaCHS Configuration
We will use only a basic configuration for DaCHS, allowing Only the minimum for DaCHS to work, port number, definition. The full configuration including registry is optional in the next paragraph
because we use dachs in a non common way:
user@yourservername:~$ sudo cp /var/gavo/etc/trustedquery /var/gavo/etc/untrustedquery
Create a file /etc/gavo.rc
using your preferred editor (for instance pico):
user@yourservername:~$ sudo pico /etc/gavo.rc
Insert the following content in that file:
[general] rootDir: /var/gavo [web] bindAddress: serverPort: 8080 serverURL: http://vo.yourservername.domain.name preloadRDs: rr/q [ivoa] authority: yourdatacenter.domain.name
In this file, replace http://vo.yourservername.domain.name
by your actual server name and yourdatacenter.domain.name
by your own authority ID that you will create during the registration of your service (e.g., at Observatoire de Paris, our authority ID is vopdc.obspm.fr
). If this is not ready at this time, you may modify it later when your have registered your service with IVOA.
Finally restart DaCHS server:
sudo gavo serve restart
AWStat Installation and Configuration
Install AWStats:
sudo apt-get install awstats
Apache Configuration
Apache should already be installed during initial configuration, otherwise :
sudo apt-get install apache2
Install the mod_proxy_html module:
sudo apt-get install libapache2-mod-proxy-html
Enable ModProxy:
sudo a2enmod proxy proxy_http proxy_html
Edit the Apache default
sudo pico /etc/apache2/sites-enabled/000-default.conf
Add the following:
blah blah blah
Restart Apache2:
sudo service apache2 restart