Specs – Open Programmable Infrastructure Project

Classic ZTP doesn’t provide enough security that customers seek nowadays
The first part of security considerations, “DPU/IPU Validation” is done using “IEEE 802.1AR – Secure Device Identity”
The second part of security considerations, “Network Validation” is done using “A Voucher Artifact for Bootstrapping Protocols”
The last step is “Artifacts Validation”, download and installation (OS, config, pre and post scripts)
The discovery is recommended but not limited to DHCP (both ipv4 and ipv6) and SLAAC (ipv6)
The monitoring of the entire process step by step is describe in the RFC in much details
check more info with detailed diagrams

all vendors can implement (both linux and non-linux based)
customers can integrate only once in their existing monitoring systems and tools
OpenTemetry supports those data sources (Traces, Metrics and Logs)
OPI is only mandating OTEL Specification link
- OTEL SDK and OTEL Collector specific implementation are left to the vendors
OTEL Recommendation (reference):
- micro-aggregator inside each DPU/IPU
- macro-aggregator across DPUs and IPUs
Next steps
- Standardize the common metrics across DPU and IPU vendors

SMBIOS is used for local access inside the DPUs and IPUs to get BIOS and System information about DPUs and IPUs

SMBIOS is a standard way to get similar information from servers, so DPUs and IPUs adoption make sense
On Linux one can access SMBIOS info locally via dmidecode or /sys/class/dmi/id/, as an example
SMBIOS provides those types of information:
- bios
- system
- baseboard
- chassis
- processor
- memory
- cache
- connector
- slot
OPI will define mandatory tables and fields for OPI compliance.
OPI will produce smbios-validation-tool like google
Check more info in Provisioning TWG