4 Commits

Author	SHA1	Message	Date
Prasanna Santhanam	4b33493a4b	bvt: marvin test for the affinity groups feature ... The test deploys two VMs in the simulator context and verifies that the default host -antiaffinity processor placed the VMs on two distinct hosts. Signed-off-by: Prasanna Santhanam <tsp@apache.org>	2013-04-08 23:18:00 +05:30
Prasanna Santhanam	eeb5d913c1	simulator context : finalize the simulator spring context ... This context is similar to the componentContext.xml.in but loads simulator components for the marvin tests. (cherry picked from commit 5610749e29)	2013-04-08 22:24:50 +05:30
Prasanna Santhanam	b798c45114	maven+marvin+simulator: Changes to the lifecycle steps ... integration test is now run as follows: Build $ mvn -Pdeveloper -Dsimulator clean install DB: $ mvn -Pdeveloper -pl developer -Ddeploydb $ mvn -Pdeveloper -pl developer -Ddeploydb-simulator Setup: $ mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/advanced.cfg -pl :cloud-marvin integration-test Test: $ mvn -Pdeveloper,marvin.test -Dmarvin.config=setup/dev/advanced.cfg -pl :cloud-marvin integration-test Signed-off-by: Prasanna Santhanam <tsp@apache.org>	2013-04-02 19:56:33 +05:30
Prasanna Santhanam	2e2046fe38	marvin changes to do an pre-integration and integration test ... Introducing the simulator spring context - simulatorComponentContext.xml.in. This separates the simulator beans so that production deployments don't have the simulator in them. Context is enabled with -Dsimulator as part of the developer profile. Also adding config files - Simulator Config for advanced zone and basic zone deployments under setup/dev. Signed-off-by: Prasanna Santhanam <tsp@apache.org>	2013-04-02 18:31:29 +05:30