This post was originally penned by Lara Rubbelke of Microsoft Azure. You can find the original post here.
Last month Microsoft and Cloudera announced the certification and availability of Cloudera Enterprise in the Azure Marketplace, giving you a quick, easy and optimized way to deploy Cloudera to the cloud. The following will walk you through the steps to provision the cluster and log into Cloudera Manager.
Deploying a New Cloudera Cluster to Azure is a Simple Process
Log into the new preview version of the Azure Portal and select Azure Marketplace. By default you will find this in the lower left corner of the preview portal. When you are in the Azure Marketplace you can search for Cloudera or find Cloudera in the Data + Analytics section. Note that while Azure Marketplace is available in both versions of our portal (our current management portal and the new preview portal), the Cloudera deployment is only available in the new preview version of the Azure Portal.
Select the Cloudera tile and click the “Create” process where you will input information about your cluster configuration.
The “Create Cloudera cluster” blade will require an OpenSSH public key which can be generated using a number of tools. PuTTYgen was used for this example. After you download and run the tool, click on Generate and move the mouse around the blank area of the interface to randomize the key. After the key is generated either save the public key in a text file or copy the key from the PuTTYgen user interface. Paste this key into the SSH Key box in the “Create Cloudera cluster” blade on the portal.
Scroll down the “Create Cloudera cluster” blade and notice the choices in pricing tier, worker configuration, storage pricing and location. Change the value in Worker Configuration to adjust the size of the cluster and Location to choose the region for the cluster. Fill in the remaining information and click “Create” to begin provisioning your Cloudera cluster.
Once the cluster has completed the provisioning process, you can view all cluster resources in the Resource Group.
Note: After the Azure provisioning has completed and you are presented with the resource group blade, additional Cloudera configuration scripts are completing in the background. Additional time may be needed before the cluster is available to load and analyze data. If you log into Cloudera Manager and the cluster data is not yet available wait 5-10 minutes before retrying.
Cloudera Manager is installed on the Management Node with the default endpoint 7180. The naming convention of the Management Node will be your cluster name followed by “-mn”. Open your favorite web browser and navigate to the domain name assigned to the Management Node to access Cloudera Manager. In my example I created a cluster named myclouderacluster, so I will navigate to http://myclouderacluster-mn.cloudapp.net:7180.
Once connected to Cloudera Manager you are presented with a login dialog. Cloudera installs with a default user “admin” and password “admin”. Log in and immediately change the admin account settings! Cloudera has excellent documentation to assist with this process.
After the successful login, you can start working with your Cloudera cluster powered by Microsoft Azure!