48 lines
1.2 KiB
Markdown
48 lines
1.2 KiB
Markdown
# sf-ana-container
|
|
|
|
SureFire-client container workload running on `sfsrv-ana` (SureFire's
|
|
Proxmox at 10.250.250.115). **PFI-managed** under the hosting
|
|
agreement.
|
|
|
|
## Client context
|
|
|
|
- **Client:** SureFire
|
|
- **PFI role:** full-service managed host
|
|
|
|
## Network
|
|
|
|
- **LAN IP:** 10.250.150.100
|
|
- **FQDN:** not in DNS yet — add to workstation `/etc/hosts`:
|
|
```
|
|
10.250.150.100 sf-ana-container
|
|
```
|
|
- **SSH:** `vhoang@10.250.150.100` (confirmed)
|
|
|
|
## Infrastructure
|
|
|
|
- **Hypervisor:** `sfsrv-ana` (SureFire Proxmox, 10.250.250.115)
|
|
- **Site:** Anaheim (PFI colo)
|
|
- **Subnet:** `10.250.150.0/24` — dedicated SF container subnet
|
|
|
|
## Role
|
|
|
|
Container/VM workload for SureFire. Specific services TBD — refresh
|
|
the server-info snapshot once SSH is verified:
|
|
|
|
```bash
|
|
scripts/refresh-server-info.sh sf-ana-container
|
|
```
|
|
|
|
## Backup coverage
|
|
|
|
- **VM-image via sfsrv-ana vzdump:** status unknown — depends on what
|
|
backup jobs are configured on that Proxmox. Audit via
|
|
`scripts/refresh-proxmox-info.sh sfsrv-ana`.
|
|
- **File-level restic:** not yet configured — worth adding once we
|
|
know what state the container runs (DBs, configs, app data).
|
|
|
|
## Discovered via
|
|
|
|
`scripts/discover-fortigate.sh 10.250.250.1` on 2026-04-21 (MAC
|
|
`6a:09:9a:8a:08:a5`).
|