incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Koushik Das" <>
Subject Review Request: CLOUDSTACK-672: Set VMware cluster max. limit based on HV version
Date Mon, 21 Jan 2013 11:44:58 GMT

This is an automatically generated e-mail. To reply, visit:

Review request for cloudstack.


For Vmware max. hosts in a cluster is specific to HV version. This configuration is read from
the hypervisor_capabilities table.
Read the dev list discussion here:

- Adding a cluster to CS - From 1st host in the list of hosts discovered, query the HV version.
Based on the version read the max_hosts_per_cluster limit from hypervisor_capabilities table
and do the validation
- Adding a host to an existing cluster - Get the HV version from one of the hosts already
present in cluster from CS db., then similar to previous scenario

The implementation is specific to Vmware only, haven't made the validation logic generic as
there are no limits for other HVs currently.
For upgraded scenarios, HV versions may not be present for the existing host table entries.
In that case the 'default' version will get used to read the limit.

This addresses bug CLOUDSTACK-672.


  api/src/com/cloud/hypervisor/ efb8a6a 
  core/src/com/cloud/hypervisor/ 56e8e0a 
  plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/ 684df54

  plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/ be3fe9f

  server/src/com/cloud/configuration/ 4ae144e 
  server/src/com/cloud/hypervisor/dao/ 8f4a475 
  server/src/com/cloud/hypervisor/dao/ 1a6fb72 
  setup/db/create-schema.sql 174f53c 
  setup/db/db/schema-40to410.sql a9d168d 



Manually verifed the scenarios mentioned above.


Koushik Das

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message