/ 14.3. Resource Options
	14.2. OCF Return Codes		14.4. Resource Operations

Resource Options

For each resource you add, you can define options. Options are used by the cluster to decide how your resource should behave—they tell the CRM how to treat a specific resource. Resource options can be set with the crm_resource --meta command or with the GUI as described in .

Table 14.3. Options for a Primitive Resource

Option	Description
`priority`	If not all resources can be active, the cluster will stop lower priority resources in order to keep higher priority ones active.
`target-role`	What state should the cluster attempt to keep this resource in? Allowed values: `Stopped`, `Started`.
`is-managed`	Is the cluster allowed to start and stop the resource? Allowed values: `true`, `false`.
`resource-stickiness`	How much does the resource prefer to stay where it is? Defaults to the value of `default- resource-stickiness`.
`migration-threshold`	How many failures should occur for this resource on a node before making the node ineligible to host this resource? Default: `none`.
`multiple-active`	What should the cluster do if it ever ﬁnds the resource active on more than one node? Allowed values: `block` (mark the resource as unmanaged), `stop_only`, `stop_start`.
`failure-timeout`	How many seconds to wait before acting as if the failure had not occurred (and potentially allowing the resource back to the node on which it failed)? Default: `never`.