GroundZero 0.11.0

Configure storage from profiles, a full hardware inventory, reports, and gz-hwreport: a hardware report with nothing to set up.

Added

• gz-hwreport: a standalone hardware report, with nothing to set up. It reads one or more BMCs
  over Redfish (read-only) and writes a self-contained HTML page and a JSON file per server.
  • With several servers it adds a comparison page with differences highlighted.
  • Each release has a single-file executable for Linux (x86_64, arm64), macOS (arm64) and Windows. No
    Python needed.
  • groundzero hwreport is the same tool inside GroundZero. See "Just want a hardware report?" in the
    install guide.
• Full hardware inventory: Discover hardware now also reads the following, and the Overview tab shows
  all of it:
  • every installed firmware version (BIOS, BMC, controllers, NICs, drives, power supplies, backplanes)
  • each memory module
  • the network adapters with their firmware
  • PCIe devices: storage controllers and HBAs, NICs, accelerators
  • power supplies
  • each drive's firmware, and the service tag
• Reports: a server's hardware and configuration on one printable page, and a cluster report that
  puts the members side by side and flags what differs (BIOS, BMC and every firmware version, model,
  memory, drives, adapters, power supplies, OS).
  • Download a report as CSV (one row per component, or one row per compared item for a cluster) or JSON.
  • Built from what GroundZero already recorded: nothing is read from the servers.
• Configure storage: apply a storage profile covering RAID volumes, controller mode (RAID, HBA,
  enhanced HBA), drive state (RAID-capable or passed straight through) and global hot spares.
  • Profiles are rules, not drive ids, so one fits every server of a kind: "on the boot card, one RAID1
    of two SSDs, the boot volume"; "on the PERC, a RAID5 of three SAS SSDs and one hot spare".
  • Save a server's layout as a profile from its Storage tab, or write one on the Config sets page.
  • The plan comes first. It lists every change in the order it's applied, marks the ones that lose
    data, and says plainly why a profile can't be applied (not enough drives, a mode that can't hold
    volumes, no matching controller).
  • The boot volume the OS runs from is never deleted unless you tick the box that allows it.
  • The layout is read again before anything is written, and the run stops if it changed since Read
    storage.
  • Changes that wait for a reset share one restart. The layout is read back until the profile is met,
    and the boot volume recorded afterwards is the one the OS install uses.
  • Specs can pick a profile for their Configure storage step. Once applied, the step goes back to ready
    if the layout drifts from the profile.
  • On the command line: groundzero storage-profile list|show|save|capture|plan|delete.
  • Tested against the simulator only (it now models PERC volumes, drive conversion, spares and mode
    changes). On the lab R740xd the BOSS holds the running ESXi and the PERC has no drives.