226 | | a. Verify Advertisement for AL2s and utah-stitch aggregate. If the new URN is missing from the '' '''stitching''' '' section, contact the appropriate aggregate team. [[BR]] |
227 | | b. Create stitched slivers with the production SCS that uses the utah-stitch network aggregate by selecting a University of Utah endpoint and any other remote GENI site that supports stitching (ex. utahddc-ig to nysernet-ig; pg-utah to nps-ig)(RSpecs are attached for this step). 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 about updating production SCS. [[BR]] |
228 | | 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" '' . Create a stitched sliver that uses any University of Utah site endpoint and any other remote GENI site that supports stitching (ex. utahddc-ig to gatech-ig)(Rspecs are attached for this step). 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 Test SCS. [[BR]] |
229 | | d. Update the GENI aggregate page for utah-stitch (http://groups.geni.net/geni/wiki/GeniAggregate/UtahStitch) to capture the new stitching ''' ''link'' ''' details. [[BR]] |
230 | | e. Normally the operator page should be reviewed to replace any instances of URN, but there is no such information for the utah-stitch operator page (http://groups.geni.net/geni/wiki/GENIRacksHome/InstageniRacks/Operators/UtahStitch).[[BR]] |
231 | | f. Update http://groups.geni.net/geni/wiki/GeniNetworkStitchingSites#GENIStitchingAL2SPathMappings to replace: [[BR]] |
| 228 | 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]] |
| 229 | |
| 230 | b. Create stitched slivers with the production SCS that uses each of the rack aggregates that were updated and connect 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 about updating production SCS. [[BR]] |
| 231 | |
| 232 | 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 Test SCS. [[BR]] |
| 233 | |
| 234 | d. Update the GENI aggregate page for GENI Aggregate (http://groups.geni.net/geni/wiki/GeniAggregate/) to capture the new stitching ''' ''link'' ''' details. [[BR]] |
| 235 | |
| 236 | e. Review the [http://groups.geni.net/geni/wiki/GENIRacksHome/Operators Operators] page to replace any instances of old URN.[[BR]] |
| 237 | |
| 238 | f. Update "http://groups.geni.net/geni/wiki/GeniNetworkStitchingSites#GENIStitchingAL2SPathMappings to replace any modified interface information, see example from Salt Lake update: [[BR]] |