Bug 810931

Summary:	REST API: For consistency rename "node_profile" to "gear_profile"
Product:	OKD	Reporter:	Clayton Coleman <ccoleman>
Component:	Pod	Assignee:	Krishna Raman <kraman>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.x	CC:	bmeng, mfisher, rmillner
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-13 18:34:22 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:

Description Clayton Coleman 2012-04-09 16:51:53 UTC

Just based on what I've seen, but if we use "gears" extensively in both the UI and the REST API /gear I'd rather use "gear_profile" over "node_profile", since "node" introduces another concept that we have to plain.  My understanding is that "gear" will be identical to "node" in all of our API uses (except possibly direct descriptor manipulation)?  If so would that make sense?

Comment 1 Meng Bo 2012-04-11 04:11:24 UTC

Verified with devenv_1713,
"node_profile" has been replaced by "gear_profile" 

      <default-value>small</default-value>
      <name>gear_profile</name>