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