cloudstack/server
prachi e0a179752d Bug 11617: Ensure the Deployment planner is choosing clusters based on aggregate capacity
Changes:
- We were ordering clusters based on capacity of the first-fit host found in each cluster. Due to this, there were cases where we deployed VMs to one cluster instead of balancing off within clusters.
- Now we order the list of clusters by aggregate capacity and choose the ones that have enough capacity for the required VM in this order.
- This should balance the load between clusters instead of bombarding one.

Conflicts:

	server/src/com/cloud/capacity/dao/CapacityDao.java
	server/src/com/cloud/capacity/dao/CapacityDaoImpl.java
2011-10-03 15:37:38 -07:00
..
conf Removed bad word from log4j config files. 2011-02-08 13:55:40 -08:00
scripts Source code committed 2010-08-11 09:13:29 -07:00
src/com/cloud Bug 11617: Ensure the Deployment planner is choosing clusters based on aggregate capacity 2011-10-03 15:37:38 -07:00
test Implemented Project Invitations 2011-09-26 17:47:20 -07:00
.classpath bug 11230, 11229: merge fix from 2.2.10 branch, fix Eclipse project settings for premium-move 2011-08-24 15:18:08 -07:00
.project Fix corrupted eclipse project settings, schema fixes and updated template download url 2010-09-29 18:41:54 -07:00