brutal. Since we don't want to be switching between maprfs/cdh3/cdh4
hadoop client configs while executing on 164, we gotta ssh over to a
target machine, and execute the h2o/hadoop jars that we copied over, all
without any passwords because it's scripted, and then the file that gets
created has to be scp'ed because it tells us the hadoop job has
succeeded and what ip/port to talk to..and the ssh wants to be a
background process. Currently the hadoop job is kicked off as
user=0xdiag