Page History

...

We can list the number of hosts that are managed by CS using listHosts API. We introduce a new parameter value in response called "cpusockets" that holds the number cpu sockets of particular host where ever we can retrieve (otherwise we mark it as NULL).

...

- In Xenserver version 6.2 there is xapi call "host-cpu-info" in which we can get the "socket-count" per each host.

- In earlier versions of Xenserver 6.2 there is no such call so we do not counting cpu sockets for those hypervisors.

...

- Using Virsh command "nodeinfo" number of cpu sockets can be retrieved.

HyperV:

-We provide the number of physical cpu sockets per host and upon listing hosts we can count the number of cpu sockets for all hosts.

Hyper-V, Oracle VM, LXC:

- For these hypervisors we will list the number of host being managed. Retrieving socket information for these hypervisors may require domain experts for the corresponding hypervisor. Now we will give the number of hosts.

...

cpu_sockets int(10) unsigned DEFAULT NULL

API Changes

Changes to existing APIs

We will introduce
1) new parameter in listhost API call named "hypervisortypehypervisor"
2) new parameter in listhost response named "cpusockets"

...

In reponse we have new parameter value "cpusockets":1

UI changes

We show the following information in 'AboutInfrastructure' tab.

From UI it looks like

...

Some minimal calculations are required from the listHost response.
1) Call listHosts API with filter "hypervisortypehypervisor" (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.

...

For Xenserver 6.2 prior versions we are not counting number of sockets. For the remaining hypervisors OVM, Hyper-V, LXC require corresponding hypervisor experts to fill in the socket information