|
| 1 | +# Ironic Redfish Inspection Guide |
| 2 | + |
| 3 | +This guide explains how to set a Baremetal node in OpenStack Ironic to use the Redfish inspection interface, run inspection, and view the gathered inspection data. |
| 4 | + |
| 5 | +--- |
| 6 | + |
| 7 | +## 1. Set the Node to Use Redfish Inspect |
| 8 | + |
| 9 | +First, update the node to use the `redfish` (or vendor-specific, e.g., `idrac-redfish`) inspect interface: |
| 10 | + |
| 11 | +```bash |
| 12 | +openstack baremetal node set <NODE_UUID_OR_NAME> --inspect-interface idrac-redfish |
| 13 | +``` |
| 14 | + |
| 15 | +Note: By default, all our nodes have the following inspection interface: |
| 16 | + |
| 17 | +```json |
| 18 | +"inspect_interface": "idrac-redfish" |
| 19 | +``` |
| 20 | + |
| 21 | +--- |
| 22 | + |
| 23 | +## 2. Run Inspection |
| 24 | + |
| 25 | +Trigger inspection on the node: |
| 26 | + |
| 27 | +```bash |
| 28 | +openstack baremetal node inspect <NODE_UUID_OR_NAME> --wait |
| 29 | +``` |
| 30 | + |
| 31 | +This command tells Ironic to boot the node into the inspection environment and gather hardware details via Redfish. |
| 32 | + |
| 33 | +### Argo Workflow Integration |
| 34 | + |
| 35 | +Our Argo [enroll-server](https://workflows.dev.undercloud.rackspace.net/workflow-templates/argo-events/enroll-server) workflow already runs Redfish inspection. |
| 36 | +Therefore, just running `openstack baremetal node inventory save` is enough to retrieve the inspection data. |
| 37 | + |
| 38 | +--- |
| 39 | + |
| 40 | +## 3. Show Inspection Data |
| 41 | + |
| 42 | +After inspection completes, you can view the data Ironic collected. |
| 43 | + |
| 44 | +```bash |
| 45 | +openstack baremetal node inventory save <NODE_UUID_OR_NAME> --file inspection-data.json |
| 46 | +``` |
| 47 | + |
| 48 | +Sample inventory data: |
| 49 | + |
| 50 | +```json |
| 51 | +{ |
| 52 | + "inventory": { |
| 53 | + "memory": { |
| 54 | + "physical_mb": 98304 |
| 55 | + }, |
| 56 | + "cpu": { |
| 57 | + "count": 32, |
| 58 | + "model_name": "AMD EPYC 9124 16-Core Processor", |
| 59 | + "frequency": 4400, |
| 60 | + "architecture": "x86_64" |
| 61 | + }, |
| 62 | + "disks": [ |
| 63 | + { |
| 64 | + "name": "Solid State Disk 0:1:0", |
| 65 | + "size": 479559942144 |
| 66 | + }, |
| 67 | + { |
| 68 | + "name": "Solid State Disk 0:1:1", |
| 69 | + "size": 479559942144 |
| 70 | + } |
| 71 | + ], |
| 72 | + "interfaces": [ |
| 73 | + { |
| 74 | + "mac_address": "D4:CB:E1:BF:8E:21" |
| 75 | + }, |
| 76 | + { |
| 77 | + "mac_address": "D4:CB:E1:BF:8E:20" |
| 78 | + } |
| 79 | + ], |
| 80 | + "system_vendor": { |
| 81 | + "product_name": "System", |
| 82 | + "serial_number": "MXVX4003C100KL", |
| 83 | + "manufacturer": "Dell Inc." |
| 84 | + }, |
| 85 | + "boot": { |
| 86 | + "current_boot_mode": "uefi" |
| 87 | + } |
| 88 | + }, |
| 89 | + "plugin_data": {} |
| 90 | +} |
| 91 | +``` |
| 92 | + |
| 93 | +This will save the inspection data (hardware details, NICs, storage, CPU, etc.) to a JSON file. |
| 94 | + |
| 95 | +You can also query directly: |
| 96 | + |
| 97 | +```bash |
| 98 | +openstack baremetal node show <NODE_UUID_OR_NAME> -f json |
| 99 | +``` |
| 100 | + |
| 101 | +Look under fields like `properties`, `extra`, and `driver_internal_info` for inspection results. |
| 102 | + |
| 103 | +--- |
0 commit comments