Bug 1041134 - [RFE][nova]: Support the vcpu-topology image metadata options inside XenAPI
Summary: [RFE][nova]: Support the vcpu-topology image metadata options inside XenAPI
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: unspecified
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/nova...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 13:45 UTC by RHOS Integration
Modified: 2019-09-09 16:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-12 21:31:43 UTC
Target Upstream Version:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.