[[PageOutline]] = InstaGENI Xen Virtualization Test Plan = 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: - Initial validation will take place on the Utah InstaGENI rack. - Upon completion of initial validation, the GPO rack will be used to test multiple site scenarios. - All two-rack scenarios will use Utah and GPO racks. See the [wiki:GENIRacksHome/InstageniRacks/XenTestStatus 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 [wiki:GENIRacksHome/InstageniRacks/SiteConfirmationTests New Site Confirmation Tests] for all new InstaGENI rack sites. == Guest Image support == 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: === IG-XN-1: Supported OS tests === 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: - FBSSD82-STD - FEDORA15-STD - UBUNTU12-64-STD - UBUNTU11-64-STD Testing will execute the following experiments: - One sliver with 4 Xen virtual hosts where each requests one of the supported images on 4 non-exclusive nodes. - One sliver with 2 Xen dedicated hosts where 2 Ubuntu OS are requested - One sliver with 2 Xen dedicated hosts where Fedora and FBSD OS are requested === IG-XN-2: Custom Xen Image Support tests === Verify custom image support for each of the supported operating systems (FBSSD82-STD, FEDORA15-STD, UBUNTU12-64-STD, UBUNTU11-64-STD) by executing these operations: - Create a custom guest image - Run experiments that uses the custom guest image - List custom images on aggregate to verify that the listing reflects guest images added. - Delete custom guest image. === IG-XN-3: Xen Guests Limits Test === Verify the guest host allocation is as expected based on the Xen Server memory (TBD) and number of cores (TBD) available for: - default memory guest size (512 MB) - Maximum memory guest size (1024 MB) 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. === IG-XN-4: Xen Negative and Boundary scenarios === Tests will be run that verify the handling of the following negative and boundary scenarios: - Request for resource using unsupported OS - Request for guests size larger that maximum allowed - Request for guests size smaller that minimum allowed - Request for guests exceeding available Xen resources == Xen Resources Allocation == Xen resources allocation will be tested in the Utah InstaGENI Rack. === IG-XN-5: Xen Single Rack Resources Tests === Various Xen resources scenarios will be validated within the Utah InstaGENI Rack as detailed below: - 2 Xen exclusive hosts with one link - 3 Xen non-exclusive hosts one link - 1 Xen exclusive host and 1 Xen non-exclusive host with one link - 1 Xen exclusive host and 1 OpenVZ exclusive host with one link - 1 Xen non-exclusive host and 1 OpenVZ non-exclusive host with one link - 2 Xen host connected by 2 links == Xen Multi-rack Topologies == Various multi-rack topologies will be validated between Utah and GPO InstaGENI/ExoGENI Racks: === IG-XN-6: IG Utah Xen to IG GPO Xen with 1 stitched VLAN === 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. [[Image(IG-XN-6.jpg)]] ''Note: If AL2S is available, it will be used in place of I2/ION'' === IG-XN-7: IG Utah Xen to IG GPO Xen with 2 stitched links === 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. [[Image(IG-XN-7.jpg)]] ''Note: If AL2S is available, it will be used in place of I2/ION'' === IG-XN-8: IG Utah Xen to ExoGENI GPO VM with 1 stitched VLAN === 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. [[Image(IG-XN-8.jpg)]] ''Note: If AL2S is available, it will be used in place of I2/ION'' === IG-XN-9: IG GPO Xen to ExoGENI GPO VM via local VLANs === 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 as the ones at BBN. [[Image(IG-XN-9.jpg)]] === IG-XN-10: IG GPO Xen to ExoGENI GPO VM via !OpenFlow === This test case verifies a topology that requests one IG GPO Xen to ExoGENI GPO VM via an !OpenFlow VLANs. [[Image(IG-XN-10.jpg)]] === IG-XN-11: IG Utah Xen to IG GPO Xen with GRE link === This test case verifies a topology that requests one IG Utah Xen VM to IG GPO Xen VM via a GRE tunnel. [[Image(IG-XN-11.jpg)]] == Monitoring == A survey of resource monitoring will be executed to determine how Xen Resources compares to required GENI monitoring features. == IG-XN-12: Xen Resource Monitoring == Verify that Monitoring provides the following: - Identify Xen VMs resources - CPU Statistics - Disk Statistics - Virtualization statistics