Changes between Version 25 and Version 26 of JBSsandbox/PlasticSlices


Ignore:
Timestamp:
04/22/14 14:47:09 (7 years ago)
Author:
Josh Smift
Comment:

Added some more ideas about how to deal with failures.

Legend:

Unmodified
Added
Removed
Modified
  • JBSsandbox/PlasticSlices

    v25 v26  
    252252If you find anomalies, you'll probably need to go back to the original output files to figure out where they came from.
    253253
    254 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.
     254This 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. (This is usually just a matter of trying again to create a sliver that failed for whatever reason.
    255255
    256256=== Get login info ===
     
    287287
    288288This 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.
     289
     290For example, if an InstaGENI rack sliver's VMs fail to boot, you can delete it and re-create it (BBN IG in ps104 in this example):
     291
     292{{{
     293somni ps104 ~/rspecs/request/ps104/bbn-instageni-ps104.rspec
     294omni -a $am deletesliver $slicename
     295omni -a $am createsliver $slicename $rspec
     296}}}
     297
     298You can then watch the spew log URL (in the createsliver output, before the manifest), or run sliverstatus to check the status:
     299
     300{{{
     301omni -a $am sliverstatus $slicename |& grep _status
     302}}}
     303
     304Watching the spew log URL is usually a better bet if you can.
    289305
    290306Once you can log in everywhere, commit to Subversion the changes to ~/slices/plastic-slices/ssh_config.