As an h/w acceptance operator or install/shipping operator, I want to know a computer meets the spec.

[130s]

Problem

It takes many steps to verify whether a computer meets the spec. Very error-prone if it's done manually.

Usecase

• I know H/W info (CPU, RAM, disk etc.) that we need. I want to know whether the computer meets the spec or not (if not what elements don't meet).

Requirement

• Input: H/W info.
  • Value range can be specified (e.g. Size of SSD can be between 400 - 600GB).
• Output:
  • Verification result (bool)
  • Exception detail.
• Implementation
  • There must be tools that provide system info. Utilize them instead of making everything from scratch. Decouple the I/F to the depended library as we might switch the underlining tool in the future.

CoS

• [ ] Investigate existing solution
• [ ] Integrate if there's no software that satisfies all the requirements.

Moved from https://github.com/130s/hut_10sqft/issues/290

[130s]

CoS

• [ ] Investigate existing solution

• lmirosevic/GBDeviceInfo: Nice concept but this only works for Apple's product.
• OSHI (Operating System and Hardware Information)
  • o Seems actively maintained.
  • Only API (i.e. No end user's client) (kind of confirmed - "Download" on github gives me a .jar file)? That's fine.
  • API is in Java.
  • Then, my usecase includes using the functionality in ROS. There seems to be a way to build java package by catkin although it's updated the last time in 2014 or so.
  • • No Ubuntu .deb seems to be released.
• Sigar / OperatingSystemMXBean: There's a comparison on OSHI's page (circa 2015) that discourages both.
• psutil provides a bunch of Python I/F to return sys info.
• otseca outputs html, no data-only format e.g. yaml. No input taken.
• hardinfo doc is not sufficient...
• indicium outputs the system info result in json, but the tool runs on .NET only.

Leaning toward using psutil as an underlining library, and implement both reporting and verifying features by myself. Maybe push that features to psutil.

[130s]

Ran into osquery via psutil's list of downstream projects. It entails a fascinating concept - providing any OS info via SQL interface.

• Assuming for Linux osquery depends on psutil under the hood, I haven't yet found (after spending an hour in trying to grasp) what's the benefit of injecting another dependency layer on top of psutil. I'll think about it more.
• Haven't seen an example of passing a requirement (e.g. hardware spec).

osquery evaluated separately in https://github.com/130s/hut_10sqft/issues/396