Start of an API for getting SSH keys installed in the right place.
Some more of the test suite.
Merge remote-tracking branch 'origin/master' into flocker-deploy-ssh-config-71
Merge remote-tracking branch 'origin/master' into flocker-deploy-ssh-config-71
Merge branch 'reusable-conch-test-server' into flocker-deploy-ssh-config-71
Generate the key.
Start trying to get keys into place on the node.
Merge branch 'reusable-conch-test-server' into flocker-deploy-ssh-config-71
mess up the tests a bunch

this is what happens when you don't make APIs asynchronous, folks.

also run a bunch of child processes, wee.
Merge branch 'reusable-conch-test-server' into flocker-deploy-ssh-config-71
Merge remote-tracking branch 'origin/master' into flocker-deploy-ssh-config-72
``configure_ssh`` assumes you can already authenticate against the nodes.
Create the directories which hold the files we want to write, if necessary.
Clean up the whitespace in the key material.
These will succeed just as the rest will succeed.  There is an SSH server running, after all.
Properly run the blocking ``configure_ssh`` function in a separate thread in one more place that was missed previously.  Also suppress output from ``ssh-add`` and do better key comparison in one more place.
Do not write duplicate entries to authorized_keys.
Put these in a more sensible location.
Adjust imports to reflect move.
expose the interface to the public