Changes between Version 15 and Version 16 of GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-3
- Timestamp:
- 08/14/12 08:50:43 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-3
v15 v16 13 13 || Step 2 ||[[Color(yellow,Complete)]]|| ||To use 100VM used resources from ExoSM and BBN SM || 14 14 || Step 3 ||[[Color(#63B8FF,In Progress)]]|| ||Writing RSpecs|| 15 || Step 4 || 16 || Step 5 || || ||||15 || Step 4 ||[[Color(yellow,Complete)]]|| || || 16 || Step 5 ||[[Color(orange,Blocked)]] || exoticket:101 ||Attempt to reserver two 25 VMs slivers fails. || 17 17 || Step 6 || || || || 18 18 || Step 7 || || || || … … 90 90 }}} 91 91 == Step 5. Create a sliver in the slice, using the RSpec defined in step 3. == 92 This step cannot be executed for 100 VM in one sliver, the step was modified to create two slivers, where each has 50 VMs. One 50-node sliver is created via the ExoSM: 92 93 This 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. 94 95 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 96 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. 97 98 One sliver is created via the ExoSM: 93 99 {{{ 94 100 $ omni.py -a exosm createsliver EG-EXP-3 EG-EXP-3-exosm.rspec 95 101 }}} 96 The second 50-nodesliver is created via the BBN SM:102 Another sliver is created via the BBN SM: 97 103 {{{ 98 104 $ omni.py -a exobbn createsliver EG-EXP-3 EG-EXP-3-exobbn.rspec