Current billing cycle end date. If the value in {@code currentCommitment} and {@code nextCommitment} are different, the value specified in {@code nextCommitment} becomes the new {@code currentCommitment} when the {@code contractEndDate} is reached. Example: {@code 2016-08-25T21:10:29.600Z}
The OCID of the deleted ESXi Host with LeftOver billing cycle.
The OCID of the Capacity Reservation.
The OCID of the Cluster that the ESXi host belongs to.
The OCID of the compartment that contains the Cluster.
The availability domain of the ESXi host.
In terms of implementation, an ESXi host is a Compute instance that is configured with the chosen bundle of VMware software. The {@code computeInstanceId} is the OCID of that Compute instance.
The billing option currently used by the ESXi host. {@link #listSupportedCommitments(ListSupportedCommitmentsRequest) listSupportedCommitments}.
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 descriptive name for the ESXi host. Does not have to be unique, and it's changeable. Avoid entering confidential information.
The version of ESXi software that Oracle Cloud VMware Solution installed on the ESXi hosts.
The OCID of the ESXi host that failed.
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 date and time when the new esxi host should start billing cycle. RFC3339. Example: {@code 2021-07-25T21:10:29.600Z}
The OCPU count of the ESXi host. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The compute shape name of the ESXi host. {@link #listSupportedHostShapes(ListSupportedHostShapesRequest) listSupportedHostShapes}.
The OCID of the ESXi host.
Indicates whether this host is in the progress of billing continuation.
Indicates whether this host is in the progress of swapping billing.
The current state of the ESXi host.
The billing option to switch to after the current billing cycle ends. If {@code nextCommitment} is null or empty, {@code currentCommitment} continues to the next billing cycle. {@link #listSupportedCommitments(ListSupportedCommitmentsRequest) listSupportedCommitments}.
The OCID of the ESXi host that will be upgraded.
The OCID of the ESXi host that is created to replace the failed host.
The OCID of the SDDC that the ESXi host belongs to.
The OCID of the active ESXi Host to swap billing with current host.
Usage of system tag keys. These predefined keys are scoped to namespaces. Example: {@code {orcl-cloud: {free-tier-retain: true}}}
The date and time the ESXi host was created, in the format defined by RFC3339.
Example: {@code 2016-08-25T21:10:29.600Z}
The date and time the ESXi host was updated, in the format defined by RFC3339.
The OCID of the ESXi host that is newly created to upgrade the original host.
The version of VMware software that Oracle Cloud VMware Solution installed on the ESXi hosts.
An ESXi host is a node in a Cluster. At a minimum, each Cluster has 3 ESXi hosts that are used to implement a functioning VMware environment.
In terms of implementation, an ESXi host is a Compute instance that is configured with the chosen bundle of VMware software.
Notice that an {@code EsxiHost} object has its own OCID ({@code id}), and a separate attribute for the OCID of the Compute instance ({@code computeInstanceId}).