Changes between Version 1 and Version 2 of GENIRacksHome/AcceptanceTests/OpenGENIAcceptanceTestsPlan
- Timestamp:
- 05/23/14 14:25:32 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIRacksHome/AcceptanceTests/OpenGENIAcceptanceTestsPlan
v1 v2 3 3 = GENI Rack Aggregate Manager Acceptance Test Plan = 4 4 5 This page captures the GENI Racks Acceptance Test Plan to be executed for the BBN GENI Rack Aggregate Manager ( GRAM). This test plan is based on the [http://groups.geni.net/geni/wiki/GeniRacks GENI Racks Requirements] and it outlines all features that are normally validated for GENI Racks. The goal of this effort is to capture the state of the current features and to generate a list of missing feature that are required to meet all GENI Racks requirements.6 7 The BBN GRAMAcceptance Test effort will generate the following:8 - a [wiki:GENIRacksHome/AcceptanceTests/ GRAMAcceptanceTestsPlan GRAMAcceptance Test Plan], this document written on 05/16/2013.9 - tickets to track GRAMissues discovered in testing - are internal only10 - an '''[wiki:GENIRacksHome/ GRAMRacks/AcceptanceTestStatusApr2014 Acceptance Test Status - April 2014]''' page where test status and logs are found.11 - an intermediate '''[wiki:GENIRacksHome/ GRAMRacks/AcceptanceTestReportApr2014 Acceptance Test Report - April 2014]''' page to summarize state.5 This page captures the GENI Racks Acceptance Test Plan to be executed for the BBN GENI Rack Aggregate Manager (OpenGENI). This test plan is based on the [http://groups.geni.net/geni/wiki/GeniRacks GENI Racks Requirements] and it outlines all features that are normally validated for GENI Racks. The goal of this effort is to capture the state of the current features and to generate a list of missing feature that are required to meet all GENI Racks requirements. 6 7 The BBN OpenGENI Acceptance Test effort will generate the following: 8 - a [wiki:GENIRacksHome/AcceptanceTests/OpenGENIAcceptanceTestsPlan OpenGENI Acceptance Test Plan], this document written on 05/16/2013. 9 - tickets to track OpenGENI issues discovered in testing - are internal only 10 - an '''[wiki:GENIRacksHome/OpenGENIRacks/AcceptanceTestStatusApr2014 Acceptance Test Status - April 2014]''' page where test status and logs are found. 11 - an intermediate '''[wiki:GENIRacksHome/OpenGENIRacks/AcceptanceTestReportApr2014 Acceptance Test Report - April 2014]''' page to summarize state. 12 12 13 13 == Assumptions and Dependencies == … … 15 15 The following assumptions are made for all tests described in this plan: 16 16 17 * GRAMClearing house credentials will be used for all tests.18 * GRAMis the slice authority for all tests in this plan.17 * OpenGENI Clearing house credentials will be used for all tests. 18 * OpenGENI is the slice authority for all tests in this plan. 19 19 * No tests using the GENI Clearinghouse and GPO ProtoGENI credentials are planned for the initial tests. 20 * Resources for each test will be requested from the GRAMAggregate Manager.20 * Resources for each test will be requested from the OpenGENI Aggregate Manager. 21 21 * Compute resources are VMs unless otherwise stated, there are no dedicated devices available for this initial evaluation. 22 22 * All Aggregate Manager requests are made via the Omni command line tool which uses the GENI AM API. 23 23 * In all scenarios, one experiment is always equal to one slice. 24 * Currently there is only one GRAMrack, which has the following test implications. All scenarios that are meant to be run on 1 rack will be run within 1 VM. All scenarios that are meant to have multiple racks, will use VMs on multiple servers.25 * GRAMwill be used as the interface to the rack !OpenFlow resources in the !OpenFlow test cases.26 27 It is expected that the GRAM Aggregate Manager will provide an interface into the (VLAN-based Multiplexed !OpenFlow Controller) VMOC aggregate. If the GRAMinterface to VMOC is not available, tests will be executed by submitting requests directly to VMOC.28 29 If the GRAM solution does not provide support for experimenters uploading custom VM images to the rack, any test case using custom images will modified to use available images for the rack. The ability to upload a custom VM image to the GRAMrack will be tested when it becomes available.24 * Currently there is only one OpenGENI rack, which has the following test implications. All scenarios that are meant to be run on 1 rack will be run within 1 VM. All scenarios that are meant to have multiple racks, will use VMs on multiple servers. 25 * OpenGENI will be used as the interface to the rack !OpenFlow resources in the !OpenFlow test cases. 26 27 It is expected that the OpenGENI Aggregate Manager will provide an interface into the (VLAN-based Multiplexed !OpenFlow Controller) VMOC aggregate. If the OpenGENI interface to VMOC is not available, tests will be executed by submitting requests directly to VMOC. 28 29 If the OpenGENI solution does not provide support for experimenters uploading custom VM images to the rack, any test case using custom images will modified to use available images for the rack. The ability to upload a custom VM image to the OpenGENI rack will be tested when it becomes available. 30 30 31 31 … … 41 41 This section describes each acceptance test by defining its goals, topology, and outline test procedure. Test cases are listed by priority in sections below. The cases that verify the largest number of requirement criteria are typically listed at a higher priority. The prerequisite tests are usually executed first to verify that baseline monitoring and administrative functions are available. This allows the execution of the experimenter test cases. Additional monitoring and administrative tests described in later sections that are also run before the completion of the acceptance test effort. 42 42 43 For the GRAMAcceptance Test evaluation some of these administrative and monitoring features may not be available but the tests are still planned in order to capture the availability of expected features.43 For the OpenGENI Acceptance Test evaluation some of these administrative and monitoring features may not be available but the tests are still planned in order to capture the availability of expected features. 44 44 45 45 == Administration Prerequisite Tests == … … 48 48 49 49 50 === GR-ADM-1: Rack Receipt and Inventory Test ===50 === OG-ADM-1: Rack Receipt and Inventory Test === 51 51 52 52 This acceptance test uses BBN as an example site because it requires physical access to the rack. The goal of this test is to verify that administrators can integrate the rack into a standard local procedures for systems hosted by the site. … … 58 58 * Power and wire the BBN rack 59 59 * Administrator configures the gramm.gpolab.bbn.com DNS namespace and 192.1.242.128/25 IP space, and enters all public IP addresses used by the rack into DNS. 60 * Administrator requests and receives administrator accounts on the rack and receive read access to all GRAMmonitoring of the rack.60 * Administrator requests and receives administrator accounts on the rack and receive read access to all OpenGENI monitoring of the rack. 61 61 * Administrator inventories the physical rack contents, network connections and VLAN configuration, and power connectivity, using standard operational inventories. 62 * Administrator, GRAM team, and GMOC share information about contact information and change control procedures, and GRAMoperators subscribe to GENI operations mailing lists and submit their contact information to GMOC.62 * Administrator, OpenGENI team, and GMOC share information about contact information and change control procedures, and OpenGENI operators subscribe to GENI operations mailing lists and submit their contact information to GMOC. 63 63 * Administrator reviews the documented parts list, power requirements, physical and logical network connectivity requirements, and site administrator community requirements, verifying that these documents should be sufficient for a new site to use when setting up a rack. 64 64 65 65 66 === GR-ADM-2: Rack Administrator Access Test ===66 === OG-ADM-2: Rack Administrator Access Test === 67 67 68 68 This test verifies local and remote administrative access to rack devices. … … 81 81 * Verify that you cannot login to the device via an unencrypted login protocol. 82 82 * Use the "enable" command or equivalent to verify privileged access. 83 3. Verify that GRAMremote console solution for rack hosts can be used to access the consoles all server hosts and experimental hosts:83 3. Verify that OpenGENI remote console solution for rack hosts can be used to access the consoles all server hosts and experimental hosts: 84 84 * Login via SSH or other encrypted protocol. 85 85 * Verify that you cannot login via an unencrypted login protocol. … … 90 90 These tests verify the availability of information needed to determine rack state, and needed to debug problems during experimental testing. Also verified is the ability to determine the rack components' test-readiness. Additional monitoring tests are defined in a later section to complete the validation in this section. 91 91 92 === GR-MON-1: Control Network Software and VLAN Inspection Test ===92 === OG-MON-1: Control Network Software and VLAN Inspection Test === 93 93 94 94 This test inspects the state of the rack control network, infrastructure nodes, and system software. … … 100 100 * A site administrator reviews the MAC address table on the control plane switch, and verifies that all entries are identifiable and expected. 101 101 102 === GR-MON-2: GENI Software Configuration Inspection Test ===102 === OG-MON-2: GENI Software Configuration Inspection Test === 103 103 104 104 This test inspects the state of the GENI AM software in use on the rack. … … 106 106 ==== Procedure ==== 107 107 108 * A site administrator uses available system data sources (process listings, monitoring output, system logs, etc) and/or AM administrative interfaces to determine the configuration of GRAMresources:108 * A site administrator uses available system data sources (process listings, monitoring output, system logs, etc) and/or AM administrative interfaces to determine the configuration of OpenGENI resources: 109 109 * How many experimental nodes are available for bare metal use, how many are configured as !OpenStack containers, and how many are configured as !PlanetLab containers. 110 110 * What operating system each !OpenStack container makes available for experimental VMs. 111 111 * How many unbound VLANs are in the rack's available pool. 112 * Whether the GRAMand !OpenFlow AMs trust the pgeni.gpolab.bbn.com slice authority, which will be used for testing. Note, that the pgeni.gpolab.bbn.com slice authority is not used in this test, a local slice authority is used for the initial evaluation.113 * A site administrator uses available system data sources to determine the configuration of !OpenFlow resources according to VMOC and GRAM.114 115 === GR-MON-3: GENI Active Experiment Inspection Test ===112 * Whether the OpenGENI and !OpenFlow AMs trust the pgeni.gpolab.bbn.com slice authority, which will be used for testing. Note, that the pgeni.gpolab.bbn.com slice authority is not used in this test, a local slice authority is used for the initial evaluation. 113 * A site administrator uses available system data sources to determine the configuration of !OpenFlow resources according to VMOC and OpenGENI. 114 115 === OG-MON-3: GENI Active Experiment Inspection Test === 116 116 117 117 This test inspects the state of the rack data plane and control networks when experiments are running, and verifies that a site administrator can find information about running experiments. … … 135 135 == Experimenter Acceptance Tests == 136 136 137 For the GRAM Acceptance Test evaluation some of these topologies normally validated in GENI Racks are not possible. This effort has only one rack available. Each test case is described as originally intended, but additionally there are details to show how the test case is modified for the initial GRAMevaluation. Topologies not be available but the tests are still planned as intended in order to capture the availability of expected features.138 139 === GR-EXP-1: Bare Metal Support Acceptance Test ===137 For the OpenGENI Acceptance Test evaluation some of these topologies normally validated in GENI Racks are not possible. This effort has only one rack available. Each test case is described as originally intended, but additionally there are details to show how the test case is modified for the initial OpenGENI evaluation. Topologies not be available but the tests are still planned as intended in order to capture the availability of expected features. 138 139 === OG-EXP-1: Bare Metal Support Acceptance Test === 140 140 141 141 Bare metal nodes are exclusive dedicated physical nodes that are used throughout the experimenter test cases. This section outlines features to be verified which are not explicitly validated in other scenarios: … … 144 144 2. Obtain 2 licensed recent Microsoft OS images for physical nodes from the site (BBN). 145 145 3. Reserve and boot 2 physical nodes using Microsoft image. 146 4. Obtain a recent Linux OS image for physical nodes from the GRAMlist.146 4. Obtain a recent Linux OS image for physical nodes from the OpenGENI list. 147 147 5. Reserve and boot a physical node using this Linux OS image. 148 148 6. Release physical node resource. … … 154 154 155 155 156 === GR-EXP-2: GRAMSingle Site Acceptance Test ===157 158 This one site test is run on the BBN GRAMrack and it includes two experiments. Each experiment requests local compute resources, which generate bidirectional traffic over a Layer 2 data plane network connection. The goals of this test are to verify basic operations of VMs and data flows within one rack; verify the ability to request a publically routable IP address and public TCP/UDP port mapping for a control interface on a compute resource; and verify the ability to add a customized image for the rack.156 === OG-EXP-2: OpenGENI Single Site Acceptance Test === 157 158 This one site test is run on the BBN OpenGENI rack and it includes two experiments. Each experiment requests local compute resources, which generate bidirectional traffic over a Layer 2 data plane network connection. The goals of this test are to verify basic operations of VMs and data flows within one rack; verify the ability to request a publically routable IP address and public TCP/UDP port mapping for a control interface on a compute resource; and verify the ability to add a customized image for the rack. 159 159 160 160 … … 163 163 This test uses this topology: 164 164 165 [[Image( GRAMSingleSiteAcceptanceTest.jpg)]]165 [[Image(OpenGENISingleSiteAcceptanceTest.jpg)]] 166 166 167 167 ''Note:'' The diagram shows the logical end-points for each experiment traffic exchange. The VMs may or may not be on different experiment nodes. … … 169 169 For the initial evaluation there are no bare metal nodes, so the test case is modified to have only VMs. Here is the actual topology run: 170 170 171 [[Image( GRAMSingleSiteAcceptanceTest-actual.jpg)]]171 [[Image(OpenGENISingleSiteAcceptanceTest-actual.jpg)]] 172 172 173 173 ''Evaluation Note:'' Test case is described for the original test case, actual procedure will be captures as part of test details available from the [https://superior.bbn.com/trac/bbn-rack/wiki/AcceptanceTestStatus Acceptance Test Status] page. … … 177 177 This test has these prerequisites: 178 178 179 * GRAMmakes available at least two Linux distributions and a FreeBSD image. If the not available, test will be run with available images.180 * Two GPO customized Ubuntu image snapshots are available and have been manually uploaded by the rack administrator using available GRAMdocumentation. One Ubuntu image is for the VM and one Ubuntu image is for the physical node in this test. Physical node are not available, so VM will be used.179 * OpenGENI makes available at least two Linux distributions and a FreeBSD image. If the not available, test will be run with available images. 180 * Two GPO customized Ubuntu image snapshots are available and have been manually uploaded by the rack administrator using available OpenGENI documentation. One Ubuntu image is for the VM and one Ubuntu image is for the physical node in this test. Physical node are not available, so VM will be used. 181 181 * Traffic generation tools may be part of image or may be installed at experiment runtime. 182 * Administrative accounts have been created for GPO staff on the BBN GRAMrack.182 * Administrative accounts have been created for GPO staff on the BBN OpenGENI rack. 183 183 * GENI Experimenter1 and Experimenter2 accounts exist at the GPO PG Clearinghouse. 184 184 * If available, use baseline Monitoring to ensure that any problems are quickly identified. … … 189 189 Do the following: 190 190 191 1. As Experimenter1, request !ListResources from BBN GRAM.191 1. As Experimenter1, request !ListResources from BBN OpenGENI. 192 192 2. Review advertisement RSpec for a list of OS images which can be loaded, and identify available resources. 193 193 3. Verify that the GPO Ubuntu customized image is available in the advertisement RSpec. … … 197 197 7. Log in to each of the systems, and send traffic to the other system sharing a VLAN. 198 198 8. Using root privileges on one of the VMs load a Kernel module. If not supported on !OpenStack nodes, testing will proceed past this step. 199 9. Run a netcat listener and bind to port XYZ on each of the VMs in the BBN GRAMrack.200 10. Send traffic to port XYZ on each of the VMs in the GRAMrack over the control network from any commodity Internet host.201 11. As Experimenter2, request !ListResources from Site2 GRAM.199 9. Run a netcat listener and bind to port XYZ on each of the VMs in the BBN OpenGENI rack. 200 10. Send traffic to port XYZ on each of the VMs in the OpenGENI rack over the control network from any commodity Internet host. 201 11. As Experimenter2, request !ListResources from Site2 OpenGENI. 202 202 12. Define a request RSpec for two physical nodes, both using the uploaded GPO Ubuntu images. If not available, VMs and other images will be used. 203 203 13. Create the second slice. … … 210 210 20. Stop traffic and delete slivers. 211 211 212 === GR-EXP-3: GRAMSingle Site 100 VM Test ===213 214 This one site test runs on the BBN GRAM rack and includes various scenarios to validate compute resource requirements for VMs. The goal of this test is not to validate the GRAM limits, but simply to verify that the GRAMrack can provide 100 VMs with its experiment nodes under various scenarios, including:212 === OG-EXP-3: OpenGENI Single Site 100 VM Test === 213 214 This one site test runs on the BBN OpenGENI rack and includes various scenarios to validate compute resource requirements for VMs. The goal of this test is not to validate the OpenGENI limits, but simply to verify that the OpenGENI rack can provide 100 VMs with its experiment nodes under various scenarios, including: 215 215 216 216 * Scenario 5: 100 Slices with 1 VM each … … 226 226 This test uses this topology: 227 227 228 [[Image( GRAMSingleSiteLimitsTest.jpg)]]228 [[Image(OpenGENISingleSiteLimitsTest.jpg)]] 229 229 230 230 ==== Prerequisites ==== … … 232 232 233 233 * Traffic generation tools may be part of image or installed at experiment runtime. 234 * Administrative accounts exist for GPO staff on the BBN GRAMrack.234 * Administrative accounts exist for GPO staff on the BBN OpenGENI rack. 235 235 * GENI Experimenter1 account exists at GPO PG Clearinghouse. 236 236 * If available, baseline Monitoring is used to ensure that any problems are quickly identified. … … 240 240 Do the following: 241 241 242 1. As Experimenter1, request !ListResources from BBN GRAM.242 1. As Experimenter1, request !ListResources from BBN OpenGENI. 243 243 2. Review !ListResources output, and identify available resources. 244 244 3. Write the Scenario 1 RSpec that requests 100 VMs evenly distributed across the experiment nodes using the default image. … … 258 258 259 259 260 === GR-EXP-4: GRAMMulti-site Acceptance Test ===260 === OG-EXP-4: OpenGENI Multi-site Acceptance Test === 261 261 262 262 This test normally includes two sites and two experiments. Only one rack is available, so the test case will be modified to run within one rack, but VMs will be requested on separate servers. Each of the compute resources will exchange traffic. In addition, the VMsin Experiment2 will use multiple data interfaces. Normally, all site-to-site experiments take place over a wide-area Layer 2 data plane network connection via Internet2 or NLR using VLANs allocated by the AM, that is not the case for the initial test evaluation, all connections will be within the rack. The goal of this test is to verify basic operations of VMs and data flows between rack resources. … … 266 266 This test uses this topology: 267 267 268 [[Image( GRAMMultiSiteAcceptanceTest.jpg)]]268 [[Image(OpenGENIMultiSiteAcceptanceTest.jpg)]] 269 269 270 270 271 271 For the initial evaluation there is only one rack, so the test case is modified to have VMs on different servers rather than different racks. Here is the actual topology run: 272 272 273 [[Image( GRAMMultiSiteAcceptanceTest-actual.jpg)]]273 [[Image(OpenGENIMultiSiteAcceptanceTest-actual.jpg)]] 274 274 275 275 ''Evaluation Note:'' Test case is described for the original test case, actual procedure will be captures as part of test details available from the [https://superior.bbn.com/trac/bbn-rack/wiki/AcceptanceTestStatus Acceptance Test Status] page. … … 280 280 This test has these prerequisites: 281 281 282 * If available, BBN GRAMconnectivity statistics will be monitored.283 * Administrative accounts have been created for GPO staff at the BBN GRAMrack.282 * If available, BBN OpenGENI connectivity statistics will be monitored. 283 * Administrative accounts have been created for GPO staff at the BBN OpenGENI rack. 284 284 * The VLANs used will be allocated by the rack AM. 285 285 * If available, baseline Monitoring is used to ensure that any problems are quickly identified. 286 * GRAMmanages private address allocation for the endpoints in this test.286 * OpenGENI manages private address allocation for the endpoints in this test. 287 287 * Normal network aggregate requirement for the availability of the ION AM do not apply to current evaluation. 288 288 … … 291 291 Do the following: 292 292 293 1. As Experimenter1, Request !ListResources from BBN GRAM.294 2. Request !ListResources for second GRAMAM (does not exist, thus skipping step).293 1. As Experimenter1, Request !ListResources from BBN OpenGENI. 294 2. Request !ListResources for second OpenGENI AM (does not exist, thus skipping step). 295 295 3. Review !ListResources output from both AMs. (only one am used in this initial evaluation). 296 4. Define a request RSpec for VMs at BBN GRAMto be on separate VM servers.297 5. Define a request RSpec for a VM at remote GRAMfor an unbound exclusive non-!OpenFlow VLAN to connect the 2 endpoints.296 4. Define a request RSpec for VMs at BBN OpenGENI to be on separate VM servers. 297 5. Define a request RSpec for a VM at remote OpenGENI for an unbound exclusive non-!OpenFlow VLAN to connect the 2 endpoints. 298 298 6. Create the first slice. 299 7. Create a sliver at each GRAMaggregate using the RSpecs defined above.299 7. Create a sliver at each OpenGENI aggregate using the RSpecs defined above. 300 300 8. Log in to each of the systems, and send traffic to the other system, leave traffic running. 301 9. As Experimenter2, Request !ListResources from BBN GRAM, (skipping second remote GRAM)302 10. Define an request RSpec for one VM and one bare metal node in the BBN GRAMrack. Each resource should have two logical interfaces and a 3rd VLAN for the local connection.303 11. Define a request RSpec to add two VMs at Site2 and two VLANs to connect the BBN GRAM to the Site2 GRAM. (Modified for one aggregate)301 9. As Experimenter2, Request !ListResources from BBN OpenGENI, (skipping second remote OpenGENI) 302 10. Define an request RSpec for one VM and one bare metal node in the BBN OpenGENI rack. Each resource should have two logical interfaces and a 3rd VLAN for the local connection. 303 11. Define a request RSpec to add two VMs at Site2 and two VLANs to connect the BBN OpenGENI to the Site2 OpenGENI. (Modified for one aggregate) 304 304 12. Create a second slice. 305 13. In the second slice, create a sliver at each GRAMaggregate using the RSpecs defined above. (Modified for one aggregate)305 13. In the second slice, create a sliver at each OpenGENI aggregate using the RSpecs defined above. (Modified for one aggregate) 306 306 14. Log in to each of the end-point systems, and send traffic to the other end-point system which shares the same VLAN. 307 307 15. Verify traffic handling per experiment, VM isolation, and MAC address assignment. … … 314 314 315 315 316 === GR-EXP-5: GRAMNetwork Resources Acceptance Test ===317 318 A three site experiment where the only GRAM resources used are !OpenFlow network resources. All compute resources are outside the GRAM rack. The experiment will use the GRAM Aggregate Manager to request the rack data plane resources. The GRAM AM configures the GRAM site !OpenFlow switch. The goal of this test is to verify !OpenFlow operations and integration with meso-scale compute resources and other compute resources external to the GRAMrack.316 === OG-EXP-5: OpenGENI Network Resources Acceptance Test === 317 318 A three site experiment where the only OpenGENI resources used are !OpenFlow network resources. All compute resources are outside the OpenGENI rack. The experiment will use the OpenGENI Aggregate Manager to request the rack data plane resources. The OpenGENI AM configures the OpenGENI site !OpenFlow switch. The goal of this test is to verify !OpenFlow operations and integration with meso-scale compute resources and other compute resources external to the OpenGENI rack. 319 319 320 320 ==== Test Topology ==== 321 321 322 [[Image( GRAMOFNetworkResourceAcceptanceTest.jpg)]]322 [[Image(OpenGENIOFNetworkResourceAcceptanceTest.jpg)]] 323 323 324 324 ''Note:'' The NLR and Internet2 !OpenFlow VLANs are the [wiki:NetworkCore GENI Network Core] static VLANs. … … 326 326 For the initial evaluation there is only one rack, so the test case is modified to have VMs on different servers rather than different racks. Here is the actual topology run: 327 327 328 [[Image( GRAMOFNetworkResourceAcceptanceTest-actual.jpg)]]328 [[Image(OpenGENIOFNetworkResourceAcceptanceTest-actual.jpg)]] 329 329 330 330 331 331 ==== Prerequisites ==== 332 332 333 - A GPO site network is connected to the GRAM!OpenFlow switch.334 - GRAM VMOC is running and can manage the GRAM!OpenFlow switch333 - A GPO site network is connected to the OpenGENI !OpenFlow switch. 334 - OpenGENI VMOC is running and can manage the OpenGENI !OpenFlow switch 335 335 - An !OpenFlow controller is run by the experimenter and is accessible via DNS hostname (or IP address) and TCP port. 336 336 - Two meso-scale remote sites make compute resources and !OpenFlow meso-scale resources available for this test. 337 - GMOC data collection for the meso-scale and GRAMrack resources is functioning for the !OpenFlow and traffic measurements required in this test.337 - GMOC data collection for the meso-scale and OpenGENI rack resources is functioning for the !OpenFlow and traffic measurements required in this test. 338 338 339 339 ''Evaluation Note:'' GMOC data collection is not available for the initial evaluation. Remote meso-scale sites are not possible for the initial evaluation and will be replaced by local rack nodes. … … 343 343 1. As Experimenter1, Determine BBN compute resources and define RSpec. 344 344 2. Determine remote meso-scale compute resources and define RSpec. (Modified for one aggregate and no meso-scale) 345 3. Define a request RSpec for !OpenFlow network resources at the BBN GRAMAM.345 3. Define a request RSpec for !OpenFlow network resources at the BBN OpenGENI AM. 346 346 4. Define a request RSpec for !OpenFlow network resources at the remote I2 Meso-scale site. (Rack nodes will replace remote meso-scale.) 347 347 5. Define a request RSpec for the !OpenFlow Core resources … … 349 349 7. Create a sliver for the BBN compute resources. 350 350 8. Create a sliver at the I2 meso-scale site using VMOC at site. (Modified for one aggregate and no meso-scale) 351 9. Create a sliver at of the BBN GRAMAM.351 9. Create a sliver at of the BBN OpenGENI AM. 352 352 10. Create a sliver for the !OpenFlow resources in the core. (Modified for one aggregate and no meso-scale) 353 353 11. Create a sliver for the meso-scale compute resources. (Modified for one aggregate and no meso-scale) … … 357 357 14. As Experimenter2, determine BBN compute resources and define RSpec. 358 358 15. Determine remote meso-scale compute resources and define RSpec. 359 16. Define a request RSpec for !OpenFlow network resources at the BBN GRAMAM.359 16. Define a request RSpec for !OpenFlow network resources at the BBN OpenGENI AM. 360 360 17. Define a request RSpec for !OpenFlow network resources at the remote NLR Meso-scale site. (Rack nodes will replace remote meso-scale.) 361 361 18. Define a request RSpec for the !OpenFlow Core resources (No core resources will be used in initial evaluation) … … 363 363 20. Create a sliver for the BBN compute resources. 364 364 21. Create a sliver at the meso-scale site using FOAM at site. 365 22. Create a sliver at of the BBN GRAMAM.365 22. Create a sliver at of the BBN OpenGENI AM. 366 366 23. Create a sliver for the !OpenFlow resources in the core. 367 367 24. Create a sliver for the meso-scale compute resources. … … 372 372 29. Stop traffic and delete slivers. 373 373 374 === GR-EXP-6: GRAMand Meso-scale Multi-site !OpenFlow Acceptance Test ===375 376 This test case normally includes three sites and three experiments, using resources in the BBN and Site2 GRAMracks as well as meso-scale resources, where the network resources are the core !OpenFlow-controlled VLANs. Each of the compute resources will exchange traffic with the others in its slice, over a wide-area Layer 2 data plane network connection, using Internet2 and NLR VLANs. In particular, the following slices will be set up for this test:377 * Slice 1: One GRAMVM at each of BBN and Site2.378 * Slice 2: Two GRAMVMs at Site2 and one VM and one bare metal node at BBN.379 * Slice 3: An GRAMVM at BBN, a PG node at BBN, and a meso-scale Wide-Area ProtoGENI (WAPG) node.374 === OG-EXP-6: OpenGENI and Meso-scale Multi-site !OpenFlow Acceptance Test === 375 376 This test case normally includes three sites and three experiments, using resources in the BBN and Site2 OpenGENI racks as well as meso-scale resources, where the network resources are the core !OpenFlow-controlled VLANs. Each of the compute resources will exchange traffic with the others in its slice, over a wide-area Layer 2 data plane network connection, using Internet2 and NLR VLANs. In particular, the following slices will be set up for this test: 377 * Slice 1: One OpenGENI VM at each of BBN and Site2. 378 * Slice 2: Two OpenGENI VMs at Site2 and one VM and one bare metal node at BBN. 379 * Slice 3: An OpenGENI VM at BBN, a PG node at BBN, and a meso-scale Wide-Area ProtoGENI (WAPG) node. 380 380 381 381 The above topology will be requested within one rack. … … 385 385 This test uses this topology: 386 386 387 [[Image( GRAMMultiSiteOpenFlowAcceptanceTest.jpg)]]387 [[Image(OpenGENIMultiSiteOpenFlowAcceptanceTest.jpg)]] 388 388 389 389 Note: The two Site2 VMs in Experiment2 must be on the same experiment node. This is not the case for other experiments. … … 392 392 For the initial evaluation there is only one rack, so the test case is modified to have VMs on different servers rather than different racks. Here is the actual topology run: 393 393 394 [[Image( GRAMMultiSiteOpenFlowAcceptanceTest-actual.jpg)]]394 [[Image(OpenGENIMultiSiteOpenFlowAcceptanceTest-actual.jpg)]] 395 395 396 396 ''Evaluation Note:'' Test case is described for the original test case, actual procedure will be captures as part of test details available from the [https://superior.bbn.com/trac/bbn-rack/wiki/AcceptanceTestStatus Acceptance Test Status] page. … … 401 401 402 402 * Meso-scale sites are available for testing 403 * BBN GRAM connectivity statistics are monitored at the GPO GRAMMonitoring site.403 * BBN OpenGENI connectivity statistics are monitored at the GPO OpenGENI Monitoring site. 404 404 * GENI Experimenter1, Experimenter2 and Experimenter3 accounts exist. 405 405 * This test will be scheduled at a time when site contacts are available to address any problems. 406 * Both GRAMaggregates can link to static VLANs. (Modified for one aggregate)406 * Both OpenGENI aggregates can link to static VLANs. (Modified for one aggregate) 407 407 * Site's !OpenFlow VLAN is implemented and is known for this test. (Use VMOC allocated OF VLANs) 408 408 * If available, baseline Monitoring is in place at each site, to ensure that any problems are quickly identified. 409 * GMOC data collection for the meso-scale and GRAMrack resources is functioning for the !OpenFlow and traffic measurements required in this test.409 * GMOC data collection for the meso-scale and OpenGENI rack resources is functioning for the !OpenFlow and traffic measurements required in this test. 410 410 * An !OpenFlow controller is run by the experimenter and is accessible via DNS hostname (or IP address) and TCP port. 411 411 * a PG !OpenFlow site is also added to the setup described in the diagram 412 412 413 413 414 ''Evaluation Note:'' There is no GMOC data colleciton and PG Site for initial GRAMevaluation.414 ''Evaluation Note:'' There is no GMOC data colleciton and PG Site for initial OpenGENI evaluation. 415 415 416 416 ==== Procedure ==== … … 418 418 Do the following: 419 419 420 1. As Experimenter1, request !ListResources from BBN GRAM, Site2 GRAM, and from VMOC at I2 and NLR Site.420 1. As Experimenter1, request !ListResources from BBN OpenGENI, Site2 OpenGENI, and from VMOC at I2 and NLR Site. 421 421 2. Review !ListResources output from all AMs. 422 3. Define a request RSpec for a VM at the BBN GRAM.423 4. Define a request RSpec for a VM at the Site2 GRAM. (only one site used)422 3. Define a request RSpec for a VM at the BBN OpenGENI. 423 4. Define a request RSpec for a VM at the Site2 OpenGENI. (only one site used) 424 424 5. Define request RSpecs for !OpenFlow resources from BBN FOAM to access GENI !OpenFlow core resources. (only one site used) 425 425 6. Define request RSpecs for !OpenFlow core resources at I2 FOAM (only one site used) … … 428 428 9. Create a sliver in the first slice at each AM, using the RSpecs defined above. 429 429 10. Log in to each of the systems, verify IP address assignment. Send traffic to the other system, leave traffic running. 430 11. As Experimenter2, define a request RSpec for one VM and one physical node at BBN GRAM.431 12. Define a request RSpec for two VMs on the same experiment node at Site2 GRAM. (only one site used)430 11. As Experimenter2, define a request RSpec for one VM and one physical node at BBN OpenGENI. 431 12. Define a request RSpec for two VMs on the same experiment node at Site2 OpenGENI. (only one site used) 432 432 11. Define request RSpecs for !OpenFlow resources from BBN FOAM to access GENI !OpenFlow core resources. (only one site used) 433 433 14. Define request RSpecs for !OpenFlow core resources at I2 FOAM. (only one site used) … … 436 436 17. Create a sliver in the second slice at each AM, using the RSpecs defined above. 437 437 18. Log in to each of the systems in the slice, and send traffic to each other systems; leave traffic running 438 19. As Experimenter3, request !ListResources from BBN GRAM, BBN meso-scale FOAM, and FOAM at Meso-scale Site (Internet2 Site BBN and NLR site). (only one site used)438 19. As Experimenter3, request !ListResources from BBN OpenGENI, BBN meso-scale FOAM, and FOAM at Meso-scale Site (Internet2 Site BBN and NLR site). (only one site used) 439 439 20. Review !ListResources output from all AMs. 440 21. Define a request RSpec for a VM at the BBN GRAM.440 21. Define a request RSpec for a VM at the BBN OpenGENI. 441 441 22. Define a request RSpec for a compute resource at the BBN meso-scale site. (only one site used) 442 442 23. Define a request RSpec for a compute resource at a meso-scale site. (only one site used) 443 24. Define request RSpecs for !OpenFlow resources to allow connection from !OpenFlow BBN GRAMto Meso-scale !OpenFlow sites(BBN and second site TBD) (I2 and NLR). (only one site used)443 24. Define request RSpecs for !OpenFlow resources to allow connection from !OpenFlow BBN OpenGENI to Meso-scale !OpenFlow sites(BBN and second site TBD) (I2 and NLR). (only one site used) 444 444 25. If PG access to !OpenFlow is available, define a request RSpec for the PG !OpenFlow resource. (only one site used) 445 445 26. Create a third slice. 446 27. Create slivers that connects the Internet2 Meso-scale !OpenFlow site to the BBN GRAMSite, and the BBN Meso-scale site; and if available, to PG node.447 28. Log in to each of the compute resources in the slice, configure data plane network interfaces on any non- GRAMresources as necessary, and send traffic to each other systems; leave traffic running.446 27. Create slivers that connects the Internet2 Meso-scale !OpenFlow site to the BBN OpenGENI Site, and the BBN Meso-scale site; and if available, to PG node. 447 28. Log in to each of the compute resources in the slice, configure data plane network interfaces on any non-OpenGENI resources as necessary, and send traffic to each other systems; leave traffic running. 448 448 29. Verify that all three experiment continue to run without impacting each other's traffic, and that data is exchanged over the path along which data is supposed to flow. 449 449 30. Review baseline monitoring statistics and checks. 450 31. As site administrator, identify all controllers that the BBN GRAM!OpenFlow switch is connected to.450 31. As site administrator, identify all controllers that the BBN OpenGENI !OpenFlow switch is connected to. 451 451 32. As Experimenter3, verify that traffic only flows on the network resources assigned to slivers as specified by the controller. 452 452 33. Verify that no default controller, switch fail-open behavior, or other resource other than experimenters' controllers, can control how traffic flows on network resources assigned to experimenters' slivers. … … 463 463 1. Verify access to documentation about which !OpenFlow actions can be performed in hardware. 464 464 465 === GR-EXP-7: Click Router Experiment Acceptance Test ===466 467 This test case uses a [http://read.cs.ucla.edu/click/click Click] modular router experiment with GRAMVM nodes. The scenario uses 2 VMs as hosts and 4 VMs as Click Routers and is based on the following [http://groups.geni.net/geni/wiki/ClickExampleExperiment Click example] experiment, although unlike the example, this test case uses VMs and it runs the Click router module in user space.465 === OG-EXP-7: Click Router Experiment Acceptance Test === 466 467 This test case uses a [http://read.cs.ucla.edu/click/click Click] modular router experiment with OpenGENI VM nodes. The scenario uses 2 VMs as hosts and 4 VMs as Click Routers and is based on the following [http://groups.geni.net/geni/wiki/ClickExampleExperiment Click example] experiment, although unlike the example, this test case uses VMs and it runs the Click router module in user space. 468 468 469 469 ==== Test Topology ==== … … 471 471 This test uses this topology: 472 472 473 [[Image( GRAMClickRouterAcceptanceTest.jpg)]]473 [[Image(OpenGENIClickRouterAcceptanceTest.jpg)]] 474 474 475 475 Note: Two VMs will be requested on the same physical worker node at each rack site for the user-level Click Router . … … 477 477 For the initial evaluation there is only one rack, so the test case is modified to have VMs on different servers rather than different racks. Here is the actual topology run: 478 478 479 [[Image( GRAMClickRouterAcceptanceTest-actual.jpg)]]479 [[Image(OpenGENIClickRouterAcceptanceTest-actual.jpg)]] 480 480 481 481 ''Evaluation Note:'' Test case is described for the original test case, actual procedure will be captures as part of test details available from the [https://superior.bbn.com/trac/bbn-rack/wiki/AcceptanceTestStatus Acceptance Test Status] page. The test case will be run within one rack. … … 491 491 Do the following: 492 492 493 1. As Experimenter1, request ListResources from BBN GRAM493 1. As Experimenter1, request ListResources from BBN OpenGENI 494 494 2. Review ListResources 495 3. Define a request RSpec for six VMs at BBN GRAM495 3. Define a request RSpec for six VMs at BBN OpenGENI 496 496 4. Create slice 497 497 5. Create a sliver … … 507 507 These tests will be performed as needed after the administration baseline tests complete successfully. For example, the Software Update Test will be performed at least once when the rack team provides new software for testing. We expect these tests to be interspersed with other tests in this plan at times that are agreeable to the GPO and the participants, not just run in a block at the end of testing. The goal of these tests is to verify that sites have adequate documentation, procedures, and tools to satisfy all GENI site requirements. 508 508 509 === GR-ADM-3: Full Rack Reboot Test ===509 === OG-ADM-3: Full Rack Reboot Test === 510 510 511 511 In this test, a full rack reboot is performed as a drill of a procedure which a site administrator may need to perform for site maintenance. … … 513 513 ''Note: this test must be run using the BBN rack because it requires physical access.'' 514 514 515 ''Evaluation note:'' Can this be executed for the BBN GRAMrack?515 ''Evaluation note:'' Can this be executed for the BBN OpenGENI rack? 516 516 517 517 ==== Procedure ==== … … 521 521 3. Power on all devices, bring all logical components back online, and use monitoring and comprehensive health tests to verify that the rack is healthy again. 522 522 523 === GR-ADM-4: Emergency Stop Test ===523 === OG-ADM-4: Emergency Stop Test === 524 524 525 525 In this test, an Emergency Stop drill is performed on a sliver in the rack. … … 528 528 529 529 * GMOC's updated Emergency Stop procedure is approved and published on a public wiki. 530 * GRAM's procedure for performing a shutdown operation on any type of sliver in an GRAM rack is published on a public wiki or on a protected wiki that all GRAMsite administrators (including GPO) can access.530 * OpenGENI's procedure for performing a shutdown operation on any type of sliver in an OpenGENI rack is published on a public wiki or on a protected wiki that all OpenGENI site administrators (including GPO) can access. 531 531 * An Emergency Stop test is scheduled at a convenient time for all participants and documented in GMOC ticket(s). 532 * A test experiment is running that involves a slice with connections to at least one GRAMrack compute resource.532 * A test experiment is running that involves a slice with connections to at least one OpenGENI rack compute resource. 533 533 534 534 ''Evaluation note:'' Emergency stop is not expected to be supported for the initial evaluation. … … 542 542 * GMOC completes the Emergency Stop workflow, including updating/closing GMOC tickets. 543 543 544 === GR-ADM-5: Software Update Test ===544 === OG-ADM-5: Software Update Test === 545 545 546 546 In this test, we update software on the rack as a test of the software update procedure. … … 548 548 ==== Prerequisites ==== 549 549 550 Minor updates of system packages for all infrastructure OSes, GRAMlocal AM software, and VMOC are available to be installed on the rack. This test may need to be scheduled to take advantage of a time when these updates are available.550 Minor updates of system packages for all infrastructure OSes, OpenGENI local AM software, and VMOC are available to be installed on the rack. This test may need to be scheduled to take advantage of a time when these updates are available. 551 551 552 552 ==== Procedure ==== … … 557 557 * At least one update of a standard (non-GENI) system package on the VMOC VM. 558 558 * At least one update of a standard (non-GENI) system package on the VM server host OS. 559 * An update of GRAMlocal AM software on control node.559 * An update of OpenGENI local AM software on control node. 560 560 * An update of VMOC software 561 561 * The admin confirms that the software updates completed successfully 562 562 * The admin updates any appropriate version tracking documentation or runs appropriate tool checks indicated by the version tracking procedure. 563 563 564 === GR-ADM-6: Control Network Disconnection Test ===564 === OG-ADM-6: Control Network Disconnection Test === 565 565 566 566 In this test, we disconnect parts of the rack control network or its dependencies to test partial rack functionality in an outage situation. … … 571 571 572 572 * Simulate an outage of ???? by inserting a firewall rule on the BBN router blocking the rack from reaching it. Verify that an administrator can still access the rack, that rack monitoring to GMOC continues through the outage, and that some experimenter operations still succeed. 573 * Simulate an outage of each of the rack server host and control plane switch by disabling their respective interfaces on the BBN's control network switch. Verify that GPO, GRAM, and GMOC monitoring all see the outage.574 575 ''Evaluation Note:'' The simulated outage does not apply to initial evaluation, there will be no monitoring by GMOC. Also there is no GRAMSNMP polling.576 577 578 === GR-ADM-7: Documentation Review Test ===573 * Simulate an outage of each of the rack server host and control plane switch by disabling their respective interfaces on the BBN's control network switch. Verify that GPO, OpenGENI, and GMOC monitoring all see the outage. 574 575 ''Evaluation Note:'' The simulated outage does not apply to initial evaluation, there will be no monitoring by GMOC. Also there is no OpenGENI SNMP polling. 576 577 578 === OG-ADM-7: Documentation Review Test === 579 579 580 580 Although this is not a single test ''per-se'', this section lists required documents that the rack teams will write. Draft documents should be delivered prior to testing of the functional areas to which they apply. Final documents must be deliveredto be made available for non-developer sites. Final documents will be public, unless there is some specific reason a particular document cannot be public (e.g. a security concern from a GENI rack site). … … 611 611 == Additional Monitoring Acceptance Tests == 612 612 613 These tests will be performed as needed after the monitoring baseline tests complete successfully. For example, the GMOC data collection test will be performed during the GRAMNetwork Resources Acceptance test, where we already use the GMOC for meso-scale !OpenFlow monitoring. We expect these tests to be interspersed with other tests in this plan at times that are agreeable to the GPO and the participants, not just run in a block at the end of testing. The goal of these tests is to verify that sites have adequate tools to view and share GENI rack data that satisfies all GENI monitoring requirements.614 615 === GR-MON-4: Infrastructure Device Performance Test ===613 These tests will be performed as needed after the monitoring baseline tests complete successfully. For example, the GMOC data collection test will be performed during the OpenGENI Network Resources Acceptance test, where we already use the GMOC for meso-scale !OpenFlow monitoring. We expect these tests to be interspersed with other tests in this plan at times that are agreeable to the GPO and the participants, not just run in a block at the end of testing. The goal of these tests is to verify that sites have adequate tools to view and share GENI rack data that satisfies all GENI monitoring requirements. 614 615 === OG-MON-4: Infrastructure Device Performance Test === 616 616 617 617 This test verifies that the rack head node performs well enough to run all the services it needs to run. … … 619 619 ==== Procedure ==== 620 620 621 While experiments involving GRAM-controlled !OpenFlow slivers and compute slivers are running:621 While experiments involving OpenGENI-controlled !OpenFlow slivers and compute slivers are running: 622 622 * View !OpenFlow control monitoring at GMOC and verify that no monitoring data is missing 623 623 * View VLAN 1750 data plane monitoring, which pings the rack's interface on VLAN 1750, and verify that packets are not being dropped … … 627 627 628 628 629 === GR-MON-5: GMOC Data Collection Test ===629 === OG-MON-5: GMOC Data Collection Test === 630 630 631 631 This test verifies the rack's submission of monitoring data to GMOC. … … 635 635 ==== Procedure ==== 636 636 637 View the dataset collected at GMOC for the BBN and Site2 GRAMracks. For each piece of required data, attempt to verify that:637 View the dataset collected at GMOC for the BBN and Site2 OpenGENI racks. For each piece of required data, attempt to verify that: 638 638 * The data is being collected and accepted by GMOC and can be viewed at gmoc-db.grnoc.iu.edu 639 * The data's "site" tag indicates that it is being reported for the GRAM rack located at the `gpolab` or GRAMsite2 site (as appropriate for that rack).639 * The data's "site" tag indicates that it is being reported for the OpenGENI rack located at the `gpolab` or OpenGENI site2 site (as appropriate for that rack). 640 640 * The data has been reported within the past 10 minutes. 641 641 * For each piece of data, either verify that it is being collected at least once a minute, or verify that it requires more complicated processing than a simple file read to collect, and thus can be collected less often. 642 642 643 643 Verify that the following pieces of data are being reported: 644 * Is each of the rack GRAMand VMOC AMs reachable via the GENI AM API right now?644 * Is each of the rack OpenGENI and VMOC AMs reachable via the GENI AM API right now? 645 645 * Is each compute or unbound VLAN resource at each rack AM online? Is it available or in use? 646 646 * Sliver count and percentage of rack compute and unbound VLAN resources in use. … … 670 670 == Issue Tracking == 671 671 1. All issues discovered in acceptance testing regardless of priority are to be tracked in a bug tracking system. 672 2. The bug tracking system to be used is the [https://superior.bbn.com/trac/bbn-rack/query?status=accepted&status=assigned&status=new&status=reopened&component=test GRAMtrac] using the "test" component.672 2. The bug tracking system to be used is the [https://superior.bbn.com/trac/bbn-rack/query?status=accepted&status=assigned&status=new&status=reopened&component=test OpenGENI trac] using the "test" component. 673 673 3. All types of issues encountered (documentation error, software bug, missing features, missing documentation, etc.) are to tracked. 674 674 4. All unresolved issues will be reviewed and published at the end of the acceptance test as part of the acceptance test report. … … 682 682 == Test Case Naming == 683 683 684 The test case in this plan follow a naming convention that uses '' GR-XXX-Y'' where ''GR'' is GRAMand ''XXX'' may equal any of the following: ''ADM'' for Administrative or ''EXP'' for Experimenter or ''MON'' for Monitoring. The final component of the test case name is the ''Y'', which is the test case number.684 The test case in this plan follow a naming convention that uses ''OG-XXX-Y'' where ''GR'' is OpenGENI and ''XXX'' may equal any of the following: ''ADM'' for Administrative or ''EXP'' for Experimenter or ''MON'' for Monitoring. The final component of the test case name is the ''Y'', which is the test case number. 685 685 686 686 = Requirements Validation =