Home

System Requirements

⚠ This page is a WIP and not finished yet.

Docker Host System Requirements

We start with an Ubuntu system where Docker is already installed and configured. We use Docker from Docker's official DEB repository and not the Docker packages that Ubuntu ships.

We use nginx as webserver to pass TCP port 3000 of ReSeeD's web container (=HTTP) to the outside world as HTTPS on port 443. For this, we use nginx from nginx's official DEB repository and not the nginx packages that Ubuntu ships.

Note that these deb repos (more precise: the strings from the Origin: and Suite: lines in the respective repo's *_InRelease file in /var/lib/apt/lists/) must also be added to /etc/apt/apt.conf.d/50unattended-upgrades to ensure that they are also used for unattended updates.

Nginx from the official nginx repo is configured slightly different from Ubuntu's nginx package. For the time being, copy the config from another ReSeeD instance and adapt the configuration to the ReSeeD instance that you are trying to set up.

On ReSeeD instances that do not require Shibboleth login, we use Let's Encrypt certificates. For instances that require Shibboleth, we use TLS certificates from RUB's partner CA (which is GEANT/Sectigo at the time of writing).

If the ReSeeD instance is supposed to send emails, we setup postfix from Ubuntu's repositories. Note that postfix requires a special RUB-specific setup to work properly. When in doubt, copy and adapt the configuration from another ReSeeD instance.

Hardware Requirements for ReSeeD

These are some notes, based on Antleaf and Cottage Labs' experience with previous projects, and not a specification. As the parameters of the RUB project become clearer, we can build on this to provide a specification.

Memory requirements for components

• ClamAV: 8GB (we have found that ClamAV requires a lot of memory and will otherwise impact the performance of the system)
• fcrepo: 4 GB [reference]
• solr: Default : 512 MB. May need up to 20 GB, depending on use case [reference]
• web, workers: ~2 GB? [reference]
• Samvera hyrax storage volume sizes: [reference]

Storage requirements

Storage requirements are difficult to estimate until we have a sense of the size of the research data. The following figures are offered to provide a sense of the comparative storage requirements based on ~34Gb of research data (from a previous project).

The intended use of a remote S3 data store does change this however!

Hyrax

# uploaded files, cache and derivative files
root@40eade334175:/data# du -hs /shared/
34G	/shared/

Solr

solr@414176b14c19:/opt/solr$ du -hs /opt/solr/server/solr/mycores/hyrax_production/
1.1G	/opt/solr/server/solr/mycores/hyrax_production/

Fedora

root@a5058779c8e1:/usr/local/tomcat# du -hs /data/
44G	/data/

PostgreSQL (Fedora)

bash-5.1# du -hs /var/lib/postgresql/data/
1.7G	/var/lib/postgresql/data

PostgreSQL (Hyrax)

bash-5.1# du -hs /var/lib/postgresql/data/
2.6G	/var/lib/postgresql/data/

Redis

root@1ff34eb338ba:/data# du -hs /data/                              
27M	/data/