To develop and agree the requirements of the hardware delivery validation, per the CNTT request, which may be included as part of the OVP Infrastructure testing requirements.
Notes
There are a number of open questions that should reach community agreement BEFORE trying to reach agreement on specific tooling (basically, lets agree the WHAT before the HOW). The following questions have inputs have been pulled from email discussions intended to drive input input this working session for Prague.
What specifically needs to be "checked" in the validation, in terms of parameters and configuration? (RAM, Disks and Disk Sizes, CPU info, Network Interfaces, Network Connectivity, etc.)
Test Type
Purpose
Examples
BIOS Settings
Verifies all applicable BIOS settings per hardware model.
Boot mode, Boot Sequence Retry, A C Power Recovery
Firmware Settings
Verifies all applicable Firmware settings
BIOS, Storage Array Controller, Intel X710
Boot Order
Verifies applicable boot order settings
First boot, Second boot
Hardware Health
Queries Intelligent Platform Management Interface (IPMI) is for all hardware components and their health status
Raid, System Board, CPU temp, etc
NIC Slot Status & MAC
Validates that all NICs are in the correct slots, with a healthy status (per IPMI), have correct MAC addresses, and are detecting a cable connection (or not).
NIC in slot/port/partition
IPMI Logs
Check for existence of logs
Physical event logged. E.g. chasis open on power up
IPMI Users
Check for existence of user accounts
Define account and log review. E.g. root
Hardware Inventory
Inventory of h/w on platform..
CPU, RAM, speed, size, model, etc
Physical Disk Configuration
Verifies disk config (type, size)
Physical disk type, firmware, capacity
SRIOV Port Validation
Verifies global and NIC level enablement
Confirm setting is enabled (or none)
Endpoint Flow Validation
Verifies northbound connectivity.
Ping/TCP connection successful
Hardware Check
Verifies basic OS config attributes
RAM size, # of CPUs
What is the entry to the HDV (hardware delivery validation)? Is this information contained / pulled from the PDF type "file," if yes, does that "file" contain all required info? If not, then what?
Mike: Entry will be remote access into the host. IPMI interface / logs used for verification. Tool/discussion will be needed for access and automation.
FQ: I would think the entry would be from PDF.
When does the HDV occur, pre stack deployment, post stake deployment? How does this handle the cloud native environment (i.e. no open stack)?
Mike: Pre-software stack deployment. i.e. RI Design complete (PDF) > Rack, Stack/Cabling > Network Config > “HVD” > then, passed on to software deployment team.
FQ: Agree. HDV is before any software is deployed in the infrustructure.
If the requirement is pre stack deployment, how is the validation done, i.e using the BMC interfaces? (this will require significant hardware vendor input).
Mike: Yes, this Baseboard Management Controller (BMC), or Integrated Lights Out (iLO) management / NIC port, dedicated to accessing the host for remote management.
[fq]we are using IPMI at first, and now also utilize redfish. It really requires significant hardware vendor input, and lots of adaptation effort
What are the required output / formats, etc.?
Mike: Varies by test type: Either Boolean, Text, Size, Version/Value, OK (health), Serial #s, etc
