When you create your instance, the default root drive is 8GB. You should change this to a larger size, maybe 50GB.   If you are creating this manually through the AWS Console, this is on "Step 4. Add Storage" in the launch instance wizard.   ... View more

Ankita,   The solution to running out of disk space is to provision an instance with a larger root partition.   What version of Cloudera Director are you running? Director does not support creation of CM or CDH instances on Ubuntu. See http://www.cloudera.com/documentation/director/latest/topics/director_deployment_requirements.html for supported versions.   Are you provisioning your instances through Director's UI or conf file?   If using Director's UI, can you provide the instance template you are using? If using conf file, can you provide the conf file you are using (with sensitive information removed)?   Also, the output of your df command did not appear to come through in your last post. Can you include that information also?   David   ... View more

Ankita,   As you've found out, CM will re-download the parcels if you delete them so you'll have to figure out why you are running out of disk space.   Can you provide the following information?   - Was this CM provisioned through Cloudera Director? I wouldn't expect this problem on instances that Director provisions unless there is a configuration issue or some error resizing the root partition on this ami.   - What is the ami id?   - Can you provide the output of your df command? I'd like to see the size of the root partition.   David ... View more

Ankita,   The no space left error likely indicates that your root partition is too small. You can check the size and usage of your mounted disks with the 'df' command.   Are you using Cloudera Director to create your CM or CDH instances? Cloudera Director by default will create a 50GB EBS drive as the root partition and will automatically resize the filesystem to use the whole disk.   Can you provide more information about what instance type and ami you are using as well as the the disk size and usage information?     David ... View more

Cerno,   Here's some answers to your questions.   1. The public IP or hostname should be used. The quickstart creates a new VPC and you will not be able to resolve private IPs from outside the VPC.   2. You enter the tunnel command in a new terminal window on your machine. I looked at the instructions and I did not see a terminal window created in Step 3.1. Step 3.1 looks like it's for determining what the ssh command is. I.e., Step 3.1 shows that you use the public IP to ssh along with the user name since some amis use different user names (e.g., "ec2-user", "root", or "centos" are common usernames). The username for the ClusterLauncher is  "ec2-user".   2. Cloudera Director runs on port 7189. Cloudera Manager runs on port 7180. You will be tunnelling to 7189 for access to Cloudera Director.   3. ProxySwitch Omega is used in conjunction with a SOCKS proxy to allow you to access all cluster instance UIs through your browser without the need to tunnel each connection individually. You need to activate the proxy profile in your browser as well open an ssh connection with the -CD <port> option. Can you describe the steps taken and your symptoms in more detail? We may be able to help if you provide some more information on the problems you are encountering.   4. The quickstart installs Cloudera Director from RPM and then seeds it with an environment and instance templates for your convenience. If you are manually installing Cloudera Director in your own VPC you would need to manually create the Environment and InstanceTemplates to point to the correct subnets, security groups, amis, credentials, etc. I think everything is ready if you have confirmed that Cloudera Director is running.   Also note that AWS has a forum for discussing quick start issues. You may find answers to issue with the Cloudformation template there. https://forums.aws.amazon.com/forum.jspa?forumID=178   David ... View more

Thanks for the followup. It's really helpful for the community to see the resolution that you have reached.   I've opened up an issue internally to investigate the log message and validation with quotes. I agree that the log message is innocuous. ... View more

This is likely caused by an issue with the version 1.0.1 of the director-google-plugin.   See Known Issues under the heading "Incorrect yum repo definitions for Google Compute Engine RHEL images"   The workaround is to specify the complete image URL for https://www.googleapis.com/compute/v1/projects/rhel-cloud/global/images/rhel-6-v20160119 instead of using the rhel6 alias.   A fix for this issue is expected to be included in the next release of the director-google-plugin and Director.   ... View more