CSEP Gitlab
The CSEP2 software development and test environment uses the Gitlab integration software.
Contents
CSEP Computers
- CSEP_Computers
- CSEP_Hardware_Inventory
- Github Docs
- SCEC CSEP Storage Summaries:
- SCEC Storage Summary: Usage Report
- Sorted by Username: Sorted Usage Report
Gitlab Installation
- Gitlab Software Options
- GitLab and Runner Installation Information
- GitLab Installation using Docker
- GitLab Runner Installation with Docker
CSEP2 System Overview Diagram
"Gitlab Server and Runner"
Gitlab AWS Commercial Configuration
Data Usage Estimates
Estimates for data usages are based on combining the two use cases for the GitLab repository (1) Code storage and (2) Storage of Large data files and experiment results. These estimates are based on data from the current CSEP project, such as current project members, current storage in current and old repositories, and rough estimates of expected data usage for past and future experiments.
Project Info:
CSEP Project Members: 20
CSEP1 Repo Size (in Gb): 1.2
Storage per experiment (in Tb): 1
(1) Code Storage
Total data stored: 25 Gb (High-end estimate including models, codes and benchmark data sets)
Data transferred: [50-500] Gb
(2) Data/Catalog Storage
Total Storage: 250 Gb
Data transferred: [100 Gb - 1 Tb]
(3) Experiment Results
Total Storage: 4 Tb
Data transferred: [100 Gb - 1 Tb]
Overall Estimates:
Total stored: ~4.5 Tb
Transferred: [250 Gb - 2.5 Tb]
Gitlab Basic System Requirements
- Recent Linux Distro (Ubuntu,Centos...)
- Generate SSH keys
- Configure SMTP Server
- 8GB RAM is the recommended minimum memory size for all installations and supports up to 100 users. 16GB RAM supports up to 500 users
- Databases: PostgreSQL
- Redis/Sidekiq: stores all user sessions and background task queue processes the background jobs with a multithreaded process
- Prometheus and it’s exporters
- Avoid installing GitLab Runner on the same machine where Gitlab is installed.
- GitLab needs JavaScript enabled in browsers to support features such as Issue Boards.
