hardware:overview

This is an old revision of the document!


Hardware Inventory Overview

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 with NVME 🟢 Active
cmpt2.lan Dell T7600 Generic Compute Server 🔴 Offline
cmpt3.lan Dell T7600 Generic Compute Server 🟢 Active
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
  • 🟢 Active - Device is operational and in use
  • 🟡 Maintenance - Device is under maintenance
  • 🔴 Offline - Device is not operational
  • âš« Retired - Device has been decommissioned

For creating a markdown overview:

1. Automatically create a preliminary Markdown via at this bash script using inxi. 2. Pass the following prompt to an LLM, together with the corresponding less-structured markdown output. Model could be for example Qwen3-235B-A22B-2507.

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]
  • hardware/overview.1757003166.txt.gz
  • Last modified: 2025/09/04 16:26
  • by fabricio