Bug 1041134

Summary: [RFE][nova]: Support the vcpu-topology image metadata options inside XenAPI
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-novaAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: hateya, markmc, ndipanov, sgordon, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/nova/+spec/xenapi-vcpu-topology
Whiteboard: upstream_milestone_none upstream_status_not-started upstream_definition_pending-approval
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-12 21:31:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 13:45:56 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/xenapi-vcpu-topology.

Description:

There is a proposal to support specifying the max threads, cores and sockets on an image:
https://wiki.openstack.org/wiki/VirtDriverGuestCPUTopology

In XenAPI we certainly have the cores-per-socket setting:
http://support.citrix.com/article/CTX126524

We should consider support the use case where a windows guest might request 8 vCPUs but have a max-sockets=4 so we can offer that guest those 8 vCPUs grouped into 4 sockets each with 2 cores.

At a later date we may need to expose more of the NUMA architecture, but for now, lets cover the above case.

Specification URL (additional information):

None
Comment 2 Stephen Gordon 2013-12-12 21:31:43 UTC 
Xen is not formally supported in RHELOSP at this time.