Revision history   OpenPOWER Library

 4.2. Software Requirements

In addition to a Linux on POWER LE (LoP-LE) mode device driver for the device, additional software is frequently required (see the table below for examples). Required software for the claimed functions of the OpenPOWER Ready I/O adapter must be available to the consumer of the device under OSI approved license or commercial license.

OpenPOWER Ready requires test of the offered software in an OpenPOWER configuration. The software test is part of the functional test requirements described below.

 

Table 4.1. Required Software Testing

Software

Requirement

Recommendation

Device Driver

  1. A LoP-LE Driver is required. Open Source License is desired.

  2. Successful Functional Test on at least one of the LoP-LE Distributions (Ubuntu, RHEL, SuSE, PowerKVM™, etc.)

Driver should follow Linux on POWER Device Driver Porting Guide

Boot

OPAL Firmware and petitboot as of op-build v1.7 (or later). Additional device drivers may be added to enable boot support off these devices.

Online Documentation available for Driver and Utilities support in OPAL/Petitboot OPAL/Petitboot GIT hub.

Serviceability and Management.

LE-LoP based utilities for device Diagnostics, FW update, and Configuration.

These utilities should target open source tools e.g. ethtool. Vendor toolset ported to LE-LoP is acceptable.

Storage Management

LE-LoP RAID Configuration Utilities and Storage Enclosure Management.

Package RAID configuration utilities as a petitboot blugin in addition to being made available for LoP linux distros

SAN Storage Software.

LE-LoP MPIO and HBA/SAN Management Software is required for FC/FCoE/ISCSI HBAs

Should target open source tools e.g. Linux MPIO. Vendor toolset ported to LE-LoP is acceptable.

Advanced Networking

LE-LoP RDMA/OFED, DPDK, OpenOnload, iSCSI, OVS, Overlay Networking etc. is required for devices claiming support of the advanced stacks.

Stacks are open source but require porting, tuning and productization for the devices.

Devices claiming support of an "advanced stack" should have the stack's respective open source ported, tuned and productized for the devices.