Changes between Version 11 and Version 12 of JBSsandbox/PlasticSlices


Ignore:
Timestamp:
04/21/14 12:53:43 (7 years ago)
Author:
Josh Smift
Comment:

Moved in notes from my general SliceNotes page.

Legend:

Unmodified
Added
Removed
Modified
  • JBSsandbox/PlasticSlices

    v11 v12  
    226226If you find anomalies, you'll probably need to go back to the original output files to figure out where they came from.
    227227
    228 Using my general slice notes, [wiki:JBSsandbox/SliceNotes#Getlogininfo get login info].
    229 
    230 Using my general slice notes, [wiki:JBSsandbox/SliceNotes#Loginstuff do other login-related stuff].
    231 
    232 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.
     228This 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.
     229
     230Get login info:
     231
     232{{{
     233cd ~/slices/plastic-slices/ssh_config
     234for 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
     235for slicename in $slices ; do mv -f $slicename-sshconfig.txt $slicename ; rm -f $slicename*.xml $slicename*.json $slicename-logininfo.txt ; done
     236}}}
     237
     238Extract your login info from those files, and put it into your ~/.ssh/config file, via whatever means you find appealing.
     239
     240Find old SSH keys for IP addresses that ExoGENI has reused, and print lines to remove them:
     241
     242{{{
     243logins grep -- -eg-
     244for login in $logins ; do ssh $login true |& grep ssh-keygen | sed -e 's/remove with://' ; done
     245}}}
     246
     247Copy 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.
     248
     249Make sure you can log in, and that each login's hostname is as expected:
     250
     251{{{
     252logins cat
     253shmux -c "hostname" $logins | egrep -v '(.+): \1'
     254}}}
     255
     256Expect 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.
     257
     258This 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.
     259
     260If 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:
     261
     262{{{
     263for slicename in $slices ; do loginfile=~/tmp/logins-$slicename.txt ; export PSSH_ERRDIR=~/tmp/prsync-errors/$slicename ; prsync -h $loginfile -a ~/.cfhome/ '' ; done
     264}}}
     265
     266Copying in connectivity test files:
     267
     268{{{
     269for 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
     270}}}
     271
     272Log in to one host in each slice, and test connectivity:
     273
     274{{{
     275fping -q -c 10 < pingtest.conf |& grep -v "ICMP Host Unreachable"
     276}}}
     277
     278If anything isn't reachable, debug why not.
    233279
    234280Copy in Zoing stuff: