Bug 1661782

Summary:	[DDF] Ambiguity
Product:	Red Hat Enterprise Linux 8	Reporter:	Direct Docs Feedback <ddf-bot>
Component:	Documentation	Assignee:	Steven J. Levine <slevine>
Documentation sub component:	DDF	QA Contact:
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	unspecified
Priority:	medium	CC:	rhel-docs
Version:	8.0
Target Milestone:	rc
Target Release:	8.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-20 16:54:54 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Direct Docs Feedback 2018-12-23 09:44:00 UTC

Ambiguity

This makes it sound like setting resource-discovery=exclusive for a node would allow a resource to be active in that location without the cluster's knowledge, just like with "never". IIUC, "exclusive" would have the opposite effect. A resource could be active on a node that is NOT a member of the "exclusive" subset, without the cluster's knowledge.

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8-beta/html/configuring_and_managing_high_availability_clusters/assembly_determining-which-node-a-resource-runs-on-configuring-and-managing-high-availability-clusters#annotations:a488b9b7-20b3-4ee7-904a-4cd9807e4611