cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Prasanna Santhanam <...@apache.org>
Subject Re: [DISCUSS] Multi-threading in test suite
Date Thu, 28 Feb 2013 05:17:22 GMT
On Tue, Feb 26, 2013 at 07:10:55PM +0530, Prasanna Santhanam wrote:
> Sorry about the delay ..
> 
> On Tue, Feb 26, 2013 at 05:42:05AM +0530, Ashutosh Kelkar wrote:
> > >
> > > Also Can you spell out the test scenario?
> > 
> > 
> > One of the test scenario is -
> > 
> > 1.Configure the concurrent.snapshots.threshold.perhost=3
> > 2.Deploy a Linux VM using default CentOS template, use small service
> > offering, disk offering
> > 3.Log into the VM and create a file with content in it.
> > 4.repeat step 2 to 3 for 10 times to create 10 vms
> > 5.Perform snapshot on the root disk of this newly created VMs(10 vms)
> > 6.perform VM live migration
> > 
> > Validation steps -
> > a. Vms should successfully  migrated to another host.
> > b. check all the snapshots jobs are running concurrently on back grounds(
> > by checking the  job description on the logs &number of mount points from
> > host to storage)
> > 
> I looked at the wiki and the tests have the common steps for 1-4.
> Disregarding the migration, etc
> 
> This should be simplified thus:
> 
> 1. deploy VMs equal to the threshold value. wait for all of them to be
> running. You'll have to deploy the VMs with a targeted host for this.
> Since this is a per host setting.
> 2. create snapshots for the root disks of each of the above VMs. use
> the asyncJobMgr to submit a group of cmds and wait. 
> 3. All jobs succeed.
> 
> For the negative scenario - where the threshold is respected, you
> should have one failed job in the entire list of jobs submitted.
> 
> Also how do we ensure that all the VMs one has deployed end up 
> > You can find other scenarios on Apache wiki page for test plans [1].
> > 
> > PS: You guys are working on github? Can you let me know the github
> > > repo so I can pull in tests from there for review and runs?
> > 
> > 

Looking back at the test plan I think the 'concurrent' in the setting
may be misnomer. The snapshot jobs on the hosts always proceeded
concurrently. This setting only controls the number of those jobs to
prevent IO hogging.

So the tests that do vm migration while snapshots are in progress,
snapshotting volumes when vm is stopped, stopping at the time of
snapshot jobs, etc should ideally just be tests with/without the
global setting. They can be included in the components/test_snapshots
suite. IOW, just the simplest form of the usecase.

HTH,


-- 
Prasanna.,

Mime
View raw message