Changes between Version 11 and Version 12 of JBSsandbox/PlasticSlices

Timestamp:

04/21/14 12:53:43 (10 years ago)

Author:

Josh Smift

Comment:

Moved in notes from my general SliceNotes page.

JBSsandbox/PlasticSlices

@@ -226 +226 @@
 If you find anomalies, you'll probably need to go back to the original output files to figure out where they came from.
 
-Using my general slice notes, [wiki:JBSsandbox/SliceNotes#Getlogininfo get login info].
-
-Using my general slice notes, [wiki:JBSsandbox/SliceNotes#Loginstuff do other login-related stuff].
-
-Using my general slice notes, [wiki:JBSsandbox/SliceNotes#Pingteststuff test connectivity]. Trying "the fast way" from one node in each slice is probably good enough, but "the reliable way" will work too if you're not in a hurry.
+This will often expose errors of the form "I don't have a sliver at this aggregate at all, for some reason". Fix any of those before continuing.
+
+Get login info:
+
+{{{
+cd ~/slices/plastic-slices/ssh_config
+for slicename in $slices ; do ams="" ; for rspec in ${rspecs[$slicename]} ; do somni $slicename $rspec ; ams="$ams -a $am" ; done ; readyToLogin --no-keys --output --prefix=$slicename --usercredfile=$HOME/.gcf/$USER-geni-usercred.xml --slicecredfile=$HOME/.gcf/$slicename-cred.xml $ams $slicename ; done
+for slicename in $slices ; do mv -f $slicename-sshconfig.txt $slicename ; rm -f $slicename*.xml $slicename*.json $slicename-logininfo.txt ; done
+}}}
+
+Extract your login info from those files, and put it into your ~/.ssh/config file, via whatever means you find appealing.
+
+Find old SSH keys for IP addresses that ExoGENI has reused, and print lines to remove them:
+
+{{{
+logins grep -- -eg-
+for login in $logins ; do ssh $login true |& grep ssh-keygen | sed -e 's/remove with://' ; done
+}}}
+
+Copy and paste the output (simply exec-ing it doesn't seem to work, and we haven't debugged why); then repeat the above and expect no output.
+
+Make sure you can log in, and that each login's hostname is as expected:
+
+{{{
+logins cat
+shmux -c "hostname" $logins | egrep -v '(.+): \1'
+}}}
+
+Expect no output from that, except possibly messages about new SSH keys. Run it again in that case, and address any other issues if you get any output.
+
+This will often expose errors of the form "I can't log in to my hosts at this aggregate, for some reason". Fix any of those before continuing.
+
+If you want to copy some dotfiles to each host, now would be an opportune time to do that. Josh used to copy the files in his ~/.cfhome directory, like so:
+
+{{{
+for slicename in $slices ; do loginfile=~/tmp/logins-$slicename.txt ; export PSSH_ERRDIR=~/tmp/prsync-errors/$slicename ; prsync -h $loginfile -a ~/.cfhome/ '' ; done
+}}}
+
+Copying in connectivity test files:
+
+{{{
+for slicename in $slices ; do loginfile=~/tmp/logins-$slicename.txt ; export PSSH_ERRDIR=~/tmp/prsync-errors/$slicename ; prsync -h $loginfile -a ~/slices/*/reachability/addrs-$slicename.conf pingtest.conf ; done
+}}}
+
+Log in to one host in each slice, and test connectivity:
+
+{{{
+fping -q -c 10 < pingtest.conf |& grep -v "ICMP Host Unreachable"
+}}}
+
+If anything isn't reachable, debug why not.
 
 Copy in Zoing stuff: