Bug 1259620 - Missing Cpu.setType api
Summary: Missing Cpu.setType api
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ovirt-4.0.0-alpha
: 4.0.0
Assignee: Juan Hernández
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-03 08:22 UTC by Ala Hino
Modified: 2016-08-01 12:28 UTC (History)
6 users (show)

Fixed In Version: ovirt 4.0.0 alpha1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-01 12:28:30 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.0.0+
ylavi: planning_ack+
juan.hernandez: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 45996 0 master MERGED restapi: Replace CPU "id" attribute with "type" element Never

Description Ala Hino 2015-09-03 08:22:46 UTC 
Description of problem:
There is no api to set cpu type; cpu.setId api is used the cpu type.
I find this inconvenience as, at least in the ui, admin specifically provides cpu type.
In addition, when using api to create objects, usually one expects the system to set the id rather than providing it.

Version-Release number of selected component (if applicable):
3.5.2.1

Additional info:
This can only be targeted in 4.0 due backward compatibility. 
Or perhaps we can add setType api and deprecate setId logic.
Comment 1 Petr Matyáš 2016-07-29 07:57:36 UTC 
Verified on 4.0.2-3
Note You need to log in before you can comment on or make changes to this bug.