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.
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 |
Note as per email discussion:-
“What needs to be validated",
We can share the details which p/m are validating as per table above or any addition”
the first goal is validation of the hardware against a bill of material or similar. This would also check against minimums agreed / set by the CNTT, so the environment or lab can be vetted to meet the requirements for VNF certification, etc.
“How it is validated"
We can present a small demo with our automated architecture approach”
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?
When does the HDV occur, pre stack deployment, post stake deployment? How does this handle the cloud native environment (i.e. no open stack)?
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).
What are the required output / formats, etc.?
Note: