Installing Cloudera Runtime

Upload License File🔗

On the Upload License File page, you can select either the trial version of or upload a license file:

Select one of the following options:
- Upload License
- Try for 60 days. The trial does not require a license file, but the trial expires after 60 days.
If you have a license file for , then perform the following steps to upload the license file:
1. Select Upload License.
2. Click Upload License File.
3. Browse to the location of the license file, select the file, and click Open.
4. Click Upload.
5. Click Continue.
If you select the Try for 60 days option which is Edition Trial, you can upload a license file at a later time. Read the license agreement and select Yes, I accept the Standard License Terms and Conditions if you accept the terms and conditions of the license agreement. Then click Continue.
Click Continue to proceed with the installation.
The Welcome page displays.

Add Cluster🔗

The Add Cluster wizard provides a brief overview of the installation and configuration procedure, as well as some links to relevant documentation.

Click Continue to proceed with the installation.

Setup Auto-TLS🔗

The Setup Auto-TLS page provides instructions for initializing the certificate manager for auto-TLS as part of setting up a new cluster.

This setup assumes that Cloudera Manager is the Certificate Authority (CA) to create and manage all the certificates for the cluster (either self-signed certificates or when Cloudera Manager acts as part of the customer intermediate Certificate Authority (CA) chain).

In case you do not approve adding Cloudera Manager to your intermediate CA chain, it means you are responsible to generate and maintain all the cluster certificates (that is the Use Case 3). In such a case, setting up AutoTLS should not be used.

Click Continue to proceed.

Setup a KDC🔗

A Key Distribution Center (KDC) is required in order to create kerberized clusters. Kerberized clusters are required for Ranger, Atlas, and other services that depend on them.

The Setup KDC for this Cloudera Manager wizard walks you through the steps to configure Cloudera Manager for Kerberos Authentication. On completing the steps, the wizard displays a message indicating that KDC is setup and you can now create kerberized clusters.

note

Setting KDC (Key Distribution Center) as part of Cloudera Manager means allowing Cloudera Manager to create and manage the Kerberos Principal creations for the cluster internally, without involving your external Kerberos server.

In case you want to manage the principals and want to create, remove, or update them on your Kerberos server, then Cloudera Manager can not be set as KDC, and the KDC wizard should not be used (hence the installation will continue without adding Kerberos at this point).

Please note that in such a case, you should not select any service which requires Kerberos (such as Ranger, RangerKMS, Atlas, Knox), and only once AutoTLS or Kerberos is set (post the Cloudera Manager Wizard deployment, separately), you can add these services to the cluster. If you deploy these services without Kerberos, the Ranger policies might not be created correctly and you need to remove them and regenerate them again.

Cluster Basics🔗

The Cluster Basics page allows you to specify the Cluster Name

For new installations, a Regular Cluster (also called a base cluster) is the only option. You can add a compute cluster after you finish installing the cluster.

For more information on regular and compute clusters, and data contexts, see Virtual Private Clusters and SDX.

Enter a cluster name and click Continue.

Specify Hosts🔗

Choose which hosts will run and other managed services.

To enable to automatically discover hosts on which to install and managed services, enter the cluster hostnames or IP addresses in the Hostnames field. You can specify hostname and IP address ranges as follows:


Expansion Range	Matching Hosts
10.1.1.[1-4]	10.1.1.1, 10.1.1.2, 10.1.1.3, 10.1.1.4
host[1-3].example.com	host1.example.com, host2.example.com, host3.example.com
host[07-10].example.com	host07.example.com, host08.example.com, host09.example.com, host10.example.com

You can specify multiple addresses and address ranges by separating them with commas, semicolons, tabs, or blank spaces, or by placing them on separate lines. Use this technique to make more specific searches instead of searching overly wide ranges. Only scans that reach hosts running SSH will be selected for inclusion in your cluster by default. You can enter an address range that spans over unused addresses and then clear the nonexistent hosts later in the procedure, but wider ranges require more time to scan.

Click Search. If there are a large number of hosts on your cluster, wait a few moments to allow them to be discovered and shown in the wizard. If the search is taking too long, you can stop the scan by clicking Abort Scan. You can modify the search pattern and repeat the search as many times as you need until you see all of the expected hosts.
note
scans hosts by checking for network connectivity. If there are some hosts where you want to install services that are not shown in the list, make sure you have network connectivity between the Server host and those hosts, and that firewalls and SE Linux are not blocking access.
Verify that the number of hosts shown matches the number of hosts where you want to install services. Clear host entries that do not exist or where you do not want to install services.
Click Continue.
The Select Repository screen displays.

Select Repository🔗

The Select Repository page allows you to specify repositories for Agent and Other software.

In the Agent section:

Select either Repository or Custom Repository for the Agent software.
If you select Custom Repository, do not include the operating system-specific paths in the URL. For instructions on setting up a custom repository, see Configuring a Local Package Repository.

In the Other software section:

Select the repository type to use for the installation. In the Install Method section select one of the following:
- Use Parcels (Recommended)
  A parcel is a binary distribution format containing the program files, along with additional metadata used by . Parcels are required for rolling upgrades. For more information, see Parcels.
- Use Packages
  A package is a standard binary distribution format that contains compiled code and meta-information such as a package description, version, and dependencies. Packages are installed using your operating system package manager.
  note
  Packages are not supported for 7.0 and higher.
Select the version of or CDH to install. If you do not see the version you want to install:
- Parcels – Click the Parcel Repository & Network Settings link to add the repository URL for your version. If you are using a local Parcel repository, enter its URL as the repository URL.
  Repository URLs for CDH 6 parcels are documented in CDH 6 Download Information
  Repository URLs for the 7 parcels are documented in Download Information
  important
  If you are using a 60-day trial license, use the following Parcel Repository URL (authentication not required):
  https://archive.cloudera.com/cdh7/7.7.1/parcels/
  Under Other Software > CDH version, if you do not view the parcel that you are intending to install, click Parcel Respositories and Network Settings and manually add the parcel repository location from the Download Information page. For example, if you want to install the 7.1.7 Service Packs, you can pick up the parcel repository location information from Download Information page.
  After adding the repository, click Save Changes and wait a few seconds for the URL to be validated. If your host uses an HTTP proxy, click the Proxy Settings button to configure your proxy.
  Note that if you have a Enterprise license and are using 6.3.3 or higher to install a CDH version 6.3.3 or higher, or a version 7.0 or higher using parcels, you do not need to add a username and password or "@" to the parcel repository URL. will authenticate to the archive using the information in your license key file. Use a link to the repository in the following format:
```
https://archive.cloudera.com/p/cdh6/6.x.x/parcels/
```
  If you are using a version of older than 6.3.3 to install CDH 6.3.3 or higher parcels, you must include the username/password and "@" in the repository URL during installation or when you configure a CDH 6.3.3 or higher parcel repository. After you add the repository, click Save Changes and wait a few seconds for the version to appear. If your host uses an HTTP proxy, click the Proxy Settings button to configure your proxy.
  note
  only displays CDH versions it can support. If an available CDH version is too new for your version, it is not displayed. If the parcels do not appear on the Parcels page, ensure that the Parcel URL you entered is correct.
- Packages – If you selected Use Packages, and the version you want to install is not listed, you can select Custom Repository to specify a repository that contains the desired version. Repository URLs for CDH 6 version are documented in CDH 6 Download Information,
  If you are using a local package repository, enter its URL as the repository URL.
note
only displays CDH or versions it can support. If an available version is too new for your version, it is not displayed.
If you selected Use Parcels, specify any Additional Parcels you want to install.
Click Continue.

Select JDK🔗

If you installed your own JDK version, such as Oracle JDK 8, in Step 2: Install Java Development Kit, select Manually manage JDK.

To allow to automatically install the OpenJDK on cluster hosts, select Install a -provided version of OpenJDK.

To install the default OpenJDK that is provided by your operating system, select Install a system-provided version of OpenJDK.

After selecting the applicable boxes, click Continue.

Enter Login Credentials🔗

Enter the root name or username for the root account that has password-less sudo privileges. (In the /etc/sudoers file, the entry for this should like this:
```
%<username> ALL=(ALL) NOPASSWD: ALL
```
Select an authentication method:
- If you select the All hosts accept same password option for password authentication, enter and confirm the password.
- If you select the All hosts accept same private key option for public-key authentication, provide a passphrase and path to the required private key files.
  Generate keys in PEM format by running the following command:
```
ssh-keygen -m pem -t rsa -f ~/.ssh/id_rsa_pem
scp ~/.ssh/id_rsa_pem.pub HOST:.ssh/
ssh HOST 'cat .ssh/id_rsa_pem.pub >> ~/.ssh/authorized_keys'
```
  note
  In the above command HOST is the hostname of a host in the cluster. You must run the second and third command lines on every host in the cluster.
You can modify the default SSH port if necessary.
Specify the maximum number of host installations to run at once. The default and recommended value is 10. You can adjust this based on your network capacity.
Click Continue.

The Install Agents page displays.

Install Agents🔗

The Install Agents page displays the progress of the installation. You can click on the Details link to view the installation log of any host. Optionally, you can click the Abort Installation button to cancel the installation and then view the installation logs to troubleshoot the problem.

If the installation fails on any hosts, you can click the Retry Failed Hosts to retry all failed hosts.

After installing the Agent on all hosts, click Continue.

The Install Parcels page displays.

Install Parcels🔗

If you selected parcels for the installation method, the Install Parcels page reports the installation progress of the parcels you selected earlier. After the parcels are downloaded, progress bars appear representing each cluster host. You can click on an individual progress bar for details about that host.

After the installation is complete, click Continue.

The Inspect Cluster page displays.

Inspect Cluster🔗

The Inspect Cluster page provides a tool for inspecting network performance as well as the Host Inspector to search for common configuration problems. recommends that you run the inspectors sequentially:

Run the Inspect Network Performance tool. You can click Advanced Options to customize some ping parameters.
After the network inspector completes, click Show Inspector Results to view the results in a new tab.
Address any reported issues, and click Run Again (if applicable).
Click Inspect Hosts to run the Host Inspector utility.
After the host inspector completes, click Show Inspector Results to view the results in a new tab.
Address any reported issues, and click Run Again (if applicable).

If the reported issues cannot be resolved in a timely manner, and you want to abandon the cluster creation wizard to address them, then click Cancel.

After addressing any identified problems, select I understand the risks of not running the inspections or the detected issues, let me continue with cluster setup, and then click Finish.

This completes the Add Cluster wizard operation and launches the Add Cluster - Configuration wizard.

Continue to Step 8: Set Up a Cluster Using the Wizard.