wiki:GENIOESSTopologiesTestStatus/OESS-TC6

Version 13 (modified by lnevers@bbn.com, 4 years ago) (diff)

--

OESS-TC6: Administrative and Operator functions

This test case verifies Administrative/Operator functions . For overall status see the GENI OESS Topologies Test Status page.

Test Status

This section captures the status for each function verified by this test plan.

Function State Ticket Notes
Allocated VLANs Color(green,Pass)?
Ad reflects VLAN allocation Color(yellow,Complete)? #1280 No "--available" support for listresources
Add/Modify/Delete VLAN
Modify the VLAN endpoints
Bandwidth allocation No bandwidth shaping in AL2S
Ad of bandwidth allocation
Traffic statistics Color(green,Pass)?
Operator deletes VLANs


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.


Test Execution Details

These functions are important for operators in GENI, so that they can track traffic to and from their site through GENI aggregates. Operator access to OESS information will be verified (note the operator is not the same as the experimenter):

Allocated VLANs

Allocated VLANs for use by Aggregate responsible for cross-connect path. Checked advertisement for the 10 cross-connect to ION and found:

          <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.clev.net.internet2.edu:e5/1:*">
                  <stitch:vlanRangeAvailability> 3900-4000 </stitch:vlanRangeAvailability>
          <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth15/1:*">
                  <stitch:vlanRangeAvailability> 3900-4000 </stitch:vlanRangeAvailability>
          <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.wash.net.internet2.edu:e5/2:*">
                  <stitch:vlanRangeAvailability> 3950-4000 </stitch:vlanRangeAvailability>
          <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.losa.net.internet2.edu:e1/1:*">
                  <stitch:vlanRangeAvailability> 3950-4000 </stitch:vlanRangeAvailability>
          <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.atla.net.internet2.edu:e15/1:*">
                  <stitch:vlanRangeAvailability> 3900-4000 </stitch:vlanRangeAvailability>
          <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.newy32aoa.net.internet2.edu:e3/2:*">
                  <stitch:vlanRangeAvailability> 3900-4000 </stitch:vlanRangeAvailability>
          <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.chic.net.internet2.edu:e3/1:*">
                  <stitch:vlanRangeAvailability> 3900-4000 </stitch:vlanRangeAvailability>
          <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.seat.net.internet2.edu:et-2/0/0.0:*">
                  <stitch:vlanRangeAvailability> 3950-4000 </stitch:vlanRangeAvailability>
          <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.houh.net.internet2.edu:e15/3:*">
                  <stitch:vlanRangeAvailability> 3900-4000 </stitch:vlanRangeAvailability>
          <stitch:link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.salt.net.internet2.edu:e15/1:*">
                  <stitch:vlanRangeAvailability> 3950-4000 </stitch:vlanRangeAvailability

Originally missing stitching advertisement for New York(sdn-sw.salt.net) and Salt Lake (sdn-sw.salt.net). Advertisement updated.

Advertisement reflects VLAN allocation

Verify Aggregate Advertisement reflects the VLAN allocation.

Tests were completed for AL2S sites TAMU and UCD which used up all advertised VLAN ranges. Successfully reserved:

  • TAMU advertised range = (940-949)
  • UCD advertised range = (1670-1679,1650-1669)

Additionally, reserved AL2S to ION topology from Chicago IG (AL2S) to NYSERNet IG (ION). Successfully reserved X VLAN across the New York cross-connect:

  • ION = "urn": "urn:publicid:IDN+ion.internet2.edu+interface+rtr.newy:et-5/0/0:al2s",
  • AL2S = "urn": "urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.newy32aoa.net.internet2.edu:e3/2:*",

Add/Modify/Delete VLANs

Add/Modify/Delete the VLANs available for the aggregate, verify Advertisement reflects change for each add/modify/delete operation.

Modify the VLAN endpoints

Modify the endpoints for a VLAN and verify Advertisement reflects change.

Bandwidth allocation

Request various link bandwidth scenarios:

Requested sliver from Stanford IG to Missouri IG with a link capacity option of "--defaultCapacity=500000":

$ stitcher.py createsliver al2s-perf ./stitch-al2s-perf.rspec --excludehop urn:publicid:IDN+instageni.stanford.edu+interface+procurve2:1.24.ion.salt.xe-0_1_1 --excludehop urn:publicid:IDN+instageni.rnet.missouri.ed
u+interface+procurve2:1.19 --defaultCapacity=500000
14:40:37 INFO    : Configured logging from file /home/lnevers/gcf-2.7-rc2/src/gcf/stitcher_logging.conf
14:40:37 INFO    : Reading slice al2s-perf credential...
14:40:37 INFO    : Slice urn:publicid:IDN+ch.geni.net:ln-test+slice+al2s-perf expires on 2014-10-02 18:38:47 UTC
14:40:37 INFO    : Using SCS at http://nutshell.maxgigapop.net:8081/geni/xmlrpc
14:40:37 INFO    : Calling SCS...
14:40:40 INFO    : Multi-AM reservation will include resources from these aggregates:
14:40:40 INFO    : 	<Aggregate missouri-ig>
14:40:40 INFO    : 	<Aggregate stanford-ig>
14:40:40 INFO    : 	<Aggregate oess>
14:40:40 INFO    : Stitcher doing createsliver at <Aggregate missouri-ig>...
14:40:57 INFO    : ... Allocation at <Aggregate missouri-ig> complete.
14:40:57 INFO    : Stitcher doing createsliver at <Aggregate stanford-ig>...
14:41:22 INFO    : ... Allocation at <Aggregate stanford-ig> complete.
14:41:22 INFO    : Stitcher doing createsliver at <Aggregate oess>...
14:41:26 INFO    : ... Allocation at <Aggregate oess> complete.
14:41:26 INFO    : All aggregates are complete.
14:41:26 INFO    : Your resources expire at 2014-10-01T18:30:40 (UTC). 
14:41:26 INFO    : Saved combined reservation RSpec at 3 AMs to file '/home/lnevers/gcf-test/oess/Xconnect-stitch/al2s-perf-manifest-rspec-multiam-combined.xml'
Success: Reserved resources in slice al2s-perf at 3 Aggregates (including 1 intermediate aggregate(s) not in the original request), creating 1 stitched link(s).

Verified bandwidth allocation in the combined manifest file al2s-perf-manifest-rspec-multiam-combined.xml:

 <hop id="1"> <link id="urn:publicid:IDN+instageni.rnet.missouri.edu+interface+procurve2:1.19.al2s.kans.eth5_1">
 <capacity> 500000          </capacity>

 <hop id="2"> <link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.kans.net.internet2.edu:eth5/1:*">
 <capacity> 500000          </capacity>

 <hop id="3"> <link id="urn:publicid:IDN+al2s.internet2.edu+interface+sdn-sw.sunn.net.internet2.edu:e5/1:*">
 <capacity> 500000          </capacity>

 <hop id="4"> <link id="urn:publicid:IDN+instageni.stanford.edu+interface+procurve2:1.24.al2s.sunn.e5_1">
 <capacity> 500000          </capacity>

Note: Performance information is captured in the next section

This section verifies the allocation by running performance tests that show the bandwidth allocation.

Stanford to Missouri Iperf with TCP window size of 23.5 KByte (default):

[ ID] Interval       Transfer     Bandwidth
[SUM]  0.0-60.2 sec  2.81 GBytes   401 Mbits/sec

Stanford to Missouri Iperf with UDP window size of 224 KByte (default):

[ ID] Interval       Transfer     Bandwidth
[ 20]  0.0-60.0 sec  3.30 GBytes   472 Mbits/sec

Aggregate Advertisement of bandwidth allocation

Verify that Aggregate Advertisement of bandwidth allocation reflects configured bandwidth allocation defined by operator.

The following bandwidth is advertised by the OESS aggregate:

  <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.clev.net.internet2.edu:e5/1">
    <stitch:capacity> 10000000 </stitch:capacity>
  <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.star.net.internet2.edu:eth7/1">
    <stitch:capacity> 10000000 </stitch:capacity>
  <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.kans.net.internet2.edu:eth15/1">
    <stitch:capacity> 10000000 </stitch:capacity>
  <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.kans.net.internet2.edu:eth5/1">
    <stitch:capacity> 10000000 </stitch:capacity>
  <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.wash.net.internet2.edu:e5/2">
    <stitch:capacity> 10000000 </stitch:capacity>
  <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.sunn.net.internet2.edu:e5/1">
    <stitch:capacity> 10000000 </stitch:capacity>
  <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.losa.net.internet2.edu:e1/1">
    <stitch:capacity> 10000000 </stitch:capacity>
  <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.atla.net.internet2.edu:e15/1">
    <stitch:capacity> 10000000 </stitch:capacity>
  <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.jack.net.internet2.edu:eth1/2">
    <stitch:capacity> 10000000 </stitch:capacity>
  <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.chic.net.internet2.edu:e3/1">
    <stitch:capacity> 10000000 </stitch:capacity>
  <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.seat.net.internet2.edu:et-2/0/0.0">
    <stitch:capacity> 10000000 </stitch:capacity>
  <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.houh.net.internet2.edu:e15/3">
    <stitch:capacity> 10000000 </stitch:capacity>
  <stitch:port id="urn:publicid:IDN+al2s.internet2.edu+stitchport+sdn-sw.houh.net.internet2.edu:e7/1">
    <stitch:capacity> 10000000 </stitch:capacity>

Traffic Statistics

Traffic statistics for all GENI traffic to/from an operators site on OESS

UDP, TCP and ICMP perfomance was verified in the ION Site to AL2S site via 10 Cross Connects tests.

UDP, TCP and ICMP perfomance was also captured in the AL2S Sites point to point tests.

Operator deletes VLAN

Operator ability to delete existing VLANs that terminate at their site (the operator is not the experimenter who set up the connections).