At present there are no fees to test a product in OCCL. Western Digital and our partners have agreed to cover the expense of running this lab and providing compatibility testing services. This may change in the future as we continue to evaluate the cost of running the lab. We also ask that as products undergo firmware updates that requests for re-test on new firmware is no more frequent than every 6 months.

OCCL can test all resources in the open composable architecture (cpu, gpu, fpga, memory, flash, disk, tape, and network or fabric) for data path compatibility. A resource to be tested will be inserted into a running baseline as an added resource or to replace an existing resource as appropriate. Resources or orchestration software products that implement the OC API can also be tested for compatibility

Yes. OCCL publishes successful results of compatibility testing on released products on the Partners tab of www.opencomplsable.com. This list is updated roughly quarterly.

Yes you can. Although we prefer that all hardware devices coming into OCCL have passed UNH IOL tests, we do not make this a hard requirement. Note that we will not be able to allocate time in our lab to debugging protocol issues that could be detected at UNH-IOL which could terminate your OCCL testing opportunity.

No. At present, OCCL is designed to let you bring in hardware or software products one-at-a-time for compatibility testing.

Typical test turn-around time is one week. This can vary depending on how busy the lab is at the time, and debugging any issues that might be identified.

Yes product testing is on-going all year long. When your product can be tested is a function of how deep the queue is when you sign up to test.

The OCCL has taken the approach of identifying the contributing components of the environment and then implementing a test suite which will provide an indicator of compatibility with the environment.  In most composable fabric environments the key components which have an impact on fabric functionality are:

• The Operating System of the “Composed” server.
• The Network Interface Card of the “Composed” server, including drivers & firmware.
• The Network Switch of the data reliable fabric, including switch O/S version.
• The fabric device, including firmware.
  

• No, however the OCCL encourages all devices that come into OCCL to have passed the UNH-IOL Ethernet and NVMe-oF test suites if appropriate.
  

The operating system that is chosen for the composed server has an immediate impact on the system’s ability to properly interface with the chosen fabric and fabric devices. The items that the OCCL will be looking for in an OS candidate will include:

• Active kernel stack development of fabric drivers such as NVMe-oF that shows support of fabric devices.
• Compatibility with Network Interface Cards that provide fabric connectivity and functionality
  

The OCCL is only concerned with compatibility with the composable fabric role and will be looking for these items in a compatibility candidate:

• Driver compatibility with chosen initiator operating system.
• Fabric protocol compatibility with chosen composable fabric. i.e. RDMA over Converged Ethernet, NVMe over TCP, NVMe over FC, and other fabric device protocols.