Andrew Purtell

Is this even a good example? I don't know offhand the original contribution of this example but it looks suspiciously like the old coprocessor we install in our production at...

Tried this: 1. docker build -t clusterdock:apache_hbase_topology apache_hbase_topology 2. Add 'CLUSTERDOCK_TOPOLOGY_IMAGE=clusterdock:apache_hbase_topology' to command invocations. build_cluster: error: argument topology: invalid choice: 'apache_hbase' (choose from 'nodebase', 'cdh') And this: 1. cd apache_hbase_topology...

Here's what worked for me 1. cp -a apache_hbase_topology clusterdock/clusterdock/topologies/apache_hbase 2. docker build -t clusterdock:latest ./clusterdock Proceed with new local clusterdock image 'clusterdock:latest' Now I'm stuck with "build_cluster: error: unrecognized...

Dropping the old '--nodebase-image' argument to build_cluster gets me further along, now INFO:clusterdock.topologies.apache_hbase.actions:Building image docker.io/apache/clusterdock:centos6.6_java-8u91_hadoop-2.7.3-sfdc-1.0.0_hbase-0.98.22-sfdc-1.0.0... Sending build context to Docker daemon 449.2 MB Step 1 : FROM docker.io/apache/clusterdock:centos6.6_nodebase Pulling repository...

I have tried CLUSTERDOCK_IMAGE=clusterdock:latest CLUSTERDOCK_PULL=false clusterdock_run \ ./bin/build_image centos6.6_nodebase followed by CLUSTERDOCK_IMAGE=clusterdock:latest CLUSTERDOCK_PULL=false clusterdock_run \ ./bin/build_cluster -o centos6.6_nodebase apache_hbase ... CLUSTERDOCK_IMAGE=clusterdock:latest CLUSTERDOCK_PULL=false clusterdock_run \ ./bin/build_cluster -o centos6.6 apache_hbase ... Step...

Well, for now I can move forward by changing apache_namespace to "cloudera" in constants.cfg :-)