Registering a Cloudera on premises environment

After you have set up the Cloudera on premises requirements, you can register the environment.

Steps

Management Console UI

Sign into the Cloudera console.
Click Environments.
On the Environments page, click Register Environment.

On the Register Environment page, provide the required information.

Environment

Environments in Cloudera on premises provide shared data, security, and governance (metadata) for your Cloudera AI and Cloudera Data Warehouse applications.


Property	Description
Environment Name	Enter a name for your environment. This name will be used to refer to this environment in Cloudera. Note: Cloudera Data Warehouse service requires that you specify the environment name 45 characters long. This is because Cloudera Data Warehouse uses a deterministic namespace and adds a prefix to the environment name. The length of the namespace ID after Cloudera Data Warehouse applies a prefix to the Environment name, including the hyphen (-), should not exceed 63 characters.

Resource Quota

Optionally you can set quota for CPU, Memory, and GPU resources for this environment. When setting a quota for the environment, ensure that it satisfies the resource requirement of the data services to be created within the environment. However, if you do not specify a quota for a resource, then no quota will be set for that resource at the time of the environment creation.


Property	Description
CPU (Cores)	You can specify a CPU quota (in Cores) for the environment. The quota must be a positive number.
Memory (GB)	You can specify a Memory quota (in GigaBytes) for the environment. The quota must be a positive number.
GPU (Cores)	You can specify a GPU quota (in Cores) for the environment. The quota must be a positive number.

Compute Cluster Resources

To run workloads, you must specify a Kubeconfig file to register a Kubernetes cluster with Cloudera on premises.


Property	Description
Kubernetes Configurations	Click Upload Files, then select a Kubeconfig file to enable Cloudera to access a Kubernetes cluster.
Storage class	The storage class on the OpenShift cluster. If you do not specify this value, the default storage class is used.
Domain	The default domain suffix for workload applications.

Data Lake

A Data Lake refers to the shared security and governance services in a Cloudera Data Center cluster linked to a Cloudera on premises environment, and managed by Cloudera Manager. To register an environment, Cloudera on premises needs to access Cloudera Manager and its Data Lake services.


Parameter	Description
Cloudera Manager URL	The Cloudera Manager URL.
Cloudera Manager Admin Username	The Cloudera Manager administrator user name.
Cloudera Manager Admin Password	The Cloudera Manager administrator password.

Under Data Lake, click Connect.When Cloudera on premises has successfully connected to Cloudera Manager, a confirmation message appears, along with the Data Lake cluster services.
Click Register.The environment page appears. The new environment is also listed on the Environments page.
note
You can repeat steps 2 through 5 to register more environments. If required, you can select a different Data Lake cluster while registering the additional environment. Cloudera Data Services on premises has multiple base cluster support, and users can create multiple environments each pointing to a different base or data lake cluster.

CLI

You can use the following command to create a new environment:

cdp environments create-private-environment \
--environment-name <value> \
--address <value> \
--authentication-token <value> \
----cluster-names <value>

For a detailed description of the command properties, use cdp environments create-private-environment --help

Creating multiple environments with different base or Data Lake clusters

To register an environment with a data lake cluster managed by a Cloudera Manager that is different from your existing Cloudera Manager, you need to add the certificates of the new Cloudera Manager to the Cloudera Management Console. If the existing Cloudera Manager and the new Cloudera Manager share the same root CA, and the root CA is already uploaded as the data lake certificate, then no additional certificate needs to be added.

Cloudera Manager certificates can be accessed from the Cloudera Manager server.

To get the certificate path on the Cloudera Manager server, navigate to the Administration tab on your Cloudera Manager UI.
Select Settings, and within the Settings, select Security as the category.
In the list of settings, Cloudera Manager TLS/SSL Server Keystore File Location points to the Cloudera Manager server certificate. This certificate needs to be combined with the certificates of your existing Cloudera Manager server(s).
note
The combined certificate needs to be in X.509 PEM format.
For information on combining certificates, see Configuring multiple base clusters with ECS .
The combined certificate then needs to be uploaded as a Datalake certificate to Cloudera Management Console > Administration > CA Certificates. This ensures that the Cloudera Data Services on premises cluster is configured to support both the new and the existing data lake clusters.