Changes between Version 1 and Version 2 of GeniNetworkStitchingTestStatus/Resources


Ignore:
Timestamp:
06/07/13 07:43:46 (6 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniNetworkStitchingTestStatus/Resources

    v1 v2  
    11
    2 = Experiment Resource Scenarios =
     2= Experiment Resources Scenarios =
    33
    4 This page captures status and execution details for the Experiment Resource Scenarios.   For overall status see the [http://groups.geni.net/geni/wiki/GeniNetworkStitchingTestStatus GENI Network Stitching Test Status] page and for test details see  the [http://groups.geni.net/geni/wiki/GeniNetworkStitchingTestPlan GENI Network Stitching Test Plan] page.
     4This page captures status and execution details for the Experiment Resources Scenarios.   For overall status see the [http://groups.geni.net/geni/wiki/GeniNetworkStitchingTestStatus GENI Network Stitching Test Status] page and for test details see  the [http://groups.geni.net/geni/wiki/GeniNetworkStitchingTestPlan GENI Network Stitching Test Plan] page.
    55
    66''Last update: 06/06/13''
     
    1717|| [[Color(#63B8FF,In Progress)]]         || Currently under test.                                                ||
    1818[[BR]]
     19
     20= Test Execution =
     21'''Assumptions:'''
     22 - pgeni.gpolab.bbn.com credential are use for tests in this page.
     23 - Unless otherwise stated, all tests in this page use a stitched sliver from IG GPO to IG Utah, which includes:
     24       * GPO InstaGENI - https://boss.instageni.gpolab.bbn.com:12369/protogeni/xmlrpc/am
     25       * Internet2/ION - http://geni-am.net.internet2.edu:12346
     26       * Utah PG - https://www.emulab.net:12369/protogeni/xmlrpc/am
     27       * Utah InstaGENI - https://boss.utah.geniracks.net:12369/protogeni/xmlrpc/am
     28
     29'''Notes:'''
     30 - Stitcher currently does not support AM API v3, because the PG AMs that claimed to do V3 were doing it incorrectly, so stitcher is delivered to run AM API V2.
     31 - Capacity '''must''' be specified for scenarios where Utah IG is end-point.
     32
     33
     34= Experimenter Resources Scenarios =
     35
     36This test case verified the the ability to create, use, and release resources for all the resource scenarios described in this plan.
     37
     38== Single slice with two endpoints using single stitched VLAN ==
     39This test verifies the following:
     40   * 1 slice includes: (Aggr1<->VLAN1<->Aggr2)
     41The sliver that was actually used included 1 slice named 1sl-2aggr-1lnk that used the following topology:
     42   * GPO IG VM <->Internet2/ION Aggregate <-> Utah PG Aggregate <-> Utah IG VM
     43
     44== Single slice with two endpoints using multiple stitched VLANs ==
     45
     46  * 1 slice includes: (Aggr1<->VLAN1<->Aggr2) + (Aggr1<->VLAN2<->Aggr2) + (Aggr1<->VLAN3<->Aggr2)
     47
     48== Multiple slices each with two endpoints using single stitched VLAN ==
     49   * slice1 includes: (Aggr1<->VLAN1<->Aggr2)
     50   * slice2 includes: (Aggr1<->VLAN2<->Aggr2)
     51
     52== Multiple slices each with two endpoints using multiple stitched VLANs ==
     53   * slice1 includes: (Aggr1<->VLAN1<->Aggr2) + (Aggr1<->VLAN2<->Aggr2)
     54   * slice2 includes: (Aggr1<->VLAN3<->Aggr2) + (Aggr1<->VLAN4<->Aggr2)