Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1259620

Summary:	Missing Cpu.setType api
Product:	[oVirt] ovirt-engine	Reporter:	Ala Hino <ahino>
Component:	RestAPI	Assignee:	Juan Hernández <juan.hernandez>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Matyáš <pmatyas>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	---	CC:	bugs, gklein, lsurette, rbalakri, srevivo, ykaul
Target Milestone:	ovirt-4.0.0-alpha	Flags:	rule-engine: ovirt-4.0.0+ ylavi: planning_ack+ juan.hernandez: devel_ack+ pstehlik: testing_ack+
Target Release:	4.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt 4.0.0 alpha1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-01 12:28:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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