Requirements and Supported Versions

The following sections describe the requirements and supported operating systems, databases, and browsers for Cloudera Director.

Continue reading:

Cloud Providers

Cloudera Director has native support for Amazon Web Services (AWS), Google Cloud Platform, and Microsoft Azure.

Each Cloudera Director release embeds the current plug-in for supported cloud providers, but a newer plug-in might have been posted on the Cloudera GitHub site subsequent to the Cloudera Director release. To check for the latest version, click the appropriate link:

Cloudera Director Service Provider Interface (SPI)

The Cloudera Director SPI defines an open source Java interface that plug-ins implement to add support for additional cloud providers to Cloudera Director. For more information, see the README.md file in the SPI Cloudera Director GitHub repository.

Supported Software and Distributions

The table below lists software requirements, recommendations, and supported versions for resources used with Cloudera Director.

  Cloudera Director Cloudera Manager and CDH
Operating Systems (64-bit only)

RHEL and CentOS 6.5, 6.7, 6.8, 7.1, 7.2, and 7.3

Ubuntu 14.04

For AWS: RHEL and CentOS 6.5, 6.7, 6.8, 7.1, 7.2, and 7.3

For Google Cloud Platform: RHEL and CentOS 6.5, 6.7, 6.8, 7.1, 7.2, and 7.3

For Microsoft Azure: RHEL and CentOS 6.7, 6.8, and 7.2

Notes:
  • RHEL 7.2 is supported only for Cloudera Manager and CDH 5.7 and higher.
  • RHEL 7.3 is supported only for Cloudera Manager and CDH 5.10 and higher.
  • AWS supports Spot instances only on Centos operating systems, not on RHEL.
  • To use Amazon EC2 D2 instances, you must run a minimum version of RHEL 6.7 or CentOS 6.7. Earlier versions of RHEL and CentOS do not support these instance types.
Oracle Java SE Development Kit (JDK)

Oracle JDK version 7 or 8

For download and installation information, see Java SE Downloads.

Oracle JDK version 7 or 8
Default Database

Embedded H2 database (not recommended for production use)

Recommended size: 10 GB. For information on shrinking the size of the database, see Shrinking an H2 Database.
Embedded PostgreSQL Database (not recommended for production use)
Supported Databases

MySQL 5.5, 5.6, 5.7

MariaDB 5.5

Recommended size: 10 GB.

MySQL 5.5, 5.6, 5.7

MariaDB 5.5

PostgreSQL 8.1, 8.3, 8.4, 9.1, 9.2, 9.3, 9.4, 9.5

Resource Requirements

The table below lists requirements for resources used with Cloudera Director.

  Cloudera Director Cloudera Manager and CDH
CPU 2 4
RAM 3.75 GB 64 GB
Disk 8 GB 500 GB
Recommended AWS instance c3.large or c4.large

Cloudera Manager: m4.xlarge or m4.4xlarge
Recommended Google Cloud Platform instance n1-standard-2 n1-highmem-4 or n1-highmem-8
Recommended Microsoft Azure instance Standard_D3 or larger
The following Azure instance types are supported:
  • Standard_D12_v2
  • Standard_D13_v2
  • Standard_D14_v2
  • Standard_D15_v2
  • Standard_DS12_v2
  • Standard_DS13_v2
  • Standard_DS14_v2
  • Standard_DS13
  • Standard_DS14
  • Standard_DS15_v2
  • Standard_GS4
  • Standard_GS5

Supported Cloudera Manager and CDH Versions

Cloudera Director 2.7 can install any version of Cloudera Manager 5 with any CDH 5 parcels. Use of CDH packages is not supported.

If you are using Cloudera Director 2.7 to deploy Cloudera Manager and CDH, the latest released version of Cloudera Manager 5.14 and CDH 5.14 is installed by default. To use any other version of Cloudera Manager or CDH, follow the instructions for installing non-default versions of Cloudera Manager and CDH in the Getting Started section for your cloud provider:

Networking and Security Requirements

Cloudera Director recommends the following inbound ports to be open:
  • TCP ports 22: These ports allow SSH to Cloudera Director instance.
  • All traffic across all ports within the security group: This rule allows connectivity with all the components within the Hadoop cluster. This rule avoids numerous individual ports to be opened in the security group.
Type Protocol Port Range Source
SSH (22) TCP (6) 22 0.0.0.0/0
ALL Traffic ALL ALL security_group_id

See note paragraph below.

To connect to the AWS network, Cloudera recommends that you open only these ports and set up a SOCKS proxy. Unless your network has direct connection to AWS, you must set this up to access the Cloudera Director instance. This is done in a later step.

In a restricted network environment, you might want to enable minimal network traffic between instances and keep open ports to a minimum rather than enabling all network traffic between cluster instances. For information about minimal port requirements, see Ports Used by Cloudera Director.

Supported Browsers

Cloudera Director supports the following browsers:
  • Mozilla Firefox 11 and higher
  • Google Chrome
  • Internet Explorer 9 and higher
  • Safari 5 and higher