SELinux allows you to set access control through policies. You can set the SELinux mode while creating a new operational database. You can configure the SELinux enforcement for your Cloudera Operational Database using the Cloudera Operational Database UI or CDP CLI. This feature is under technical preview. To use this feature, you must have the CDP_SECURITY_ENFORCING_SELINUX entitlement in your Cloudera environment and the minimum runtime version of 7.2.18.700 or 7.3.1.100. Contact Cloudera support if you do not have this entitlement. Using the CDP CLI: You can define the SELinux mode using the seLinux parameter in the create-database command. The supported SELinux modes are: ENFORCING: Enables SELinux in enforced mode, actively applying security policies. PERMISSIVE (default): Sets SELinux to permissive mode, logging any security violations without enforcing policies. If you do not define the seLinux parameter, by default, the PERMISSIVE mode is applied. The following example shows usage of the seLinux parameter. opdb create-database --environment-name [***ENVIRONMENT_NAME***] --database-name [***DATABASE_NAME***] --security-request '{"seLinux": string}' opdb create-database --environment-name cod-7218-micro1 --database-name testDB --security-request '{"seLinux": "ENFORCING"}' opdb create-database --environment-name cod-7218-micro1 --database-name testDB --security-request '{"seLinux": "PERMISSIVE"}' For more information, see CDP CLI documentation and Setting SELinux Mode. Using the Cloudera Operational Database UI: In the Cloudera Operational Database UI, go to Create Database > Settings > Advanced > SELinux to configure the SELinux enforcement. You can configure the SELinux option as Permissive or Enforcing. This feature is available starting in COD v1.50, and you do not need to upgrade to a higher version of Cloudera Operational Database to benefit from it. Take a tour of the Cloudera Operational Database product, Product Tour. ... View more

Cloudera Operational Database cluster deployments on AWS Graviton environments are now generally available. AWS Graviton is a family of general-purpose, ARM-based processors designed for cloud workloads. Cloudera Operational Database supports the following Graviton versions: Graviton2: Used in Cloudera Operational Database deployments on I4G instances Graviton4: Used in Cloudera Operational Database deployments on I8G instances AWS Graviton processors deliver exceptional price performance for workloads running on AWS EC2. With Graviton4, you can further optimize costs while achieving superior performance. For additional details, see the AWS press release. To help you choose the most suitable ARM processor for your performance requirements, consult the AWS Graviton Processors documentation, which provides a detailed comparison between the Graviton2 and Graviton4 instances. For more information on AWS Graviton support, see AWS Graviton instances in Cloudera Operational Database. This feature is available starting in COD v1.50, and you do not need to upgrade to a higher version of Cloudera Operational Database to benefit from it. Take a tour of the Cloudera Operational Database product, Product Tour. ... View more

Cloudera Operational Database supports setting a user as an ODAdmin at the database level. In earlier versions of the Cloudera Operational Database, you could set the ODAdmin at the environment level only, however, for better usability and enhanced security, now you can set it at the database level too.   This is available starting in COD v1.48 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

Cloudera Operational Database supports creating a database with SELinux enforcement using the Cloudera Operational Database CLI. To use SELinux support, you must have the CDP_SECURITY_ENFORCING_SELINUX entitlement. Please get in touch with Cloudera support if you do not have this entitlement. The SELinux allows you to set access control through policies. You can set the SELinux mode while creating a new operational database. You can define the SELinux mode using the seLinux parameter in the create-database command. The supported SELinux modes are: ENFORCING: Enables SELinux in enforced mode, actively applying security policies. PERMISSIVE (default): Sets SELinux to permissive mode, logging any security violations without enforcing policies. If you do not define the seLinux parameter, by default, the PERMISSIVE mode is applied. The following example shows the usage of the seLinux parameter.   opdb create-database --environment-name [***ENVIRONMENT_NAME***] --database-name [***DATABASE_NAME***] --security-request '{"seLinux": string}' opdb create-database --environment-name cod-7218-micro1 --database-name testDB --security-request '{"seLinux": "ENFORCING"}' opdb create-database --environment-name cod-7218-micro1 --database-name testDB --security-request '{"seLinux": "PERMISSIVE"}'   Doc references: Cloudera CLI documentation Setting SELinux Mode   This is available starting in COD v1.48 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

The feature to scale up the HBase REST server using the Apache HBase REST API is no longer a technical preview and is now generally available (GA).   For more information, see HBase REST server scaling in COD. This is available starting in COD v1.46 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

A new CLI option --switch-instance-type is added to the update-database command to switch the instance types to custom instance types for the COD clusters after the database creation. You must have the COD_USE_CUSTOM_INSTANCE_TYPES entitlement to use this option.   If you plan to scale up the cluster vertically or change the existing instance type to any custom instance type, you can use the --switch-instance-type option. However, the custom instance types must be included in the allowlist by the Cloudera Operational Database. Use the list-supported-instance-types command to fetch the list of supported instance types.   Following is an example of the usage.   cdp opdb update-database --environment-name <env_name> --database-name <database_name> --switch-instance-type instanceGroup=INSTANCEGROUP,instanceType=instancetype  For more information, see CDP CLI documentation. This is available starting in COD v1.46 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

Cloudera Operational Database UI provides two new UI options Configure Database and Configure Edge Nodes to configure the worker and edge node properties in your existing operational database. You can access these menu items using the Actions menu item inside the database details page. For more information, see Configuring a database.  This is available starting in COD v1.46 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

Cloudera Operational Database adds a new CLI command, list-supported-instance-types, allowing you to list the supported instance types for a combination of cloud platform, scale type, and storage type. You can filter using the instance group and architecture as well.   The --custom-instance-types option in the create-database command allows you to pick and choose instance types for the COD. However, it is essential that these instance types are included in the COD allowlist. The list-supported-instance-types command is useful to fetch the list of supported instance types.   Following is an example of the command.   cdp opdb list-supported-instance-types --cloud-platform AZURE --storage-type CLOUD_WITH_EPHEMERAL --scale-type MICRO --instance-group WORKER --architecture X86_64 For more information, see CDP CLI documentation. This is available starting in COD v1.46 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

When you create an operational database with HDFS storage type in an AWS environment, the Operational Database on HDFS clusters now also supports m6i and m7i instances for the applicable nodes. The Operational Database clusters with HDFS storage type are upgraded to enhance the operational database's performance and usability. The following are the new custom instance types supported by the Operational Database. AWS, HEAVY, HDFS: Worker: m6i.4xlarge, m7i.4xlarge Master: m6i.8xlarge, m7i.8xlarge Compute/edge/leader: m6i.2xlarge, m7i.2xlarge Gateway: r6i.8xlarge, r7i.8xlarge AWS, LIGHT, HDFS: Worker: m6i.4xlarge, m7i.4xlarge Compute/edge/leader/gateway: m6i.2xlarge, m7i.2xlarge Master: m6i.4xlarge, m7i.4xlarge This is available starting in COD v1.45 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more

The Cloudera Operational Database CDP CLI adds a new option --custom-instance-types to the create-database command. Using this option, you can define custom instance types; however, the instance types must be included in the allowlist by the Operational Database. Currently, the allowlist is not accessible, however, the following are the new custom instance types supported by the Operational Database. AWS, HEAVY, HDFS: Worker: m6i.4xlarge, m7i.4xlarge Master: m6i.8xlarge, m7i.8xlarge Compute/edge/leader: m6i.2xlarge, m7i.2xlarge Gateway: r6i.8xlarge, r7i.8xlarge AWS, LIGHT, HDFS: Worker: m6i.4xlarge, m7i.4xlarge Compute/edge/leader/gateway: m6i.2xlarge, m7i.2xlarge Master: m6i.4xlarge, m7i.4xlarge The following is a sample output of the create-database command highlighting the usage of the --custom-instance-types option. cdp opdb create-database --environment-name cod_env --database-name cod_db --custom-instance-types masterType=m7i.4xlarge,workerType=m7i.4xlarge,leaderType=m7i.2xlarge,gatewayType=m7i.2xlarge --storage-type=HDFS --scale-type LIGHT The --storage-type option is now optional. If you do not define the --storage-type option, the Operational Database considers the default storage type. The default storage type is blob storage. If the ephemeral storage is enabled, the Operational Database considers the storage type CLOUD_WITH_EPHEMERAL; otherwise, CLOUD is considered. For more information, see CDP CLI documentation. This is available starting in COD v1.45 and you do not need to upgrade to a higher version of COD to benefit from this feature. Try the Cloudera Operational Database for free with Test Drive (no cloud account or setup is needed). ... View more