= Experiment Resources Scenarios = This 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. ''Last update: 06/06/13'' || '''Scenario''' || '''State''' || ''' Ticket ''' || '''Comments''' || ||Scenario 1 ||[[Color(#63B8FF,In Progress)]]|| || || || ||Scenario 2 || || || || || ||Scenario 3 || || || || || ||Scenario 4 || || || || || [[BR]] || '''State Legend''' || '''Description''' || || [[Color(green,Pass)]] || Test completed and met all criteria || || [[Color(#98FB98,Pass: most criteria)]] || Test completed and met most criteria. Exceptions documented || || [[Color(red,Fail)]] || Test completed and failed to meet criteria. || || [[Color(yellow,Complete)]] || Test completed but will require re-execution due to expected changes || || [[Color(orange,Blocked)]] || Blocked by ticketed issue(s). || || [[Color(#63B8FF,In Progress)]] || Currently under test. || [[BR]] = Test Execution = '''Assumptions:''' - pgeni.gpolab.bbn.com credential are use for tests in this page. - Unless otherwise stated, all tests in this page use a stitched sliver from IG GPO to IG Utah, which includes: * GPO InstaGENI - https://boss.instageni.gpolab.bbn.com:12369/protogeni/xmlrpc/am * Internet2/ION - http://geni-am.net.internet2.edu:12346 * Utah PG - https://www.emulab.net:12369/protogeni/xmlrpc/am * Utah InstaGENI - https://boss.utah.geniracks.net:12369/protogeni/xmlrpc/am '''Notes:''' - 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. - Capacity '''must''' be specified for scenarios where Utah IG is end-point. = Experimenter Resources Scenarios = This test case verified the the ability to create, use, and release resources for all the resource scenarios described in this plan. == Scenarios 1 - Single slice with two endpoints using single stitched VLAN == This test verifies the use of 1 slice to connected 2 aggregates via a stitched VLAN. The sliver that was actually used included 1 slice named ''1sl-2aggr-1lnk'' that used the following topology: * GPO IG VM <->Internet2/ION Aggregate <-> Utah PG Aggregate <-> Utah IG VM First created a slice: {{{ $ omni.py createslice 1sl-2aggr-1lnk INFO:omni:Loading config file /home/lnevers/.gcf/omni_config INFO:omni:Using control framework pg INFO:omni:Created slice with Name 1sl-2aggr-1lnk, URN urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+1sl-2aggr-1lnk, Expiration 2013-06-08 12:45:56+00:00 INFO:omni: ------------------------------------------------------------ INFO:omni: Completed createslice: Options as run: framework: pg Args: createslice 1sl-2aggr-1lnk Result Summary: Created slice with Name 1sl-2aggr-1lnk, URN urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+1sl-2aggr-1lnk, Expiration 2013-06-08 12:45:56+00:00 INFO:omni: ============================================================ }}} == Scenarios 2 - Single slice with two endpoints using multiple stitched VLANs == * 1 slice includes: (Aggr1<->VLAN1<->Aggr2) + (Aggr1<->VLAN2<->Aggr2) + (Aggr1<->VLAN3<->Aggr2) == Scenarios 3 - Multiple slices each with two endpoints using single stitched VLAN == * slice1 includes: (Aggr1<->VLAN1<->Aggr2) * slice2 includes: (Aggr1<->VLAN2<->Aggr2) == Scenarios 4 - Multiple slices each with two endpoints using multiple stitched VLANs == * slice1 includes: (Aggr1<->VLAN1<->Aggr2) + (Aggr1<->VLAN2<->Aggr2) * slice2 includes: (Aggr1<->VLAN3<->Aggr2) + (Aggr1<->VLAN4<->Aggr2)