Changes between Version 18 and Version 19 of GeniNetworkStitchingConfirmationTests


Ignore:
Timestamp:
07/28/14 12:01:23 (5 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniNetworkStitchingConfirmationTests

    v18 v19  
    1515=== IG-ST-1 New Site to GPO IG topology ===
    1616
    17 A stitching test between the new site and the GPO IG rack will be performed for each network path available at the new site.  For example, if the site is connected to both ION and AL2S, two separate tests will be run to verify that both paths can be requested and used between the two Xen VMs at each site. This is the ION topology that will be verified:
     17A 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.
     18
     19==== IG-ST-1a ION Site ====
     20
     21If the new site is connected to ION, then this ION topology that will be verified:
    1822
    1923  [[Image(IG-ST-1-ion.jpg)]]
    2024
    21 If the New IG site is connected to AL2S, then it will be connected to another AL2S site first to verify basic connectivity:
     25==== IG-ST-1b AL2S Site ====
     26
     27If the new site is connected to AL2S, then it will be connected to another AL2S site (ex. Stanford IG):
    2228
    2329  [[Image(IG-ST-1-al2s.jpg)]]
    2430 
    25 Once basic AL2S connectivity it verified, the New IG site is then connected via AL2S and ION to the the GPO IG site as shown in the following topology:
     31Once 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:
    2632
    2733  [[Image(IG-ST-1-al2s-ion.jpg)]]
    2834
    29 
    30 For each stitching path tested in this test case, performance data will be captured between the New IG Site and GPO IG for TCP, UDP and ping statistics.
    31 
    32 
    33 === IG-ST-1a New Site to GPO IG !OpenFlow topology ===
    34 
    35 
    36 
    37 
    38 === IG-ST-2 New Site to GPO IG Loop topology ===
     35=== IG-ST-2 New Site Loop topology ===
    3936
    4037A 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:
     
    7572 
    7673
     74=== IG-ST-6 New Site !OpenFlow topology ===
     75
     76A 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. 
     77
     78
     79==== IG-ST-6a ION !OpenFlow ====
     80
     81If the new site is connected to ION, then this stitching topology with !OpenFlow will be verified to the GPO IG ION site:
     82
     83  [[Image(IG-ST-1-ion.jpg)]]
     84
     85==== IG-ST-6b AL2S OpenFlow ====
     86
     87If the new site is connected to AL2S, then this stitching topology with !OpenFlow will be verified to another AL2S site (ex. Stanford IG):
     88
     89  [[Image(IG-ST-1-al2s.jpg)]]
     90 
     91Once 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:
     92
     93  [[Image(IG-ST-1-al2s-ion.jpg)]]
     94
    7795== ExoGENI Stitching Test Topologies ==
    7896