Ramesh Iyyar | 1f971f2 | 2021-05-17 06:13:25 -0500 | [diff] [blame] | 1 | description: > |
| 2 | Implement to provide the isolated hardware entry attributes. |
| 3 | |
| 4 | The object which implements this interface must implement |
Patrick Williams | a134741 | 2022-12-06 10:56:22 -0600 | [diff] [blame] | 5 | xyz.openbmc_project.Association.Definitions to point associated object, for |
| 6 | example, isolated hardware inventory path and error log if it caused to |
| 7 | isolate hardware. The isolated hardware association of forward and reverse |
| 8 | name must be following respectively "isolated_hw" and "isolated_hw_entry". |
| 9 | The error log association of forward and reverse types must be following |
Ramesh Iyyar | 1f971f2 | 2021-05-17 06:13:25 -0500 | [diff] [blame] | 10 | respectively "isolated_hw_errorlog" and "isolated_hw_entry". |
| 11 | |
| 12 | The object which implements this interface should implement |
Patrick Williams | a134741 | 2022-12-06 10:56:22 -0600 | [diff] [blame] | 13 | xyz.openbmc_project.Object.Delete to allow the deletion of individual |
| 14 | isolated hardware object. |
Ramesh Iyyar | 1f971f2 | 2021-05-17 06:13:25 -0500 | [diff] [blame] | 15 | |
| 16 | The object which implements this interface must implement |
Patrick Williams | a134741 | 2022-12-06 10:56:22 -0600 | [diff] [blame] | 17 | xyz.openbmc_project.Time.EpochTime for the isolated hardware creation time. |
Ramesh Iyyar | 1f971f2 | 2021-05-17 06:13:25 -0500 | [diff] [blame] | 18 | |
| 19 | properties: |
| 20 | - name: Severity |
| 21 | type: enum[self.Type] |
| 22 | description: > |
| 23 | The severity of hardware isolation. |
| 24 | - name: Resolved |
| 25 | type: boolean |
| 26 | default: false |
| 27 | description: > |
Patrick Williams | a134741 | 2022-12-06 10:56:22 -0600 | [diff] [blame] | 28 | The isolated hardware resolution status is used to indicate whether |
| 29 | the isolated hardware is repaired or replaced. Setting this to "true" |
| 30 | may not delete this entry object because in a few system platforms |
| 31 | isolated hardware entries may not be deleted and used for further |
| 32 | analysis. |
Ramesh Iyyar | 1f971f2 | 2021-05-17 06:13:25 -0500 | [diff] [blame] | 33 | |
| 34 | enumerations: |
| 35 | - name: Type |
| 36 | description: > |
| 37 | Possible severity for hardware isolation. |
| 38 | values: |
Patrick Williams | 8da396c | 2022-03-14 14:21:02 -0500 | [diff] [blame] | 39 | - name: Critical |
| 40 | description: > |
| 41 | Critical hardware to repair or replace. |
| 42 | - name: Warning |
| 43 | description: > |
Patrick Williams | a134741 | 2022-12-06 10:56:22 -0600 | [diff] [blame] | 44 | The system can boot without the isolated hardware but, will lose |
| 45 | the system configuration benefits of isolated hardware. |
Patrick Williams | 8da396c | 2022-03-14 14:21:02 -0500 | [diff] [blame] | 46 | - name: Manual |
| 47 | description: > |
Patrick Williams | a134741 | 2022-12-06 10:56:22 -0600 | [diff] [blame] | 48 | A user attempted to isolate hardware to proceed with the host to |
| 49 | boot. |