1 | This file describes the various scenarios that are to be tested as part of the ExoGENI acceptance test EG-EXP-5, the "ExoGENI OpenFlow Network Resources" test case. |
---|
2 | |
---|
3 | Each of the scenarios includes 2 BBN Campus VMs which are NOT part of the ExoGENI rack. The OpenFlow flowspaces are managed with the ExoGENI FOAM aggregate. For each scenario there are 2 mesoscale remotes, one WAPG node on Internet2 and one MyPLC node on NLR. |
---|
4 | |
---|
5 | The request RSpecs used in each of the scenarios are captured in a directory matching the scenario name: |
---|
6 | |
---|
7 | EG-EXP-5-scenario1: |
---|
8 | |
---|
9 | The initial run includes some modifications to cover as many features as possible concurently in a limited amount of time. |
---|
10 | Experiments were combined and run by one experimenter that includes the following ExoGENI !OpenFlow Network Resources. Here is an outline of the experiment run for the initial test run: |
---|
11 | |
---|
12 | '''Experiment1''': OF VLAN 1750 |
---|
13 | - Two BBN Campus VMs are used as endpoints. |
---|
14 | - BBN Campus hosts access OF VLAN 1750 via flowspaces through the ExoGENI OpenFlow switch. |
---|
15 | - The !OpenFlow flowspaces for OF VLAN 1750 are managed with the ExoGENI FOAM aggregate. |
---|
16 | - Three meso-scale remote sites: 1 WAPG at Rutgers(Internet2), 1 MyPLC at Clemson (NLR) and one at MyPLC at BBN. |
---|
17 | - Two BBN rack ExoGENI VMs on OF shared VLAN 1750 |
---|
18 | - NRL and Internet2 OpenFlow VLAN 3716 is used for all hosts in experiment1 to exchange traffic |
---|
19 | - Two RENCI rack ExoGENI VMs on OF shared VLAN 1750 |
---|
20 | |
---|
21 | |
---|
22 | '''Experiment 2''': Non-OF Multi-point VLAN 3705 |
---|
23 | - Two BBN campus VMs are used as endpoints. |
---|
24 | - BBN Campus hosts access non-OF Multi-point VLAN 3705 via flowspaces through the ExoGENI FOAM. |
---|
25 | - Four remote end-points: Washington, Winsonsin, Indiana, and a BBN host available in GPOLab. |
---|
26 | |
---|
27 | |
---|
28 | EG-EXP-5-scenario3: (to be added in future test runs) |
---|
29 | |
---|
30 | This scenario includes 2 campus VMs with an interface on VLAN 3705. We think that we'd just request some flowspace for this VM, for traffic on VLAN 3705 matching its MAC address or IP address or whatever, on the relevant ports. |
---|
31 | |
---|
32 | A pair of VMs, one with an interface on VLAN 1720 and one on 1721. This is a little more complicated, because our flowspace needs to include: |
---|
33 | Traffic on VLAN 1720 or VLAN 1721 from the campus uplink port. |
---|
34 | Traffic on VLAN 1750 from the GENI uplink port that matches your nodes in some way (MAC address, IP address, whatever). |
---|
35 | A controller that can do VLAN translation. |
---|
36 | |
---|
37 | |
---|