Bug 1371239

Summary: Docs: [REST API] - Client is stating that the use of Instance Types is supposed to be part of 4.0 and is looking for documentation as to how to use.
Product: Red Hat Enterprise Virtualization Manager Reporter: Jason <jbryant>
Component: DocumentationAssignee: rhev-docs <rhev-docs>
Status: CLOSED CURRENTRELEASE QA Contact: rhev-docs <rhev-docs>
Severity: medium Docs Contact:
Priority: high    
Version: 4.0.0CC: jbryant, lbopf, lsurette, rbalakri, rmcswain, srevivo, ykaul, ylavi
Target Milestone: ovirt-4.0.7   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-24 14:57:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Docs RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1148393    

Description Jason 2016-08-29 16:58:03 UTC
Further information from client:

Instance Types are part of the new model of templating according to oVirt

http://www.ovirt.org/develop/release-management/features/virt/instance-types/

"Enhancing oVirt template model to allow for more flexible options in
creating virtual machines targeted at improving self service for the
private cloud use cases."

Comment 1 Robert McSwain 2016-11-14 15:43:21 UTC
Any updates here?

Comment 2 Yaniv Lavi 2016-11-15 10:03:32 UTC
(In reply to Robert McSwain from comment #1)
> Any updates here?

We are planning to add this in a coming docs sprint of the API docs.

Comment 4 Lucy Bopf 2017-01-31 08:14:46 UTC
Jason, Robert,

Some information about Instance Types has been added to the new 4.0 REST API Guide, though it is yet to be reviewed by the documentation team:

https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/rest-api-guide/#services-instance_type

Please let me know if you feel that any detail is missing.

Moving this bug to ON_QA while the content is pending docs review.