Changes between Version 3 and Version 4 of URNConsolidation
- Timestamp:
- 07/12/16 21:44:48 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
URNConsolidation
v3 v4 3 3 = GENI Switch Consolidation Procedure = 4 4 5 This page defines the steps required to update stitching to handle PoP device consolidation that is taking place in Internet2 AL2S. This consolidation will replace existing AL2S Brocade devices with Juniper devices, and will converge the two distinct devices that currently provide L2 and L3 services into a single converged Juniper device in locations where AL2S services exist. These steps outline the actions required at the GENI rack, AL2S AM, andSCS servers to incorporate URN changes (due to port changes) resulting from the consolidation.6 7 The steps show examples based on details from previous switch consolidation and itseffect on GENI stitching sites connected to this switch.5 This page defines the steps required to update stitching to handle PoP device consolidation that is taking place in Internet2 AL2S. This consolidation effort will replace existing AL2S Brocade devices with Juniper devices, and will converge the two distinct devices that currently provide L2 and L3 services into a single converged Juniper device in locations where AL2S services exist. These steps outline the actions required at the GENI rack, AL2S AM, and at the SCS servers to incorporate URN changes (due to port changes) resulting from the consolidation. 6 7 The steps show examples based on details from previous switch consolidation and their effect on GENI stitching sites connected to this switch. 8 8 9 9 == 0. Generate Tickets and check for conflicts with any upcoming ticketed GENI events == 10 10 11 Make sure tickets are opened at GMOC for the events listing all affected GENI resources. Also make sure that GMOC generates corresponding requests to Internet2 Engineering (GRNOC). Tickets should notify operators and experimenters. Adam Williams will coordinate efforts for GMOC, but initial requests should go to the usual GMOC email for ticket requests. (This has already been done for NYC maintenance.)11 Make sure tickets are opened at GMOC for the events listing all affected GENI resources. Also make sure that GMOC generates corresponding requests to Internet2 Engineering (GRNOC). Tickets should notify operators and experimenters. Adam Williams will coordinate efforts for GMOC, but initial requests should go to the usual GMOC email for ticket requests. 12 12 13 13 Note that Internet2 schedules both an IP and an AL2S outage (usually on different days) for each PoP consolidation. The IP event has no related GENI URN work needed, and will simply result in the GENI resources being unreachable (because the entire device is disconnected). The GMOC should create tickets for both events, since they both have GENI impact, and the rack admins should see the tickets if they read their GENI operators email. … … 15 15 Internet2 won't change their schedule, but you should notify any conflicting events about the maintenance and work with them to avoid any impact as much as possible. 16 16 17 If the event goes longer than the scheduled tickets, be sure to email updates to the GMOC when you know that will happen, and every 2 hours thereafter. If the event will continues to the next day, say so in your last ticket update, and tell them when you'll check in again the next day. (You don't have to update in between).17 If the consolidation event goes longer than the scheduled tickets, be sure to email updates to the GMOC when you know that will happen, and every 2 hours thereafter. If the event will continues to the next day, say so in your last ticket update, and tell them when you'll check in again the next day. (You don't have to update in between). 18 18 19 19 If there are any significant problems during the event, be sure to escalate to Heidi Dempsey (hdempsey@bbn.com) while you work on them (in addition to noting them in the ticket). … … 21 21 == 1. Find Current Stitching Configuration == 22 22 23 The aggregate advertisement includes a ''stitching'' section which defines how VLANs are to be connected and which VLANs are associated with that stitching endpoint. To determine the impact of a consolidation on stitching you must start by collecting the the AL2S advertisement:23 The GENI aggregate advertisement includes a ''stitching'' section which defines how VLANs are to be connected and which VLANs are associated with that stitching site. To determine the impact of a consolidation on stitching you must start by collecting the the AL2S advertisement and reviewing its stitching definitions: 24 24 {{{ 25 25 omni -a al2s listresources -o 26 26 }}} 27 Review the content of the stitching section in the output file rspec-al2s-internet2-edu.xml and see that there any site affected.27 Review the content of the stitching section in the output file rspec-al2s-internet2-edu.xml and see if there any site affected for the switch being consolidated. 28 28 29 29 For example there were several stitching endpoints for sdn-sw.newy32aoa.net.internet2.edu. Here is the list from an AL2S Advertisement: … … 42 42 }}} 43 43 44 From the above we will only request the "<stitch:link id" transition, the "<stitch:port id" transitions are implicit. From the above list there are 6 aggregates (2 InstaGENI, 2 ExoGENI, 1 OpenGENI, 1 network aggregate(iMinds) and 1 fixed endpoint (host-gpolab). 45 46 In Stitching a fixed endpoint is a resource that is not a GENI aggregate but still supports stitching. Fixed endpoint and are statically configured in the SCS servers to capture stitching information and are generally set up for specific demonstrations. 44 From the above we will only request the "<stitch:link id" to be updated, the "<stitch:port id" transitions are implicit. From the above New York switch list there are 6 aggregates (2 InstaGENI, 2 ExoGENI, 1 OpenGENI, 1 network aggregate(iMinds) and 1 fixed endpoint (host-gpolab). 45 46 In Stitching a fixed endpoint is a resource that is not a GENI aggregate but still supports stitching. Fixed endpoints are statically configured in the SCS servers to capture stitching information and are generally set up for specific demonstrations, or peering points. 47 47 48 48 49 49 50 == 2. Define Stitching Configuration Changes == 50 51 51 Review announced changes to define expected changed. Using details from the consolidation email from Eric Boyd of Internet2 for the New York Switch: 52 Review Internet2 announced changes for switch names and ports. Based on the information, identify the changes to be made to stitching definitions. 53 54 For example, using details from the consolidation email from Internet2 for the New York Switch: 52 55 53 56 {{{ … … 77 80 78 81 79 == 3. Request Stitching Changes from GENI Aggregate Operations Teams ==80 81 URN transition require co-ordination with the appropriate team. Following are the teams/contributors that handle the transition:82 == 3. Request Stitching Changes from GENI Aggregates Operations Teams == 83 84 URN transition require co-ordination with various teams. Following are the teams/contributors that handle the transition based on the type of aggregate: 82 85 * InstaGENI: (geni-ops@googlegroups.com) Request is handled by Hussam Nasir (nasir@netlab.uky.edu) 83 * ExoGENI: (exogeni-ops@renci.org) Request is handled by Mert Cevik (mcevik@renci.org) or Ilya Baldin (ilbadin@renci.org)86 * ExoGENI: (exogeni-ops@renci.org). Request is handled by Mert Cevik (mcevik@renci.org) or Ilya Baldin (ilbadin@renci.org) 84 87 * OpenGENI: Marshall Brinn (Mbrinn@bbn.com) and Regina Rosales-Hain (rrhain@bbn.com) 85 * AL2S Aggregate and Production SCS: GMOC requests(gmoc@grnoc.iu.edu). Updates handled by Luke Fowler (luke@grnoc.iu.edu) or AJ Ragusa (aragusa@grnoc.iu.edu), cc: both on initial request. 88 * iMinds - Brecht Vermeulen (brecht.vermeulen@iminds.be> 89 * host-gpolab - Was configured locally and are to be made to those local definitions. 90 * AL2S GENI Aggregate: GMOC requests(gmoc@grnoc.iu.edu). AL2S Advertisement updates handled by Luke Fowler (luke@grnoc.iu.edu) or AJ Ragusa (aragusa@grnoc.iu.edu), cc: both on initial request. 91 * Internet2 Production SCS: GMOC requests(gmoc@grnoc.iu.edu). Updates handled by Luke Fowler (luke@grnoc.iu.edu) or AJ Ragusa (aragusa@grnoc.iu.edu), cc: both on initial request. 86 92 * Test SCS - Xi Yang (xyang@maxgigapop.net) 87 * iMinds - Brecht Vermeulen (brecht.vermeulen@iminds.be>88 * host-gpolab - was configured by Ali and he updates the local definitions. 93 94 Note: All Aggregates advertisements '''must''' be update before the SCS servers. The SCS discovers the new stitching path information from the Aggregates stitching advertisements. SCS is statically configured for fixed endpoints. 89 95 90 96 === 3a. Define Change Request Details === 97 91 98 Based on the existing Stitching information and the announced changes, generate a list of new link ids to be used at each site. 92 99 … … 169 176 170 177 171 ''' ''Once the requested changes are completed, verify that the requested changes appear in the rack aggregateadvertisement.''' ''178 ''' ''Once the requested changes are completed, verify that the requested changes appear in each of the GENI aggregates stitching advertisement.''' '' 172 179 {{{ 173 180 $ for i in gpo-ig gpo-og gpo-eg nysernet-ig al2s wall2 ; do stitcher listresources -a $i -o; done … … 197 204 198 205 199 == 4. Request SCS Update ==200 201 In order for GENI Network Stitching to pick up these path configuration changes, an SCS Update must be run. There are two SCS systems:206 == 4. Request SCS Servers Update == 207 208 In order for GENI Network Stitching to pick up these path configuration changes, an SCS update must be run. There are two SCS systems: 202 209 - Test SCS maintained by Xi Yang (xyang@maxgigapop.net) 203 - Production SCS maint ed by the Internet2 (gmoc@grnoc.iu.edu). Updates handled by Luke Fowler (luke@grnoc.iu.edu) or AJ Ragusa (aragusa@grnoc.iu.edu).204 205 The Production and Test SCS include stitching information for different sets of aggregates, to find out which SCS knows about which aggregates, issue the following :210 - Production SCS maintained by the Internet2 (gmoc@grnoc.iu.edu). Updates handled by Luke Fowler (luke@grnoc.iu.edu) or AJ Ragusa (aragusa@grnoc.iu.edu). 211 212 The Production and Test SCS include stitching information for different sets of aggregates, to find out which SCS knows about which aggregates, issue the following GENI tools commands: 206 213 207 214 For the Production SCS: … … 209 216 $ python ~/gcf/src/gcf/omnilib/stitch/scs.py --listaggregates --scs_url http://geni-scs.net.internet2.edu:8081/geni/xmlrpc >scs-prod 210 217 }}} 211 The above listaggregatesfunction shows that the GPO IG, GPO EG, and NYSERnet IG sites are known to the Production SCS.218 Look for the aggregates identified in the earlier steps. For example for the New York switch consolidation effort, the 'listaggregates' function shows that the GPO IG, GPO EG, and NYSERnet IG sites are known to the Production SCS. 212 219 213 220 For the Test SCS: … … 215 222 python gcf/gcf-current/src/gcf/omnilib/stitch/scs.py --listaggregates --scs_url http://nutshell.maxgigapop.net:8081/geni/xmlrpc > scs-test 216 223 }}} 217 The listaggregates function shows that sites GPO IG, GPO EG, GPO OG, NYSERnet IG, iMinds, and Umass. Both Production and Test SCSare known to the test SCS.224 Look for the aggregates identified in the earlier steps. For example for the New York switch consolidation effort, the 'listaggregates' function shows that sites GPO IG, GPO EG, GPO OG, NYSERnet IG, iMinds, and Umass are known to the test SCS. 218 225 219 226 Send a request to: … … 246 253 ||salt.net.internet2.edu || et-4/3/0 || utah-stitch || 2100-3499 ||[[BR]] 247 254 248 g. 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 "rtsw.salt.net.internet2.edu" and make sure the following are returned:255 g. 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: 249 256 * a switch is listed with the new name "rtsw.salt.net.internet2.edu", 250 * interface statistics are available for the new switch 257 * interface statistics are available for the new switch, 251 258 * VLAN are being reported for the new switch[[BR]] 252 259