Additional data that can be exposed to the customer. Will include raw fault codes for strategic customers
The availability domain of the compute host.
Example: {@code Uocm:US-CHICAGO-1-AD-2}
The OCID for the Capacity Reserver that is currently on host
The OCID for the compartment. This should always be the root compartment.
The OCID for the Customer-unique host group associated with the Compute Bare Metal Host.
Configuration state of the Compute Bare Metal Host.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
Example: {@code {\"Operations\": {\"CostCenter\": \"42\"}}}
A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
A fault domain is a grouping of hardware and infrastructure within an availability domain. Each availability domain contains three fault domains. Fault domains let you distribute your instances so that they are not on the same physical hardware within a single availability domain. A hardware failure or Compute hardware maintenance that affects one fault domain does not affect instances in other fault domains.
This field is the Fault domain of the host
The OCID for the Customer-unique firmware bundle associated with the Host.
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags.
Example: {@code {\"Department\": \"Finance\"}}
The OCID for Customer-unique GPU Memory Fabric
The heathy state of the host
The ID that remains consistent when a host moves between capacity pools within the same tenancy.
The OCID for Customer-unique HPC Island
The OCID for the Customer-unique host
A list that contains impacted components related to an unhealthy host. An impacted component will be a free-form structure of key values pairs that will provide more or less details based on data tiering
The public OCID for the Virtual Machine or Bare Metal instance
A free-form description detailing why the host is in its current state.
The lifecycle state of the host
The OCID for Customer-unique Local Block
The OCID for Customer-unique Network Block
The platform of the host
The shape of host
The date and time that the compute bare metal host configuration check was updated, in the format defined by RFC3339.
Example: {@code 2016-08-25T21:10:29.600Z}
The date and time that the compute host record was created, in the format defined by [RFC3339](https://tools .ietf.org/html/rfc3339).
Example: {@code 2016-08-25T21:10:29.600Z}
The date and time that the compute host record was updated, in the format defined by RFC3339.
Example: {@code 2016-08-25T21:10:29.600Z}
The customer facing object includes host details.