[jira] [Resolved] (CLOUDSTACK-605) Host physical CPU is incorrectly calculated for Vmware hosts

["Joe Brockmeier (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Brockmeier resolved CLOUDSTACK-605.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 4.1.0

I've applied this to master and the 4.0 branch.

4.0 commit: 47711186eadaecd8cdb799f1c2e0ed38288725e2
Master commit: 3dfd81fd6bcca92edab1f9ea814d0850d3202451
                
> Host physical CPU is incorrectly calculated for Vmware hosts
> ------------------------------------------------------------
>
>                 Key: CLOUDSTACK-605
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-605
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>    Affects Versions: pre-4.0.0, 4.0.0
>            Reporter: Koushik Das
>            Assignee: Koushik Das
>             Fix For: 4.0.1, 4.1.0
>
>
> There is a mismatch in host CPU count displayed in CS UI (displayed under the 'Statistics' tab when a host is selected) compared to that in vCenter. The mismatch happens for ESX hosts having > 1 cpu package. This will affect VM allocation logic.
> Currently host CPU is computed based on below logic (HostHardwareSummary is defined in Vmware library)
> HostHardwareSummary hardwareSummary = getHostHardwareSummary();
> summary.setCpuCount(hardwareSummary.getNumCpuCores()*hardwareSummary.getNumCpuPkgs());
> The correct logic is to use hardwareSummary.getNumCpuCores() only.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira