Create Exascale VM Clusters

This page describes how to create Exascale VM Clusters in Google Cloud.

Oracle Database@Google Cloud lets you create Exascale VM Clusters in the Google Cloud using Google Cloud console and the API.

You must create your Exascale VM Cluster in the same region and zone as your ODB Network to ensure optimal performance and seamless communication.

Each Exascale VM Cluster is associated with an Exascale Storage Vault. An Exascale Storage Vault provides instant, zero-downtime expansion of scalable, high-performance Exadata storage. While provisioning an Exascale VM Cluster, you can choose to create a new Exascale Storage Vault or select an existing one. You can use an Exascale Storage Vault with multiple Exascale VM Clusters.

For a list of regions and zones in which you can create Exascale VM Clusters, see Supported regions and zones.

Before you begin

Set up the gcloud CLI and enable the API.
Confirm that you have an active marketplace order for Oracle Database@Google Cloud.
Enable the Oracle Database@Google Cloud API for the project.

Enable the Oracle Database@Google Cloud API
Create an ODB Network and ODB Subnets. A DB system requires a single client subnet.
Confirm that you have the required Identity and Access Management (IAM) roles and permissions to create an Exascale VM Cluster:
- roles/oracledatabase.exadbVmClusterAdmin
- roles/oracledatabase.exascaleDbStorageVaultAdmin
For information on how to assign roles, see Apply IAM roles.

Create an Exascale VM Cluster

To create an Exascale VM Cluster, do the following:

Console

Go to the Exadata Database Service > Exascale Infrastructure page.

Go to Exascale Infrastructure
On VM Clusters page, click Create.
Enter a Display name for your Exascale VM Cluster. This name appears in the Google Cloud console. The display name must be unique within your Google Cloud project.
Enter a VM Cluster ID as a unique identifier for your Exascale VM Cluster. You can't change the Exascale VM Cluster ID later.
Select a Region and a GCP Oracle zone. The region and zone choice is permanent; you can't change it later.
Select an Oracle Grid Infrastructure release.
Select an Oracle Grid Infrastructure version.
Select a Database storage based on the Oracle Grid Infrastructure version you selected.

If you selected 23ai release, then you can select either Exascale 23ai smart storage or Exascale 19c compatible block storage.

If you selected 19c release, then you can only select Exascale 19c compatible block storage.
Enter the following values for VM Cluster configuration:
- Number of VMs in the cluster. The maximum number of VMs per cluster is 10.
- Enabled ECPUs per VM. The number of Enabled ECPUs can range from 8 to 200, and must be entered in multiples of 4.
- Optional: Reserved ECPUs per VM. The number of reserved ECPUs can range from 0 to 192, and must be entered in multiples of 4.
  
  Reserved ECPUs let you scale and maintain consistent performance by eliminating allocation delays.
To configure VM file system storage, enter a value for Storage capacity per VM which is the local storage allocated to each VM.

For Exascale 23ai smart storage, the storage capacity can range from 220 GB to 1100 GB. For Exascale 19c compatible block storage, the storage capacity can range from 260 GB to 1100 GB.
License type. The available options are License included and Bring Your Own License.
Configure an Exascale Storage Vault for your cluster.

Choose an existing vault or create a new one that meets your cluster's capacity, performance, and security requirements.
- To use an existing vault, click Select existing vault and choose a vault from the list.
  
  Select a vault that is in the same zone as your Exascale VM Cluster.
- To create a new vault, do the following:
  1. Click Create new vault.
  2. Enter a Display name for your vault. This name appears in the Google Cloud console. The display name must be unique within your Google Cloud project.
  3. Enter a Vault ID as a unique identifier for your vault. You can't change the vault ID later.
  4. Enter a Storage capacity for database. The storage capacity can range from 300 GB to 100000 GB.
    
    Note: The vault's storage capacity must match or exceed the total storage capacity across the cluster.
  5. Enter a value for Smart flash and memory cache.
In the SSH keys section, add the SSH keys you'd like to use for the cluster. To add a key, enter the SSH key name in the SSH Key 1 field. For each additional key, click ADD ITEM.

For more information about how to generate SSH keys, see Generate SSH keys.
In the Networking section, define the network configuration for the DB system:
1. From the Network project list, select the project that contains your ODB Network.
2. Select the ODB Network.
  
  Select an ODB Network that is in the same zone as the your Exascale VM Cluster.
3. Select a Client subnet and a Backup subnet.
4. Enter a Hostname prefix. This prefix can only contain letters, numbers, or hyphens, and must start with a letter. The maximum allowed length is 12 characters.
5. (Optional) In the Advanced network settings section, you can provide a Private IP address. This must be an available IP address within the subnet's CIDR.
  
  If you don't specify an IP address, Google Cloud automatically assigns a private IP address from the subnet.
In the Diagnostics collection section, configure monitoring for your Exascale VM Cluster:
1. Select the Enable diagnostic events checkbox to track all cluster diagnostic events.
2. Select the Enable health monitoring checkbox to use the monitoring console to monitor cluster health metrics.
3. Select the Enable incident logs and trace collection checkbox to enable incident logging for your cluster.
In the Advanced settings, you can optionally modify the following settings:
- Select a Timezone which you'd like to use for diagnostic collection. This timezone applies to event timestamps.
- Assign a SCAN Listener Port (TCP/IP). The port value can range from 1024 to 8999. The default value is 1521.
Click Create.

The provisioning workflow first creates the vault, and then creates the cluster.

API

To create an Exascale VM Cluster using the API, do the following:

Create an Exascale Storage Vault. If you want to use an existing vault, you can skip this step and then proceed to create the Exascale VM Cluster as explained in the next step.

To create an Exascale Storage Vault, run the following curl command:
```
curl -X POST \
-H "Authorization: Bearer $(gcloud auth print-access-token)" \
-H "Content-Type: application/json" \
"https://oracledatabase.googleapis.com/v1/projects/PROJECT_ID/locations/REGION/exascaleDbStorageVaults/VAULT_ID"
-d \
'{
 "display_name": "VAULT_DISPLAY_NAME",
 "gcp_oracle_zone": "GCP_ORACLE_ZONE",
 "name": "projects/PROJECT_ID/locations/REGION/exascaleDbStorageVaults/VAULT_NAME",
 "properties": {
   "exascale_db_storage_details": {
     "total_size_gbs": "STORAGE_SIZE"
    }
  }
}'
```
Replace the following:
- PROJECT_ID: the ID of your Google Cloud project in which to create the vault.
- REGION: the region in which to create the vault.
- VAULT_ID: a unique identifier for your vault.
- VAULT_DISPLAY_NAME: a name for your vault that appears in the Google Cloud console.
- GCP_ORACLE_ZONE: the GCP Oracle zone for your vault. For the list of available regions and zones, see Supported regions and zones.
- VAULT_NAME: a name for your vault.
- STORAGE_SIZE: the storage capacity of your vault. It can range from 300 GB to 100000 GB.
  
  Note: The storage capacity for the vault must match or exceed the total storage capacity across the cluster.
Create an Exascale VM Cluster. Run the following curl command:
```
curl -X POST \
-H "Authorization: Bearer $(gcloud auth print-access-token)" \
-H "Content-Type: application/json" \
"https://oracledatabase.googleapis.com/v1/projects/PROJECT_ID/locations/REGION/exadbVmClusters/CLUSTER_ID"
-d \
'{
 "display_name": "CLUSTER_DISPLAY_NAME",
 "gcp_oracle_zone": "GCP_ORACLE_ZONE",
 "name": "projects/PROJECT_ID/locations/REGION/exadbVmClusters/CLUSTER_NAME",
 "odb_network": "projects/ODB_NETWORK_PROJECT_ID/locations/REGION/odbNetworks/ODB_NETWORK_ID",
 "odb_subnet": "projects/ODB_NETWORK_PROJECT_ID/locations/REGION/odbNetworks/ODB_NETWORK_ID/odbSubnets/CLIENT_SUBNET_ID",
 "backup_odb_subnet": "projects/ODB_NETWORK_PROJECT_ID/locations/REGION/odbNetworks/ODB_NETWORK_ID/odbSubnets/BACKUP_SUBNET_ID",
 "properties": {
   "cluster_name": "CLUSTER_NAME",
   "grid_image_id": GRID_IMAGE_ID,
   "node_count": NODE_COUNT,
   "enabled_ecpu_count_per_node": ENABLED_ECPU_COUNT,
   "additional_ecpu_count_per_node": "ADDITIONAL_ECPU_COUNT",
   "vm_file_system_storage": {
     "size_in_gbs_per_node": STORAGE_SIZE
   },
   "license_model": "LICENSE_TYPE",
   "exascaleDbStorageVault": "projects/PROJECT_ID/locations/REGION/exascaleDbStorageVaults/VAULT_ID",
   "hostname_prefix": "HOSTNAME_PREFIX",
   "ssh_public_keys": ["SSH_PUBLIC_KEY"],
   "data_collection_options": {
     "is_diagnostics_events_enabled": EVENTS_ENABLED,
     "is_health_monitoring_enabled": HEALTH_MONITORING_ENABLED,
     "is_incident_logs_enabled": INCIDENT_LOGS_ENABLE
    },
   "time_zone": {
     "id": "TIMEZONE"
    }
  }
}'
```
Replace the following:
- PROJECT_ID: the ID of your Google Cloud project in which to create the cluster.
- REGION: the region in which to create the cluster.
- CLUSTER_ID: a unique identifier for your cluster.
- CLUSTER_DISPLAY_NAME: a name for your cluster that appears in the Google Cloud console.
- GCP_ORACLE_ZONE: the GCP Oracle zone for your cluster. For the list of available regions and zones, see Supported regions and zones.
- For odb_network, odb_subnet, and backup_odb_subnet properties, replace the following:
  - ODB_NETWORK_PROJECT_ID: the ID of your Google Cloud project which contains your ODB Network. If you're using a Shared VPC, then this is the ID of your host project.
  - REGION: the region of your ODB Network.
  - ODB_NETWORK_ID: the ID of your ODB Network.
  - CLIENT_SUBNET_ID: the ID of your client ODB Subnet.
  - BACKUP_SUBNET_ID: the ID of your backup ODB Subnet.
- CLUSTER_NAME: a name for your cluster.
- GRID_IMAGE_ID: the Oracle Grid Infrastructure release image.
- NODE_COUNT: the number of nodes for your cluster.
- ENABLED_ECPU_COUNT: the number of enabled ECPUs per VM. The number of Enabled ECPUs can range from 8 to 200, and must be entered in multiples of 4.
- ADDITIONAL_ECPU_COUNT: the number of reserved ECPUs per VM. The number of reserved ECPUs can range from 0 to 192, and must be entered in multiples of 4.
- STORAGE_SIZE: storage capacity per VM.
  
  For Exascale 23ai smart storage, the storage capacity can range from 220 GB to 1100 GB. For Exascale 19c compatible block storage, the storage capacity can range from 260 GB to 1100 GB.
- LICENSE_TYPE: the license type associated with your Oracle Database@Google Cloud order. The only accepted values are bring-your-own-license or license-included.
- For exascaleDbStorageVault property, replace the following:
  - PROJECT_ID: the ID of your Google Cloud project which contains your Exascale Storage Vault.
  - REGION: the region of your Exascale Storage Vault.
  - VAULT_ID: the ID of your Exascale Storage Vault.
- HOSTNAME_PREFIX: a hostname prefix. This prefix can only contain letters, numbers, or hyphens, and must start with a letter. The maximum allowed length is 12 characters.
- SSH_PUBLIC_KEY: the SSH public keys for your cluster. You can enter a single value for a single key, or an array of values for multiple keys.
- EVENTS_ENABLED: set to true to track all cluster diagnostic events.
- HEALTH_MONITORING_ENABLED: set to true to enable the use of the monitoring console to monitor cluster health metrics.
- INCIDENT_LOGS_ENABLE: set to true to enable incident logging for your cluster.
- TIMEZONE: the timezone you'd like to use for diagnostic collection. This timezone applies to event timestamps.

What's next

Learn about Exadata Database Service on Exascale Infrastructure
Learn to manage your Exascale VM Clusters.
Learn to delete an Exascale VM Cluster.
Learn to view details of an Exascale VM Cluster.