wiki:SystemAdministration

Version 116 (modified by Willem Elbers, 8 years ago) (diff)

--

Hosts

Planning of application/service migration: Google Doc

Internally managed

Canonical FQDN
(click for maintenance procedure)
Aliases IPv4-address OS Docker (v)CPUs Memory
(GiB)
Storage
(GiB)
Hoster Responsible (ordered) Support Collectd
lvps92-51-161-129.dedicated.hosteurope.de? vlo.clarin.eu 92.51.161.129 CentOS 7.1.1503 n/a 8 32 500 HostEurope sysops@clarin.eu support@hosteurope.de 5.5
clarinvm.ics.muni.cz? catalog.clarin.eu
docker.clarin.eu
nexus.clarin.eu
office.clarin.eu
147.251.9.199 CentOS 7.1.1503 1.8.2 8 32 500 CESNET sysops@clarin.eu Boris Parak
Miroslav Ruda
5.5
idp1-clarin.esc.rzg.mpg.de? idp.clarin.eu
aai1.clarin.eu
130.183.206.196 Scientific Linux 7.1 1.6.2 2 4 20 MPCDF sysops@clarin.eu clarin-support@rzg.mpg.de 5.5
idp2-clarin.esc.rzg.mpg.de? aai2.clarin.eu 130.183.206.33 Scientific Linux 7.1 1.9.1 2 4 20 MPCDF sysops@clarin.eu clarin-support@rzg.mpg.de 5.5
dev-idp-clarin.esc.rzg.mpg.de? dev-idp.clarin.eu 130.183.206.39 Scientific Linux 7.1 1.9.1 2 4 20 MPCDF sysops@clarin.eu clarin-support@rzg.mpg.de 5.5
centres-clarin.esc.rzg.mpg.de? centres.clarin.eu 130.183.206.32 SLES 11.3 n/a 1 1 17 MPCDF sysops@clarin.eu clarin-support@rzg.mpg.de no
centres2-clarin.esc.rzg.mpg.de? centres{-staging,}.clarin.eu 130.183.206.40 Scientific Linux 7.1 1.7.1 1 1 2 MPCDF sysops@clarin.eu clarin-support@rzg.mpg.de no
beta-vlo-clarin.esc.rzg.mpg.de? beta-vlo.clarin.eu 130.183.206.198 Scientific Linux 7.1 1.7.1 8 16 1000 MPCDF sysops@clarin.eu clarin-support@rzg.mpg.de 5.5
catalog-clarin.esc.rzg.mpg.de? alpha-vlo.clarin.eu 130.183.206.35 SLES 11.3 n/a 4 8 125 MPCDF Twan Goosen clarin-support@rzg.mpg.de 5.4.2
ems04.mpi.nl? infra.clarin.eu
trac.clarin.eu
stats.clarin.eu
svn.clarin.eu
user.clarin.eu
192.87.79.165 Ubuntu 12.04.5 LTS n/a 1 4 10 MPI-PL sysops@clarin.eu helpdesk@mpi.nl 4.10
dev-clarin-eu.hum.uu.nl? www-dev.clarin.eu 131.211.143.192 Debian 8 1.5-1 1 4 28 UU Bas van der Veen
Sander Maijers
Hans Nijbacker no
vz07-clarin-eu.im.hum.uu.nl? www.clarin.eu?
tst.clarin.eu?
131.211.143.186 Debian 6 n/a 8 8 73 UU Bas van der Veen
Sander Maijers
Hans Nijbacker no
149-210-236-86.colo.transip.net? 149-210-236-86.colo.transip.net
proxy.clarin.eu
discovery.clarin.eu
149.210.236.86 CentOS 7.1.1503 1.8.2 2 4 150 TransIP sysops@clarin.eu ? 5.5

Externally managed, with central services

Canonical FQDN
(click for maintenance procedure)
Aliases IPv4-address OS Docker (v)CPUs Memory
(GiB)
Storage
(GiB)
Hoster Responsible (ordered)
vz07-clarin-list.im.hum.uu.nl? lists.clarin.eu 131.211.143.192 Debian 6 n/a ? ? ? UU ictenmedia@uu.nl
clarin.fz-juelich.de? clarin.fz-juelich.de n/a FZJCLARIN-support@fz-juelich.de
clarin.ids-mannheim.de? clarin.ids-mannheim.de 193.196.8.17 CentOS 5.11 n/a 4 16 64 IDSOliver Schonefeld
weblicht.sfs.uni-tuebingen.de? weblicht.sfs.uni-tuebingen.de 130.183.206.38 Scientific Linux 6.7 n/a 4 64 500 UTUemanuel.dima@uni-tuebingen.de

Decommissioned

Canonical FQDN Aliases IPv4-address OS Docker Hoster Responsible (ordered)
idp-clarin.esc.rzg.mpg.de? - 130.183.206.37 SLES 11.3 n/a MPCDF sysops@clarin.eu
stoor146.meta.zcu.cz?* - 147.228.242.146 CentOS Linux release 7.1.1503 (Core) 1.5.0 CESNET sysops@clarin.eu
catalog.clarin.eu? catalog.clarin.eu 192.87.79.171 SUSE Linux Enterprise Server 11.2 n/a MPI sysops@clarin.eu

DNS entries and TLS certificates

Hosted by Networking4All

admins: Dieter Van Uytvanck, Sander Maijers, Willem Elbers

Getting access

Shell access to the CLARIN hosts is only possible via key-based SSH.

Contact sysops@clarin.eu to request access to a host. Make sure to include your public SSH key.

Instructions and guidelines on how to create your OpenSSH key pair can be found here?.

Default VM setup

These instructions describe how we install/provision/configure each host by default.

SLES 11

We are in the process of migration our SLES 11 machines to CentOS/Scientific Linux. We collect some notes? on administering SLES hosts.

Docker

If possible we aim to dockerize the applications in our environment. The main advantage of this approach is that we can provide identical environments across servers, including development, staging and production.

Read more about the usage of Docker here?.