CPU heavy, for regular compute workloads. Might have a GPU, but not optimized for it.
| Hostname | Model | Primary Function | Status |
|---|---|---|---|
| cmpt1.lan | Dell T7600 | Generic Compute Server | 🟢 Active |
| cmpt2.lan | Dell T7600 | Generic Compute Server | 🔴 Offline |
| cmpt3.lan | Dell T7600 | Generic Compute Server | 🟢 Active /broken HDDs) |
| dl2.lan | HP Z6 Generation 4 | DeepLearn Server | 🟢 Active |
| strg1.lan | HPE ProLiant ML350p | Minio | 🟢 Active |
| basel.lan | HPE ProLiant ML350p | Databases, Web-Services, Compute Communications | 🟢 Active |
| sand.lan | Old HP | Wildly test different things, from proxmox to SLURM. | 🔴 Incomplete |
| Former Hostname | Model | Primary Function | Status |
|---|---|---|---|
| dl1.lan | ASUS | DeepLearn Server | 🔴 Broken |
| ? | HPE ProLiant ML350p | Not yet known | 🔴 Incomplete |
For creating a markdown overview:
Please process the following hardware inventory information and format it according to these requirements: 1. Create a concise hardware overview focusing on: - Essential hardware components (CPU, RAM, storage, GPU) - High-level software stack (OS + version) - Remove unnecessary technical details while preserving key specifications 2. Format the output as DokuWiki-compatible markdown with: - Headers using "=" syntax (e.g., "====== Title ======") - Proper table formatting with "^" for headers - Clean organization of critical information only 3. Maintain these sections in the output: - System Overview (with hardware configuration table) - Storage Layout - Memory Usage - Notes (highlighting key capabilities) - Last Updated - Placeholder sections for Current Issues, Future Upgrades, and Maintenance Log 4. If any section would be empty, keep it as a placeholder to complete later 5. Return the entire formatted document wrapped in a code block using triple backticks Here is the hardware inventory information to process: [PASTE YOUR HARDWARE INVENTORY DETAILS HERE]