Number of nodes desired in the cluster, in standalone clusters, between 5 and 15 inclusive. In station clusters, between 15 and 30 inclusive. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
Type of cluster.
List of existing workloads that should be provisioned on the nodes.
The OCID of the compartment containing the RoverCluster.
Validation code returned by data validation tool. Required for return shipping label generation if data import was requested.
The defined tags associated with this resource, if any. Each key is predefined and scoped to namespaces. 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.
The type of enclosure rover nodes in this cluster are shipped in.
The freeform tags associated with this resource, if any. 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"}}
An OCID of a compartment where data will be imported to upon Rover cluster return.
Name of a bucket where files from NFS share will be imported to upon Rover cluster return.
The flag indicating that customer requests data to be imported to OCI upon Rover cluster return.
The current state of the RoverCluster.
A property that can contain details on the lifecycle.
Customer provided master key ID to encrypt secret information. If not provided, Rover's master key will be used for encryption.
Tracking Url for the shipped Rover Cluster.
Name of point of contact for this order if customer is picking up.
Phone number of point of contact for this order if customer is picking up.
Preference for device delivery.
Shipping vendor of choice for orace to customer shipping.
ID provided to customer after successful subscription to Rover Stations.
Root password for the rover cluster.
The system tags associated with this resource, if any. The system tags are set by Oracle cloud infrastructure services. Each key is predefined and scoped to namespaces. For more information, see Resource Tags. Example: {@code {orcl-cloud: {free-tier-retain: true}}}
Expected date when customer wants to pickup the cluster if they chose customer pickup.
Password to unlock the rover cluster.
The information required to create a RoverCluster.