Bug 891729

Summary:	[Doc] PRD32 - [RFE] Support cpu -host (passthrough) for virtual machines
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Stephen Gordon <sgordon>
Component:	Documentation	Assignee:	Cheryn Tan <chetan>
Status:	CLOSED NOTABUG	QA Contact:	ecs-bugs
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.2.0	CC:	rlandman, sgordon, thildred
Target Milestone:	---	Keywords:	Documentation, FutureFeature, Tracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	http://wiki.ovirt.org/wiki/Features/Cpu-host_Support
Whiteboard:	virt sla
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	cpu_host
Clones:	891732 891733 (view as bug list)		Environment:
Last Closed:	2013-04-04 06:15:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	891732, 891733
Bug Blocks:	838469

Comment 1 Stephen Gordon 2013-01-03 19:41:44 UTC

I've asked on Bug # 838469 but I'm expecting impacts to at least:

Administration Guide
Developer Guide

As well as possibly the Command Line Shell Guide.

Comment 2 Tim Hildred 2013-01-09 08:12:33 UTC

Steve, 

Do bugs that affect the CLI Shell Guide automatically affect the Developer Guide? 

Administration Guide:
http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_Enterprise_Virtualization/3.1/html-single/Administration_Guide/index.html#sect-Explanation_of_Settings_and_Controls_in_the_New_Virtual_Machine_and_Edit_Virtual_Machine_Windows

Comment 3 Stephen Gordon 2013-01-15 16:16:18 UTC

(In reply to comment #2)
> Steve, 
> 
> Do bugs that affect the CLI Shell Guide automatically affect the Developer
> Guide? 

"It depends". The "core" is really the REST API content in the Developer Guide, when it changes corresponding changes *may* be required to the CLI and SDK content but not always - further analysis required. 

The reason is that in the CLI and SDK materials we don't go through and re-document every single construct available in the API. Instead we provide a brief overview of how to interact with the objects using the CLI or SDK specific logic and refer users to the REST API content as the object reference detailing all valid object types, properties, actions, etc.

Comment 4 Cheryn Tan 2013-04-04 06:07:09 UTC

Tracker bug -- closing to move off the 3.2 queue.