Collegium:Imperium System: Difference between revisions
Jump to navigation
Jump to search
AdminIsidore (talk | contribs) No edit summary |
AdminIsidore (talk | contribs) No edit summary |
||
| Line 19: | Line 19: | ||
| NFS (''nfs-kernel-server'', ''nfs-common''); configure ''/etc/exports'' on ''Torta'', mount on ''Roma''/''Horreum'' | | NFS (''nfs-kernel-server'', ''nfs-common''); configure ''/etc/exports'' on ''Torta'', mount on ''Roma''/''Horreum'' | ||
| Read/write access across nodes with static IPs, tested via file creation/listing on ''pomerium_via'' paths | | Read/write access across nodes with static IPs, tested via file creation/listing on ''pomerium_via'' paths | ||
| Completed (October 09, 2025) | |||
|- | |- | ||
| '''NFS-Plus GPU Dispatching''' | | '''NFS-Plus GPU Dispatching''' | ||
| Line 97: | Line 98: | ||
* Missions adhere to the Lingua standard, using Latin terms (e.g., ''pomerium_via'' for NFS paths, ''frumentarii_transfer'' for RSYNC jobs) to support script interoperability and quarterly audits for AI training. | * Missions adhere to the Lingua standard, using Latin terms (e.g., ''pomerium_via'' for NFS paths, ''frumentarii_transfer'' for RSYNC jobs) to support script interoperability and quarterly audits for AI training. | ||
* The plan prioritizes foundational infrastructure (NFS, GPU dispatching) before security mechanisms (data diodes, sandboxing) and pipeline tests, culminating in automation for scalability. | * The plan prioritizes foundational infrastructure (NFS, GPU dispatching) before security mechanisms (data diodes, sandboxing) and pipeline tests, culminating in automation for scalability. | ||
* Mission 1 (NFS Setup) was completed with fixed port configurations for NFS services and verified through multi-node file creation, concurrent writes, and cleanup tests, establishing unified access in Pomerium. | |||