ironcore-dev / ironcore-dev/roadmap
Automate Inventorying Hardware
Open
@5kt is already working on this.
Since Apr 2, 2025.
area/metal-automation
- Dominant language
- Shell
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Summary
In order to prepare all the hardware for the showroom environment and before it is going to be onboarded certain tasks need to be done.
We need to collect and document detailed hardware inventory information from each server, run performance benchmarks and compare against baseline expectations.
❗ This is still subject to change.
Scope
✅ In Scope
CPU & Memory
- Document CPU vendor/model and flags.
- Record total RAM and count of DIMMs.
- Identify NUMA zones and memory distribution.
PCIe
- Enumerate PCIe devices.
- Document PCIe bus topology.
Network Cards
- Identify NICs via PCIe.
- Document port types/sizes.
- Record firmware versions.
- Use LLDP to determine switch connection details.
Storage Devices
- List block devices and NVMe drives.
- Determine CPU attachment of each NVMe.
- Record firmware versions of storage components.
Benchmarking
- Run performance benchmarks on all block devices.
- Run NVMe-specific benchmarks.
- Record results and compare to expected thresholds.
❌ Out of Scope
Responsible Areas
Metal Automation Documentation
Contributors
- @5kt
- @MalteJ
- @afritzler
Acceptance Criteria
-
Metal Automation
- A tool needs to be provided that is going to inventorise the servers
- Have predefined benchmarks
-
Documentation
- Provide documentation on the inventory process and the tool to run it
- Provide documentation on the benchmarks that are required
Action Items
- Assign labels (e.g.,
area/ironcore-api,kind/design) - Set milestone (e.g.,
H1/2025) - Assign dependent sub-issues in each required area
- Assign an owner to the issue using the GitHub "Assignee" field
- List all contributors in the "Contributors" section above
- Add this issue to the
Roadmapproject board
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.