Options
All
  • Public
  • Public/Protected
  • All
Menu

Interface CreateComputeClusterRequest

example

Click here to see how to use CreateComputeClusterRequest.

Hierarchy

Properties

createComputeClusterDetails

createComputeClusterDetails: CreateComputeClusterDetails

The data for creating a compute cluster. A compute cluster is an empty remote direct memory access (RDMA) network group.

After the compute cluster is created, you can use the compute cluster's OCID with the {@link #launchInstance(LaunchInstanceRequest) launchInstance} operation to create instances in the compute cluster. The instances must be created in the same compartment and availability domain as the cluster.

Use compute clusters when you want to manage instances in the cluster individually in the RDMA network group.

For details about creating a cluster network that uses instance pools to manage groups of identical instances, see {@link #createClusterNetworkDetails(CreateClusterNetworkDetailsRequest) createClusterNetworkDetails}.

Optional opcRequestId

opcRequestId: undefined | string

Unique identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.

Optional opcRetryToken

opcRetryToken: undefined | string

A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations (for example, if a resource has been deleted and purged from the system, then a retry of the original creation request may be rejected).

Optional retryConfiguration

retryConfiguration: RetryConfiguration

RetryConfiguration to be used for the request NOTE : Retries are not supported for requests that have binary or stream bodies this also affects UploadManager operations For all requests with binary/stream bodies, retry attempts are not made