Changes between Version 20 and Version 21 of GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-3


Ignore:
Timestamp:
12/06/12 13:23:10 (7 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-3

    v20 v21  
    22= EG-EXP-3: ExoGENI Single Site 100 VM Test =
    33
    4 This page captures status for the test case EG-EXP-3, which verifies the ability to support 100 VM in one rack. For overall status see the [wiki:GENIRacksHome/ExogeniRacks/AcceptanceTestStatus ExoGENI Acceptance Test Status] page. ''Last update: 08/14/12''
     4This page captures status for the test case EG-EXP-3, which verifies the ability to support 100 VM in one ExoGENI rack. For overall status see the [wiki:GENIRacksHome/ExogeniRacks/AcceptanceTestStatus ExoGENI Acceptance Test Status] page. ''Last update: 12/06/12''
    55
     6Due to the rack configuration a set of scenarios are being tested to capture scaling to 100 VMs, the following table captures scenario tested:
     7
     8||   ''' Test Scenario'''           ||'''Results'''                             || '''Notes'''                            ||
     9||Test 1: 10 slivers with 10 VMs each||[[Color(#63B8FF,In Progress)]]           || 89VMs ok, 11 VMs failed, exoticket:134 ||
     10||Test 2: 4 slivers w/20VMS +2 slivers w/10 VMs||[[Color(#63B8FF,In Progress)]] || 88VMs ok, 12 VMs failed, exoticket:134 ||
     11||Test 3: 20 slivers with 5 VMs each ||[[Color(#63B8FF,In Progress)]]           || 90VMs ok, 10 VMs failed, exoticket:134 ||
     12||Test 4: 100 Sliver with 1 VM       ||[[Color(#63B8FF,In Progress)]]           ||41 VMs ok, BBN SM failed, exoticket:135 ||
     13||Test 5: 1 slivers with 100 VMs     ||[[Color(red,Fail)]]                      || Not allowed with current rack configuration ||
     14||Test 6: 2 slivers with 50 VMs each ||[[Color(#63B8FF,In Progress)]]           || Allowed with current rack configuration, but untested ||
    615
    716
     
    1019
    1120|| '''Step''' || '''State'''             || ''' Tickets'''    || '''Comments''' ||
    12 || Step 1     ||[[Color(yellow,Complete)]]||                  || 50/50 allocation forces use of both ExoSM and BBN SM ||
    13 || Step 2     ||[[Color(yellow,Complete)]]||                  ||To use 100VM used resources from ExoSM and BBN SM  ||
     21|| Step 1     ||[[Color(yellow,Complete)]]||                  || Rack 50/50 resource allocation forces use of ExoSM and BBN SM ||
     22|| Step 2     ||[[Color(yellow,Complete)]]||                  ||                ||
    1423|| Step 3     ||[[Color(yellow,Complete)]]||                  ||                ||
    1524|| Step 4     ||[[Color(yellow,Complete)]]||                  ||                ||
    16 || Step 5     ||[[Color(orange,Blocked)]] ||  exoticket:101   ||Attempt to reserve two 25 VMs slivers fails.     ||
     25|| Step 5     ||[[Color(orange,Blocked)]] ||                  ||                ||
    1726|| Step 6     ||                         ||                   ||                ||
    1827|| Step 7     ||                         ||                  ||                ||
     
    3544= Test Plan Steps =
    3645
    37 The steps in this test case review baseline monitoring, but its features are still being implemented, therefore results are not yet final.
    38 
    39 The omni_configuration file used in this test case includes the following nick_named:
     46The Omni configuration file used in this test case includes the following nick_names for ExoGENI Aggregates:
    4047{{{
    41 exobbn=,https://bbn-hn.exogeni.net:11443/orca/xmlrpc
    42 exorci=,https://rci-hn.exogeni.net:11443/orca/xmlrpc
    43 exosm=,https://geni.renci.org:11443/orca/xmlrpc
     48eg-gpo=,https://bbn-hn.exogeni.net:11443/orca/xmlrpc
     49eg-renci=,https://rci-hn.exogeni.net:11443/orca/xmlrpc
     50eg-sm=,https://geni.renci.org:11443/orca/xmlrpc
    4451}}}
    4552
    46 Testing will use ''<sliver_type name="m1.small"/>'' for the resource requests, which will generate a 1 core VM with 128 MBytes of RAM and 3 GBytes of disk space.
    47  
    48 For a full list of available resource types and associated cores, RAM and Disk space allocation see the following [https://wiki.exogeni.net/doku.php?id=public:experimenters:resource_types:start resource type table] at the ExoGENI wiki site.
     53Testing uses ''<sliver_type name="m1.small"/>'' for the resource requests, which generates a 1 core VM with 128 MBytes of RAM and 3 GBytes of disk space. For a full list of available resource types and associated cores, RAM and Disk space allocation see the following [https://wiki.exogeni.net/doku.php?id=public:experimenters:resource_types:start resource type table] at the ExoGENI wiki site.
    4954
    5055== Step 1. Request !ListResources from BBN ExoGENI. ==
    51 The following command is executed to collect resource from the ExoGENI rack:
     56
     57The following command is executed to collect resource from the BBN ExoGENI rack:
    5258{{{
    53 $ omni.py -a exobbn listresources -o
     59$ omni.py -a eg-bbn listresources -o
    5460}}}
    5561
    56 The rack resource allocation is 50/50 for the local BBN rack SM and the ExoSM, therefore collecting listresources on both to get the complete list of resources available within the BBN Rack. 
     62The rack resource allocation is 50% of resources for the local rack SM and 50% for the ExoSM, therefore one must collect listresources on both to get the complete list of resources available within an ExoGENI Rack. 
    5763{{{
    58 $ omni.py -a exosm listresources -o
     64$ omni.py -a eg-sm listresources -o
    5965}}}
    6066== Step 2. Review !ListResources output, and identify available resources. ==
    6167
    62 The listresources output file for the ExoSM named rspec-geni-renci-org-11443-orca.xml shows:
     68The ExoGENI RSpec provides an indication of the potentially available VMs in the "type_slots" element. The listresources output file  generated from previous step for the ExoSM named rspec-geni-renci-org-11443-orca.xml shows:
    6369{{{
    6470<node component_id="urn:publicid:IDN+exogeni.net:bbnvmsite+node+orca-vm-cloud" component_manager_id="urn:publicid:IDN+exogeni.net:bbnvmsite+authority+am" component_name="orca-vm-cloud" exclusive="false">
    6571            <hardware_type name="orca-vm-cloud">
    66                   <ns3:node_type type_slots="51"/>
     72                  <ns3:node_type type_slots="54"/>
    6773            </hardware_type>
    6874            <available now="true"/>
     
    7379      <node component_id="urn:publicid:IDN+exogeni.net:bbnvmsite+node+orca-vm-cloud" component_manager_id="urn:publicid:IDN+exogeni.net:bbnvmsite+authority+am" component_name="orca-vm-cloud" exclusive="false">
    7480            <hardware_type name="orca-vm-cloud">
    75                   <ns3:node_type type_slots="52"/>
     81                  <ns3:node_type type_slots="48"/>
    7682            </hardware_type>
    7783            <available now="true"/>
     
    8187== Step 3. Write a RSpec that requests 100 VMs evenly distributed across the worker nodes using the default image.  ==
    8288 
    83 This step cannot be executed for 100 VM in one sliver due to the current rack resource allocation which is 50/50 for local BBN SM and global ExoSM. The test case step was modified to create two RSpecs, where each has 50 VMs.
     89This step cannot be executed for 100 VM in one sliver due to the current rack resource allocation, which allocates 50% of the resources to the local aggregate manager (BBN SM) and 50% of the resources to the global aggregate manager (ExoSM). The test case step was modified to create RSpecs which are used at each local and global aggregate manager.
    8490
    8591== Step 4. Create a slice. ==
     
    9399This step cannot be executed for 100 VM in one sliver, due to the resource allocation which is 50/50 between the local BBN SM and the global ExoSM. Based on the allocation, the test case description was modified to create two slivers, where each has 50 VMs in the BBN Rack, with one request to the BBN SM and one request to the ExoSM.
    94100
    95 '''NOTE:''' Because of the issues seen in testing with 18 VMs, decided that for the first test run try, the request is reduced to ensure that it could be addressed by the ExoGENI rack. Therefore reduced each sliver to 25 VMs, but each request resulted in a large number of failures as captured in exoticket:101.
     101'''NOTE:''' Rspecs with 50 VMs have not been tests, but other scenarios have been tested and are covered in this page.
    96102
    97 One sliver is created via the ExoSM:
     103To set up a sliver in the BBN rack that is created via the ExoSM, this type of command is used:
    98104{{{
    99 $ omni.py -a exosm createsliver EG-EXP-3 EG-EXP-3-exosm.rspec
     105$ omni.py -a eg-sm createsliver EG-EXP-3 EG-EXP-3.rspec
    100106}}}
    101 Another sliver is created via the BBN SM:
     107To set up a sliver in the BBN rack that is created via the BBN SM:
    102108{{{
    103 $ omni.py -a exobbn createsliver EG-EXP-3 EG-EXP-3-exobbn.rspec
     109$ omni.py -a eg-gpo createsliver EG-EXP-3 EG-EXP-3.rspec
    104110}}}
     111
     112'''Note:''' The same sliver name and Rspec can be used concurrently via BBN Sm and ExoSM, and that is the approach used in all tests described in this page.
    105113
    106114== Step 6. Log into several of the VMs, and send traffic to several other systems. ==