Bug 843807

Summary:	What number gives a higher priority?
Product:	[Retired] CloudForms Cloud Engine	Reporter:	Forrest Taylor <ftaylor>
Component:	Documentation	Assignee:	Dan Macpherson <dmacpher>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Giulio Fidente <gfidente>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.1.0	CC:	cpelland, dajohnso, gfidente, lbrindle
Target Milestone:	beta6
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-10 21:48:55 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:

Description Forrest Taylor 2012-07-27 12:05:52 UTC

Description of problem:
When creating a Cloud Resource Provider, there is an opportunity to include a priority.  However there is no documentation regarding what the values mean.  If I assign a value of 1 to one provider and a value of 10 to another, which one is the higher priority?  Is it the higher number or the first number?

Also, there is no mention where this comes into play.  Is this value referenced when I choose auto-select in the Cluster when I launch?

Lastly, what are the available values?  Is 0 a higher (or lower) priority than 1?  What about -1000?

Comment 1 Dave Johnson 2012-08-08 18:39:48 UTC

related to bug 828463

Comment 2 Dan Macpherson 2012-08-29 02:11:32 UTC

Modified doc text for Cloud Resource Provider Account creation:

"Type the Priority for your Cloud Resource Provider. This defines to order of priority that CloudForms Cloud Engine utilizes Cloud Resource Providers. Priority is ranked from lowest to highest. For example, a priority of 3 ranks higher than a priority of 5."

Comment 6 Giulio Fidente 2012-10-23 16:35:02 UTC

as per comment from Imre Farkas on bug 864457:

"""
The provider selection during deployment launch has changed a lot since 1.0. In 1.1 we are randomly picking from the set of available provider accounts. The priority attribute is only used for the weight of the random selection.

So you cannot conclude that the provider account with the higher priority will be selected, or the one with the lower priority. Since it's based on random selection it can happen either way.
"""

Comment 8 Lana Brindley 2012-11-19 02:42:54 UTC

This documentation has now been dropped to translation ahead of publication. For any further issues, please open a new a bug.

LKB

Comment 9 Lana Brindley 2012-12-10 21:48:55 UTC

This document is now publicly available on access.redhat.com. For any further issues, please raise a new bug.

LKB