Hi Kirk - > 1. The application log doesn't reveal the aws CLI commands that are run. Is there a way to > see those commands? Either before (as a dry run feature) or after? Cloudera Director integrates with the AWS API using the Java SDK. There is no straightforward way to translate those method calls as AWS CLI commands you can run standalone. In theory you should be able to figure out how to use the AWS CLI to start similar instances by inspecting the existing ones. > 2. The nodes that get provisioned do not have anything in the /etc/hosts file. How are they resolving each other? > Typically, the hosts file configuration is critical to getting Cloudera Manager to run successfully. We expect DNS configuration to be handled outside of Cloudera Director using different mechanisms: VPC configuration to use AmazonProvidedDNS via DHCP Options Sets custom bootstrap script that Director runs to configure the hostname scripts embedded into a custom AMI that configure the proper hostname during boot and handle DNS registration Cloudera Director doesn't attempt to perform any DNS configs.
... View more
