| 24 | | 1. Create slice which results in VLANs allocation between AL2S InstaGENI end-point |
| 25 | | 2. Delete VLANs and verify release of VLANs via AL2S router proxy. |
| 26 | | 3. Submit multiple concurrent requests to add and to delete flow spaces. |
| 27 | | 4. Configure various rate limits and verify enforcement. |
| 28 | | 4. Query FSF status and rules via !FloodLight rest API. |
| 29 | | 5. Generate traffic outside of pre-defined flowspace and verify that it is handled properly. |
| 30 | | |
| 31 | | = Topology Scenarios = |
| 32 | | |
| 33 | | == FSF-T2 Two Site tests == |
| 34 | | |
| 35 | | Initial testing will take place with two sites that are already connected to AL2S. Multiple slivers will be created by multiple experimenters. Functional testing will be executed in this topology. |
| | 24 | Initial testing will take place with two sites that are already connected to AL2S. Multiple slivers will be created by multiple experimenters. |
| | 27 | |
| | 28 | |
| | 29 | Functional testing is executed within these simple node experiments: |
| | 30 | |
| | 31 | 1. Create slice which results in VLANs allocation between AL2S InstaGENI end-point and exchange traffic. Verify AL2S router proxy statistics. |
| | 32 | 2. Create slices to use configured number of VLANs, verify configuration is enforced and reflected in AL2S router proxy statistics. |
| | 33 | 3. Delete slices and and verify release of VLANs via AL2S router proxy. |
| | 34 | 4. Submit multiple concurrent requests to add and to delete flow spaces. |
| | 35 | 5. Configure various rate limits and verify enforcement. |
| | 36 | 6. Query FSF status and rules via !FloodLight rest API. |
| | 37 | 7. Generate traffic outside of pre-defined flowspace and verify that it is handled properly. |
| | 38 | 8. Create slice requesting specific VLAN outside of FSFW range, verify rejection. |
| | 39 | 9. Request network capacity beyond configured FSFW capacity, verify enforcement. |
