To prevent a manual conformation for adding a new host to the known_hosts file, you can add this snippet to your ~/.ssh/config file:
This will automatically add any ec2 host to your known_hosts file and sets this file to /dev/null, which prevents a lot of one time ec2 host names in your known_hosts file.
I cannot comment on your NFS sharing performance concerns. You can always start by writing your data in the local scratch space and transferring the end results to the master node in one batch step.
From: Yehuda Landau [mailto:didist_at_gmail.com]
Sent: Monday, November 11, 2013 5:58 PM
To: Steve Darnell
Subject: Re: [StarCluster] technical problem
Thanks for your kind reply
Concerning the same issue of running scripts i have a linux shell script running on my LOCAL machine which starts starcluster cluster
BUT then when i send the first remote command
e.g. startcluster sshmaster mycluster "easy_install [package name]"
I have to confirm the first SSH connection
but if i am not near the keyboard for a minute or two the connection is broken and the script fails
HOW can i make the password less ssh ALSO not to ask the first confirmation
I understand i have to had the ip to the known_hosts file somehow but every time a connect to ec2 i get a different machine?
And another small issue since STARCLUSTER was NFS share for the /home directory of the nodes if my application writes a big amount of data is it better to write it to different directory than /home because the sharing will cause delay?
On Mon, Nov 11, 2013 at 11:28 PM, Steve Darnell <darnells_at_dnastar.com<mailto:darnells_at_dnastar.com>> wrote:
Is 'sgeadmin' even in the sudoers list (/etc/sudoers)? I did not think so, but I do not have a cluster running to confirm. If not, sgeadmin will not have sudo privileges without a configuration change.
Alternatively, the 'ubuntu' user should be preinstalled and configured for password-less sudo by Amazon (http://askubuntu.com/questions/192050/how-to-run-sudo-command-with-no-password
) since the starcluster image is based on an Ubuntu instance.
Another option is to run a single remote command as root with sshmaster/sshnode (http://star.mit.edu/cluster/docs/latest/manual/runcommands.html?highlight=sshmaster
). This approach is functionally similar to sudo with regards to preventing the accidental use of an open root shell. Neither approach will prevent the actual script from doing "bad things" with elevated privileges. This is the approach I have used in the past since it is well supported in starcluster.
From: starcluster-bounces_at_mit.edu<mailto:starcluster-bounces_at_mit.edu> [mailto:starcluster-bounces_at_mit.edu<mailto:starcluster-bounces_at_mit.edu>] On Behalf Of Yehuda Landau
Sent: Monday, November 11, 2013 1:12 PM
Subject: [StarCluster] technical problem
I want to write a bash script and run on an instance
To do so i login as a user (sgeamin) --> starcluster sshmaster -u sgeadmin mycluster
but then i like to run a script using : sudo [script_name]
BUT was is the SU PASSWORD
i know i can login as root but i would prefer not to
Received on Mon Nov 11 2013 - 19:23:03 EST