Tokio Marine
Overview
Section titled “Overview”tokio.core.lef (instance np-tokio) hosts Thinkwise Tokio environments in the EVEO private cloud.
This VM runs on np-leftec-hipervisorA-1.
Purpose
Section titled “Purpose”- Run Tokio/TokioCred Thinkwise environments.
Inventory
Section titled “Inventory”| Item | Value |
|---|---|
| Provider | EVEO private cloud (VM) |
| Instance | np-tokio |
| VMID (Proxmox) | 106 |
| OS | AlmaLinux 9 |
| vCPU | 8 |
| RAM | 16 GB |
| Disk | 40 GB |
| LAN IP | 192.168.20.25 |
Entry points
Section titled “Entry points”- SSH (VPN/LAN required):
tokio.core.lef - Environment hostnames (examples): see Tokio Marine
Host entries (login profiles)
Section titled “Host entries (login profiles)”| Host entry | User | Purpose | Related |
|---|---|---|---|
np-tw-tokio | root | Host maintenance | — |
np-tw-tokio-marine | marine | Client environment (Tokio Marine) | Tokio (dev) |
np-tw-tokio-tokiocred | tokiocred | Client environment (TokioCred) | TokioCred |
Hosted services
Section titled “Hosted services”- Thinkwise Tokio environments
- Database backends for:
tokio.db.lef
- EVEO DBaaS is also used for at least one production SQL endpoint (see
tokio-prod.db.lefin TCP proxy).
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).
Backup & recovery
Section titled “Backup & recovery”- This VM is backed up daily via EVEO (see
np-leftec-hipervisorA-1).