ControlTier Inc. > CTL
 
Font size:      

nodeset

Description

The nodeset type specifies filtering options used by the nodedispatch execution strategy of execute action for the controller task.

nodeset

AttributeDescriptionRequired
keepgoingif an error continues continue other executionsNo (default false)
threadcountNumber of threads to execute dispatchNo. (default "1")

elements

ElementDescriptionRequired
includeInclude filter patternNo
excludeExclude filter patternNo

Include/Exclude filter attributes

The values allowed for each of these attributes can be a literal value, a comma separated list or a Java style regular expression.

The attribute tags can also use boolean operators to specify additional set logic.

The dominant attribute declares whether the Include or Exclude element takes precendence in the case that a node matches both filters. E.g. When Exclude is dominant (the default), and osfamily is set to "unix", then all nodes that are Unix will be excluded, even if a specific filter in the Include element may match some Unix nodes.

AttributeDescriptionRequired
hostnameNode hostname value, which may be formatted as username@hostname. E.g. "dev01", "user1@host2.test.com" No
osarchNode os-arch value. E.g. "x86", "x386" No
osfamilyNode os-family value. E.g. "unix","windows"No
osnameNode os-name value. E.g. "Macintosh OS X", "Windows NT", "Linux"No
osversionNode os-version valueNo
tagsTag names. When specifying more than one tag, use the comma (",") to specify a boolean OR operation, and a plus-sign ("+") to specify a boolean AND operation. E.g. To require both tags "alpha" and "beta", specify "alpha+beta". This will match nodes that have both tags only. To match any nodes that have one or the other tags, use "alpha,beta". Thus "alpha,beta+gamma" will match nodes with either the the tag "alpha", or both tags "beta" and "gamma". No
nameNode name value. This is the name of the objectNo
typeNode type name. This is the name of the node type, typically the base type "Node".No
dominantBoolean specifying if this filter should take precedence over the other.No (default false for Include, and true for Exclude)

Examples

	<nodeset keepgoing="${opts.keepgoing}" threadCount="${opts.threadCount}">
	  <include hostname="${opts.node-hostname}"
		   name="${opts.node-name}"
		   tags="${opts.node-tags}"
		   osfamily="${opts.node-os-family}"
		   osarch="${opts.node-os-arch}"
		   osversion="${opts.node-os-version}"
		   osname="${opts.node-os-name}"
		   type="${opts.node-type}"
		   dominant="${opts.node-dominant}"
		   />
	  <exclude hostname="${opts.xnode-hostname}"
		   name="${opts.xnode-name}"
		   tags="${opts.xnode-tags}"
		   osfamily="${opts.xnode-os-family}"
		   osarch="${opts.xnode-os-arch}"
		   osversion="${opts.xnode-os-version}"
		   osname="${opts.xnode-os-name}"
		   type="${opts.xnode-type}"
		   dominant="${opts.xnode-dominant}"
		   />
	</nodeset>