Version 39 (modified by 9 years ago) (diff) | ,
---|
Servers
Canonical hostname | Aliases | IP | Distro | Docker | Hoster | Responsible |
---|---|---|---|---|---|---|
lvps92-51-161-129.dedicated.hosteurope.de?* | vlo.clarin.eu | 92.51.161.129 | CentOS Linux release 7.1.1503 (Core) | n/a | HostEurope | sysops@clarin.eu |
stoor146.meta.zcu.cz?* | nexus.clarin.eu | 147.228.242.146 | CentOS Linux release 7.1.1503 (Core) | 1.5.0 | CESNET | sysops@clarin.eu |
registry.clarin.eu | ||||||
clarinvm.ics.muni.cz?* | nexus.clarin.eu | 147.251.9.199 | CentOS Linux release 7.1.1503 (Core) | 1.6.2 | CESNET | sysops@clarin.eu |
registry.clarin.eu | ||||||
idp-clarin.esc.rzg.mpg.de | idp.clarin.eu | 130.183.206.37 | SUSE Linux Enterprise Server 11.3 | n/a | RZG | sysops@clarin.eu |
discovery.clarin.eu | ||||||
dev-idp-clarin.esc.rzg.mpg.de? | dev-idp.clarin.eu | 130.183.206.39 | Scientific Linux release 7.1 (Nitrogen) | 1.6.0 | RZG | sysops@clarin.eu |
centres.esc.rzg.mpg.de? | centres.clarin.eu | 130.183.206.32 | ? | n/a | RZG | sysops@clarin.eu |
centres-staging.clarin.eu | ||||||
catalog.clarin.eu? | catalog.clarin.eu | 192.87.79.171 | SUSE Linux Enterprise Server 11.2 | n/a | MPI | sysops@clarin.eu |
ems04.mpi.nl? | svn.clarin.eu | 192.87.79.165 | Ubuntu 12.04.5 LTS (precise) | n/a | MPI | sysops@clarin.eu |
clarin.mpi.nl | ||||||
trac.clarin.eu | ||||||
infra.clarin.eu | ||||||
stats.clarin.eu | ||||||
lists.clarin.eu | lists.clarin.eu | 131.211.143.192 | Debian 6 | n/a | UU | Hans Nijbacker ictenmedia@uu.nl |
www.clarin.eu? | www.clarin.eu | 131.211.143.186 | Debian 6 | n/a | UU | Jurriaan Roelofs (info@jurr.me), Hans Nijbacker (ictenmedia@uu.nl) |
Planning of application / service migration: Google Doc
DNS entries + certificates
hosted at https://www.networking4all.com/
admins: Dieter Van Uytvanck <Dieter Van Uytvanck>, Sander Maijers <Sander Maijers>, Willem Elbers <Willem Elbers>
Getting access
Access to the CLARIN servers marked with a * is only possible via a public ssh key.
Contact sysops@clarin.eu to request access to a server. Make sure to include your public ssh key.
Instructions and guidelines on how to create your ssh key can be found here?.