wiki:GeniNetworkStitchingTestStatus/GNS-T6

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

--

GNS-T6 - Topology 6 - Utah PG to GPO InstaGENI

This page captures status and execution details for Topology 6 - Utah PG to GPO InstaGENI. For overall status see the GENI Network Stitching Test Status page and for test details see the GENI Network Stitching Test Plan page.

Last update: 07/16/13

Step State Ticket Comments
Step 1 Color(green,Pass)?
Step 2 Color(green,Pass)?
Step 3 Color(green,Pass)?
Step 4 Color(green,Pass)?
Step 5 Color(green,Pass)?
Step 6 Color(green,Pass)?
Step 7 Color(green,Pass)? Completed in Measurements Tests
Step 8
Step 9
Step 10


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

Assumptions and Notes:

  • GENI Clearinghouse credential are used.
  • Stitcher currently does not support AM API v3, and is delivered to run AM API V2.

GNS-T1 - Utah ProtoGENI to GPO InstaGENI

Verify stitching path for a scenario that has the end-points Utah ProtoGENI and GPO InstaGENI via Internet2 ION. This scenario will verify experimenter functions and some operator functions as described below.

Step 1. Create sliver

As Experimenter, use GENI AM API client to submit create sliver for initial Request RSpec. No aggregate needs to be specified, aggregates are determined from the Request RSpec.

$ omni.py createslice ig-gpo-pg-utah
20:21:11 INFO     omni: Loading config file /home/lnevers/.gcf/omni_config
20:21:11 INFO     omni: Using control framework portal
20:21:13 INFO     omni: Created slice with Name ig-gpo-pg-utah, URN urn:publicid:IDN+ch.geni.net:ln-prj+slice+ig-gpo-pg-utah, Expiration 2013-07-24 00:21:12
20:21:13 INFO     omni:  ------------------------------------------------------------
20:21:13 INFO     omni:  Completed createslice:

  Options as run:
		framework: portal
		project: ln-prj

  Args: createslice ig-gpo-pg-utah

  Result Summary: Created slice with Name ig-gpo-pg-utah, URN urn:publicid:IDN+ch.geni.net:ln-prj+slice+ig-gpo-pg-utah, Expiration 2013-07-24 00:21:12
20:21:13 INFO     omni:  ============================================================
$ stitcher.py createsliver ig-gpo-pg-utah ./stitch-ig-gpo-pg-utah.rspec -o
20:21:47 INFO     stitcher: Loading config file /home/lnevers/.gcf/omni_config
20:21:47 INFO     stitcher: Using control framework portal
20:21:47 INFO     stitcher: Checking that slice ig-gpo-pg-utah is valid...
20:21:48 INFO     stitcher: Slice urn:publicid:IDN+ch.geni.net:ln-prj+slice+ig-gpo-pg-utah expires on 2013-07-24 00:21:12 UTC
20:21:48 INFO     stitcher: <Aggregate urn:publicid:IDN+instageni.gpolab.bbn.com+authority+cm> speaks AM API v3, but sticking with v2
20:21:48 INFO     stitcher: <Aggregate urn:publicid:IDN+emulab.net+authority+cm> speaks AM API v3, but sticking with v2
20:21:48 INFO     stitch.Aggregate: Writing to '/tmp/ig-gpo-pg-utah-createsliver-request-11-instageni-gpolab-bbn-com.xml'
20:21:48 INFO     stitch.Aggregate: 
	Stitcher doing createsliver at https://boss.instageni.gpolab.bbn.com:12369/protogeni/xmlrpc/am
20:22:02 INFO     stitch.Aggregate: Allocation at <Aggregate urn:publicid:IDN+instageni.gpolab.bbn.com+authority+cm> complete.
20:22:02 WARNING  stitch.Aggregate: Slivers at PG Utah may not be requested initially for > 5 days. PG Utah slivers will expire earlier than at other aggregates - requested expiration being reset from 2013-07-24T00:21:12Z to 2013-07-22T00:02:02Z
20:22:02 INFO     stitch.Aggregate: Writing to '/tmp/ig-gpo-pg-utah-createsliver-request-11-emulab-net.xml'
20:22:02 INFO     stitch.Aggregate: 
	Stitcher doing createsliver at https://www.emulab.net:12369/protogeni/xmlrpc/am
20:22:37 INFO     stitch.Aggregate: Allocation at <Aggregate urn:publicid:IDN+emulab.net+authority+cm> complete.
20:22:37 INFO     stitch.Aggregate: Writing to '/tmp/ig-gpo-pg-utah-createsliver-request-11-ion-internet2-edu.xml'
20:22:37 INFO     stitch.Aggregate: 
	Stitcher doing createsliver at http://geni-am.net.internet2.edu:12346
20:23:20 INFO     stitch.Aggregate: DCN AM <Aggregate urn:publicid:IDN+ion.internet2.edu+authority+am>: must wait for status ready....
20:23:20 INFO     stitch.Aggregate: Pause to let circuit become ready...
20:23:57 INFO     stitch.Aggregate: DCN circuit 22981 is ready
20:24:04 INFO     stitch.Aggregate: Allocation at <Aggregate urn:publicid:IDN+ion.internet2.edu+authority+am> complete.
20:24:04 INFO     stitch.launcher: All aggregates are complete.
20:24:04 INFO     stitcher: Writing to 'ig-gpo-pg-utah-manifest-rspec-stitching-combined.xml'
20:24:04 INFO     stitcher: Saved combined reservation RSpec at 3 AMs to file ig-gpo-pg-utah-manifest-rspec-stitching-combined.xml
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).

Step 2. Verify Request RSpec for each Stitching Path Aggregate

Verify that request RSpec is expanded after Path Computation into one RSpec for each Stitching Path Aggregates (PG Utah, ION, and IG GPO).

All /tmp/ig-gpo-pg-utah-createsliver-request-* files were reviewed for accuracy, no issues found.

Step 3. Verify VLAN negotiation for PG Utah

Verify that workflow agent negotiates VLAN with Utah ProtoGENI using the RSpec from step 2 and generates a manifest for PG Utah resources.

Requested VLANs were available and no negotiation took place.

Step 4. Verify VLAN negotiation for IG GPO

Verify that workflow agent negotiates VLAN with GPO InstaGENI using the GPO RSpec from step 2 and generates a manifest for GPO resources.

Requested VLANs were available and no negotiation took place.

Step 5. Verify VLAN negotiation for I2/ION aggregate

Verify that workflow agent negotiates VLAN with ION using the ION RSpec from step 2 and generates a manifest for ION resources.

Requested VLANs were available and no negotiation took place. Also requested DCN circuits were available.

Step 6. Verify combined Manifest RSpec

Verify that the final "combined" RSpec reflects the allocate stitching and non-stitching resources.

Reviewed the combined manifest RSpec file ig-gpo-pg-utah-manifest-rspec-stitching-combined.xml was reviewed and contained the following stitching information:

	<stitching lastUpdateTime="2013-07-17T00:23:51.688Z" xmlns="http://hpn.east.isi.edu/rspec/ext/stitch/0.1/" xmlns:xsi="http://www.w3.org/2001/X
MLSchema-instance" xsi:schemaLocation="http://hpn.east.isi.edu/rspec/ext/stitch/0.1/ http://hpn.east.isi.edu/rspec/ext/stitch/0.1/stitch-schema.xsd">
		<path id="link">
			<globalId>
        ion.internet2.edu-22981
			</globalId>
			<lifetime id="ion.internet2.edu-22981">
				<start type="xgc">
          2013-07-24T00:21:12.000Z
				</start>
				<end type="xgc">
          2013-07-17T00:23:51.688Z
				</end>
			</lifetime>
			<hop id="1">
				<link id="urn:publicid:IDN+instageni.gpolab.bbn.com+interface+procurve2:5.24">
					<trafficEngineeringMetric>
						10
					</trafficEngineeringMetric>
					<capacity>
						100000
					</capacity>
					<switchingCapabilityDescriptor>
						<switchingcapType>
							l2sc
						</switchingcapType>
						<encodingType>
							ethernet
						</encodingType>
						<switchingCapabilitySpecificInfo>
							<switchingCapabilitySpecificInfo_L2sc>
								<interfaceMTU>
									9000
								</interfaceMTU>
								<vlanRangeAvailability>
									3748
								</vlanRangeAvailability>
								<suggestedVLANRange>
									3748
								</suggestedVLANRange>
								<vlanTranslation>
									false
								</vlanTranslation>
							</switchingCapabilitySpecificInfo_L2sc>
						</switchingCapabilitySpecificInfo>
					</switchingCapabilityDescriptor>
				</link>
				<nextHop>
					2
				</nextHop>
			</hop>
			<hop id="4">
				<link id="urn:publicid:IDN+emulab.net+interface+procurve-pgeni-atla:3.21">
					<trafficEngineeringMetric>
						10
					</trafficEngineeringMetric>
					<capacity>
						100000
					</capacity>
					<switchingCapabilityDescriptor>
						<switchingcapType>
							l2sc
						</switchingcapType>
						<encodingType>
							ethernet
						</encodingType>
						<switchingCapabilitySpecificInfo>
							<switchingCapabilitySpecificInfo_L2sc>
								<interfaceMTU>
									9000
								</interfaceMTU>
								<vlanRangeAvailability>
									775
								</vlanRangeAvailability>
								<suggestedVLANRange>
									775
								</suggestedVLANRange>
								<vlanTranslation>
									false
								</vlanTranslation>
							</switchingCapabilitySpecificInfo_L2sc>
						</switchingCapabilitySpecificInfo>
					</switchingCapabilityDescriptor>
				</link>
				<nextHop>
					null
				</nextHop>
			</hop>
		</path>
	</stitching>

Step 7. End-point to end-point measurements

Log in to compute resources at each Utah ProtoGENI and GPO InstaGENI, gather delay and throughput measurements. Leave traffic exchange running between the end-hosts.

Measurements are captured in http://groups.geni.net/geni/wiki/GeniNetworkStitchingTestStatus/Measurements.

Step 8. Operator review of experiment resources

As Operator, verify that nodes, ports, links, capacity can be determined as allocated for this experiment.

Step 9. Sliver expiration and resource de-allocation

As Experimenter, leave resources running with traffic being exchanged. Allow sliver to expire, verify that sliver resources/traffic have been deleted.

Step 10. Operator verify resources release

As Operator, verify that expired resource resources (nodes, ports, links, capacity) are released properly and made available and part of the Advertisement RSpec.