Comment 3 for bug 1156456

Patch Set 1:

I suppose the bug really is around how sockets are being reported on NUMA based systems, not necessarily with reporting on the NUMA cell count.

Most of this is copied from a comment I made on the review but cross posting here for those who aren't looking at the review.

On a dual socket Intel Xeon E5-2650 system the topology being reported via nova is the following.

"topology": {"cores": "8", "threads": "2", "sockets": "1"}

This is accurate in that it is what is reported via the getCapabilities call, but it is not accurate from the perspective of what is physically present on the system. So I believe we still need to fix this in some way to properly report on NUMA systems. 3rd party software that is trying to rely on the API can't get an accurate representation of what is physically present today.

I assume (and Daniel please correct me if I am wrong) that libvirt reports that based upon the understanding that this is per NUMA cell? Or is this a case were we need a newer version of libvirt that properly reports on a NUMA system? We don't have any asymmetric NUMA systems to look at so I don't know how its presented in the asymmetric case. What would be the correct way of reporting the number of cores, threads, and sockets on a NUMA based system, without representing the entire NUMA topology?