Important Notes

Azure Resources Managed by Cloudera Director

The Azure plugin for Cloudera Director creates the following resource:
  • A storage account for each VM. Data drives created by Cloudera Director on Azure have a fixed size of 1 TB.
  • A NIC for each VM.
  • A public IP address for each VM, if public IP addresses are enabled.

Deploying Production Clusters

While the Cloudera Director web UI can be used for proof-of-concept deployments on Azure, you must use the published sample configuration files for production deployments (see Useful Links below). You can modify the sample configuration file to fit your specific deployment environment, remove services you don’t need, and customize the sample bootstrap script. Configurations related to logging and data storage for individual services must not be changed. Deploying a cluster using the Cloudera Director command line interface and configuration file based on the examples ensures a repeatable deployment with the proper settings for Azure.

Refer to the Cloudera Reference Architecture for Microsoft Azure Deployments document for more details.

Deletion Behavior

The deletion behavior is as follows:
  • The storage account created by the plugin is used for the VM OS drive and cluster data drive. If you have manually attached a drive from a different storage account not created by the plugin, it will not be deleted.
  • The NIC created by the plugin is attached to the VM. We assume that only one NIC is used per VM. Do not manually attach NICs to the VM created by the plugin.
  • Deleting the NIC also deletes the public IP (PIP) attached to the NIC. This includes PIPs created by Cloudera Director as well as PIPs attached manually.

Useful Links