API Guide

"overallSummary": {
"compliantStatus": "{Compliance Status}",
"nonCompliantType": "{Non-compliant Type}",
"noncompliantTypeDescription": "{Firmware version is different for N number
of component (s)}"
},
"componentDriftList": [
{
"componentDetails": {
"componentID": "{Component ID}",
"packageID": "{Package ID}",
"bundleID": "{Bundle ID}",
"instanceID": "{Instance ID}",
"componentName": "{Component Name}",
"componentType": "{Component Type}",
"componentTypeDisplay": "{Component Type Display}",
"upgrade": "Component Update required True or False",
"criticality": "{Importance of component update}",
"rebootRequired": "Host reboot required (True or False)",
"pciDeviceInfo": {
"deviceID": "{PCI device ID}",
"subDeviceID": "{PCI sub device ID}",
"subVendorID": "{PCI sub vendor ID}",
"vendorID": "{PCI vendor ID}"
}
},
"complianceSummary": {
"compliantStatus": "{Compliance Status}",
"nonCompliantType": "{non-compliance type}",
"noncompliantTypeDescription": "{Reason for non-compliance}"
},
"complianceDetails": {
"driftedVersionInfo": "{Component Version in Host}",
"baselineVersionInfo": "{Component version in Repository}"
}
}
]
}
]
NOTE:
After you upgrade OMIVV to 5.2 (RPM Upgrade or backup and restore), the value of model, revisionHistory, and
description are displayed as null until firmware repository is refreshed. To refresh the repository profile, on the repository
profile page, click Edit and complete the wizard without doing any modification. After repository profile is updated, update
the associated cluster profile. Drift detection job runs after you update the cluster profile.
For more information, see Response body on page 39.
Drift management
35