| 1 | [[PageOutline]] |
| 2 | |
| 3 | = InstaGENI Xen Virtualization Test Plan = |
| 4 | |
| 5 | This page provides an outline of the planned testing to validate the InstaGENI support for paravirtualized Xen guests. This plan executes a survey of functional, limits and topology features. Testing will be executed using omni tools and GENI portal credentials. The following assumptions are made for the testing described in this page: |
| 6 | - Initial validation will take place on the Utah InstaGENI rack. |
| 7 | - Upon completion of initial validation, the GPO rack will also add Xen support. |
| 8 | - All two rack scenarios will use Utah and GPO racks. |
| 9 | |
| 10 | See the [wiki:InstageniXenTestStatus InstaGENI Xen Virtualization Test Status] page for detailed information about each test case execution and results. Upon successful completion of these tests, InstaGENI Xen Hosts will be introduced in the [http://groups.geni.net/geni/wiki/GENIRacksHome/InstageniRacks/SiteConfirmationTests New Site Confirmation Tests] for all new InstaGENI rack sites. |
| 11 | |
| 12 | == Guest Image support == |
| 13 | A series of test cases will be executed to verify Guest Image support, and they include the 3 test cases in the following sub-sections: |
| 14 | |
| 15 | === IG-XN-1: Supported OS tests === |
| 16 | |
| 17 | Verify each of the supported guest images with non-exclusive and exclusive resources. Guest image support tests will be executed on the Utah InstaGENI rack and will validate images supported for these operating systems: |
| 18 | |
| 19 | - FBSSD82-STD |
| 20 | - FEDORA15-STD |
| 21 | - UBUNTU12-64-STD |
| 22 | - UBUNTU11-64-STD |
| 23 | |
| 24 | Testing will execute the following experiments: |
| 25 | - One sliver with 4 Xen virtual hosts where each requests one of the supported images on 4 non-exclusive nodes. |
| 26 | - One sliver with 2 Xen dedicated hosts where 2 Ubuntu OS are requested |
| 27 | - One sliver with 2 Xen dedicated hosts where Fedora and FBSD OS are requested |
| 28 | |
| 29 | === IG-XN-2: Custom Xen Image Support tests === |
| 30 | |
| 31 | Verify custom image support for these operations: |
| 32 | - Create a custom guest image |
| 33 | - Run experiments that uses the custom guest image |
| 34 | - List custom images on aggregate to verify that the listing reflects guest images added. |
| 35 | - Delete custom guest image. |
| 36 | |
| 37 | === IG-XN-3: Xen Guests Limits Test === |
| 38 | |
| 39 | Verify the guest host allocation is as expected based on the Xen Server memory (TBD) and number of cores (TBD) available for: |
| 40 | - default memory guest size (512 MB) |
| 41 | - Maximum memory guest size (1024 MB) |
| 42 | |
| 43 | Tests will be executed incrementally and requests will be submitted sequentially until limit is reached. These tests will be scheduled in advance, as they have a major impact on the rack's resources. |
| 44 | |
| 45 | === IG-XN-4: Xen Negative and Boundary scenarios === |
| 46 | |
| 47 | Tests will be run that verify the handling of the following negative and boundary scenarios: |
| 48 | - Request for resource using unsupported OS |
| 49 | - Request for guests size larger that maximum allowed |
| 50 | - Request for guests size smaller that minimum allowed |
| 51 | - Request for guests exceeding available Xen resources |
| 52 | |
| 53 | |
| 54 | == Xen Resources Allocation == |
| 55 | |
| 56 | Xen resources allocation will be tested in the Utah InstaGENI Rack. |
| 57 | |
| 58 | === IG-XN-5: Xen Single Rack Resources Tests === |
| 59 | |
| 60 | Various Xen resources scenarios will be validated within the Utah InstaGENI Rack as detailed below: |
| 61 | |
| 62 | - 2 Xen exclusive hosts with one link |
| 63 | - 3 Xen non-exclusive hosts one link |
| 64 | - 1 Xen exclusive host and 1 Xen non-exclusive host with one link |
| 65 | - 1 Xen exclusive host and 1 OpenVZ exclusive host with one link |
| 66 | - 1 Xen non-exclusive host and 1 OpenVZ non-exclusive host with one link |
| 67 | - 2 Xen host connected by 2 links |
| 68 | |
| 69 | |
| 70 | == Xen Multi-rack Topologies == |
| 71 | |
| 72 | Various multi-rack topologies will be validated between Utah and GPO InstaGENI/ExoGENI Racks: |
| 73 | |
| 74 | === IG-XN-6: IG Utah Xen to IG GPO Xen with 1 stitched VLAN === |
| 75 | |
| 76 | This test case verifies a topology that requests one IG Utah Xen VM to one IG GPO Xen VM via 1 stitched VLAN via the Internet2 ION aggregate: |
| 77 | |
| 78 | [[Image(IG-XN-6.jpg)]] |
| 79 | |
| 80 | ''Note: If AL2S is available, it will be used in place of I2/ION'' |
| 81 | |
| 82 | === IG-XN-7: IG Utah Xen to IG GPO Xen with 2 stitched links === |
| 83 | |
| 84 | This test case verifies a topology that requests one IG Utah Xen VM to one IG GPO Xen connected with 2 stitched VLANs via the Internet2 ION aggregate. |
| 85 | |
| 86 | [[Image(IG-XN-7.jpg)]] |
| 87 | |
| 88 | ''Note: If AL2S is available, it will be used in place of I2/ION'' |
| 89 | |
| 90 | === IG-XN-8: IG Utah Xen to ExoGENI GPO VM with 1 stitched VLAN === |
| 91 | |
| 92 | This test case verifies a topology that requests one IG Utah Xen to one ExoGENI GPO VM with 1 stitched VLAN via the Internet2 ION aggregate. |
| 93 | |
| 94 | [[Image(IG-XN-8.jpg)]] |
| 95 | |
| 96 | ''Note: If AL2S is available, it will be used in place of I2/ION'' |
| 97 | |
| 98 | === IG-XN-9: IG GPO Xen to ExoGENI GPO VM via local VLANs === |
| 99 | |
| 100 | This test case verifies a topology that requests one IG GPO Xen to ExoGENI GPO VM via local VLANs. There is no GENI Network stitching support for the co-located racks such |
| 101 | as the ones at BBN. |
| 102 | |
| 103 | [[Image(IG-XN-9.jpg)]] |
| 104 | |
| 105 | === IG-XN-10: IG GPO Xen to ExoGENI GPO VM via OpenFlow === |
| 106 | |
| 107 | This test case verifies a topology that requests one IG GPO Xen to ExoGENI GPO VM via an OpenFlow VLANs. |
| 108 | |
| 109 | [[Image(IG-XN-10.jpg)]] |
| 110 | |
| 111 | === IG-XN-11: IG Utah Xen to IG GPO Xen with GRE link === |
| 112 | |
| 113 | This test case verifies a topology that requests one IG Utah Xen VM to IG GPO Xen VM via a GRE tunnel: |
| 114 | |
| 115 | [[Image(IG-XN-11.jpg)]] |
| 116 | |