Detail: VM Life cycle tests needed minor changes to run them against a
devcloud - basic zone, local storage envrioment.
Signed-off-by: Prasanna Santhanam <tsp@apache.org> 1354760111 -0800
Detail:
This is a fix
1. to populate 'destzoneid' as part of the test data by issuing
listZones API. Earlier, this is provided manually in the test data.
2. to wait till the ISO/template is downloaded & installed successfully
before being deleted as part of the cleanup.
BUG-ID: CLOUDSTACK-567
Reviewed-by: Prasanna Santhanam
Reported-by: Prasanna Santhanam
Signed-off-by: Prasanna Santhanam <tsp@apache.org> 1354234426 -0800
Detail: The listOsTypes API will filter when given the ostype name as
centOS 5.3. There is now no need to hardcode the uuids into the test
Signed-off-by: Prasanna Santhanam <tsp@apache.org> 1354228309 -0800
Detail: multiprocess plugin will drive each module in a seperate
process. the test runs will now be speeded up.
Signed-off-by: Prasanna Santhanam <tsp@apache.org> 1352465966 +0530
Detail: The secondary storage tests are now simplified. Since before
running tests we already ensure the health checks - template, builtin,
system vms are ready. there is no need to add additonal wait/sleep here.
Signed-off-by: Prasanna Santhanam <tsp@apache.org> 1351595163 +0530
Detail: Integration tests use these libraries (base,utils,common) for
simplifying the usage of the API. These define the verbs of each
entity's usage (create, delete, add etc). For the CLI to present the
simplified API we'll leverage the integration libraries.
+ Fixes to setup-test-data.sh - kvm and xen each use a different version
of the built-in Cent OS template, 5.5 and 5.3 namely.
At a later point the setup-test-data script needs to be obsoleted.
ostypeids in tests should directly be determined from listOsTypes API
calls
Signed-off-by: Prasanna Santhanam <tsp@apache.org> 1351520707 +0530
Detail: test_secondary_storage.py.test_systemvm_start() would try to
verify system VMs running under the zone but would filter by podid which
is not reqd. As systemVMs space a zone, filtering them zone-by-zone is
sufficient.
Signed-off-by: Prasanna Santhanam <tsp@apache.org> 1351506366 +0530
Detail: Marvin auto-manages its connections now and there is no need to
call dbclient.close on tearDown of the test setup.
Signed-off-by: Prasanna Santhanam <tsp@apache.org> 1351152797 +0530
Snapshots take many hours to run because the lowest snapshot period for
testing is an HOURLY snapshot. The component tests are the right place
to run any long running tests. This will also speed up the smoke tests
to under an hour.
* expunge.interval determines the ExpungeTask interval to cleanup the
VM and post expunge.delay seconds we delete the VM entry. So let's just
wait long enough
