colearendt/clusterdock

clusterdock's Issues

Figure out differences with `clusterdock/clusterdock`

Figure out what is different with the clusterdock repo and if we can just use it!

Network configuration dependency

clusterdock advertises that you can configure which network you want to use. However, if you use any network other than cluster, the setup hangs and services are left in a weird state. Need to find and resolve the dependency on the network name.

[ec2-user... clusterdock]$ CLUSTERDOCK_IMAGE=clusterdock_manual clusterdock_run ./bin/start_cluster -n test_cloudera cdh                                                
INFO:clusterdock.cluster:Network (test_cloudera) not present, creating it...
INFO:clusterdock.cluster:Successfully setup network (name: test_cloudera).
INFO:clusterdock.cluster:Successfully started node-2.test_cloudera (IP address: 192.168.123.3).
INFO:clusterdock.cluster:Successfully started node-1.test_cloudera (IP address: 192.168.123.2).
INFO:clusterdock.cluster:Started cluster in 21.76 seconds.
INFO:clusterdock.topologies.cdh.actions:Changing server_host to node-1.test_cloudera in /etc/cloudera-scm-agent/config.ini...
INFO:clusterdock.topologies.cdh.actions:Restarting CM agents...
cloudera-scm-agent is already stopped
cloudera-scm-agent is already stopped
Starting cloudera-scm-agent: [  OK  ]
Starting cloudera-scm-agent: [  OK  ]
INFO:clusterdock.topologies.cdh.actions:Waiting for Cloudera Manager server to come online...
INFO:clusterdock.topologies.cdh.actions:Detected Cloudera Manager server after 45.06 seconds.
INFO:clusterdock.topologies.cdh.actions:CM server is now accessible at http://ip-172-30-1-131.us-west-2.compute.internal:32779
INFO:clusterdock.topologies.cdh.cm:Detected CM API v13.
INFO:clusterdock.topologies.cdh.cm_utils:Updating database configurations...
INFO:clusterdock.topologies.cdh.cm:Updating NameNode references in Hive metastore...