Running Cloudera Director Client
After you modify the configuration file, you can run Cloudera Director client. The client can run in standalone mode, or, if you already have a server, you can run the client against the server using the commands bootstrap-remote and terminate-remote. For more information on using the client to deploy clusters on the server, see Submitting a Cluster Configuration File.
- From the cluster launcher, enter the following:
[ec2-user@ip-10-1-1-18 cloudera-director-1.1.0]$ cloudera-director bootstrap aws.conf
Cloudera Director displays output similar to the following:Installing Cloudera Manager ... * Starting ... done * Requesting an instance for Cloudera Manager .................. done * Inspecting capabilities of 10.1.1.194 .............. done * Normalizing 10.1.1.194 ................... done * Installing python (1/4) .... done * Installing ntp (2/4) .... done * Installing curl (3/4) .... done * Installing wget (4/4) ................ done * Installing repositories for Cloudera Manager ............... done * Installing jdk (1/5) ..... done * Installing cloudera-manager-daemons (2/5) ..... done * Installing cloudera-manager-server (3/5) ..... done * Installing cloudera-manager-server-db-2 (4/5) ..... done * Installing cloudera-manager-agent (5/5) .... done * Starting embedded PostgreSQL database ..... done * Starting Cloudera Manager server ...... done * Waiting for Cloudera Manager server to start .... done * Configuring Cloudera Manager ..... done * Starting Cloudera Management Services ...... done * Inspecting capabilities of 10.1.1.194 ......... done * Done ... Cloudera Manager ready. Creating cluster C5-Sandbox-AWS ... * Starting ... done * Requesting 3 instance(s) .......... done * Inspecting capabilities of new instance(s) ....... done * Running basic normalization scripts ......... done * Registering instance(s) with Cloudera Manager .... done * Waiting for Cloudera Manager to deploy agents on instances ... done * Creating CDH4 cluster using the new nodes ...... done * Downloading CDH-4.6.0-1.cdh4.6.0.p0.26 parcel ..... done * Distributing CDH-4.6.0-1.cdh4.6.0.p0.26 parcel ... done * Activating CDH-4.6.0-1.cdh4.6.0.p0.26 parcel ...... done * Done ... Cluster ready. - To monitor Cloudera Director, log in to the cluster launcher and view the application log:
$ ssh ec2-user@54.186.148.151 Last login: Tue Mar 18 20:33:38 2014 from 65.50.196.130 [ec2-user@ip-10-1-1-18]$ tail -f ~/.cloudera-director/logs/application.log [...]