Changes between Version 28 and Version 29 of URNConsolidation


Ignore:
Timestamp:
07/13/16 14:54:46 (8 years ago)
Author:
asydney@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • URNConsolidation

    v28 v29  
    247247When the updates are completed for all Aggregates and for the SCS servers, testing takes place to verify the URN changes. Validation includes:
    248248
    249  a. Verify Advertisement for AL2s and GENI aggregate that were updated. If the new URN is missing from the '' '''stitching''' '' section, contact the appropriate aggregate team. [[BR]]
    250 
    251  b. Create stitched slivers with the production SCS that uses each of the rack aggregates that were updated and connects it to a remote stitching site.   Login in to one node for each sliver and leave some ping traffic running.  _DO NOT_ delete these slivers used later in monitoring verification. If Production SCS reports unknown path, contact Luke or AJ about updating the production SCS. [[BR]]
    252 
    253  c. Create stitched slivers with the test SCS, which can be done by using the omni/stitcher option '' "--scsURL https://nutshell.maxgigapop.net:8443/geni/xmlrpc" '' that uses each of the rack aggregates that were updated and connect them to a remote stitching site.    Login in to one node for each sliver and leave some ping traffic running.  _DO NOT_ delete these slivers used later in monitoring verification. If Test SCS reports unknown path contact Xi about updating the Test SCS. [[BR]]
    254 
    255  d. Update the GENI aggregate page for GENI Aggregate (http://groups.geni.net/geni/wiki/GeniAggregate/) to capture the new stitching ''' ''link'' ''' details. [[BR]]
    256 
    257  e. Review the [http://groups.geni.net/geni/wiki/GENIRacksHome/Operators Operators] page to replace any instances of old URNs or old switch/port names.  Check the network drawings as well as the text.  It is OK to add notes to the network drawing section, because revising the drawings usually requires getting a new drawing from the site, which takes longer than the scheduled outage.[[BR]]
    258  
    259  f. Review the GENI VLAN Delegation page at https://wiki.maxgigapop.net/twiki/bin/view/GENI/StaticNetworksView, to make sure that instances of the old switch name no longer appear. If old instances appear, send email to GPO Infrastructure group (gpo-infra@geni.net) and cc: Ali Sydney (asydney@bbn.com) to make corrections.
    260 
    261  g. Update "http://groups.geni.net/geni/wiki/GeniNetworkStitchingSites#GENIStitchingAL2SPathMappings to replace any modified interface information, see example from Salt Lake update: [[BR]] 
     249 * Verify Advertisement for AL2s and GENI aggregate that were updated. If the new URN is missing from the '' '''stitching''' '' section, contact the appropriate aggregate team. [[BR]]
     250
     251 * Create stitched slivers with the production SCS that uses each of the rack aggregates that were updated and connects it to a remote stitching site.   Login in to one node for each sliver and leave some ping traffic running.  _DO NOT_ delete these slivers used later in monitoring verification. If Production SCS reports unknown path, contact Luke or AJ about updating the production SCS. [[BR]]
     252
     253 * Create stitched slivers with the test SCS, which can be done by using the omni/stitcher option '' "--scsURL https://nutshell.maxgigapop.net:8443/geni/xmlrpc" '' that uses each of the rack aggregates that were updated and connect them to a remote stitching site.    Login in to one node for each sliver and leave some ping traffic running.  _DO NOT_ delete these slivers used later in monitoring verification. If Test SCS reports unknown path contact Xi about updating the Test SCS. [[BR]]
     254
     255 * Update the GENI aggregate page for GENI Aggregate (http://groups.geni.net/geni/wiki/GeniAggregate/) to capture the new stitching ''' ''link'' ''' details. [[BR]]
     256
     257 * Review the [http://groups.geni.net/geni/wiki/GENIRacksHome/Operators Operators] page to replace any instances of old URNs or old switch/port names.  Check the network drawings as well as the text.  It is OK to add notes to the network drawing section, because revising the drawings usually requires getting a new drawing from the site, which takes longer than the scheduled outage.[[BR]]
     258 
     259 * Review the GENI VLAN Delegation page at https://wiki.maxgigapop.net/twiki/bin/view/GENI/StaticNetworksView, to make sure that instances of the old switch name no longer appear. If old instances appear, send email to GPO Infrastructure group (gpo-infra@geni.net) and cc: Ali Sydney (asydney@bbn.com) to make corrections.
     260
     261 * Update "http://groups.geni.net/geni/wiki/GeniNetworkStitchingSites#GENIStitchingAL2SPathMappings to replace any modified interface information, see example from Salt Lake update: [[BR]] 
    262262   
    263263    ||''' Router'''           ||''' Interface''' ||''' Site ''' ||''' VLAN Range''' ||
     
    269269    ||salt.net.internet2.edu  || et-4/3/0        || utah-stitch || 2100-3499      ||[[BR]]
    270270 
    271  h. GENI Monitoring URN Validation. Login into https://genimondev.uky.edu and use the '' '''search''' '' feature to find all data relating to the new AL2S switch, for example "rtsw.salt.net.internet2.edu". Make sure the following are returned:
     271 * GENI Monitoring URN Validation. Login into https://genimondev.uky.edu and use the '' '''search''' '' feature to find all data relating to the new AL2S switch, for example "rtsw.salt.net.internet2.edu". Make sure the following are returned:
    272272  * a switch is listed with the new name "rtsw.salt.net.internet2.edu",
    273273  * interface statistics are available for the new switch,
    274274  * VLAN are being reported for the new switch[[BR]]   
    275275 
    276  i. Report back about test finding or any outstanding/unresolved issues.
     276 * Report back about test finding or any outstanding/unresolved issues.
    277277
    278278