Alma
Overview
Section titled “Overview”alma.core.lef (instance np-alma) hosts Thinkwise client environments in the EVEO private cloud.
This VM runs on np-leftec-hipervisorA-1.
Purpose
Section titled “Purpose”- Run Thinkwise environments and services for client workloads.
Inventory
Section titled “Inventory”| Item | Value |
|---|---|
| Provider | EVEO private cloud (VM) |
| Instance | np-alma |
| VMID (Proxmox) | 105 |
| OS | AlmaLinux 9 |
| vCPU | 16 |
| RAM | 32 GB |
| Disk | 160 GB |
| LAN IP | 192.168.20.21 |
Entry points
Section titled “Entry points”- SSH (VPN/LAN required):
alma.core.lef - Environment hostnames (examples): see Clients
- DB endpoints (examples): see TCP proxy
Host entries (login profiles)
Section titled “Host entries (login profiles)”| Host entry | User | Purpose | Related |
|---|---|---|---|
np-alma | root | Host maintenance | — |
np-alma-development | development | Development environment | Solutions (dev) |
np-alma-sapore | sapore | Client environment (Sapore) | Sapore |
np-alma-unimed | unimed | Client environment (Unimed) | Unimed |
Hosted services
Section titled “Hosted services”- Client environments (Sapore, Unimed, Solutions)
- Database backends for:
solutions.db.lefunimed.db.lefsapore.db.leftools.db.lef
Dependencies
Section titled “Dependencies”- DB endpoints are exposed via HAProxy on
proxy.core.lef(see TCP proxy). - Public ingress (where applicable) is via
web.core.lef(see web.core.lef).
Operational notes
Section titled “Operational notes”- Treat environments as client-scoped; coordinate changes with the owning team.
Backup & recovery
Section titled “Backup & recovery”- This VM is backed up daily via EVEO (see
np-leftec-hipervisorA-1).
Known risks / failure modes
Section titled “Known risks / failure modes”- DB endpoint health depends on both HAProxy and the backend instance.
- Split-horizon DNS mistakes can break access from inside VPN/LAN.