8 commits

Author	SHA1	Message	Date
jaffee	a3a1bccd18	don't connect to hosts twice when creating remote cluster	2017-01-13 14:52:42 -06:00
jaffee	2a50ed9c6d	rename ssh stuff for consistency and less stuttering	2017-01-12 14:32:50 -06:00
jaffee	7594e65667	options to build and copy pilosa binary for cluster creation ... also some refactoring	2017-01-12 14:32:50 -06:00
jaffee	537b3878ef	build and copy pilosactl to remote agents	2016-12-22 12:19:18 -06:00
jaffee	73c0ea2f0c	refactor/cleanup remote file creation	2016-12-22 09:23:55 -06:00
jaffee	0c6e6e4f44	creator can set GOMAXPROCS for remote pilosa nodes	2016-12-14 15:05:50 -06:00
jaffee	9d5acdeecd	cleanup cluster shutdown and extra logging	2016-12-14 10:53:14 -06:00
jaffee	968e82d1ad	clean up remote create, kill remote cluster ... Had to jump through some hoops to kill the remote cluster reliably. Not all ssh server implementations respect signals, so in order to kill the cluster, we request a pty for the ssh session. This allows us to send the byte 0x03 which is effectively the same has hitting Ctrl-c in an interactive ssh session. With a pty, just closing the session also seems to kill the remote process.	2016-12-13 16:36:52 -06:00