Hardware Compatibility Integration
SELF-TEST SERVERS AND COMPONENTS WITH MIRANTIS OPENSTACK
OpenStack is engineered to work with the widest range of standards-based server, component and network hardware. But as hardware engineers add new features, build in density and stretch the price/performance envelope, incompatibilities can still materialize. This page describes Mirantis Unlocked Hardware Compatibility Integration — a simple process making use of Mirantis tools — that lets Mirantis Unlocked Partners (and end-users) test hardware platforms and components for basic compatibility with Mirantis OpenStack. Unlocked Partners may request inclusion of self-tested hardware in the Mirantis Unlocked Hardware Compatibility List and other Mirantis online catalogs.
Important: Before beginning this process, please engage with the Mirantis Unlocked team and Become a Mirantis Unlocked Partner Community Member
What HCL Self-Testing Means
Mirantis’ HCL script is intended to test if particular hardware supports Mirantis OpenStack. The script accesses Fuel to list all the hardware discovered on OpenStack nodes. Discovery means that hardware has been recognized appropriately by the Linux operating system. HCL self-test only determines whether hardware is visible to Linux kernel modules used in the Mirantis OpenStack installation. It does not test the full scope of hardware functionality claimed by the OEM.
Hardware Compatibility Self-Test Process
To complete the hardware self-test process, you’ll need to set up Fuel for OpenStack deployment and management, follow the other preliminary steps outlined below, perform the testing itself, and then send the results to Mirantis.
CREATE TEST CLUSTER
- Download the Mirantis OpenStack .iso from mirantis.com.
- Study the Fuel Install Guide to familiarize yourself with OpenStack configuration and deployment using Fuel.
- Set up a Fuel Master Node using the .iso, by following these instructions. We recommend but don’t require a Fuel Master node to be tested against your HW, so you may install it as a VM. The installation process will conclude by displaying local and subnet IP addresses and credentials for accessing the Fuel Web UI (we’ll call this FUEL_URL) and for logging into fuel with SSH as the root/administrator (we’ll call this FUEL_IP). Record this information.
- Set up the hardware you wish to test on the same network as the Fuel Master, setting servers to PXE boot (see Mirantis OpenStack User Guide).
- Boot all the nodes and make sure they all are discovered by Fuel.
PREPARE TO TEST
- The following assumes you are using Linux. Make sure your computer has a bash console with network access to the Fuel Master node. To verify, execute the following command, using the access address for the Fuel Web UI generated in Step 3, above:
&& echo OK
Make sure the command returns ‘OK.’
- Download the hardware self-test tool from https://validation.mirantis.com/mirantis_validation_tool.sh.
- To begin, copy the self-test tool you downloaded in Step 2, above, to the Fuel Master node as follows:
$ scp PATH_TO_SCRIPT root@FUEL_IP:SOME_FOLDER
$ scp /tmp/mirantis_validation_tool.sh firstname.lastname@example.org:/tmp
- Log into the Fuel Master node at FUEL_IP using root credentials, and run the script:
$ ssh root@FUEL_IP
# cd PATH_TO_SCRIPT_FOLDER
# bash mirantis_validation_tool.sh
$ ssh email@example.com
# cd /tmp
# bash mirantis_validation_tool.sh
After testing is complete, the Mirantis hardware self-test tool displays test results and saves them to a file with a naming convention such as “HW_validation_report_XXXX.txt” where “XXXX” is the current Unix time. Then submit your review request to Mirantis as follows:
- Copy and paste the successful results in an email.
- Add the following information manually to the email:
- List of network cards, including manufacturer(s) and chipset(s).
- List of RAID adapters, including manufacturer(s) and chipset(s).
The Mirantis Unlocked team will check results and award Mirantis Unlocked | Community Hardware Compatibility List status to products correctly identified by test scripts.