Bug 1513550

Summary:	Support tagging
Product:	Red Hat Enterprise Linux 7	Reporter:	Ken Gaillot <kgaillot>
Component:	pcs	Assignee:	Tomas Jelinek <tojeline>
Status:	CLOSED DUPLICATE	QA Contact:	cluster-qe <cluster-qe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	cfeist, cluster-maint, idevat, jpokorny, omular, tojeline
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-05 11:01:03 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 Ken Gaillot 2017-11-15 15:34:06 UTC

Pacemaker supports tagging of XML elements:

http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Explained/index.html#_tagging_configuration_elements

This will be important for pcs primarily for nodes and resources, because tagging is expected to be part of the solution for Bug 1300597 and Bug 1300604. The idea is that the user will be able to tag certain nodes and/or resources, then use (not yet implemented) options to crm_mon to display the status of just those.

An example of how it might eventually work:

pcs resource tag myrsc1 special
pcs resource create myrsc2 Dummy --tag special
pcs status --resources=special # shows status of myrsc1 and myrsc2 only

This bz is just for the tagging functionality, which is already supported by pacemaker. A separate bz will be opened for the pcs status functionality once the crm_mon interface is finalized.

I can imagine tagging coming in handy in other situations in the future. Pacemaker implements tags mainly for UI use, so feel free to use tags elsewhere in pcs for any purpose.

Comment 2 Ken Gaillot 2017-11-15 15:42:43 UTC

FYI, because tags are XML IDs, they are guaranteed to be unique with respect to resource names and node IDs (sadly, not node names). That gives you the option of accepting tag names wherever a resource name can be used, rather than requiring a special syntax in that situation.

Comment 3 Jan Pokorný [poki] 2017-11-15 15:48:40 UTC

See also bottom of [bug 1441332 comment 5] + a link from the subsequent
comment.

Comment 4 Tomas Jelinek 2019-03-05 11:01:03 UTC

This feature is unlikely to be implemented in RHEL 7 due to its high complexity and demand on resources. Since there is already a RHEL 8 bz for the same feature, I am closing this as a duplicate.

*** This bug has been marked as a duplicate of bug 1684676 ***