Changes between Version 73 and Version 74 of GeniNetworkStitchingTestStatus/Functional

Timestamp:

07/30/13 09:53:19 (11 years ago)

Author:

lnevers@bbn.com

Comment:

--

GeniNetworkStitchingTestStatus/Functional

@@ -2712 +2712 @@
 
 === 3.1 Allocate not advertised ===
+
 At ION, InstaGENI and ExoGENI, allocate resources that are not advertised, verify failure.  
 
@@ -2719 +2720 @@
 At ION, create a sliver that requests a VLAN 4321 which does not exist, and verify that request fails:
 {{{
-2$ omni.py createsliver lnstitch4321 -a i2 ./stitch-ion-no-exist.rspec 
+$ omni.py createsliver lnstitch4321 -a i2 ./stitch-ion-no-exist.rspec 
 11:44:16 INFO     omni: Loading config file /home/lnevers/.gcf/omni_config
 11:44:16 INFO     omni: Using control framework pg
@@ -2741 +2742 @@
 }}}
 
-Failed as expected.
+'''Results:''' Failed as expected.
 
 === 3.2 Request VLAN already in use ===
@@ -3078 +3079 @@
 }}}
 
-
 Now create a second sliver requesting the same VLAN 850 and verify status:
 {{{
@@ -3146 +3146 @@
 }}}
 
-Failed as expected. 
+'''Results:''' Failed as expected. 
 
 === 3.2 Recovery and logging for killed circuit === 
+
 In this scenario, an ION circuit is killed manually to verify impact on sliver and how aggregates handle the circuit being killed, the recovery, and logging of event.
 
 First created a slice "ig-gpo-pg-utah" and then created a sliver between GPO IG and PG Utah:
 {{{
-$ stitcher.py createsliver ig-gpo-pg-utah stitch-ig-gpo-pg-utah.rspec --ionRetryIntervalSecs 180
-10:42:28 INFO     stitcher: Loading config file /home/lnevers/.gcf/omni_config
-10:42:28 INFO     stitcher: Using control framework portal
-Unable to read rspec file stitch-ig-gpo-pg-utah.rspec: [Errno 2] No such file or directory: 'stitch-ig-gpo-pg-utah.rspec'
-lnevers@sendaria:~/gcf-2.4-preview4$ cd stitch-test
 lnevers@sendaria:~/gcf-2.4-preview4/stitch-test$ stitcher.py createsliver ig-gpo-pg-utah stitch-ig-gpo-pg-utah.rspec --ionRetryIntervalSecs 180
 10:42:34 INFO     stitcher: Loading config file /home/lnevers/.gcf/omni_config
@@ -3372 +3368 @@
 Stitching success: Reserved resources in slice ig-gpo-pg-utah at 3 Aggregates (including 1 intermediate aggregate(s) not in the original request), creating 1 link(s).
 }}}
-Started traffic between the end-point and then requested for circuit to be deleted by Internet2 folks. Once deleted it takes 15 minutes for status to show up:
+Started traffic between the end-point and then requested for circuit to be deleted by Internet2 folks. Once deleted it takes ''' ''15 minutes'' ''' for status to reflect the deletion:
 {{{
 $ omni.py sliverstatus -a i2 ig-gpo-pg-utah 
@@ -3429 +3425 @@
 Deleted slivers on 3 out of a possible 3 aggregates
 }}}
+
 === 3.3 Race condition ===
 
@@ -3439 +3436 @@
 }}}
 
+It was found that the order of the sliver creation is controlled by the SCS and so this test cannot be executed.
+
 === 3.4 Pseudo loop scenario ===
-Request PG Utah to ION to IG GPO. Then request a 2nd interface at PG Utah node to ION to same interface on same node at IG GPO.  If that fails, then request a 2nd interface on that node at IG GPO - that should work.
-
+
+This 2 part test scenario will request and invalid topology which uses PG Utah to ION to InstaGENI GPO. 
+
+__Part 1:__ Request the following incorrect links in one RSpec:
+
+       Utah PG if0 <-ION-> GPO IG if0 [[BR]]
+       Utah PG if1 <-ION-> GPO IG if0  [[BR]]
+
+__Part 2:__Once the part 1 fails, switch to the following definition:
+
+       Utah  PG if0 <-ION-> GPO IG if0 [[BR]]
+       Utah  PG if1 <-ION-> GPO IG if1  [[BR]]
+
+
+Part 1 test run output:
+
+Using the following link definition:
+{{{
+        <link client_id="link">
+                <component_manager name="urn:publicid:IDN+instageni.gpolab.bbn.com+authority+cm"/>
+                <component_manager name="urn:publicid:IDN+ion.internet2.edu+authority+am"/><component_manager name="urn:publicid:IDN+emulab.net+authority+cm"/>
+                <interface_ref client_id="ig-gpo:if0"/>
+                <interface_ref client_id="pg-utah:if0"/>
+                <property dest_id="pg-utah:if0" source_id="ig-gpo:if0"/>
+                <property dest_id="ig-gpo:if0" source_id="pg-utah:if0"/>
+        </link>
+        <link client_id="link2">
+                <component_manager name="urn:publicid:IDN+instageni.gpolab.bbn.com+authority+cm"/>
+                <component_manager name="urn:publicid:IDN+ion.internet2.edu+authority+am"/><component_manager name="urn:publicid:IDN+emulab.net+authority+cm"/>
+                <interface_ref client_id="ig-gpo:if0"/>
+                <interface_ref client_id="pg-utah:if1"/>
+                <property dest_id="pg-utah:if1" source_id="ig-gpo:if0"/>
+                <property dest_id="ig-gpo:if0" source_id="pg-utah:if1"/>
+        </link>
+}}}
+
+Created a sliver:
+
+{{{
+$ stitcher.py createsliver lnloop ./stitch-loop-bad.rspec 
+
+TODO capture
+}}}
+
+
+'''Results''': Failed as expected
+
+
+Part 2 test run output:
+
+Modified RSpec linkd to:
+{{{
+  <link client_id="link">
+    <component_manager name="urn:publicid:IDN+instageni.gpolab.bbn.com+authority+cm"/>
+    <component_manager name="urn:publicid:IDN+emulab.net+authority+cm"/>
+    <interface_ref client_id="ig-gpo:if0"/>
+    <interface_ref client_id="pg-utah:if0"/>
+    <property source_id="ig-gpo:if0" dest_id="pg-utah:if0"/>
+    <property source_id="pg-utah:if0" dest_id="ig-gpo:if0"/>
+  </link>
+  <link client_id="link2">
+    <component_manager name="urn:publicid:IDN+instageni.gpolab.bbn.com+authority+cm"/>
+    <component_manager name="urn:publicid:IDN+emulab.net+authority+cm"/>
+    <interface_ref client_id="ig-gpo:if1"/>
+    <interface_ref client_id="pg-utah:if1"/>
+    <property source_id="ig-gpo:if1" dest_id="pg-utah:if1"/>
+    <property source_id="pg-utah:if1" dest_id="ig-gpo:if1"/>
+  </link>
+}}}
+and created a sliver:
+{{{
+$ stitcher.py createsliver lnloop ./stitch-loop.rspec 
+
+TODO CAPTURE
+}}}
+
+
+?? Get definition from source: Then request a 2nd interface at PG Utah node to ION to same interface on same node at IG GPO.  If that fails, then request a 2nd interface on that node at IG GPO - that should work.??
+