Gbif Spain Production environment
This document tries to document the IT infrastructure of the Spanish Atlas accessible at datos.gbif.es.
Our main infrastructure is hosted in the CSIC-IFCA datacenter.
| URL | Component |
|---|---|
| datos.gbif.es | main page |
| colecciones.gbif.es | collectory |
| registros.gbif.es | biocache-hub |
| registros-ws.gbif.es | biocache-service |
| jenkins.gbif.es | biocache-cli, cassandra, jenkins |
| index.gbif.es | solr |
| geo-ws.gbif.es | geoserver, layer-service |
| regiones.gbif.es | regions |
| especies.gbif.es | species lists (wip) |
| logger.gbif.es | logger |
| imágenes.gbif.es | images |
| demo.gbif.es | demo site |
Our custom branding is in this github repo.
We do the backups using backuppc software. It's not secure to backup database directories where the databases are running. To avoid this, be use ninjabackup to backup our mysql and postgres databases periodically. Later backupppc backup the dumps stored by ninjabackup in /var/backups.
Some storage stats:
All our services are monitorized using icinga externally.
We also use mmonit internally to monitor that the basic services (ssh, apache2, tomcat, mysql, etc) are running correctly and restart then if not.
We use ELK (Elasticsearch, Logstash/Filebeat & Kibana) for logs agregation, indexing, and analytics. We don't store the logs for more than a week. This is very useful for us to do bugs and error hunting.
We also use netdata to analyze metrics of resources usage and other data (CPU, RAM, disks, network, monit status, etc). Useful for tunning resources, diagnostic, etc.
We collect js errors in browser clients using sentry. This can be useful also for collect java exceptions & errors but ALA software should be patched for that.
Our servers are updated automatically via the debian package unattended-upgrades.
All this software is managed via ansible using an internal ansible extras repo (TODO: make this repo more generic and share it with other portals).
We also maintain a demo test site in https://demo.gbif.es.