Actions
Bug #22117
closedAdd support for specifying number for sockets for oVirt
Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - oVirt
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1458754
It should be possible to specify the number of sockets to be set
for the VM. Setting 2 cores and 9 sockets should lead to
having 9 sockets, each with 2 cores, so the total number or cores would be 18.
The topology element should be <topology cores="2" sockets="9"/>
Updated by Ivan Necas about 7 years ago
- Subject changed from Add support for specifying number for sockets for oVirt to Add support for specifying number for sockets for oVirt
- Assignee deleted (
Marek Hulán) - Target version set to 113
Updated by The Foreman Bot almost 7 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/5425 added
Updated by Shira Maximov almost 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 073046ccd8c469633e4ca1c345038b26bd156895.
Updated by Ori Rabin over 6 years ago
- Related to Bug #23916: Create Host -> RHEV Image: Incorrect CPU cores count filled when using APIv4 added
Updated by Ondřej Pražák over 6 years ago
- Translation missing: en.field_release set to 330
Updated by The Foreman Bot over 6 years ago
- Assignee set to Ondřej Pražák
- Pull request https://github.com/theforeman/foreman/pull/5738 added
Updated by Ivan Necas over 6 years ago
- Related to Bug #24219: The empty field for sockets (which is the default) causes ovirt provisioning to fail added
Updated by Tomer Brisker over 6 years ago
- Assignee changed from Ondřej Pražák to Shira Maximov
- Triaged set to No
Actions