Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of bharat.kumar@citrix.com
 designates 203.166.19.134 as permitted sender)
From: Bharat Kumar <bharat.kumar@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Tue, 12 Feb 2013 14:57:55 +0530
Subject: Regarding cpu and ram overcommit feature
Thread-Topic: Regarding cpu and ram overcommit feature
Thread-Index: Ac4JAz2M8TaMC28yRqmkCDQaR2KXWw==
Message-ID: <2E5D5B0D-21B3-45EF-AED2-3B8EAC9DBEF2@citrix.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi all,

As a part of this feature we need to implement a method to update the overc=
ommit 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 woul=
d like this operation to be asynchronous.

There are two ways to do this
1. ) To use the existing updateCluster Api=20
2.) Implement a new api=20

The problems with 1 are that it is synchronous command and making it asynch=
ronous  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.=20

Thanks.
Bharat.=