Lab
Overview
Section titled “Overview”lab.core.lef (instance ds-lab) is the bare metal lab host inside the EVEO environment. It runs several lab/workbench environments under dedicated service accounts.
Purpose
Section titled “Purpose”- Provide compute and storage for lab environments that don’t fit well on smaller VMs.
- Host environments like Concepts and the trainee platform.
Inventory
Section titled “Inventory”| Item | Value |
|---|---|
| Provider | EVEO bare metal |
| EVEO contract label | sd-leftec-2 (SP1) |
| Data center | SP1 (Cotia) |
| Instance | ds-lab |
| CPU | 2× Intel Xeon E5-2670 v2 |
| OS | RHEL 9 |
| vCPU | 32 |
| RAM | 96 GB |
| Disk | 2×1.92 TB (RAID1) |
| LAN IP | 192.168.20.11 |
| Public uplink | 1 Gbps (public), unlimited monthly traffic |
| Public IPv4 | 1 address (value not documented here) |
Entry points
Section titled “Entry points”- SSH (VPN/LAN required):
lab.core.lef
Host entries (login profiles)
Section titled “Host entries (login profiles)”These are common SSH login profiles for the same host using different service accounts.
| Host entry | User | Purpose | Related |
|---|---|---|---|
ds-lab | root | OS maintenance | — |
ds-lab-concepts | concepts | Concepts / POCs | Concepts |
ds-lab-specials | specials | Specials & lab work | — |
ds-lab-trainees | trainees | Trainee platform | Trainee environment |
Hosted services
Section titled “Hosted services”- Concepts (Thinkwise environment)
- Trainee environment (Thinkwise environment)
- Specials / lab experiments (shared)
Dependencies
Section titled “Dependencies”- Database access is typically routed via HAProxy (
*.db.lef) (see TCP proxy). - Public access (where applicable) goes through
web.core.lef(see Services).
Operational notes
Section titled “Operational notes”- This host is shared across environments; coordinate disruptive changes via Infra.
- When troubleshooting an environment, capture:
- which service account it runs under
- which DB endpoint it uses (e.g.,
concepts.db.lef) - which public hostname (if any) fronts it
Backup & recovery
Section titled “Backup & recovery”- This host does not have automated backups; restores are manual and project-specific.
- SQL Server backups for instances running here are manual to S3 (MinIO): see SQL Server → S3 backup & restore.
Known risks / failure modes
Section titled “Known risks / failure modes”- Resource contention between environments (CPU/RAM/disk IO).
- If internal DNS or VPN is down, many services become unreachable even if they are healthy.