cloudstack/api
prachi 5706041ef7 Manual merge of Bug 9539 - cpu.overprovisioning.factor does not work
Partial Changes:
- Changed host allocators/planner  to use cpu.overprovisioning.factor
- Removed following: while adding a new host, we were setting the total_cpu in op_host_capacity to be actual_cpu * cpu.overprovisioning.factor. Now we set it to actual_cpu.
- ListCapacities response now calculates the total CPU as actual * cpu.overprovisioning.factor (This change does not add anything new - listCapacities was pulling total CPU from op_host_capacity DB earlier which had the cpu.overprovisioning.factor applied already. Now we need to apply it over the DB entry.)
- HostResponse has a new field: 'cpuWithOverprovisioning' that returns the cpu after applying the cpu.overprovisioning.factor

- Db Upgrade 222 to 224 now updates the total_cpu in op_host_capacity to be the actual_cpu for each Routing host.

Conflicts:

	server/src/com/cloud/agent/manager/AgentManagerImpl.java
	server/src/com/cloud/api/ApiDBUtils.java
	server/src/com/cloud/api/ApiResponseHelper.java
	server/src/com/cloud/deploy/BareMetalPlanner.java
	server/src/com/cloud/server/ManagementServerImpl.java
2011-04-22 18:54:16 -07:00
..
src/com/cloud Manual merge of Bug 9539 - cpu.overprovisioning.factor does not work 2011-04-22 18:54:16 -07:00
.classpath Use exports for jar dependecy 2011-02-01 11:10:37 -08:00
.project Source code committed 2010-08-11 09:13:29 -07:00