Changes between Version 17 and Version 18 of GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-3
- Timestamp:
- 08/14/12 08:52:45 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-3
v17 v18 81 81 == Step 3. Write a RSpec that requests 100 VMs evenly distributed across the worker nodes using the default image. == 82 82 83 This step cannot be executed for 100 VM in one sliver , the step was modified to create two RSpecs, where each has 50 VMs. Rspecs are being written.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. 84 84 85 85 == Step 4. Create a slice. == … … 93 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 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. 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. 97 96 98 97 One sliver is created via the ExoSM:
