New Features and Changes in Cloudera Director

New Features and Changes in Cloudera Director 2

The following sections describe what’s new and changed in each Cloudera Director 2 release.

A number of issues have been fixed. See Issues Fixed in Cloudera Director 2.2.0 for details.
Support for AWS EBS volumes. See Using EBS Volumes for Cloudera Manager and CDH.
On-demand and automatically-upon-failure diagnostic data collection. See Diagnostic Data Collection.
Improved readability and validation of input configuration files.
Support for Cloudera 5.9 out of the box.
Support for the following Microsoft Azure Storage Account types. Refer to the Cloudera Reference Architecture on Azure for supported configurations using these Storage Account types:
- PremiumLRS
- StandardLRS
Support for Azure’s P20 (512 GiB) disk type for Premium Storage Accounts. This is in addition to the already-supported P30 disk type. Refer to the Cloudera Reference Architecture on Azure for supported disk size configurations.
On Microsoft Azure, support for the RHEL 7.2 image published by Red Hat in partnership with Microsoft and the CentOS 7.2 image published by Cloudera.

A number of issues have been fixed. See Issues Fixed in Cloudera Director 2.1.1 for details.
Cloudera Director now includes support for the following Microsoft Azure instance types:
- Standard_DS12_v2
- Standard_DS13_v2
- Standard_DS14_v2
On Microsoft Azure, Cloudera Director now supports the RHEL 6.7 image published by Red Hat in partnership with Microsoft.

Usage-based billing, where the cost of running a cluster is based on cluster usage, is supported. See Usage-Based Billing.
Running CM and CDH clusters on Microsoft Azure is supported. See Getting Started on Microsoft Azure
Deploying Cloudera Manager and CDH on a different cloud provider or region than Cloudera Director with a simple network setup is supported. See Running Cloudera Director and Cloudera Manager in Different Regions or Clouds.
Cloudera 5.7 is supported out of the box.
A number of issues have been fixed. See Issues Fixed in Cloudera Director 2.1.0 for details.

AWS Spot Instances and Google Cloud Platform Preemptible Instances are supported.
Setup of clusters that are highly available and authenticated through Kerberos is automated.
You can automate submission of jobs to clusters with dynamic creation and termination of clusters.
You can run custom scripts after cluster setup and before cluster termination.
The user interface is enhanced, with deeper insights into cluster health.
Reliability of cluster modifications is increased, including rollback in some failure scenarios.
RHEL 7.1 is supported.
A number of issues have been fixed. See Issues Fixed in Cloudera Director 2.0.0 for details.

The following sections describe what’s new and changed in each Cloudera Director 1 release.

Cloudera Director now supports RHEL 6.7.
A number of issues have been fixed. See Issues Fixed in Cloudera Director 1.5.2 for details.

A number of issues have been fixed. See Issues Fixed in Cloudera Director 1.5.1 for details.

Cloudera Director now supports multiple cloud providers through an open-source plugin interface, the Cloudera Director Service Provider Interface (Cloudera Director SPI).
Google Cloud Platform is now supported through an open-source implementation of the Cloudera Director SPI, the Cloudera Director Google Plugin.
Database servers set up by Cloudera Director can now be managed from the web UI.
You can now specify custom scripts to be run after cluster creation. Example scripts for enabling HDFS high availability and Kerberos are available on the Cloudera GitHub site.
The Cloudera Director database can now be encrypted. Encryption is enabled by default for new installations.
Cluster and Cloudera Manager configurations can now be set through the web UI.
A number of issues have been fixed. See Issues Fixed in Cloudera Director 1.5.0 for details.

A number of issues have been fixed. See Issues Fixed in Cloudera Director 1.1.3 for details.
The Cloudera Director disk preparation method now supports RHEL 6.6, which is supported by Cloudera Manager 5.4.
Custom endpoints for AWS Identity and Access Management (IAM) are now supported.
To ensure version compatibility between Cloudera Manager and CDH, Cloudera Director now defaults to installing the latest 5.3 version of Cloudera Manager and CDH, rather than installing the latest post-5.3 version.

A number of issues have been fixed. See Issues Fixed in Cloudera Director 1.1.2 for details.

A number of issues have been fixed. See Issues Fixed in Cloudera Director 1.1.1 for details.

Support for demand-based shrinking of clusters
Integration with Amazon RDS to enable end-to-end setup of clusters as well as related databases
Native client bindings for Cloudera Director API in Java and Python
Faster bootstrap of Cloudera Manager and clusters
Improved User Interface of Cloudera Director server including display of health of clusters and ability to customize cluster setups
Improvements to usability and documentation

Categories: Director | New Features | Release Notes | All Categories