Skip to content

akn9050/director-scripts

 
 

Repository files navigation

Cloudera Director Public Scripts

Contributing Code

In order to contribute code you must sign one of two agreements. If you are choosing to contribute on your own behalf then sign the ICLA. If you are contributing on behalf of an organization or a company you must sign the CCLA. It is a requirement that you sign one of the license agreements for us to recognize and use the code you have contributed. You only need to sign an agreement once and then can get started. Submit your signed agreements to [email protected]. Thank you for your contributions!

Overview

Cloudera Director has two points during the cluster creation process where custom made user scripts can be run. Bootstrap scripts are run on an instance on startup, and post-creation scripts are run on the cluster level after a cluster has been successfully created. This repository is a collection of freely available example scripts that Cloudera Director users can use to augment their clusters with advanced functionality.

Please refer to the [Cloudera Director documentation] (http://www.cloudera.com/content/cloudera/en/documentation/cloudera-director/latest/topics/director_intro.html) for more details on where and how to add scripts.

Bootstrap scripts

There are currently no example bootstrap scripts available.

Post-creation scripts

high-availability

This post-creation script will configure the HDFS service on a cluster for high availability. The included README.md and example cluster configurations explain how to construct a cluster for use with this script.

There are Groovy and Python implementations of this script. We recommend using the Python script because Python is preinstalled on most linux distributions. The Python script depends on the argparse, cm-api, and retrying libraries, which can be installed by the cm-script-dependency-installer post-creation script.

kerberos

This post-creation script will configure a cluster to use Kerberos for authentication. An existing KDC must be supplied; this is demonstrated in the aws.reference.conf that comes with the Cloudera Director client.

The script depends on the argparse, cm-api, and retrying libraries, which can be installed by the cm-script-dependency-installer post-creation script.

cm-script-dependency-installer

This post-creation script is meant to be run before either high-availability or kerberos. It will install the necessary Python dependencies required for both scripts.

Additional utility scripts

The util directory contains additional utility scripts.

About

Cloudera Director sample code

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Shell 57.2%
  • Python 35.9%
  • Groovy 6.9%