[[PageOutline]] = New Site GENI Stitching Confirmation Tests = Upon completion of the [wiki:GENIRacksHome/InstageniRacks/SiteConfirmationTests InstaGENI Confirmation Tests] or [wiki:GENIRacksHome/ExogeniRacks/SiteConfirmationTests ExoGENI Confirmation Tests] for a new GENI Rack site, the GPO also completes a series of GENI Network Stitching Confirmation Tests to validate supported stitching topologies for the GENI site. These Stitching confirmation tests verify experimenter ability to stitch network resources and the the ability to monitor the topology when possible. All stitching experiments defined in this plan assume that Omni tools are used for all AM API operations. See the '''[wiki:GeniNetworkStitchingConfirmationTestStatus New Site Stitching Confirmation Tests Status]''' page for details about sites that have been tested. For each topology outlined on this page, omni tools will be used to request and manage resources, once the resources are available some performance statistics will be collected using for UDP, TCP and ICMP traffic. ''Note: All test outlined on this page have been modified to use dedicated hosts (raw-pcs) to collect performance data in place of VMs'' == InstaGENI Stitching Test Topologies == The InstaGENI (IG) Stitching Tests (ST) verify some basic topologies that are common to all rack types, but it is expected that network access will vary across rack types. Therefore, a set of tests is defined for each rack type. === IG-ST-1 New Site to GPO IG topology === A stitching test between the new site and the GPO IG rack will be performed for each network path available at the new site. Testing for stitching connections will consider how the site is connected (ION, AL2S, or both) and then test will be executed accordingly. ==== IG-ST-1a ION Site ==== If the new site is connected to ION, then this ION topology that will be verified: [[Image(IG-ST-1-ion.jpg)]] ==== IG-ST-1b AL2S Site ==== If the new site is connected to AL2S, then it will be connected to another AL2S site (ex. Stanford IG): [[Image(IG-ST-1-al2s.jpg)]] Once basic AL2S connectivity it verified, the New IG site is then connected via AL2S and ION to the GPO IG site as shown in the following topology: [[Image(IG-ST-1-al2s-ion.jpg)]] === IG-ST-2 New Site Loop topology === A stitching test between the new site and the GPO IG rack will be performed which uses two stitched links between the 2 sites sites using OpenVZ VMs: [[Image(IG-ST-2-ion.jpg)]] If the New IG site is connected to AL2S, then it will be connected to another AL2S site rather than the GPO IG ION site. [[Image(IG-ST-2-al2s.jpg)]] === IG-ST-3 New Site 3 node linear topology === A stitching test that uses the new site as an intermediate hop in a linear topology between an ION and an AL2S site: [[Image(IG-ST-3-ion-al2s.jpg)]] === IG-ST-4 New Site to GPO EG interoperability === A stitching test between the new site and the GPO EG rack will be performed for each network path available at the new site. For each stitching path tested in this test case, performance data will be captured between the New IG site and GPO EG for TCP, UDP and ping statistics. [[Image(IG-ST-4-ion.jpg)]] If the New IG site is connected to AL2s and the GPO EG is connected to ION, the following topology will be verified: [[Image(IG-ST-4-al2s.jpg)]] ''Note'': Test was modified to use dedicated hosts (raw-pcs) to collect performance data. Also plan to switch the ExoGENI host to bare metal, when stitching to bare metal is supported. === IG-ST-5 Site Information === As part of the Site Stitching verification, the following will take place: - Verify new site has stitching VLAN and Device URN information in the InstaGENI [wiki:GeniAggregate Aggregate] page. - Verification that Delegated GENI Stitching VLANs for site are documented [https://wiki.maxgigapop.net/twiki/bin/view/GENI/StaticNetworksView here]. - Review Stitching Computation Service logs during each test case. - Record test status and results on the [GeniNetworkStitchingConfirmationTestStatus stitching test status page]. - Upon completion, add site to the list of [wiki:GeniNetworkStitchingSites GENI Network Stitching Sites]. === IG-ST-6 New Site !OpenFlow topology === A stitching topology using OpenFlow will be tested for each network path available at the new site. Basically all tests executed in test case IG-ST-1 will be re-executed but with the addition of !OpenFlow. ==== IG-ST-6a ION !OpenFlow ==== If the new site is connected to ION, then this stitching topology with !OpenFlow will be verified to the GPO IG ION site: [[Image(IG-ST-1-ion.jpg)]] ==== IG-ST-6b AL2S !OpenFlow ==== If the new site is connected to AL2S, then this stitching topology with !OpenFlow will be verified to another AL2S site (ex. Stanford IG): [[Image(IG-ST-1-al2s.jpg)]] Once basic AL2S connectivity it verified, the new site will be connected connected with stitching and using !OpenFlow via AL2S and ION to the GPO IG site as shown in the following topology: [[Image(IG-ST-1-al2s-ion.jpg)]] == ExoGENI Stitching Test Topologies == The ExoGENI (EG) GENI Stitching Tests (ST) are intended to verify the same basic topologies that are verified for InstaGENI, but it is expected that network access will vary significantly at ExoGENI sites. Therefore ExoGENI tests will be specifically defined for each site, at least for the first few EG racks we test. Check the [wiki:GeniNetworkStitchingConfirmationTestStatus stitching test status page] for information on a particular EG rack.