Changes between Version 6 and Version 7 of OperationsProcedures/URNRename

Timestamp:

06/08/17 15:08:38 (7 years ago)

Author:

lnevers@bbn.com

Comment:

--

OperationsProcedures/URNRename

@@ -76 +76 @@
  - 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.
+== 2. Review Affected Stitching Endpoint and plan start time ==
 
+Before URN renaming takes place, collect Aggregate Advertisement for all Aggregates impacted by the planned update: {{{ $omni listresources -a $aggr -o}}}
 
+To determine which GENI sites are impacted by a switch name change, refer to the [wiki:OperationsProcedures/URNRename#GENISites GENI Sites] section above.
+Note the output advertisements are used for comparisons after the upgrade to ensure that the expected changes are made and that no information is added or deleted unexpectedly.
+
+Schedule details for chat participation, identify participants and define details for expected stitching details.
+
+== 3. Update Advertisement ==
+
+Once the switch name change takes place and captured in ticket activity, the aggregate teams can proceed to make required changes:
+
+ a. AL2S Aggregate changes Stitching definition in Advertisement using the new switch name and updated stitching section.
+ b. Site Aggregate changes Stitching definition in Advertisement for IG, EG, or CLab site to reflect AL2S definitions.
+ c. Notify team chat of completion of this step.
+
+== 4. GPO Validates Advertisements ==
+Once Advertisement updates are completed, GPO will validate:
+
+ a. Content of Advertisement RSPec for AL2S. Verify both switch and stitching definitions. 
+ b. Content of Advertisement RSPec(s) for GENI site(s).
+ c. Notify team chat of completion of this step
+
+== 5. Stitching Computation Service Picks up changes ==
+
+Once Advertisement updates are validated, the SCS owners can proceed to make the required changes:
+ a. Production and/or Test SCS pick up new advertisements change for the AL2S and the GENI sites identified in ticket.  
+ b. As each is completed, the responsible will notify team chat of completion of this step. 
+
+== 6. Updates for Monitoring ==
+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.
+  b. Notify GENI Monitoring folks to pick up updated delegation from previous step.
+
+== 7. Validate end-to-end connections ==
+
+Once SCS has picked for the Sites and AL2S, GPO will validate the following:
+  a. Request stitching topology using updated sites from Production SCS, if applicable.
+  b. Request stitching topology using updated sites from Test SCS, if applicable.
+  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].
+
+  f. Notify team chat of completion of this step