Changes between Version 6 and Version 7 of URNConsolidation


Ignore:
Timestamp:
07/13/16 08:44:34 (8 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • URNConsolidation

    v6 v7  
    11[[PageOutline(1-3)]]
    22
    3 = GENI Switch Consolidation Procedure =
     3= GENI Internet2 Switch Consolidation Procedure =
    44
    55This 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.
    66
    7 The steps show examples based on details from previous switch consolidation and their effect on GENI stitching sites connected to this switch.
    8 
    9 == 0. Generate Tickets and check for conflicts with upcoming ticketed GENI events ==
     7The steps include examples based on details from previous switch consolidation and their effect on GENI stitching sites connected to this switch.
     8
     9== 1. Generate Tickets and check for conflicts with upcoming GENI events ==
    1010
    1111Make 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. 
     
    1919If 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).
    2020
    21 == 1. Find Current Stitching Configuration ==
    22 
    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:
     21== 2. Find Affected Stitching Configuration ==
     22
     23The 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 AL2S advertisement and reviewing its stitching definitions:
    2424{{{
    2525   omni -a al2s listresources -o
     
    2727Review 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. 
    2828
    29 For example there were several stitching endpoints for sdn-sw.newy32aoa.net.internet2.edu.  Here is the list from an AL2S Advertisement:
     29For example there were several stitching endpoints for "sdn-sw.newy32aoa.net.internet2.edu" in the AL2S Advertisement:
    3030{{{
    3131 <stitch:node id="urn:publicid:IDN+al2s.internet2.edu+node+sdn-sw.newy32aoa.net.internet2.edu">
     
    4242}}}
    4343
    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 
    48 
    49 == 2. Define Stitching Configuration Changes ==
    50 
    51 Review Internet2 announced changes for switch names and ports. Based on the information, identify the changes to be made to stitching definitions.
     44From the above list we will request the "<stitch:link id" to be updated, the "<stitch:port id" transitions are implicit. In this example, there are 6 stitching endpoints requiring updates (2 InstaGENI, 2 ExoGENI, 1 OpenGENI, 1 network aggregate(iMinds) and 1 fixed endpoint (host-gpolab). 
     45
     46In GENI Network 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. <<CHECKING WITH XI>>.
     47
     48
     49== 3. Define Stitching Configuration Changes ==
     50
     51Review Internet2 announced changes for switch names and ports. Based on the information, identify the changes to be made to stitching definitions for the stitching endpoints identified in the previous step.
    5252
    5353For example, using details from the consolidation email from Internet2 for the New York Switch:
     
    7979
    8080
    81 == 3. Request Stitching Changes from GENI Aggregates Operations Teams ==
     81== 4. Request Stitching Changes from GENI Aggregates Operations Teams ==
    8282
    8383URN transition require co-ordination with various teams. Following are the teams/contributors that handle the transition based on the type of aggregate:
     
    9393Note: 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.
    9494
    95 === 3a. Define Change Request Details ===
     95=== 4a. Define Change Request Details ===
    9696
    9797Based on the existing Stitching information and the announced changes, generate a list of new link ids to be used at each site.
     
    161161}}}
    162162
    163 === 3b. Make Requests for Aggregate Updates ===
     163=== 4b. Make Requests for Aggregate Updates ===
    164164
    165165Send Email to each of the teams to request the above changes:
     
    203203   
    204204
    205 == 4. Request SCS Servers Update ==
     205== 5. Request SCS Servers Update ==
    206206
    207207In order for GENI Network Stitching to pick up these path configuration changes, an SCS update must be run.  There are two SCS systems:
     
    228228
    229229
    230 == 5. Validate Updated Stitching ==
     230== 6. Validate Updated Stitching ==
    231231
    232232When the updates are completed for all Aggregates and for the SCS servers, testing takes place to verify the URN changes. Validation includes:
     
    260260
    261261
    262 == 6. Update and close all tickets ==
     262== 7. Update and close all tickets ==
    263263
    264264Assuming all tests are successful, update and close all tickets by emailing the GMOC.  If there are outstanding issues that are significant, leave the ticket open until they are resolved.  If there are smaller outstanding issues, close the maintenance tickets, and open new tickets with the appropriate owners to track and resolve, ideally before the next maintenance.