Package com.oracle.bmc.ocvp

Interface DatastoreClusterAsync

All Superinterfaces:

AutoCloseable

All Known Implementing Classes:

DatastoreClusterAsyncClient

@Generated(value="OracleSDKGenerator",
           comments="API Version: 20230701")
public interface DatastoreClusterAsync
extends AutoCloseable

Use the Oracle Cloud VMware API to create SDDCs and manage ESXi hosts and software.

For more information, see Oracle Cloud VMware Solution.

Method Summary

Modifier and Type	Method	Description
Future<AddDatastoreToDatastoreClusterResponse>	addDatastoreToDatastoreCluster(AddDatastoreToDatastoreClusterRequest request, AsyncHandler<AddDatastoreToDatastoreClusterRequest,AddDatastoreToDatastoreClusterResponse> handler)	Add the specified Datastore to the provided Datastore Cluster.
Future<AttachDatastoreClusterToClusterResponse>	attachDatastoreClusterToCluster(AttachDatastoreClusterToClusterRequest request, AsyncHandler<AttachDatastoreClusterToClusterRequest,AttachDatastoreClusterToClusterResponse> handler)	Attach the specified Datastore Cluster to the provided Vmware Cluster.
Future<AttachDatastoreClusterToEsxiHostResponse>	attachDatastoreClusterToEsxiHost(AttachDatastoreClusterToEsxiHostRequest request, AsyncHandler<AttachDatastoreClusterToEsxiHostRequest,AttachDatastoreClusterToEsxiHostResponse> handler)	Attach the specified Datastore Cluster to the provided ESXi Hosts.
Future<ChangeDatastoreClusterCompartmentResponse>	changeDatastoreClusterCompartment(ChangeDatastoreClusterCompartmentRequest request, AsyncHandler<ChangeDatastoreClusterCompartmentRequest,ChangeDatastoreClusterCompartmentResponse> handler)	Moves an Datastore Cluster into a different compartment within the same tenancy.
Future<CreateDatastoreClusterResponse>	createDatastoreCluster(CreateDatastoreClusterRequest request, AsyncHandler<CreateDatastoreClusterRequest,CreateDatastoreClusterResponse> handler)	Creates a Oracle Cloud VMware Solution Datastore Cluster.
Future<DeleteDatastoreClusterResponse>	deleteDatastoreCluster(DeleteDatastoreClusterRequest request, AsyncHandler<DeleteDatastoreClusterRequest,DeleteDatastoreClusterResponse> handler)	Deletes the specified Datastore Cluster.
Future<DetachDatastoreClusterFromClusterResponse>	detachDatastoreClusterFromCluster(DetachDatastoreClusterFromClusterRequest request, AsyncHandler<DetachDatastoreClusterFromClusterRequest,DetachDatastoreClusterFromClusterResponse> handler)	Detach the specified Datastore Cluster from the provided Vmware Cluster.
Future<DetachDatastoreClusterFromEsxiHostResponse>	detachDatastoreClusterFromEsxiHost(DetachDatastoreClusterFromEsxiHostRequest request, AsyncHandler<DetachDatastoreClusterFromEsxiHostRequest,DetachDatastoreClusterFromEsxiHostResponse> handler)	Detach the specified Datastore Cluster from the provided ESXi Hosts.
Future<GetDatastoreClusterResponse>	getDatastoreCluster(GetDatastoreClusterRequest request, AsyncHandler<GetDatastoreClusterRequest,GetDatastoreClusterResponse> handler)	Get the specified Datastore Cluster information.
String	getEndpoint()	Gets the set endpoint for REST call (ex, https://www.example.com)
Future<ListDatastoreClustersResponse>	listDatastoreClusters(ListDatastoreClustersRequest request, AsyncHandler<ListDatastoreClustersRequest,ListDatastoreClustersResponse> handler)	List the Datastore Clusters in the specified compartment.
void	refreshClient()	Rebuilds the client from scratch.
Future<RemoveDatastoreFromDatastoreClusterResponse>	removeDatastoreFromDatastoreCluster(RemoveDatastoreFromDatastoreClusterRequest request, AsyncHandler<RemoveDatastoreFromDatastoreClusterRequest,RemoveDatastoreFromDatastoreClusterResponse> handler)	Remove the specified Datastore from the provided Datastore Cluster.
void	setEndpoint(String endpoint)	Sets the endpoint to call (ex, https://www.example.com).
void	setRegion(Region region)	Sets the region to call (ex, Region.US_PHOENIX_1).
void	setRegion(String regionId)	Sets the region to call (ex, ‘us-phoenix-1’).
Future<UpdateDatastoreClusterResponse>	updateDatastoreCluster(UpdateDatastoreClusterRequest request, AsyncHandler<UpdateDatastoreClusterRequest,UpdateDatastoreClusterResponse> handler)	Updates the specified Datastore Cluster.
void	useRealmSpecificEndpointTemplate(boolean realmSpecificEndpointTemplateEnabled)	Determines whether realm specific endpoint should be used or not.

Methods inherited from interface java.lang.AutoCloseable

close

Method Detail

refreshClient

void refreshClient()

Rebuilds the client from scratch.

Useful to refresh certificates.

setEndpoint

void setEndpoint(String endpoint)

Sets the endpoint to call (ex, https://www.example.com).

Parameters:

endpoint - The endpoint of the serice.

getEndpoint

String getEndpoint()

Gets the set endpoint for REST call (ex, https://www.example.com)

setRegion

void setRegion(Region region)

Sets the region to call (ex, Region.US_PHOENIX_1).

Note, this will call setEndpoint after resolving the endpoint. If the service is not available in this region, however, an IllegalArgumentException will be raised.

Parameters:

region - The region of the service.

setRegion

void setRegion(String regionId)

Sets the region to call (ex, ‘us-phoenix-1’).

Note, this will first try to map the region ID to a known Region and call setRegion.

If no known Region could be determined, it will create an endpoint based on the default endpoint format (Region.formatDefaultRegionEndpoint(Service, String) and then call setEndpoint.

Parameters:

regionId - The public region ID.

useRealmSpecificEndpointTemplate

void useRealmSpecificEndpointTemplate(boolean realmSpecificEndpointTemplateEnabled)

Determines whether realm specific endpoint should be used or not.

Set realmSpecificEndpointTemplateEnabled to “true” if the user wants to enable use of realm specific endpoint template, otherwise set it to “false”

Parameters:

realmSpecificEndpointTemplateEnabled - flag to enable the use of realm specific endpoint template

addDatastoreToDatastoreCluster

Future<AddDatastoreToDatastoreClusterResponse> addDatastoreToDatastoreCluster(AddDatastoreToDatastoreClusterRequest request,
                                                                              AsyncHandler<AddDatastoreToDatastoreClusterRequest,AddDatastoreToDatastoreClusterResponse> handler)

Add the specified Datastore to the provided Datastore Cluster.

Parameters:

request - The request object containing the details to send

handler - The request handler to invoke upon completion, may be null.

Returns:

A Future that can be used to get the response if no AsyncHandler was provided. Note, if you provide an AsyncHandler and use the Future, some types of responses (like java.io.InputStream) may not be able to be read in both places as the underlying stream may only be consumed once.

attachDatastoreClusterToCluster

Future<AttachDatastoreClusterToClusterResponse> attachDatastoreClusterToCluster(AttachDatastoreClusterToClusterRequest request,
                                                                                AsyncHandler<AttachDatastoreClusterToClusterRequest,AttachDatastoreClusterToClusterResponse> handler)

Attach the specified Datastore Cluster to the provided Vmware Cluster.

Use the WorkRequest operations to track the attachment of the Datastore.

Parameters:

request - The request object containing the details to send

handler - The request handler to invoke upon completion, may be null.

Returns:

A Future that can be used to get the response if no AsyncHandler was provided. Note, if you provide an AsyncHandler and use the Future, some types of responses (like java.io.InputStream) may not be able to be read in both places as the underlying stream may only be consumed once.

attachDatastoreClusterToEsxiHost

Future<AttachDatastoreClusterToEsxiHostResponse> attachDatastoreClusterToEsxiHost(AttachDatastoreClusterToEsxiHostRequest request,
                                                                                  AsyncHandler<AttachDatastoreClusterToEsxiHostRequest,AttachDatastoreClusterToEsxiHostResponse> handler)

Attach the specified Datastore Cluster to the provided ESXi Hosts.

Use the WorkRequest operations to track the attachment of the Datastore.

Parameters:

request - The request object containing the details to send

handler - The request handler to invoke upon completion, may be null.

Returns:

A Future that can be used to get the response if no AsyncHandler was provided. Note, if you provide an AsyncHandler and use the Future, some types of responses (like java.io.InputStream) may not be able to be read in both places as the underlying stream may only be consumed once.

changeDatastoreClusterCompartment

Future<ChangeDatastoreClusterCompartmentResponse> changeDatastoreClusterCompartment(ChangeDatastoreClusterCompartmentRequest request,
                                                                                    AsyncHandler<ChangeDatastoreClusterCompartmentRequest,ChangeDatastoreClusterCompartmentResponse> handler)

Moves an Datastore Cluster into a different compartment within the same tenancy.

For information about moving resources between compartments, see Moving Resources to a Different Compartment.

Parameters:

request - The request object containing the details to send

handler - The request handler to invoke upon completion, may be null.

Returns:

A Future that can be used to get the response if no AsyncHandler was provided. Note, if you provide an AsyncHandler and use the Future, some types of responses (like java.io.InputStream) may not be able to be read in both places as the underlying stream may only be consumed once.

createDatastoreCluster

Future<CreateDatastoreClusterResponse> createDatastoreCluster(CreateDatastoreClusterRequest request,
                                                              AsyncHandler<CreateDatastoreClusterRequest,CreateDatastoreClusterResponse> handler)

Creates a Oracle Cloud VMware Solution Datastore Cluster.

Parameters:

request - The request object containing the details to send

handler - The request handler to invoke upon completion, may be null.

Returns:

A Future that can be used to get the response if no AsyncHandler was provided. Note, if you provide an AsyncHandler and use the Future, some types of responses (like java.io.InputStream) may not be able to be read in both places as the underlying stream may only be consumed once.

deleteDatastoreCluster

Future<DeleteDatastoreClusterResponse> deleteDatastoreCluster(DeleteDatastoreClusterRequest request,
                                                              AsyncHandler<DeleteDatastoreClusterRequest,DeleteDatastoreClusterResponse> handler)

Deletes the specified Datastore Cluster.

Parameters:

request - The request object containing the details to send

handler - The request handler to invoke upon completion, may be null.

Returns:

A Future that can be used to get the response if no AsyncHandler was provided. Note, if you provide an AsyncHandler and use the Future, some types of responses (like java.io.InputStream) may not be able to be read in both places as the underlying stream may only be consumed once.

detachDatastoreClusterFromCluster

Future<DetachDatastoreClusterFromClusterResponse> detachDatastoreClusterFromCluster(DetachDatastoreClusterFromClusterRequest request,
                                                                                    AsyncHandler<DetachDatastoreClusterFromClusterRequest,DetachDatastoreClusterFromClusterResponse> handler)

Detach the specified Datastore Cluster from the provided Vmware Cluster.

Use the WorkRequest operations to track the detachment of the Datastore.

Parameters:

request - The request object containing the details to send

handler - The request handler to invoke upon completion, may be null.

Returns:

A Future that can be used to get the response if no AsyncHandler was provided. Note, if you provide an AsyncHandler and use the Future, some types of responses (like java.io.InputStream) may not be able to be read in both places as the underlying stream may only be consumed once.

detachDatastoreClusterFromEsxiHost

Future<DetachDatastoreClusterFromEsxiHostResponse> detachDatastoreClusterFromEsxiHost(DetachDatastoreClusterFromEsxiHostRequest request,
                                                                                      AsyncHandler<DetachDatastoreClusterFromEsxiHostRequest,DetachDatastoreClusterFromEsxiHostResponse> handler)

Detach the specified Datastore Cluster from the provided ESXi Hosts.

Use the WorkRequest operations to track the detachment of the Datastore.

Parameters:

request - The request object containing the details to send

handler - The request handler to invoke upon completion, may be null.

Returns:

A Future that can be used to get the response if no AsyncHandler was provided. Note, if you provide an AsyncHandler and use the Future, some types of responses (like java.io.InputStream) may not be able to be read in both places as the underlying stream may only be consumed once.

getDatastoreCluster

Future<GetDatastoreClusterResponse> getDatastoreCluster(GetDatastoreClusterRequest request,
                                                        AsyncHandler<GetDatastoreClusterRequest,GetDatastoreClusterResponse> handler)

Get the specified Datastore Cluster information.

Parameters:

request - The request object containing the details to send

handler - The request handler to invoke upon completion, may be null.

Returns:

A Future that can be used to get the response if no AsyncHandler was provided. Note, if you provide an AsyncHandler and use the Future, some types of responses (like java.io.InputStream) may not be able to be read in both places as the underlying stream may only be consumed once.

listDatastoreClusters

Future<ListDatastoreClustersResponse> listDatastoreClusters(ListDatastoreClustersRequest request,
                                                            AsyncHandler<ListDatastoreClustersRequest,ListDatastoreClustersResponse> handler)

List the Datastore Clusters in the specified compartment.

The list can be filtered by compartment, Datastore Cluster, Display name and Lifecycle state

Parameters:

request - The request object containing the details to send

handler - The request handler to invoke upon completion, may be null.

Returns:

A Future that can be used to get the response if no AsyncHandler was provided. Note, if you provide an AsyncHandler and use the Future, some types of responses (like java.io.InputStream) may not be able to be read in both places as the underlying stream may only be consumed once.

removeDatastoreFromDatastoreCluster

Future<RemoveDatastoreFromDatastoreClusterResponse> removeDatastoreFromDatastoreCluster(RemoveDatastoreFromDatastoreClusterRequest request,
                                                                                        AsyncHandler<RemoveDatastoreFromDatastoreClusterRequest,RemoveDatastoreFromDatastoreClusterResponse> handler)

Remove the specified Datastore from the provided Datastore Cluster.

Parameters:

request - The request object containing the details to send

handler - The request handler to invoke upon completion, may be null.

Returns:

A Future that can be used to get the response if no AsyncHandler was provided. Note, if you provide an AsyncHandler and use the Future, some types of responses (like java.io.InputStream) may not be able to be read in both places as the underlying stream may only be consumed once.

updateDatastoreCluster

Future<UpdateDatastoreClusterResponse> updateDatastoreCluster(UpdateDatastoreClusterRequest request,
                                                              AsyncHandler<UpdateDatastoreClusterRequest,UpdateDatastoreClusterResponse> handler)

Updates the specified Datastore Cluster.

*Important:** Updating a Datastore Cluster affects only certain attributes in the `Datastore Cluster` object and does not affect the VMware environment currently running.

Parameters:

request - The request object containing the details to send

handler - The request handler to invoke upon completion, may be null.

Returns:

A Future that can be used to get the response if no AsyncHandler was provided. Note, if you provide an AsyncHandler and use the Future, some types of responses (like java.io.InputStream) may not be able to be read in both places as the underlying stream may only be consumed once.