Cloudera Docs

Adding CDP Private Cloud Base cluster for use in Replication Manager and Data Catalog (CCMv1)

After you register the CDP Private Cloud Base cluster as a classic cluster using Cloudera Manager and Knox endpoints, you can use the classic cluster in Replication Manager and Data Catalog.

Ensure that the following components and role are available:

  • The CDP Private Cloud Base cluster has an active Knox service.
  • A proxy to Cloudera Manager through Knox for communication purposes. For more information, see Proxy Cloudera Manager through Apache Knox.

  • LDAP is configured in the Cloudera Manager of CDP Private Cloud Base cluster. For more information, see Configure authentication using an LDAP-compliant identity service.

  • A minimum of one LDAP user with the Full Administrator role.
  • An LDAP-based topology with CM-API, CM-UI, ATLAS, ATLAS-API, RANGERUI, and RANGER services. The topology name is used during the classic cluster registration process.
  1. Log in to CDP Management Console.
  2. Click Classic Clusters.
  3. On the Classic Clusters page, click ADD CLUSTER.
  4. In the Add Cluster dialog box, go to the CDP Private Cloud Base tab.
    1. IP address - Enter the IP address of the Cloudera Manager of the CDP Private Cloud Base cluster. The Management Console uses this IP address to identify the cluster for registration purposes.
    2. Port - Enter the port of the Cloudera Manager of the CDP Private Cloud Base cluster.
    3. Data center - Enter a unique datacenter name for the CDP Private Cloud Base cluster.
    4. Select the My cluster runs on HTTPS option if the CDP Private Cloud Base cluster uses HTTPS.
    5. Select the Register KNOX endpoint (Optional) option.
    6. KNOX IP Address - Enter the IP address of the Knox host for the CDP Private Cloud Base cluster.
    7. KNOX Port - Enter the port for the Knox service.
    8. Click CONNECT.

    The Management Console acquires the configuration details from Cluster Connectivity Manager (CCM) service.

  5. On the Classic Clusters page, click Files in the Step 2 pane.
  6. In the Setup Connectivity Client dialog box, click ccm-autossh-client, ssh_tunnel_setup_files or cluster_connectivity_setup_files, and ssh_tunnel_setup_files_knox or cluster_connectivity_setup_files_knox links to download the RPM for AutoSSH from the specified location and the connectivity-installation scripts from CDP and Knox to your machine.
  7. In the Setup Connectivity Client dialog box, click Close.
  8. When the Cloudera Manager and Knox service are on the same host, perform the following steps to create two reverseSSH tunnels to the Cloudera Manager and Knox service:
    1. In the command line interface, copy the RPM and ZIP files to the Cloudera Manager host.
    2. To establish the first SSH tunnel between the Cloudera Manager and Management Console, SSH to the Cloudera Manager host.
    3. Run the following command to install AutoSSH RPM using the ccm-autossh-client rpm file: 
      yum --nogpgcheck localinstall [***downloaded ccm_autossh-client-rpm***]

      If the installation of CCM autossh-client rpm fails with “No package autossh available”, refer to Troubleshooting: Install autossh package.

    4. Extract the ssh_tunnel_setup_files.zip or cluster_connectivity_setup_files.zip file to a temporary directory.
    5. Run the install script in the directory using the ./install.sh command.
    6. Optionally, you can check the Cluster Connectivity Manager (CCM) service status using the systemctl status ccm-tunnel@CM.service command to verify whether the SSH tunnel is established.
    7. To establish the second SSH tunnel between the Knox service and Management Console, extract the ssh_tunnel_setup_files_knox.zip or cluster_connectivity_setup_files_knox.zip file to a temporary directory.
    8. Run the install script in the temporary directory using the ./install.sh command.
    9. Enter the Knox topology details that you created earlier when the Enter knox topology name that contains LDAP setup: prompt appears.
    10. Optionally, you can check the Cluster Connectivity Manager (CCM) service status using the systemctl status ccm-tunnel@KNOX.service command to verify whether the SSH tunnel is established.
  9. When the Cloudera Manager and Knox service are on the different hosts, perform the following steps to create a SSH tunnel to Cloudera Manager and another SSH tunnel to the Knox service:
    1. In the command line interface, copy the ccm-autossh-client, and ssh_tunnel_setup_files or cluster_connectivity_setup_files to the Cloudera Manager host.
    2. To establish the first SSH tunnel between the Cloudera Manager host and and Management Console, SSH to the Cloudera Manager host.
    3. Run the following command to install AutoSSH RPM using the ccm-autossh-client rpm file:
      yum --nogpgcheck localinstall [***downloaded ccm_autossh-client-rpm***]
    4. Extract the ssh_tunnel_setup_files.zip or cluster_connectivity_setup_files.zip file to a temporary directory.
    5. Run the install script in the directory using the ./install.sh command.
    6. Optionally, you can check the Cluster Connectivity Manager (CCM) service status using the systemctl status ccm-tunnel@CM.service command to verify whether the SSH tunnel is established.
    7. To establish the second SSH tunnel between the Knox service and Management Console, copy the ccm-autossh-client and ssh_tunnel_setup_files_knox or cluster_connectivity_setup_files_knox files to the Knox host.
    8. SSH to the Knox host.
    9. Run the following command to install AutoSSH RPM using the ccm-autossh-client rpm file:
      yum --nogpgcheck localinstall [***downloaded ccm_autossh-client-rpm file***]
    10. Extract the ssh_tunnel_setup_files_knox.zip or cluster_connectivity_setup_files_knox.zip file to a temporary directory.
    11. Run the install script in the temporary directory using the ./install.sh command.
    12. Enter the Knox topology details that you created earlier when the Enter knox topology name that contains LDAP setup: prompt appears.
    13. Optionally, you can check the Cluster Connectivity Manager (CCM) service status using the systemctl status ccm-tunnel@KNOX.service command to verify whether the SSH tunnel is established.
  10. On the Classic Clusters page, click Test Connection in the Step 2 pane to verify whether the tunnel connection is successful.
  11. On the Classic Clusters page, click Register in the Step 3 pane.
  12. In the Cluster Details dialog box, enter the Cloudera Manager credentials that has Admin access to Cloudera Manager and the cluster services.
  13. Click CONNECT.
  14. To complete the registration, enter the following details on the Classic Clusters page:
    1. Cluster Location - Enter the geographical location of the Data Lake.
    2. Data Center- Ensure that the data center name is the name that you provided for CDP Private Cloud Base cluster during registration.
    3. Tags - Optionally, enter the tags for the cluster, if any.
    4. Description- Optionally, enter a description.
  15. Click Add.
You can use the registered classic cluster in Replication Manager and Data Catalog.