#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2018-05-14 18:03-0500\n"
"PO-Revision-Date: 2018-05-14 18:03-0500\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
#, no-c-format
msgid "Rules"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<anchor id=\"ch-rules\" xreflabel=\"Chapter 8, Rules\"></anchor> <indexterm> <primary>Resource</primary><secondary>Constraint</secondary><tertiary>Rule</tertiary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Rule</secondary> </indexterm> <indexterm> <primary>Rule</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Rules can be used to make your configuration more dynamic. One common example is to set one value for <literal>resource-stickiness</literal> during working hours, to prevent resources from being moved back to their most preferred location, and another on weekends when no-one is around to notice an outage."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Another use of rules might be to assign machines to different processing groups (using a node attribute) based on time and to then use that attribute when creating location constraints."
msgstr ""
#. Tag: para
#, no-c-format
msgid "Each rule can contain a number of expressions, date-expressions and even other rules. The results of the expressions are combined based on the rule’s <literal>boolean-op</literal> field to determine if the rule ultimately evaluates to <literal>true</literal> or <literal>false</literal>. What happens next depends on the context in which the rule is being used."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Rule Properties"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a Rule"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Field"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Default"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Description"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>id</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the rule (required) <indexterm> <primary>id</primary><secondary>Constraint Rule</secondary> </indexterm> <indexterm> <primary>Constraint Rule</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Rule</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Rule</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>role</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>Started</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Limits the rule to apply only when the resource is in the specified role. Allowed values are <literal>Started</literal>, <literal>Slave</literal>, and <literal>Master</literal>. A rule with <literal>role=\"Master\"</literal> cannot determine the initial location of a clone instance and will only affect which of the active instances will be promoted. <indexterm> <primary>role</primary><secondary>Constraint Rule</secondary> </indexterm> <indexterm> <primary>Constraint Rule</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Rule</secondary><tertiary>role</tertiary> </indexterm> <indexterm> <primary>Rule</primary><secondary>role</secondary> </indexterm> <indexterm> <primary>role</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>score</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The score to apply if the rule evaluates to <literal>true</literal>. Limited to use in rules that are part of location constraints. <indexterm> <primary>score</primary><secondary>Constraint Rule</secondary> </indexterm> <indexterm> <primary>Constraint Rule</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Rule</secondary><tertiary>score</tertiary> </indexterm> <indexterm> <primary>Rule</primary><secondary>score</secondary> </indexterm> <indexterm> <primary>score</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>score-attribute</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The node attribute to look up and use as a score if the rule evaluates to <literal>true</literal>. Limited to use in rules that are part of location constraints. <indexterm> <primary>score-attribute</primary><secondary>Constraint Rule</secondary> </indexterm> <indexterm> <primary>Constraint Rule</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Rule</secondary><tertiary>score-attribute</tertiary> </indexterm> <indexterm> <primary>Rule</primary><secondary>score-attribute</secondary> </indexterm> <indexterm> <primary>score-attribute</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>boolean-op</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>and</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "How to combine the result of multiple expression objects. Allowed values are <literal>and</literal> and <literal>or</literal>. <indexterm> <primary>boolean-op</primary><secondary>Constraint Rule</secondary> </indexterm> <indexterm> <primary>Constraint Rule</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Rule</secondary><tertiary>boolean-op</tertiary> </indexterm> <indexterm> <primary>Rule</primary><secondary>boolean-op</secondary> </indexterm> <indexterm> <primary>boolean-op</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Node Attribute Expressions"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Resource</primary><secondary>Constraint</secondary><tertiary>Attribute Expression</tertiary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Attribute Expression</secondary> </indexterm> <indexterm> <primary>Attribute Expression</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Expression objects are used to control a resource based on the attributes defined by a node or nodes."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of an Expression"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the expression (required) <indexterm> <primary>id</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Attribute Expression</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Attribute Expression</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>attribute</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The node attribute to test (required) <indexterm> <primary>attribute</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Attribute Expression</secondary><tertiary>attribute</tertiary> </indexterm> <indexterm> <primary>Attribute Expression</primary><secondary>attribute</secondary> </indexterm> <indexterm> <primary>attribute</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>type</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>string</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Determines how the value(s) should be tested. Allowed values are <literal>string</literal>, <literal>integer</literal>, and <literal>version</literal>. <indexterm> <primary>type</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Attribute Expression</secondary><tertiary>type</tertiary> </indexterm> <indexterm> <primary>Attribute Expression</primary><secondary>type</secondary> </indexterm> <indexterm> <primary>type</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>operation</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The comparison to perform (required). Allowed values:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>lt:</literal> True if the value of the node’s <literal>attribute</literal> is less than <literal>value</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>gt:</literal> True if the value of the node’s <literal>attribute</literal> is greater than <literal>value</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>lte:</literal> True if the value of the node’s <literal>attribute</literal> is less than or equal to <literal>value</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>gte:</literal> True if the value of the node’s <literal>attribute</literal> is greater than or equal to <literal>value</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>eq:</literal> True if the value of the node’s <literal>attribute</literal> is equal to <literal>value</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>ne:</literal> True if the value of the node’s <literal>attribute</literal> is not equal to <literal>value</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>defined:</literal> True if the node has the named attribute"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>not_defined:</literal> True if the node does not have the named attribute <indexterm> <primary>operation</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Attribute Expression</secondary><tertiary>operation</tertiary> </indexterm> <indexterm> <primary>Attribute Expression</primary><secondary>operation</secondary> </indexterm> <indexterm> <primary>operation</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>value</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "User-supplied value for comparison (required) <indexterm> <primary>value</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Attribute Expression</secondary><tertiary>value</tertiary> </indexterm> <indexterm> <primary>Attribute Expression</primary><secondary>value</secondary> </indexterm> <indexterm> <primary>value</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>value-source</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>literal</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "How the <literal>value</literal> is derived. Allowed values:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>literal</literal>: <literal>value</literal> is a literal string to compare against"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>param</literal>: <literal>value</literal> is the name of a resource parameter to compare against (only valid in location constraints)"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>meta</literal>: <literal>value</literal> is the name of a resource meta-attribute to compare against (only valid in location constraints) <indexterm> <primary>value</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Attribute Expression</secondary><tertiary>value</tertiary> </indexterm> <indexterm> <primary>Attribute Expression</primary><secondary>value</secondary> </indexterm> <indexterm> <primary>value</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "In addition to any attributes added by the administrator, the cluster defines special, built-in node attributes for each node that can also be used."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Built-in node attributes"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Name"
msgstr ""
#. Tag: entry
#, no-c-format
msgid "Value"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>#uname</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Node <link linkend=\"s-node-name\">name</link>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>#id</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Node ID"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>#kind</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Node type. Possible values are <literal>cluster</literal>, <literal>remote</literal>, and <literal>container</literal>. Kind is <literal>remote</literal> for Pacemaker Remote nodes created with the <literal>ocf:pacemaker:remote</literal> resource, and <literal>container</literal> for Pacemaker Remote guest nodes and bundle nodes"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>#is_dc</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "\"true\" if this node is a Designated Controller (DC), \"false\" otherwise"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>#cluster-name</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The value of the <literal>cluster-name</literal> cluster property, if set"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>#site-name</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The value of the <literal>site-name</literal> cluster property, if set, otherwise identical to <literal>#cluster-name</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>#role</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The role the relevant promotable clone resource has on this node. Valid only within a rule for a location constraint for a promotable clone resource."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Time- and Date-Based Expressions"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Time Based Expressions</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Constraint</secondary><tertiary>Date/Time Expression</tertiary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date/Time Expression</secondary> </indexterm> <indexterm> <primary>Date/Time Expression</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "As the name suggests, <literal>date_expressions</literal> are used to control a resource or cluster option based on the current date/time. They may contain an optional <literal>date_spec</literal> and/or <literal>duration</literal> object depending on the context."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a Date Expression"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>start</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A date/time conforming to the <ulink url=\"http://en.wikipedia.org/wiki/ISO_8601\">ISO8601</ulink> specification. <indexterm> <primary>start</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date/Time Expression</secondary><tertiary>start</tertiary> </indexterm> <indexterm> <primary>Date/Time Expression</primary><secondary>start</secondary> </indexterm> <indexterm> <primary>start</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>end</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A date/time conforming to the <ulink url=\"http://en.wikipedia.org/wiki/ISO_8601\">ISO8601</ulink> specification. Can be inferred by supplying a value for <literal>start</literal> and a <literal>duration</literal>. <indexterm> <primary>end</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date/Time Expression</secondary><tertiary>end</tertiary> </indexterm> <indexterm> <primary>Date/Time Expression</primary><secondary>end</secondary> </indexterm> <indexterm> <primary>end</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Compares the current date/time with the start and/or end date, depending on the context. Allowed values:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>gt:</literal> True if the current date/time is after <literal>start</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>lt:</literal> True if the current date/time is before <literal>end</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>in_range:</literal> True if the current date/time is after <literal>start</literal> and before <literal>end</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>date_spec:</literal> True if the current date/time matches a <literal>date_spec</literal> object (described below) <indexterm> <primary>operation</primary><secondary>Constraint Expression</secondary> </indexterm> <indexterm> <primary>Constraint Expression</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date/Time Expression</secondary><tertiary>operation</tertiary> </indexterm> <indexterm> <primary>Date/Time Expression</primary><secondary>operation</secondary> </indexterm> <indexterm> <primary>operation</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "As these comparisons (except for <literal>date_spec</literal>) include the time, the <literal>eq</literal>, <literal>neq</literal>, <literal>gte</literal> and <literal>lte</literal> operators have not been implemented since they would only be valid for a single second."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Date Specifications"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Constraint</secondary><tertiary>Date Specification</tertiary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>date_spec</literal> objects are used to create cron-like expressions relating to time. Each field can contain a single number or a single range. Instead of defaulting to zero, any field not supplied is ignored."
msgstr ""
#. Tag: para
#, no-c-format
msgid "For example, <literal>monthdays=\"1\"</literal> matches the first day of every month and <literal>hours=\"09-17\"</literal> matches the hours between 9am and 5pm (inclusive). At this time, multiple ranges (e.g. <literal>weekdays=\"1,2\"</literal> or <literal>weekdays=\"1-2,5-6\"</literal>) are not supported; depending on demand, this might be implemented in a future release."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Properties of a Date Specification"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A unique name for the object <indexterm> <primary>id</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>id</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>id</secondary> </indexterm> <indexterm> <primary>id</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>hours</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Allowed values: 0-23 <indexterm> <primary>hours</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>hours</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>hours</secondary> </indexterm> <indexterm> <primary>hours</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>monthdays</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Allowed values: 1-31 (depending on month and year) <indexterm> <primary>monthdays</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>monthdays</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>monthdays</secondary> </indexterm> <indexterm> <primary>monthdays</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>weekdays</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Allowed values: 1-7 (1=Monday, 7=Sunday) <indexterm> <primary>weekdays</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>weekdays</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>weekdays</secondary> </indexterm> <indexterm> <primary>weekdays</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>yeardays</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Allowed values: 1-366 (depending on the year) <indexterm> <primary>yeardays</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>yeardays</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>yeardays</secondary> </indexterm> <indexterm> <primary>yeardays</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>months</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Allowed values: 1-12 <indexterm> <primary>months</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>months</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>months</secondary> </indexterm> <indexterm> <primary>months</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>weeks</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Allowed values: 1-53 (depending on weekyear) <indexterm> <primary>weeks</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>weeks</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>weeks</secondary> </indexterm> <indexterm> <primary>weeks</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>years</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Year according to the Gregorian calendar <indexterm> <primary>years</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>years</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>years</secondary> </indexterm> <indexterm> <primary>years</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>weekyears</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Year in which the week started; e.g. 1 January 2005 can be specified as <emphasis>2005-001 Ordinal</emphasis>, <emphasis>2005-01-01 Gregorian</emphasis> or <emphasis>2004-W53-6 Weekly</emphasis> and thus would match <literal>years=\"2005\"</literal> or <literal>weekyears=\"2004\"</literal> <indexterm> <primary>weekyears</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>weekyears</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>weekyears</secondary> </indexterm> <indexterm> <primary>weekyears</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>moon</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Allowed values are 0-7 (0 is new, 4 is full moon). Seriously, you can use this. This was implemented to demonstrate the ease with which new comparisons could be added. <indexterm> <primary>moon</primary><secondary>Date Specification</secondary> </indexterm> <indexterm> <primary>Date Specification</primary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Date Specification</secondary><tertiary>moon</tertiary> </indexterm> <indexterm> <primary>Date Specification</primary><secondary>moon</secondary> </indexterm> <indexterm> <primary>moon</primary> </indexterm>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Durations"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Duration</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Constraint</secondary><tertiary>Duration</tertiary> </indexterm> <indexterm> <primary>Constraint</primary><secondary>Duration</secondary> </indexterm> <indexterm> <primary>Duration</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Durations are used to calculate a value for <literal>end</literal> when one is not supplied to <literal>in_range</literal> operations. They contain the same fields as <literal>date_spec</literal> objects but without the limitations (e.g. you can have a duration of 19 months). As with <literal>date_specs</literal>, any field not supplied is ignored."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Sample Time-Based Expressions"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A small sample of how time-based expressions can be used:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "True if now is any time in the year 2005"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "<rule id=\"rule1\">\n"
" <date_expression id=\"date_expr1\" start=\"2005-001\" operation=\"in_range\">\n"
" <duration years=\"1\"/>\n"
" </date_expression>\n"
"</rule>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Equivalent expression"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "<rule id=\"rule2\">\n"
" <date_expression id=\"date_expr2\" operation=\"date_spec\">\n"
" <date_spec years=\"2005\"/>\n"
" </date_expression>\n"
"</rule>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "9am-5pm Monday-Friday"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "<rule id=\"rule3\">\n"
" <date_expression id=\"date_expr3\" operation=\"date_spec\">\n"
" <date_spec hours=\"9-16\" days=\"1-5\"/>\n"
" </date_expression>\n"
"</rule>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Please note that the <literal>16</literal> matches up to <literal>16:59:59</literal>, as the numeric value (hour) still matches!"
msgstr ""
#. Tag: title
#, no-c-format
msgid "9am-6pm Monday through Friday or anytime Saturday"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "<rule id=\"rule4\" boolean-op=\"or\">\n"
" <date_expression id=\"date_expr4-1\" operation=\"date_spec\">\n"
" <date_spec hours=\"9-16\" days=\"1-5\"/>\n"
" </date_expression>\n"
" <date_expression id=\"date_expr4-2\" operation=\"date_spec\">\n"
" <date_spec days=\"6\"/>\n"
" </date_expression>\n"
"</rule>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "9am-5pm or 9pm-12am Monday through Friday"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "<rule id=\"rule5\" boolean-op=\"and\">\n"
" <rule id=\"rule5-nested1\" boolean-op=\"or\">\n"
" <date_expression id=\"date_expr5-1\" operation=\"date_spec\">\n"
" <date_spec hours=\"9-16\"/>\n"
" </date_expression>\n"
" <date_expression id=\"date_expr5-2\" operation=\"date_spec\">\n"
" <date_spec hours=\"21-23\"/>\n"
" </date_expression>\n"
" </rule>\n"
" <date_expression id=\"date_expr5-3\" operation=\"date_spec\">\n"
" <date_spec days=\"1-5\"/>\n"
" </date_expression>\n"
" </rule>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Mondays in March 2005"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "<rule id=\"rule6\" boolean-op=\"and\">\n"
" <date_expression id=\"date_expr6-1\" operation=\"date_spec\">\n"
" <date_spec weekdays=\"1\"/>\n"
" </date_expression>\n"
" <date_expression id=\"date_expr6-2\" operation=\"in_range\"\n"
" start=\"2005-03-01\" end=\"2005-04-01\"/>\n"
" </rule>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Because no time is specified with the above dates, 00:00:00 is implied. This means that the range includes all of 2005-03-01 but none of 2005-04-01. You may wish to write <literal>end=\"2005-03-31T23:59:59\"</literal> to avoid confusion."
msgstr ""
#. Tag: title
#, no-c-format
msgid "A full moon on Friday the 13th"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "<rule id=\"rule7\" boolean-op=\"and\">\n"
" <date_expression id=\"date_expr7\" operation=\"date_spec\">\n"
" <date_spec weekdays=\"5\" monthdays=\"13\" moon=\"4\"/>\n"
" </date_expression>\n"
"</rule>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Using Rules to Determine Resource Location"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Rule</primary><secondary>Determine Resource Location</secondary> </indexterm> <indexterm> <primary>Determine Resource Location</primary> </indexterm> <indexterm> <primary>Resource</primary><secondary>Location</secondary><tertiary>Determine by Rules</tertiary> </indexterm> <indexterm> <primary>Location</primary><secondary>Determine by Rules</secondary> </indexterm> <indexterm> <primary>Determine by Rules</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A location constraint may contain rules. When the constraint’s outermost rule evaluates to <literal>false</literal>, the cluster treats the constraint as if it were not there. When the rule evaluates to <literal>true</literal>, the node’s preference for running the resource is updated with the score associated with the rule."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If this sounds familiar, it is because you have been using a simplified syntax for location constraint rules already. Consider the following location constraint:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Prevent myApacheRsc from running on c001n03"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "<rsc_location id=\"dont-run-apache-on-c001n03\" rsc=\"myApacheRsc\"\n"
" score=\"-INFINITY\" node=\"c001n03\"/>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "This constraint can be more verbosely written as:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Prevent myApacheRsc from running on c001n03 - expanded version"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "<rsc_location id=\"dont-run-apache-on-c001n03\" rsc=\"myApacheRsc\">\n"
" <rule id=\"dont-run-apache-rule\" score=\"-INFINITY\">\n"
" <expression id=\"dont-run-apache-expr\" attribute=\"#uname\"\n"
" operation=\"eq\" value=\"c00n03\"/>\n"
" </rule>\n"
"</rsc_location>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The advantage of using the expanded form is that one can then add extra clauses to the rule, such as limiting the rule such that it only applies during certain times of the day or days of the week."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Location Rules Based on Other Node Properties"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The expanded form allows us to match on node properties other than its name. If we rated each machine’s CPU power such that the cluster had the following nodes section:"
msgstr ""
#. Tag: title
#, no-c-format
msgid "A sample nodes section for use with score-attribute"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "<nodes>\n"
" <node id=\"uuid1\" uname=\"c001n01\" type=\"normal\">\n"
" <instance_attributes id=\"uuid1-custom_attrs\">\n"
" <nvpair id=\"uuid1-cpu_mips\" name=\"cpu_mips\" value=\"1234\"/>\n"
" </instance_attributes>\n"
" </node>\n"
" <node id=\"uuid2\" uname=\"c001n02\" type=\"normal\">\n"
" <instance_attributes id=\"uuid2-custom_attrs\">\n"
" <nvpair id=\"uuid2-cpu_mips\" name=\"cpu_mips\" value=\"5678\"/>\n"
" </instance_attributes>\n"
" </node>\n"
"</nodes>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "then we could prevent resources from running on underpowered machines with this rule:"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "<rule id=\"need-more-power-rule\" score=\"-INFINITY\">\n"
" <expression id=\"need-more-power-expr\" attribute=\"cpu_mips\"\n"
" operation=\"lt\" value=\"3000\"/>\n"
"</rule>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Using <literal>score-attribute</literal> Instead of <literal>score</literal>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "When using <literal>score-attribute</literal> instead of <literal>score</literal>, each node matched by the rule has its score adjusted differently, according to its value for the named node attribute. Thus, in the previous example, if a rule used <literal>score-attribute=\"cpu_mips\"</literal>, <literal>c001n01</literal> would have its preference to run the resource increased by <literal>1234</literal> whereas <literal>c001n02</literal> would have its preference increased by <literal>5678</literal>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Using Rules to Control Resource Options"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Often some cluster nodes will be different from their peers. Sometimes, these differences — e.g. the location of a binary or the names of network interfaces — require resources to be configured differently depending on the machine they’re hosted on."
msgstr ""
#. Tag: para
#, no-c-format
msgid "By defining multiple <literal>instance_attributes</literal> objects for the resource and adding a rule to each, we can easily handle these special cases."
msgstr ""
#. Tag: para
#, no-c-format
msgid "In the example below, <literal>mySpecialRsc</literal> will use eth1 and port 9999 when run on <literal>node1</literal>, eth2 and port 8888 on <literal>node2</literal> and default to eth0 and port 9999 for all other nodes."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Defining different resource options based on the node name"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "<primitive id=\"mySpecialRsc\" class=\"ocf\" type=\"Special\" provider=\"me\">\n"
" <instance_attributes id=\"special-node1\" score=\"3\">\n"
" <rule id=\"node1-special-case\" score=\"INFINITY\" >\n"
" <expression id=\"node1-special-case-expr\" attribute=\"#uname\"\n"
" operation=\"eq\" value=\"node1\"/>\n"
" </rule>\n"
" <nvpair id=\"node1-interface\" name=\"interface\" value=\"eth1\"/>\n"
" </instance_attributes>\n"
" <instance_attributes id=\"special-node2\" score=\"2\" >\n"
" <rule id=\"node2-special-case\" score=\"INFINITY\">\n"
" <expression id=\"node2-special-case-expr\" attribute=\"#uname\"\n"
" operation=\"eq\" value=\"node2\"/>\n"
" </rule>\n"
" <nvpair id=\"node2-interface\" name=\"interface\" value=\"eth2\"/>\n"
" <nvpair id=\"node2-port\" name=\"port\" value=\"8888\"/>\n"
" </instance_attributes>\n"
" <instance_attributes id=\"defaults\" score=\"1\" >\n"
" <nvpair id=\"default-interface\" name=\"interface\" value=\"eth0\"/>\n"
" <nvpair id=\"default-port\" name=\"port\" value=\"9999\"/>\n"
" </instance_attributes>\n"
"</primitive>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "The order in which <literal>instance_attributes</literal> objects are evaluated is determined by their score (highest to lowest). If not supplied, score defaults to zero, and objects with an equal score are processed in listed order. If the <literal>instance_attributes</literal> object has no rule or a <literal>rule</literal> that evaluates to <literal>true</literal>, then for any parameter the resource does not yet have a value for, the resource will use the parameter values defined by the <literal>instance_attributes</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "For example, given the configuration above, if the resource is placed on node1:"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>special-node1</literal> has the highest score (3) and so is evaluated first; its rule evaluates to <literal>true</literal>, so <literal>interface</literal> is set to <literal>eth1</literal>."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>special-node2</literal> is evaluated next with score 2, but its rule evaluates to <literal>false</literal>, so it is ignored."
msgstr ""
#. Tag: para
#, no-c-format
msgid "<literal>defaults</literal> is evaluated last with score 1, and has no rule, so its values are examined; <literal>interface</literal> is already defined, so the value here is not used, but <literal>port</literal> is not yet defined, so <literal>port</literal> is set to <literal>9999</literal>."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Using Rules to Control Cluster Options"
msgstr ""
#. Tag: para
#, no-c-format
msgid "<indexterm> <primary>Rule</primary><secondary>Controlling Cluster Options</secondary> </indexterm> <indexterm> <primary>Controlling Cluster Options</primary> </indexterm> <indexterm> <primary>Cluster</primary><secondary>Setting Options with Rules</secondary> </indexterm> <indexterm> <primary>Setting Options with Rules</primary> </indexterm>"
msgstr ""
#. Tag: para
#, no-c-format
msgid "Controlling cluster options is achieved in much the same manner as specifying different resource options on different nodes."
msgstr ""
#. Tag: para
#, no-c-format
msgid "The difference is that because they are cluster options, one cannot (or should not, because they won’t work) use attribute-based expressions. The following example illustrates how to set a different <literal>resource-stickiness</literal> value during and outside work hours. This allows resources to automatically move back to their most preferred hosts, but at a time that (in theory) does not interfere with business activities."
msgstr ""
#. Tag: title
#, no-c-format
msgid "Change <literal>resource-stickiness</literal> during working hours"
msgstr ""
#. Tag: programlisting
#, no-c-format
msgid "<rsc_defaults>\n"
" <meta_attributes id=\"core-hours\" score=\"2\">\n"
" <rule id=\"core-hour-rule\" score=\"0\">\n"
" <date_expression id=\"nine-to-five-Mon-to-Fri\" operation=\"date_spec\">\n"
" <date_spec id=\"nine-to-five-Mon-to-Fri-spec\" hours=\"9-16\" weekdays=\"1-5\"/>\n"
" </date_expression>\n"
" </rule>\n"
" <nvpair id=\"core-stickiness\" name=\"resource-stickiness\" value=\"INFINITY\"/>\n"
" </meta_attributes>\n"
" <meta_attributes id=\"after-hours\" score=\"1\" >\n"
" <nvpair id=\"after-stickiness\" name=\"resource-stickiness\" value=\"0\"/>\n"
" </meta_attributes>\n"
"</rsc_defaults>"
msgstr ""
#. Tag: title
#, no-c-format
msgid "Ensuring Time-Based Rules Take Effect"
msgstr ""
#. Tag: para
#, no-c-format
msgid "A Pacemaker cluster is an event-driven system. As such, it won’t recalculate the best place for resources to run unless something (like a resource failure or configuration change) happens. This can mean that a location constraint that only allows resource X to run between 9am and 5pm is not enforced."
msgstr ""
#. Tag: para
#, no-c-format
msgid "If you rely on time-based rules, the <literal>cluster-recheck-interval</literal> cluster option (which defaults to 15 minutes) is essential. This tells the cluster to periodically recalculate the ideal state of the cluster."
msgstr ""
#. Tag: para
#, no-c-format
msgid "For example, if you set <literal>cluster-recheck-interval=\"5m\"</literal>, then sometime between 09:00 and 09:05 the cluster would notice that it needs to start resource X, and between 17:00 and 17:05 it would realize that X needed to be stopped. The timing of the actual start and stop actions depends on what other actions the cluster may need to perform first."
msgstr ""