incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bharat Kumar <bharat.ku...@citrix.com>
Subject Re: Regarding cpu and ram overcommit feature
Date Tue, 12 Feb 2013 13:56:22 GMT
Well i think it is not about the advantage or disadvantage of doing this,  it is only about
 the use case we want to support. 
The use case which we are trying to support requires this.

Bharat.

On Feb 12, 2013, at 6:58 PM, Nitin Mehta <Nitin.Mehta@citrix.com> wrote:

> What is the down side if we do not update the overcommit ratios on
> existing vms ?
> I donĀ¹t see these ratios being changed quite often in the cloud.
> 
> On 12/02/13 2:57 PM, "Bharat Kumar" <bharat.kumar@citrix.com> wrote:
> 
>> Hi all,
>> 
>> As a part of this feature we need to implement a method to update the
>> overcommit ratios.
>> 
>> when we update the overcommit ratios all the Vms in the cluster need to
>> be reconfigured as per the new values.
>> 
>> In order to do this i need to send some commands to the hypervisor and
>> would like this operation to be asynchronous.
>> 
>> There are two ways to do this
>> 1. ) To use the existing updateCluster Api
>> 2.) Implement a new api
>> 
>> The problems with 1 are that it is synchronous command and making it
>> asynchronous  will break the backward compatibility and
>> in case of 2 we need to add a new api to change the overcommit ratios (
>> a cluster attribute ) which I think is not intuitive.
>> 
>> Please suggest a way to implement this.
>> 
>> Thanks.
>> Bharat.
> 


Mime
View raw message