Changes between Version 4 and Version 5 of GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-EXP-2


Ignore:
Timestamp:
05/14/12 16:12:23 (12 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-EXP-2

    v4 v5  
    88This section captures the status for each step in the acceptance test plan.
    99
    10 || '''Step''' || '''State'''           || '''Date completed'''    ||''' Ticket ''' || '''Comments''' ||
    11 || Step 1     ||                       ||                         ||               ||                ||
    12 || Step 2     ||                       ||                         ||               ||                ||
     10|| '''Step''' || '''State'''                           || '''Date completed'''    ||''' Ticket ''' || '''Comments''' ||
     11|| Step 1     ||[[Color( #F0FFF0, #100000 , Complete)]]||                         ||               ||                ||
     12|| Step 2     ||[[Color( #F0FFF0, #100000 , Complete)]]||                         ||               ||                ||
    1313|| Step 3     ||                       ||                         ||               ||                ||
    1414|| Step 4     ||                       ||                         ||               ||                ||
     
    7373= Test Plan Steps =
    7474
    75  1. As Experimenter1, request !ListResources from Utah InstaGENI.
    76  2. Review advertisement RSpec for a list of OS images which can be loaded, and identify available resources.
    77  3. Verify that the GPO Ubuntu customized image is available in the advertisement RSpec.
    78  4. Define a request RSpec for two VMs, each with a GPO Ubuntu image. Request a publically routable IP address and public TCP/UDP port mapping for the control interface on each node.
    79  5. Create the first slice.
    80  6. Create a sliver in the first slice, using the RSpec defined in step 4.
    81  7. Log in to each of the systems, and send traffic to the other system sharing a VLAN.
    82  8. Using root privileges on one of the VMs load a Kernel module. It is expected this will not work on shared OpenVZ nodes, testing will proceed past this step.
    83  9. Run a netcat listener and bind to port XYZ on each of the VMs in the Utah rack.
    84  10. Send traffic to port XYZ on each of the VMs in the Utah rack over the control network from any commodity Internet host.
    85  11. As Experimenter2, request !ListResources from Utah InstaGENI.
    86  12. Define a request RSpec for two physical nodes, both using the uploaded GPO Ubuntu images.
    87  13. Create the second slice.
    88  14. Create a sliver in the second slice, using the RSpec defined in step 12.
    89  15. Log in to each of the systems, and send traffic to the other system.
    90  16. Verify that experimenters 1 and 2 cannot use the control plane to access each other's resources (e.g. via unauthenticated SSH, shared writable filesystem mount)
    91  17. Review system statistics and VM isolation and network isolation on data plane.
    92  18. Verify that each VM has a distinct MAC address for that interface.
    93  19. Verify that VMs' MAC addresses are learned on the data plane switch.
    94  20. Stop traffic and delete slivers.
     75== Step 1. As Experimenter1, request !ListResources from Utah InstaGENI ==
     76
     77As experimenter lnevers@bbn.com requested the list of available resources as follows:
     78{{{
     79 $ ./src/omni.py -a insta-utah listresources --available --api-version 2 -t GENI 3 --available -o
     80}}}
     81
     82== Step 2. Review advertisement RSpec for a list of OS images which can be loaded, and identify available resources ==
     83
     84Used the output file from previous step to determine list of OS images available and available compute resources:
     85{{{
     86 $ egrep "node component|disk_image|available" rspec-boss-utah-geniracks-net-protogeni-xmlrpc-am-2-0.xml
     87}}}
     88
     89The following disk images were listed:
     90{{{
     91<disk_image description="FreeBSD 8.2 32-bit version" name="urn:publicid:IDN+utah.geniracks.net+image+emulab-ops:FBSD82-STD" os="FreeBSD" version="8.2"/>     
     92<disk_image default="true" description="Standard 32-bit Fedora 15 image" name="urn:publicid:IDN+utah.geniracks.net+image+emulab-ops:FEDORA15-STD" os="Fedora" version="15"/>     
     93<disk_image description="Standard 64-bit Ubuntu 11 image" name="urn:publicid:IDN+utah.geniracks.net+image+emulab-ops:UBUNTU11-64-STD" os="Linux" version="11.04"/>     
     94<disk_image default="true" description="Standard 32-bit Fedora 15 image" name="urn:publicid:IDN+utah.geniracks.net+image+emulab-ops:FEDORA15-STD" os="Fedora" version="15"/>     
     95}}}
     96
     97Note instaticket:14 written for duplicate default image in the Advertisement RSpec.
     98
     99== Step 3. Verify that the GPO Ubuntu customized image is available in the advertisement RSpec ==
     100== Step 4. Define a request RSpec for two VMs, each with a GPO Ubuntu image. Request a publically routable IP address and public TCP/UDP port mapping for the control interface on each node ==
     101== Step 5. Create the first slice ==
     102== Step 6. Create a sliver in the first slice, using the RSpec defined in step 4 ==
     103== Step 7. Log in to each of the systems, and send traffic to the other system sharing a VLAN ==
     104== Step 8. Using root privileges on one of the VMs load a Kernel module. It is expected this will not work on shared OpenVZ nodes, testing will proceed past this step ==
     105== Step 9. Run a netcat listener and bind to port XYZ on each of the VMs in the Utah rack ==
     106== Step 10. Send traffic to port XYZ on each of the VMs in the Utah rack over the control network from any commodity Internet host ==
     107== Step 11. As Experimenter2, request !ListResources from Utah InstaGENI ==
     108== Step 12. Define a request RSpec for two physical nodes, both using the uploaded GPO Ubuntu images ==
     109== Step 13. Create the second slice ==
     110== Step 14. Create a sliver in the second slice, using the RSpec defined in step 12 ==
     111== Step 15. Log in to each of the systems, and send traffic to the other system ==
     112== Step 16. Verify that experimenters 1 and 2 cannot use the control plane to access each other's resources (e.g. via unauthenticated SSH, shared writable filesystem mount) =
     113== Step 17. Review system statistics and VM isolation and network isolation on data plane ==
     114== Step 18. Verify that each VM has a distinct MAC address for that interface ==
     115== Step 19. Verify that VMs' MAC addresses are learned on the data plane switch ==
     116== Step 20. Stop traffic and delete slivers ==