Your browser is out of date!

Update your browser to view this website correctly. Update my browser now

×

Sign in or complete our product interest form to continue.

Please Read and Accept our Terms

 

Take advantage of CDH in the cloud.

Cloudera Director provides a single administration interface for central IT to deliver agility and for end-users to self-service provision and elastically scale clusters, all while ensuring auditability.

 

Cloudera Director runs as a web application. You can download and install the Cloudera Director server and client by selecting Standard Installation in the dropdown above. If you are new to Cloudera Director, you can get started quickly by selecting AWS Quick Start and following the wizard.

 

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 may have been posted on the Cloudera GitHub site subsequent to the Cloudera Director release. To check for the latest version, click the appropriate link:

Selected tab: CloudProviders

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 for the SPI Cloudera Director GitHub repository.

Selected tab: ClouderaDirectorServiceProviderInterfaceSPI

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, 7.1, and 7.2

Ubuntu 14.04

RHEL and CentOS 6.5, 6.7, 7.1, and 7.2

RHEL 7.2 is supported only for Cloudera Manager and CDH 5.7 and higher, not for lower versions of Cloudera Manager and CDH.

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 Embedded PostgreSQL Database
Supported Databases

MySQL 5.5, 5.6

MariaDB 5.5

MySQL 5.5, 5.6

MariaDB 5.5

 

Note: By default, Cloudera Director stores its environment and cluster data in an embedded H2 database located at /var/lib/cloudera-director-server/state.h2.db. Back up this file to avoid losing the data. For information on using an external MySQL database in place of the H2 embedded database, see Using MySQL for Cloudera Director Server. Cloudera recommends using an external database for both Cloudera Director and Cloudera Manager for production environments.

Selected tab: SupportedSoftwareandDistributions

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

The recommended instance for Cloudera Manager depends on the workload. Contact your Cloudera account representative for more information.

Recommended Google Cloud Platform instance n1-standard-2 n1-highmem-4 or n1-highmem-8
Selected tab: ResourceRequirements

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

Selected tab: SupportedClouderaManagerandCDHVersions

Cloudera Director requires 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.

 

Note: This second rule requires the security group id. If users are creating a security group from scratch, create the security group with the SSH rule and then go back and edit the security group to add allow all traffic within the security group to be allowed.

 

In order to connect to the AWS network Cloudera recommends to open only these ports and set up a SOCKS proxy. Unless your network has direct connection to AWS you will have to set this up to access the Cloudera Director instance. This will be done in a later step.

 

Cloudera Director also expects the following ports to be available in a typical deployment:

  • 7189: Cloudera Director's web interface is open on this port.
  • 80 and 443: Cloudera Director relies on HTTP and HTTPS.
  • 123: Cloudera Director uses this port for NTP.
Selected tab: NetworkingandSecurityRequirements

Cloudera Director supports the following browsers:

  • Mozilla Firefox 11 and higher
  • Google Chrome
  • Internet Explorer 9 and higher
  • Safari 5 and higher
Selected tab: SupportedBrowsers
Selected tab: SystemRequirements

What's New in Cloudera Director 2.1.0

 

Selected tab: WhatsNew

Want to Get Involved or Learn More?

Check out our other resources

Cloudera Community

Collaborate with your peers, industry experts, and Clouderans to make the most of your investment in Hadoop.

Cloudera University

Receive expert Hadoop training through Cloudera University, the industry's only truly dynamic Hadoop training curriculum that’s updated regularly to reflect the state of the art in big data.