cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Prachi Damle <>
Subject RE: Renaming updateVMAffinityGroup -> updateAffinityGroup
Date Tue, 30 Apr 2013 17:31:46 GMT
Hi Prasanna,

The API is to update a VirtualMachine's affinity group associations - it's not really an update
operation on an affinity group - hence the odd naming. The resource the API is acting on is
a VM.
Please suggest any other name that seems meaningful and fits the conventions...


-----Original Message-----
From: Prasanna Santhanam [] 
Sent: Tuesday, April 30, 2013 7:25 AM
To: CloudStack Dev
Cc: Prachi Damle
Subject: Renaming updateVMAffinityGroup -> updateAffinityGroup

Hi Prachi, 

Sorry for bringing this up so late -

Since the feature is not yet released and the API not out in the wild I thought perhaps the
name updateVmAffinityGroup makes more sense as updateAffinityGroup. This will make it conform
with the rest of the APIs associated with AffinityGroups(create/delete/list). Just makes it
easier to identify the resource the API is acting upon and more intuitive.

Does the update API do something different that warrants the odd naming?



Powered by

View raw message