Creating AWS Graviton-based Cloudera Operational Database clusters

Learn how to create AWS Graviton-based Cloudera Operational Database clusters using the Cloudera Operational Database UI or CDP CLI command.

You can create AWS Graviton-based Cloudera Operational Database clusters using the Cloudera Operational Database UI or by executing CDP CLI commands.

In the Cloudera Operational Database web interface, click Create Database.
Specify the location of the database where you want to store it.
1. Provide a name for the database in the Database Name field.
2. Select the Cloudera environment with which you want to associate the database. The environment does not have to be Graviton-based; it must use a Cloudera version that supports Cloudera Operational Database on Graviton.
3. Click Next.
  If an environment does not exist, you can create one by clicking Create New Environment.
  For more information, see Register your first environment.
Select ARM64 as the Architecture from the drop-down list.
Commission your database by defining a scale for your database using a predefined Data Lake template. Select Heavy Duty.
The template helps you to structure your database automatically thereby saving your time and cost. Cloudera Operational Database creates the predefined number of HEAVY gateway and master nodes, a set of worker nodes, and also adds additional functionalists into the new database. In case you need to modify the default number of nodes defined in the template, you can do so after the database creation.
The available templates are Micro Duty, Light Duty, and Heavy Duty. By default, Light Duty is selected.
Configure your database by selecting the storage type as Cloud Storage with Caching.
The storage type Cloud Storage with Caching is equivalent to using --storage-type CLOUD_WITH_EPHEMERAL option on CDP CLI while creating an operational database.
Check or update the settings for your database.
1. Check all the default settings for your database under the Default tab.
2. Go to the Advanced tab if you need to modify any of the default values.
  - The HDFS Volume Type option appears under the Advanced tab only if you select HDFS as the storage type in the Configuration step.
  - If you disable the Autoscaling option using the Advanced tab, the Worker Nodes and Compute Nodes options are hidden. Instead, a Node Count option appears.
  The minimum and maximum number of worker nodes vary for different storage types.
  - Micro duty: Minimum node count: 1. Maximum node count: 5.
  - Light duty: Minimum node count: 3. Maximum node count: 100.
  - Heavy duty: Minimum node count: 3. Maximum node count: 800.
Review the details before creating the database.
Click Show CLI Command to get the complete command details corresponding to your settings. You can use it to create the database using CDP CLI.
Alternatively, you can use the following sample command to create the database using CDP CLI.
```
cdp opdb create-database --environment-name cod-731 --database-name test --architecture ARM64 --scale-type HEAVY --storage-type CLOUD_WITH_EPHEMERAL --auto-scaling-parameters '{"minWorkersForDatabase":5, "maxWorkersForDatabase":100}' --num-edge-nodes 0
```
Click Create Database.
Alternatively, you can use the CDP CLI to create the Cloudera Operational Database.
1. Launch the beta CDP CLI tool.
2. Run the following command to create Graviton-based Cloudera Operational Database clusters.
  cdp opdb create-database --environment-name [***env_name***] --database-name [***database_name***] --architecture [***string***] --storage-type CLOUD_WITH_EPHEMERAL --scale-type HEAVY
  For example,
```
cdp opdb create-database --environment-name aws_test --database-name cod_7214 --architecture ARM64 --storage-type CLOUD_WITH_EPHEMERAL --scale-type HEAVY
```
On the Cloudera Operational Database UI, an information page is displayed that shows the status of the database. Your new database is ready to be used once its status becomes Available.