Changes between Version 3 and Version 4 of OperationsProcedures/URNRename

Timestamp:

06/08/17 14:27:41 (7 years ago)

Author:

lnevers@bbn.com

Comment:

--

OperationsProcedures/URNRename

@@ -5 +5 @@
 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. 
 
-== Impacted Sites ==
+== Impacted AL2S Switches ==
 
 The renaming effort impacts 26 AL2S switches whose URN is to be changed.  Only 9 AL2S switches that are to be renamed have have stitching sites and require updates to GENI Aggregates, GENI Stitching Computation Service and GENI Monitoring. The AL2S switches with GENI Stitching sites connected are:
@@ -19 +19 @@
 || sdn-sw.pitt.net.internet2.edu || rtsw.pitt.net.internet2.edu ||
 || sdn-sw.star.net.internet2.edu || rtsw.star.net.internet2.edu ||
+
+== Impacted GENI Sites ==
 
 The 9 AL2S switches above have __23 GENI aggregates__ whose advertisement is to be reconfigured (1 AL2S +22 GENI Sites) to pick up the name change. Following are the details for the AL2S switches that will be reconfigured and tested along with the number of ports configured for switching and the switching sites associated with those ports.
@@ -55 +57 @@
   [2] Not sure how this stitching endpoint is used or how to test. [[BR]]
 
+Remember!!! Each AL2S Switch renaming impacts the AL2S Aggregate which advertises the network topology and '''must''' always capture the correct naming for each switch in the network.
 
 = URN Renaming Procedure =
 
-== 1. Generate Ticket and check for conflicts with upcoming events == 
+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.
+ 
+Following is the procedure to be followed when the URN renaming takes place. 
 
-== 2. Review Affected Stitching Endpoint 
+== 1. Generate GMOC Ticket == 
+
+GMOC tickets must be generated capturing:
+ - Date and duration of the URN change activity
+ - Impacted to GENI sites.  Scheduling 
+
+== 2. Review Affected Stitching Endpoint ==
+Before URN renaming takes place, collect Aggregate Advertisement for all Aggregates impacted. To determine which sites are impacted, refer to the [xxx Impacted GENI Sites] section above.
+