| 82 | To determine which GENI sites are impacted by a switch name change, refer to the [wiki:OperationsProcedures/URNRename#GENISites GENI Sites] section above. |
| 83 | 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. |
| 84 | |
| 85 | Schedule details for chat participation, identify participants and define details for expected stitching details. |
| 86 | |
| 87 | == 3. Update Advertisement == |
| 88 | |
| 89 | Once the switch name change takes place and captured in ticket activity, the aggregate teams can proceed to make required changes: |
| 90 | |
| 91 | a. AL2S Aggregate changes Stitching definition in Advertisement using the new switch name and updated stitching section. |
| 92 | b. Site Aggregate changes Stitching definition in Advertisement for IG, EG, or CLab site to reflect AL2S definitions. |
| 93 | c. Notify team chat of completion of this step. |
| 94 | |
| 95 | == 4. GPO Validates Advertisements == |
| 96 | Once Advertisement updates are completed, GPO will validate: |
| 97 | |
| 98 | a. Content of Advertisement RSPec for AL2S. Verify both switch and stitching definitions. |
| 99 | b. Content of Advertisement RSPec(s) for GENI site(s). |
| 100 | c. Notify team chat of completion of this step |
| 101 | |
| 102 | == 5. Stitching Computation Service Picks up changes == |
| 103 | |
| 104 | Once Advertisement updates are validated, the SCS owners can proceed to make the required changes: |
| 105 | a. Production and/or Test SCS pick up new advertisements change for the AL2S and the GENI sites identified in ticket. |
| 106 | b. As each is completed, the responsible will notify team chat of completion of this step. |
| 107 | |
| 108 | == 6. Updates for Monitoring == |
| 109 | Once SCS has picked for the Sites and AL2S, GPO will: |
| 110 | |
| 111 | a. Request that VLAN Delegation repository be updated to capture changes. Delegation file is used by Monitoring to identify stitching links. |
| 112 | b. Notify GENI Monitoring folks to pick up updated delegation from previous step. |
| 113 | |
| 114 | == 7. Validate end-to-end connections == |
| 115 | |
| 116 | Once SCS has picked for the Sites and AL2S, GPO will validate the following: |
| 117 | a. Request stitching topology using updated sites from Production SCS, if applicable. |
| 118 | b. Request stitching topology using updated sites from Test SCS, if applicable. |
| 119 | c. Exchange traffic over stitched topology using updated devices. |
| 120 | d. Request stitching OpenFlow topology and exchange traffic between endpoints. |
| 121 | e. Review monitoring to verify that URN is properly captured and that metrics are available for stitching topologies in previous steps. |
| 122 | f. Update wiki pages: [GeniAggregate GENI Aggregate] pages, [wiki:GENIRacksHome/Operators GENI Operators pages], [wiki:GeniNetworkStitchingSites GENI Network Stitching Sites]. |
| 123 | |
| 124 | f. Notify team chat of completion of this step |