[
https://issues.apache.org/jira/browse/CLOUDSTACK-5052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajani Karuturi updated CLOUDSTACK-5052:
----------------------------------------
Fix Version/s: (was: 4.3.0)
4.3.2
> [UI] host socket count per hypervisor
> -------------------------------------
>
> Key: CLOUDSTACK-5052
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5052
> Project: CloudStack
> Issue Type: Sub-task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
> Affects Versions: 4.3.0
> Reporter: Harikrishna Patnala
> Fix For: 4.3.2
>
>
> UI changes are mentioned in the FS:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Report+CPU+sockets
> Changes to existing APIs
> We will introduce
> 1) new parameter in listhost API call named "hypervisortype"
> 2) new parameter in listhost response named "cpusockets"
> http://localhost:8080/client/api?command=listHosts&hypervisor=xenserver&sessionkey=uMjdI0ko3GbIkvPk3GLSnn7zNTY%3D&page=1&pageSize=20&type=routing&listAll=true&_=1382505530956
> In reponse we have new parameter value "cpusockets":1
> UI changes
> -------------------
> We show the following information in 'Infrastructure' tab.
> From UI it looks like
> ===========================================================
> Hypervisor | Hosts | Sockets
> ===========================================================
> VMware | 20 | 45
> ----------------------------------------------
> XenServer 6.2| 50 | 70
> ----------------------------------------------
> XenServer | 50 | unknown
> ----------------------------------------------
> KVM | 15 | 35
> ----------------------------------------------
> Hyper-V | 30 | unknown
> ===========================================================
> Some minimal calculations are required from the listHost response.
> 1) Call listHosts API with filter "hypervisor" (say xenserver)
> 2) take the count of number of hosts
> 3) In the response we need to take sum of all the values of parameter
> "cpusockets". If cpusockets are not mentioned for particular hypervisor type
> we leave the value as unknown.
> This we need to for all hypervisor types.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)