Changes between Version 11 and Version 12 of OperationsProcedures/URNRename

Timestamp:

06/08/17 15:43:01 (7 years ago)

Author:

lnevers@bbn.com

Comment:

--

OperationsProcedures/URNRename

@@ -2 +2 @@
 = GENI Internet2 Switch URN Renaming =
 
-Internet2 plans an effort to migrate from SDN to MPLS in the AL2S backbone. The implementation of MPLS is to be verified by the ability to exchange GENI experiment traffic both via stitching or OpenFlow Over stitching after the upgrade has taken place. (Validation covered in step 7 in the procedure below.)
+Internet2 plans an effort to migrate from SDN to MPLS in the AL2S backbone. The implementation of MPLS is not expected to impact GENI sites and its implementation will be verified by running GENI experiment traffic both via stitching or OpenFlow Over stitching after the upgrade has taken place.
 
-This effort also includes a task to rename AL2S Switches from '''sdn-sw''' to '''rtsw'''.  The renaming effort impacts: 1) GENI Aggregates, 2) Stitching Computation Services and 3) GENI Monitoring 4) Numerous wiki pages capturing network connectivity details. Thus is the bulk of the effort covered in all sections below. 
+The effort also includes a task to rename AL2S Switches from '''sdn-sw''' to '''rtsw'''.  The renaming effort impacts: 1) GENI Aggregates, 2) Stitching Computation Services and 3) GENI Monitoring 4) Numerous wiki pages capturing network connectivity details. Thus is the bulk of the effort covered in this documents and sections below capture required activities and validation. 
 
 == AL2S Switches ==
@@ -54 +54 @@
 = URN Renaming Procedure =
 
-This procedure assumes the following:
-  - Sites will be migrates in batches to streamline effort and allow for efficiency.
-  - A common chat tool/live messaging is used to coordinate effort when sites are transitioned to the new URN
-  - Representatives for the impacted aggregates and for both Test and Production SCS are available for transition.
-  - URN Name transition will be planned while considering upcoming events.
+Procedure assumes the following:
+  - Sites are migrated in batches to streamline the effort and allow for efficiency.
+  - Alive messaging/chat tool is used to coordinate effort when sites are transitioned to the new URN.
+  - Representatives for the impacted aggregates (AL2S+GENI Sites) and for both SCS (Test & Production) are available.
+  - URN Name transition has been planned considering upcoming events.
  
-Following is the procedure to be followed when the URN renaming takes place. 
+Procedure Steps for the URN renaming:
 
 == 1. Generate GMOC Ticket == 
@@ -101 +101 @@
 Once SCS has picked for the Sites and AL2S, GPO will:
 
-  a. Request that VLAN Delegation repository be updated to capture changes. Delegation file is used by Monitoring to identify stitching links.
+  a. Request that VLAN Delegation repository be updated to capture URN changes. Delegation file is used by Monitoring to identify stitching links.
   b. Notify GENI Monitoring folks to pick up updated delegation from previous step.
 
@@ -111 +111 @@
   c. Exchange traffic over stitched topology using updated devices.
   d. Request stitching OpenFlow topology and exchange traffic between endpoints.
-  e. Review monitoring to verify that URN is properly captured and that metrics are available for stitching topologies in previous steps.
-  f. Update wiki pages: [GeniAggregate GENI Aggregate] pages, [wiki:GENIRacksHome/Operators GENI Operators pages], [wiki:GeniNetworkStitchingSites GENI Network Stitching Sites].
+  e. Review monitoring to verify: 1) URN is properly captured, 2) metrics are available for new Switch URN, and 3) stitching links using new URN are identified properly.
+  f. Update wiki pages: 1)[GeniAggregate GENI Aggregate] pages, 2)[wiki:GENIRacksHome/Operators GENI Operators pages], and 3)[wiki:GeniNetworkStitchingSites GENI Network Stitching Sites].
+  f. Notify team chat of completion of this step.
+  g. Notify GMOC to close ticket.
 
-  f. Notify team chat of completion of this step