diff --git a/ChangeLog b/ChangeLog index 5d2911b6b9..974143b11f 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,2459 +1,2508 @@ +* Fri Oct 06 2017 Ken Gaillot Pacemaker-1.1.18-rc1 +- Update source tarball to revision: cb21fde +- Changesets: 428 +- Diff: 153 files changed, 7895 insertions(+), 4415 deletions(-) + +- Features added since Pacemaker-1.1.17 + + warnings are now logged when using legacy syntax to be removed in 2.0 + + agents: ifspeed agent is now installed when building + + alerts: support alert filters + + alerts: support alerts for node attribute changes (experimental) + + crmd,pengine: support unfencing of remote nodes + + pengine: bundles now support all constraint types + + pengine: bundles now support rkt containers + + pengine: bundles support new container-attribute-target parameter + + pengine: guest nodes are now probed like any other node + + pengine,tools: logs and crm_mon show why resources changed state + + stonith-ng: support new fencing resource parameter pcmk_delay_base + + tools: new crm_resource option --why explains why resources are stopped + +- Changes since Pacemaker-1.1.17 + + many documentation improvements + + agents: ifspeed properly calculates speed of hfi1 interfaces + + agents: ClusterMon now interprets "update" less than 1000 as seconds + + attrd: don't lose attributes set between attrd start-up and cluster join + + attrd: fix multiple minor memory leaks + + crmd: correctly record that unfencing is complete + + lrmd: remote resource operations return immediate error if key setup fails + + pengine: validate no-quorum-policy=suicide correctly + + pengine: avoid crash when alerts section has comments + + pengine: detect permanent master scores at start-up + + pengine: do not re-add a node's default score for each location constraint + + pengine: allow resources inside bundles to receive clone notifications + + pengine: default to non-interleaved bundle ordering for safety + + pengine: ensure bundle nodes and child resources are correctly cleaned up + + pengine: prevent graph loops when fencing the host underneath a bundle + + pengine: probe bundle connection resources + + pengine: bundles now respect PCMK_authkey_location + + pengine: fix multiple memory issues (use-after-free, use-of-NULL) with bundles + + pengine: resources in bundles respect failcounts + + pengine: ensure nested container connections run on the same host + + pengine: ensure unrecoverable remote nodes are fenced even if no resources can run on them + + pengine: handle resource migrating behind a migrating remote connection + + pengine: make sure calculated resource scores are consistent on different architectures + + pengine: retrigger unfencing for changed device parameters only when necessary + + stonith-ng: make fencing-device reappear properly after reenabling + + stonith-ng: include pcmk_on_action in meta-data so 'on' can be overridden + + tools: allow crm_report to work with no log files specified + + tools: fix use-after-free in crm_diff introduced in 1.1.17 + * Thu Jul 06 2017 Ken Gaillot Pacemaker-1.1.17-1 - Update source tarball to revision: 301bc44 - Changesets: 539 - Diff: 177 files changed, 11525 insertions(+), 5036 deletions(-) - Features added since Pacemaker-1.1.16 + New "bundle" resource type for Docker container use cases (experimental) + New "PCMK_node_start_state" environment variable to start node in standby + New "value-source" rule expression attribute in location constraints to compare a node attribute against a resource parameter + New "stonith-max-attempts" cluster option to specify how many times fencing can fail for a target before the cluster will no longer immediately re-attempt it (previously hard-coded at 10) + New "cluster-ipc-limit" cluster option to avoid IPC client eviction in large clusters + Failures are now tracked per operation type, as well as per node and resource (the "fail-count" and "last-failure" node attribute names now end in "#OPERATION_INTERVAL") + attrd: Pacemaker Remote node attributes and regular expressions are now supported on legacy cluster stacks (heartbeat, CMAN, and corosync plugin) + tools: New "crm_resource --validate" option + tools: New "stonith_admin --list-targets" option + tools: New "crm_attribute --pattern" option to match a regular expression + tools: "crm_resource --cleanup" and "crm_failcount" can now take --operation and --interval options to operate on a single operation type - Changes since Pacemaker-1.1.16 + Fix multiple memory issues (leaks, use-after-free) in libraries + pengine: unmanaging a guest node resource puts guest in maintenance mode + cib: broadcasts of cib changes should always pass ACL checks + crmd,libcrmcommon: update throttling when CPUs are hot-plugged + crmd: abort transition whenever we lose quorum + crmd: avoid attribute write-out on join when atomic attrd is used + crmd: check for too many stonith failures only when aborting for that reason + crmd: correctly clear failure counts only for a specified node + crmd: don't fence old DC if it's shutting down as soon-to-be DC joins + crmd: forget stonith failures when forgetting node + crmd: all nodes should track stonith failure counts in case they become DC + crmd: update cache status for guest node whose host is fenced + dbus: prevent lrmd from hanging on dbus calls + fencing: detect newly added constraints for stonith devices + pengine: order remote actions after connection recovery (regression introduced in 1.1.15) + pengine: quicker recovery from failed demote + libcib: determine remote nodes correctly from node status entries + libcrmcommon: avoid evicting IPC client if messages spike briefly + libcrmcommon: better XML comment handling prevents infinite election loop + libcrmcommon: set month correctly in date/time string sent to alert agents + libfencing,fencing: intelligently remap "action" wrongly specified in config + libservices: ensure completed ops aren't on blocked ops list + libservices: properly detect and cancel in-flight systemd/upstart ops + libservices: properly watch writable DBus handles + libservices: systemd service that is reloading doesn't cause monitor failure + pacemaker_remoted: allow graceful shutdown while unmanaged + pengine,libpe_status: don't clear same fail-count twice + pengine: consider guest node unclean if its host is unclean + pengine: do not re-add a node's default score for each location constraint + pengine: avoid restarting services when recovering remote connection + pengine: better guest node recovery when host fails + pengine: guest node fencing doesn't require stonith enabled + pengine: allow probes of guest node connection resources + pengine: properly handle allow-migrate explicitly set for remote connection + pengine: fence failed remote nodes even if no resources can run on them + tools: resource agents will now get the correct node name on Pacemaker Remote nodes when using crm_node and crm_attribute + tools: avoid grep crashes in crm_report when looking for system logs + tools: crm_resource -C now clears last-failure as well as fail-count + tools: implement crm_failcount command-line options correctly + tools: properly ignore version with crm_diff --no-version * Wed Nov 30 2016 Ken Gaillot Pacemaker-1.1.16-1 - Update source tarball to revision: 76876b3 - Changesets: 382 - Diff: 145 files changed, 7200 insertions(+), 5621 deletions(-) - Features added since Pacemaker-1.1.15 + Location constraints may use rsc-pattern, with submatches expanded + node-health-base available with node-health-strategy=progressive + new Pacemaker Development document for working on pacemaker code base + new PCMK_panic_action variable allows crash instead of reboot on panic + resources: add resource agent for managing a node attribute + systemd: include socket units when listing all systemd agents - Changes since Pacemaker-1.1.15 + Important security fix for CVE-2016-7035 + Logging is now synchronous when blackboxes are enabled + All python code except CTS is now compatible with python 2.6+ and 3.2+ + build: take advantage of compiler features for security and performance + build: update SuSE spec modifications for recent spec changes + build: avoid watchdog reboot when upgrading pacemaker_remote with sbd + build: numerous other improvements in environment detection, etc. + cib: fix infinite loop when no schema validates + crmd: cl#5185 - record pending operations in CIB before they are performed + crmd: don't abort transitions for CIB comment changes + crmd: resend shutdown request if DC loses original request + documentation: install improved README in doc instead of now-removed AUTHORS + documentation: clarify licensing and provide copy of all licenses + documentation: document various features and upgrades better + fence_legacy: use "list" action when searching cluster-glue agents + libcib: don't stop sending alerts after releasing DC role + libcrmcommon: properly handle XML comments when comparing v2 patchset diffs + libcrmcommon: report errors consistently when waiting for data on connection + libpengine: avoid potential use-of-NULL + libservices: use DBusError API properly + pacemaker_remote: init script stop should always return 0 + pacemaker_remote: allow remote clients to timeout/reconnect + pacemaker_remote: correctly calculate remaining timeout when receiving messages + pengine: avoid transition loop for start-then-stop + unfencing + pengine: correctly update dependent actions of un-runnable clones + pengine: do not fence a node in maintenance mode if it shuts down cleanly + pengine: set OCF_RESKEY_CRM_meta_notify_active_* for multistate resources + resources: ping - avoid temporary files for fping check, support FreeBSD + resources: SysInfo - better support for FreeBSD + resources: variable name typo in docker-wrapper + systemd: order pacemaker after time-sync target + tools: correct attrd_updater help and error messages when using CMAN + tools: crm_standby --version/--help should work without cluster running + tools: make crm_report sanitize CIB before generating readable version + tools: display pending resource state by default when available + tools: avoid matching other process with same PID in ClusterMon * Tue Jun 21 2016 Ken Gaillot Pacemaker-1.1.15-1 - Update source tarball to revision: 32fa6a5 - Changesets: 533 - Diff: 219 files changed, 6659 insertions(+), 3989 deletions(-) - Features added since Pacemaker-1.1.14 + Event-driven alerts allow scripts to be called after significant events + build: Some files moved from pacemaker package to pacemaker-cli for cleaner pacemaker-remote dependencies + build: ./configure --with-configdir argument for /etc/sysconfig, /etc/default, etc. + fencing: Simplify watchdog integration + fencing: Support concurrent fencing actions via new pcmk_action_limit option + remote: pacemaker_remote may be stopped without disabling resource first + remote: Report integration status of Pacemaker Remote nodes in CIB node_state + tools: crm_mon now reports why resources are not starting + tools: crm_report now obscures passwords in logfiles + tools: attrd_updater --update-both/--update-delay options allow changing dampening value + tools: allow stonith_admin -H '*' to show history for all nodes - Changes since Pacemaker-1.1.14 + Fix multiple memory issues (leaks, use-after-free) in daemons, libraries and tools + Make various log messages more user-friendly + Improve FreeBSD and Hurd support + attrd: Prevent possible segfault on exit + cib: Fix regression to restore support for compressed CIB larger than 1MB + common: fix regression in 1.1.14 that made have-watchdog always true + controld: handle DLM "wait fencing" state better + crmd: Fix regression so that fenced unseen nodes do not remain unclean + crmd: Take start-delay into account when calculation action timeouts + crmd: Avoid timeout on older peers when cancelling a resource operation + fencing: Allow fencing by node ID (e.g. by DLM) even if node left cluster + lrmd: Fix potential issues when cluster is stopped via systemd shutdown + pacemakerd: Properly respawn stonithd if it fails + pengine: Fix regression with multiple monitor levels that could ignore failure + pengine: Correctly set OCF_RESKEY_CRM_meta_timeout when start-delay is configured + pengine: Properly order actions for master/slave resources in anti-colocations + pengine: Respect asymmetrical ordering when trying to move resources + pengine: Properly order stop actions on guest node relative to host stonith + pengine: Correctly block actions dependent on unrunnable clones + remote: Allow remote nodes to have node attributes even with legacy attrd + remote: Recover from remote node fencing more quickly + remote: Place resources on newly rejoined remote nodes more quickly + resources: ping agent can now use fping6 for IPv6 hosts + resources: SysInfo now resets #health_disk to green when there's sufficient free disk + tools: crm_report is now more efficient and handles Pacemaker Remote nodes better + tools: Prevent crm_resource segfault when --resource is not supplied with --restart + tools: crm_shadow --display option now works + tools: crm_resource --restart handles groups, target-roles and moving resources better * Thu Jan 14 2016 Ken Gaillot Pacemaker-1.1.14-1 - Update source tarball to revision: f0b585a - Changesets: 724 - Diff: 179 files changed, 13142 insertions(+), 7695 deletions(-) - Features added since Pacemaker-1.1.13 + crm_resource: Indicate common reasons why a resource may not start after a cleanup + crm_resource: New --force-promote and --force-demote options for debugging + fencing: Support targeting fencing topologies by node name pattern or node attribute + fencing: Remap sequential topology reboots to all-off-then-all-on + pengine: Allow resources to start and stop as soon as their state is known on all nodes + pengine: Include a list of all and available nodes with clone notifications + pengine: Addition of the clone resource clone-min metadata option + pengine: Support of multiple-active=block for resource groups + remote: Resources that create guest nodes can be included in a group resource + remote: reconnect_interval option for remote nodes to delay reconnect after fence - Changes since Pacemaker-1.1.13 + improve support for building on FreeBSD and Debian + fix multiple memory issues (leaks, use-after-free, double free, use-of-NULL) in components and tools + cib: Do not terminate due to badly behaving clients + cman: handle corosync-invented node names of the form Node{id} for peers not in its node list + controld: replace bashism + crm_node: Display node state with -l and quorum status with -q, if available + crmd: resources would sometimes be restarted when only non-unique parameters changed + crmd: fence remote node after connection failure only once + crmd: handle resources named the same as cluster nodes + crmd: Pre-emptively fail in-flight actions when lrmd connections fail + crmd: Record actions in the CIB as failed if we cannot execute them + crm_report: Enable password sanitizing by default + crm_report: Allow log file discovery to be disabled + crm_resource: Allow the resource configuration to be modified for --force-{check,start,..} calls + crm_resource: Compensate for -C and -p being called with the child resource for clones + crm_resource: Correctly clean up all children for anonymous cloned groups + crm_resource: Correctly clean up failcounts for inactive anonymous clones + crm_resource: Correctly observe --force when deleting and updating attributes + crm_shadow: Fix "crm_shadow --diff" + crm_simulate: Prevent segfault on arches with 64bit time_t + fencing: ensure "required"/"automatic" only apply to "on" actions + fencing: Return a provider for the internal fencing agent "#watchdog" instead of logging an error + fencing: ignore stderr output of fence agents (often used for debug messages) + fencing: fix issue where deleting a fence device attribute can delete the device + libcib: potential user input overflow + libcluster: overhaul peer cache management + log: make syslog less noisy + log: fix various misspellings in log messages + lrmd: cancel currently pending STONITH op if stonithd connection is lost + lrmd: Finalize all pending and recurring operations when cleaning up a resource + pengine: Bug cl#5247 - Imply resources running on a container are stopped when the container is stopped + pengine: cl#5235 - Prevent graph loops that can be introduced by "load_stopped -> migrate_to" ordering + pengine: Correctly bypass fencing for resources that do not require it + pengine: do not timeout remote node recurring monitor op failure until after fencing + pengine: Ensure recurring monitor operations are cancelled when clone instances are de-allocated + pengine: fixes segfault in pengine when fencing remote node + pengine: properly handle blocked clone actions + pengine: ensure failed actions that occurred in node shutdown are displayed + remote: Correctly display the usage of the ocf:pacemaker:remote resource agent + remote: do not fail operations because of a migration + remote: enable reloads for select remote connection options + resources: allow for top output with or without percent sign in HealthCPU + resources: Prevent an error message on stopping "Dummy" resource + systemd: Prevent segfault when logging failed operations + systemd: Reconnect to System DBus if the connection is closed + systemd: set systemd resources' timeout values higher than systemd's own default + tools: Do not send command lines to syslog + tools: update SNMP MIB + upstart: Ensure pending structs are correctly unreferenced * Wed Jun 24 2015 Andrew Beekhof Pacemaker-1.1.13-1 - Update source tarball to revision: 2a1847e - Changesets: 750 - Diff: 156 files changed, 11323 insertions(+), 3725 deletions(-) - Features added since Pacemaker-1.1.12 + Allow fail-counts to be removed en-mass when the new attrd is in operation + attrd supports private attributes (not written to CIB) + crmd: Ensure a watchdog device is in use if stonith-watchdog-timeout is configured + crmd: If configured, trigger the watchdog immediately if we lose quorum and no-quorum-policy=suicide + crm_diff: Support generating a difference without versions details if --no-version/-u is supplied + crm_resource: Implement an intelligent restart capability + Fencing: Advertise the watchdog device for fencing operations + Fencing: Allow the cluster to recover resources if the watchdog is in use + fencing: cl#5134 - Support random fencing delay to avoid double fencing + mcp: Allow orphan children to initiate node panic via SIGQUIT + mcp: Turn on sbd integration if pacemakerd finds it running + mcp: Two new error codes that result in machine reset or power off + Officially support the resource-discovery attribute for location constraints + PE: Allow natural ordering of colocation sets + PE: Support non-actionable degraded mode for OCF + pengine: cl#5207 - Display "UNCLEAN" for resources running on unclean offline nodes + remote: pcmk remote client tool for use with container wrapper script + Support machine panics for some kinds of errors (via sbd if available) + tools: add crm_resource --wait option + tools: attrd_updater supports --query and --all options + tools: attrd_updater: Allow attributes to be set for other nodes - Changes since Pacemaker-1.1.12 + pengine: exclusive discovery implies rsc is only allowed on exclusive subset of nodes + acl: Correctly implement the 'reference' acl directive + acl: Do not delay evaluation of added nodes in some situations + attrd: b22b1fe did uuid test too early + attrd: Clean out the node cache when requested by the admin + attrd: fixes double free in attrd legacy + attrd: properly write attributes for peers once uuid is discovered + attrd: refresh should force an immediate write-out of all attributes + attrd: Simplify how node deletions happen + Bug rhbz#1067544 - Tools: Correctly handle --ban, --move and --locate for master/slave groups + Bug rhbz#1181824 - Ensure the DC can be reliably fenced + cib: Ability to upgrade cib validation schema in legacy mode + cib: Always generate digests for cib diffs in legacy mode + cib: assignment where comparison intended + cib: Avoid nodeid conflicts we don't care about + cib: Correctly add "update-origin", "update-client" and "update-user" attributes for cib + cib: Correctly set up signal handlers + cib: Correctly track node state + cib: Do not update on disk backups if we're just querying them + cib: Enable cib legacy mode for plugin-based clusters + cib: Ensure file-based backends treat '-o section' consistently with the native backend + cib: Ensure upgrade operations from a non-DC get an acknowledgement + cib: No need to enforce cib digests for v2 diffs in legacy mode + cib: Revert d153b86 to instantly get cib synchronized in legacy mode + cib: tls sock cleanup for remote cib connections + cli: Ensure subsequent unknown long options are correctly detected + cluster: Invoke crm_remove_conflicting_peer() only when the new node's uname is being assigned in the node cache + common: Increment current and age for lib common as a result of APIs being added + corosync: Bug cl#5232 - Somewhat gracefully handle nodes with invalid UUIDs + corosync: Avoid unnecessary repeated CMAP API calls + crmd/pengine: handle on-fail=ignore properly + crmd: Add "on_node" attribute for *_last_failure_0 lrm resource operations + crmd: All peers need to track node shutdown requests + crmd: Cached copies of transient attributes cease to be valid once a node leaves the membership + crmd: Correctly add the local option that validates against schema for pengine to calculate + crmd: Disable debug logging that results in significant overhead + crmd: do not remove connection resources during re-probe + crmd: don't update fail count twice for same failure + crmd: Ensure remote connection resources timeout properly during 'migrate_from' action + crmd: Ensure throttle_mode() does something on Linux + crmd: Fixes crash when remote connection migration fails + crmd: gracefully handle remote node disconnects during op execution + crmd: Handle remote connection failures while executing ops on remote connection + crmd: include remote nodes when forcing cluster wide resource reprobe + crmd: never stop recurring monitor ops for pcmk remote during incomplete migration + crmd: Prevent the old version of DC from being fenced when it shuts down for rolling-upgrade + crmd: Prevent use-of-NULL during reprobe + crmd: properly update job limit for baremetal remote-nodes + crmd: Remote-node throttle jobs count towards cluster-node hosting conneciton rsc + crmd: Reset stonith failcount to recover transitioner when the node rejoins + crmd: resolves memory leak in crmd. + crmd: respect start-failure-is-fatal even for artifically injected events + crmd: Wait for all pending operations to complete before poking the policy engine + crmd: When container's host is fenced, cancel in-flight operations + crm_attribute: Correctly update config options when -o crm_config is specified + crm_failcount: Better error reporting when no resource is specified + crm_mon: add exit reason to resource failure output + crm_mon: Fill CRM_notify_node in traps with node's uname rather than node's id if possible + crm_mon: Repair notification delivery when the v2 patch format is in use + crm_node: Correctly remove nodes from the CIB by nodeid + crm_report: More patterns for finding logs on non-DC nodes + crm_resource: Allow resource restart operations to be node specific + crm_resource: avoid deletion of lrm cache on node with resource discovery disabled. + crm_resource: Calculate how long to wait for a restart based on the resource timeouts + crm_resource: Clean up memory in --restart error paths + crm_resource: Display the locations of all anonymous clone children when supplying the children's common ID + crm_resource: Ensure --restart sets/clears meta attributes + crm_resource: Ensure fail-counts are purged when we redetect the state of all resources + crm_resource: Implement --timeout for resource restart operations + crm_resource: Include group members when calculating the next timeout + crm_resource: Memory leak in error paths + crm_resource: Prevent use-after-free + crm_resource: Repair regression test outputs + crm_resource: Use-after-free when restarting a resource + dbus: ref count leaks + dbus: Ensure both the read and write queues get dispatched + dbus: Fail gracefully if malloc fails + dbus: handle dispatch queue when multiple replies need to be processed + dbus: Notice when dbus connections get disabled + dbus: Remove double-free introduced while trying to make coverity shut up + ensure if B is colocated with A, B can never run without A + fence_legacy: Avoid passing 'port' to cluster-glue agents + fencing: Allow nodes to be purged from the member cache + fencing: Correctly make args for fencing agents + fencing: Correctly wait for self-fencing to occur when the watchdog is in use + fencing: Ensure the hostlist parameter is set for watchdog agents + fencing: Force 'stonith-ng' as the system name + fencing: Gracefully handle invalid metadata from agents + fencing: If configured, wait stonith-watchdog-timer seconds for self-fencing to complete + fencing: Reject actions for devices that haven't been explicitly registered yet + ipc: properly allocate server enforced buffer size on client + ipc: use server enforced buffer during ipc client send + lrmd, services: interpret LSB status codes properly + lrmd: add back support for class heartbeat agents + lrmd: cancel pending async connection during disconnect + lrmd: enable ipc proxy for docker-wrapper privileged mode + lrmd: fix rescheduling of systemd monitor op during start + lrmd: Handle systemd reporting 'done' before a resource is actually stopped + lrmd: Hint to child processes that using sd_notify is not required + lrmd: Log with the correct personality + lrmd: Prevent glib assert triggered by timers being removed from mainloop more than once + lrmd: report original timeout when systemd operation completes + lrmd: store failed operation exit reason in cib + mainloop: resolves race condition mainloop poll involving modification of ipc connections + make targetted reprobe for remote node work, crm_resource -C -N + mcp: Allow a configurable delay when debugging shutdown issues + mcp: Avoid requiring 'export' for SYS-V sysconfig options + Membership: Detect and resolve nodes that change their ID + pacemakerd: resolves memory leak of xml structure in pacemakerd + pengine: ability to launch resources in isolated containers + pengine: add #kind=remote for baremetal remote-nodes + pengine: allow baremetal remote-nodes to recover without requiring fencing when cluster-node fails + pengine: allow remote-nodes to be placed in maintenance mode + pengine: Avoid trailing whitespaces when printing resource state + pengine: cl#5130 - Choose nodes capable of running all the colocated utilization resources + pengine: cl#5130 - Only check the capacities of the nodes that are allowed to run the resource + pengine: Correctly compare feature set to determine how to unpack meta attributes + pengine: disable migrations for resources with isolation containers + pengine: disable reloading of resources within isolated container wrappers + pengine: Do not aggregate children in a pending state into the started/stopped/etc lists + pengine: Do not record duplicate copies of the failed actions + pengine: Do not reschedule monitors that are no longer needed while resource definitions have changed + pengine: Fence baremetal remote when recurring monitor op fails + pengine: Fix colocation with unmanaged resources + pengine: Fix the behaviors of multi-state resources with asymmetrical ordering + pengine: fixes pengine crash with orphaned remote node connection resource + pengine: fixes segfault caused by malformed log warning + pengine: handle cloned isolated resources in a sane way + pengine: handle isolated resource scenario, cloned group of isolated resources + pengine: Handle ordering between stateful and migratable resources + pengine: imply stop in container node resources when host node is fenced + pengine: only fence baremetal remote when connection can fails or can not be recovered + pengine: only kill process group on timeout when on-fail does not equal block. + pengine: per-node control over resource discovery + pengine: prefer migration target for remote node connections + pengine: prevent disabling rsc discovery per node in certain situations + pengine: Prevent use-after-free in sort_rsc_process_order() + pengine: properly handle ordering during remote connection partial migration + pengine: properly recover remote-nodes when cluster-node proxy goes offline + pengine: remove unnecessary whitespace from notify environment variables + pengine: require-all feature for ordered clones + pengine: Resolve memory leaks + pengine: resource discovery mode for location constraints + pengine: restart master instances on instance attribute changes + pengine: Turn off legacy unpacking of resource options into the meta hashtable + pengine: Watchdog integration is sufficient for fencing + Perform systemd reloads asynchronously + ping: Correctly advertise multiplier default + Prefer to inherit the watchdog timeout from SBD + properly record stop args after reload + provide fake meta data for ra class heartbeat + remote: report timestamps for remote connection resource operations + remote: Treat recv msg timeout as a disconnect + service: Prevent potential use-of-NULL in metadata lookups + solaris: Allow compilation when dirent.d_type is not available + solaris: Correctly replace the linux swab functions + solaris: Disable throttling since /proc doesn't exist + stonith-ng: Correctly observe the watchdog completion timeout + stonith-ng: Correctly track node state + stonith-ng: Reset mainloop source IDs after removing them + systemd: Correctly handle long running stop actions + systemd: Ensure failed monitor operations always return + systemd: Ensure we don't call dbus_message_unref() with NULL + systemd: fix crash caused when canceling in-flight operation + systemd: Kindly ask dbus NOT to kill the process if the dbus connection fails + systemd: Perform actions asynchronously + systemd: Perform monitor operations without blocking + systemd: Tell systemd not to take DBus down from underneath us + systemd: Trick systemd into not stopping our services before us during shutdown + tools: Improve crm_mon output with certain option combinations + upstart: Monitor actions always return 'ok' or 'not running' + upstart: Perform more parts of monitor operations without blocking + xml: add 'require-all' to xml schema for constraints + xml: cl#5231 - Unset the deleted attributes in the resulting diffs + xml: Clone the latest constraint schema in preparation for changes" + xml: Correctly create v1 patchsets when deleting attributes + xml: Do not change the ordering of properties when applying v1 cib diffs + xml: Do not dump deleted attributes + xml: Do not prune leaves from v1 cib diffs that are being created with digests + xml: Ensure ACLs are reapplied before calculating what a replace operation changed + xml: Fix upgrade-1.3.xsl to correctly transform ACL rules with "attribute" + xml: Prevent assert errors in crm_element_value() on applying a patch without version information + xml: Prevent potential use-of-NULL * Tue Jul 22 2014 Andrew Beekhof Pacemaker-1.1.12-1 - Update source tarball to revision: 93a037d - Changesets: 795 - Diff: 195 files changed, 13772 insertions(+), 6176 deletions(-) - Features added since Pacemaker-1.1.11 + Changes to the ACL schema to support nodes and unix groups + cib: Check ACLs prior to making the update instead of parsing the diff afterwards + cib: Default ACL support to on + cib: Enable the more efficient xml patchset format + cib: Implement zero-copy status update + cib: Send all r/w operations via the cluster connection and have all nodes process them + crmd: Set "cluster-name" property to corosync's "cluster_name" by default for corosync-2 + crm_mon: Display brief output if "-b/--brief" is supplied or 'b' is toggled + crm_report: Allow ssh alternatives to be used + crm_ticket: Support multiple modifications for a ticket in an atomic operation + extra: Add logrotate configuration file for /var/log/pacemaker.log + Fencing: Add the ability to call stonith_api_time() from stonith_admin + logging: daemons always get a log file, unless explicitly set to configured 'none' + logging: allows the user to specify a log level that is output to syslog + PE: Automatically re-unfence a node if the fencing device definition changes + pengine: cl#5174 - Allow resource sets and templates for location constraints + pengine: Support cib object tags + pengine: Support cluster-specific instance attributes based on rules + pengine: Support id-ref in nvpair with optional "name" + pengine: Support per-resource maintenance mode + pengine: Support site-specific instance attributes based on rules + tools: Allow crm_shadow to create older configuration versions + tools: Display pending state in crm_mon/crm_resource/crm_simulate if --pending/-j is supplied (cl#5178) + xml: Add the ability to have lightweight schema revisions + xml: Enable resource sets in location constraints for 1.2 schema + xml: Support resources that require unfencing - Changes since Pacemaker-1.1.11 + acl: Authenticate pacemaker-remote requests with the node name as the client + acl: Read access must be explicitly granted + attrd: Ensure attribute dampening is always observed + attrd: Remove offline nodes from node cache for "peer-remove" requests + Bug cl#5055 - Improved migration support. + Bug cl#5184 - Ensure pending probes that ultimately fail are correctly updated + Bug cl#5196 - pengine: Check values after expanding templates + Bug cl#5212 - Do not promote instances when quorum is lots and no-quorum-policy=freeze + Bug cl#5213 - Ensure role colocation with -INFINITY is enforced + Bug cl#5213 - Limit the scope of the previous commit to the masters role + Bug cl#5219 - pengine: Allow unrelated resources with a common colocation target to remain promoted + Bug cl#5222 - cib: Repair rolling update capability + Bug cl#5222 - Enable legacy mode whenever a broadcast update is detected + Bug rhbz#1036631 - Stop members of cloned groups when dependencies are stopped + Bug rhbz#1054307 - cname pattern match should be more restrictive in init script + Bug rhbz#1057697 - Use native DBus library for systemd/upstart support to avoid problematic use of threads + Bug rhbz#1097457 - Limit the scope of the previous fix and include a helpful comment + Bug rhbz#1097457 - Prevent invalid transition when resource are ordered to start after the container they're started in + cib: allow setting permanent remote-node attributes + cib: Auto-detect which patchset format to use + cib: Determine the best value of validate-with if one is not supplied + cib: Do not disable cib disk writes if on-disk cib is corrupt + cib: Ensure 'cibadmin -R/--replace' commands get replies + cib: Erasing the cib is an admin action, bump the admin_epoch instead + cib: Fix remote cib based on TLS + cib: Ignore patch failures if we already have their contents + cib: Validate that everyone still sees the same configuration once all updates have completed + cibadmin: Allow priviliged clients to perform tasks as unpriviliged users + cibadmin: Remove dangerous commands that exposed unnecessary implementation internal details + cluster: Fix segfault on removing a node + cluster: Prevent search of unames from attempting to create node entries for unknown nodes + cluster: Remove unknown offline nodes with conflicting unames from node cache + controld: Do not consider the dlm up until the address list is present + controld: handling startup fencing within the controld agent, not the dlm + controld: Return OCF_ERR_INSTALLED instead of OCF_NOT_INSTALLED + crmd: Ack pending operations that were cancelled due to rsc deletion + crmd: Actions can only be executed if their pre-requisits completed successfully + crmd: avoid double free caused by nested hash table removal + crmd: Avoid spamming the cib by triggering a transition only once per non-status change + crmd: Correctly react to successful unfencing operations + crmd: Correctly recognise operation cancellations we initiated + crmd: Do not erase the status section for unfenced nodes + crmd: Do not overwrite existing node state when fencing completes + crmd: Do not start timers for already completed operations + crmd: Ensure crm_config options are re-read on updates + crmd: Fenced nodes that return prior to an election do not need to have their status section reset + crmd: make lrm_state hash table not case sensitive + crmd: make node_state erase correctly + crmd: Only write fence_averride if open() returns a positive file descriptor + crmd: Prevent manual fencing confirmations from attempting to create node entries for unknown nodes + crmd: Prevent SIGPIPE when notifying CMAN about fencing operations + crmd: Remove state of unknown nodes with conflicting unames from CIB + crmd: Remove unknown nodes with conflicting unames from CIB + crmd: Report unsuccessful unfencing operations + crm_diff: Allow the generation of xml patchsets without digests + crm_mon: Allow the file created by --as-html to be world readable + crm_mon: Ensure resource attributes have been unpacked before displaying connectivity data + crm_node: Only remove the named resource from the cib + crm_report: Gracefully handle rediculously large logfiles + crm_report: Only gather dlm data if dlm_controld is running + crm_resource: Gracefully handle -EACCESS when querying the cib + crm_verify: Perform a full set of calculations whenever the status section is present + fencing: Advertise support for reboot/on/off in the metadata for legacy agents + fencing: Automatically switch from 'list' to 'status' to 'static-list' if those actions are not advertised in the metadata + fencing: Cache metadata lookups to avoid repeated blocking during device registration + fencing: Correctly record which peer performed the fencing operation + fencing: default to 'off' when agent does not advertise 'reboot' in metadata + fencing: Do not unregister/register all stonith devices on every resource agent change + fencing: Execute all required fencing devices regardless of what topology level they are at + fencing: Fence using all required devices + fencing: Pass the correct options when looking up the history by node name + fencing: Update stonith device list only if stonith is enabled + get_cluster_type: failing concurrent tool invocations on heartbeat + ignore SIGPIPE when gnutls is in use + iso8601: Different logic is needed when logging and calculating durations + iso8601: Fix memory leak in duration calculation + Logging: Bootstrap daemon logging before processing arguments but configure it afterwards + lrmd: Cancel recurring operations before stop action is executed + lrmd: Expose logging variables expected by OCF agents + lrmd: Handle systemd reporting 'done' before a resource is actually stopped/started + lrmd: Merge duplicate recurring monitor operations + lrmd: Prevent OCF agents from logging to random files due to "value" of setenv() being NULL + lrmd: Provide stderr output from agents if available, otherwise fall back to stdout + mainloop: Better handle the killing of processes in the act of exiting + mainloop: Canceling in-flight operations should not fail if child process has already exited. + mainloop: Fixes use after free in process monitor code + mcp: Tell systemd not to respawn us if we exit with rc=100 + membership: Avoid duplicate peer entries in the peer cache + pengine: Allow container nodes to migrate with connection resource + pengine: avoid assert by searching for stop action on correct node during LogActions + pengine: Block restart of resources if any dependent resource in a group is unmanaged + pengine: cl#5186 - Avoid running rsc on two nodes when node is fenced during migration + pengine: cl#5187 - Prevent resources in an anti-colocation from even temporarily running on a same node + pengine: cl#5200 - Before migrating utilization-using resources to a node, take off the load that will no longer run there if it's not introducing transition loop + pengine: Correctly handle origin offsets in the future + pengine: Correctly observe requires=nothing + pengine: Default sequential to TRUE for resource sets for consistency with colocation sets + pengine: Delay unfencing until after we know the state of all resources that require unfencing + pengine: Do not initiate fencing for unclean nodes when fencing is disabled + pengine: Ensure instance numbers are preserved for cloned templates + pengine: Ensure unfencing only happens once, even if the transition is interrupted + pengine: Fencing devices default to only requiring quorum in order to start + pengine: fixes invalid transition caused by clones with more than 10 instances + pengine: Force record pending for migrate_to actions + pengine: handles edge case where container order constraints are not honored during migration + pengine: Ignore failure-timeout only if the failed operation has on-fail="block" + pengine: Mark unrunnable stop actions as "blocked" and show the correct current locations + pengine: Memory leaks + pengine: properly handle fencing of container remote-nodes when the container is orphaned + pengine: properly place resource within a container when container is a remote-node. + pengine: Unfencing is based on device probes, there is no need to unfence when normal resources are found active + pengine: Use "#cluster-name" in rules for setting cluster-specific instance attributes + pengine: Use "#site-name" in rules for setting site-specific instance attributes + remote: Allow baremetal remote-node connection resources to migrate + remote: clear remote-node status correctly + remote: Enable migration support for baremetal connection resources by default + remote: Handle request/response ipc proxy correctly + services: Correctly reset the nice value for lrmd's children + services: Do not allow duplicate recurring op entries + services: Do not block synced service executions + services: Fixes segfault associated with cancelling in-flight recurring operations. + services: Remove cancelled recurring ops from internal lists as early as possible + services: Remove file descriptors from mainloop as soon as we have drained them + services: Reset the scheduling policy and priority for lrmd's children without replying on SCHED_RESET_ON_FORK + services_action_cancel: Interpret return code from mainloop_child_kill() correctly + stonith_admin: Ensure pointers passed to sscanf() are properly initialized + stonith_api_time_helper now returns when the most recent fencing operation completed + systemd: Prevent use-of-NULL when determining if an agent exists + systemd: Try to handle dbus actions that complete prior to configuring a callback + Tools: Non-daemons shouldn't abort just because xml parsing failed + Upstart: Allow comilation with glib versions older than 2.28 + Upstart: Do not attempt upstart jobs if we cannot connect to dbus + When data was old, it fixed so that the newest cib might not be acquired. + xml: Check all available schemas when doing upgrades + xml: Correctly determine the lowest allowed schema version + xml: Correctly enforce ACLs after a replace operation + xml: Correctly infer attribute changes after a replace operation + xml: Create the correct diff when only part of a document is changed + xml: Detect attribute ordering changes + xml: Detect content that is added and removed in the same update + xml: Do not prune meaningful leaves from v1 patchsets + xml: Empty patchsets are considered to have applied cleanly + xml: Ensure patches always have version details set + xml: Find the minimal set of changes when part of a document is replaced + xml: If validate-with is missing, we find the most recent schema that accepts it and go from there + xml: Introduce a 'move' primitive for v2 patch sets + xml: Preserve the attribute order in the patch for subsequent digest validation + xml: Resolve memory leak when logging xml blobs + xml: Update xml validation to allow '' * Thu Feb 13 2014 David Vossel Pacemaker-1.1.11-1 - Update source tarball to revision: 33f9d09 - Changesets: 462 - Diff: 147 files changed, 6810 insertions(+), 4057 deletions(-) - Features added since Pacemaker-1.1.10 + attrd: A truly atomic version of attrd for use where CPG is used for cluster communication + cib: Allow values to be added/updated and removed in a single update + cib: Support XML comments in diffs + Core: Allow blackbox logging to be disabled with SIGUSR2 + crmd: Do not block on proxied calls from pacemaker_remoted + crmd: Enable cluster-wide throttling when the cib heavily exceeds its target load + crmd: Make the per-node action limit directly configurable in the CIB + crmd: Slow down recovery on nodes with IO load + crmd: Track CPU usage on cluster nodes and slow down recovery on nodes with high CPU/IO load + crm_mon: add --hide-headers option to hide all headers + crm_node: Display partition output in sorted order + crm_report: Collect logs directly from journald if available + Fencing: On timeout, clean up the agent's entire process group + Fencing: Support agents that need the host to be unfenced at startup + ipc: Raise the default buffer size to 128k + PE: Add a special attribute for distinguishing between real nodes and containers in constraint rules + PE: Allow location constraints to take a regex pattern to match against resource IDs + pengine: Distinguish between the agent being missing and something the agent needs being missing + remote: Properly version the remote connection protocol - Changes since Pacemaker-1.1.10 + Bug rhbz#1011618 - Consistently use 'Slave' as the role for unpromoted master/slave resources + Bug rhbz#1057697 - Use native DBus library for systemd and upstart support to avoid problematic use of threads + attrd: Any variable called 'cluster' makes the daemon crash before reaching main() + attrd: Avoid infinite write loop for unknown peers + attrd: Drop all attributes for peers that left the cluster + attrd: Give remote-nodes ability to set attributes with attrd + attrd: Prevent inflation of attribute dampen intervals + attrd: Support SI units for attribute dampening + Bug cl#5171 - pengine: Don't prevent clones from running due to dependent resources + Bug cl#5179 - Corosync: Attempt to retrieve a peer's node name if it is not already known + Bug cl#5181 - corosync: Ensure node IDs are written to the CIB as unsigned integers + Bug rhbz#902407 - crm_resource: Handle --ban for master/slave resources as advertised + cib: Correctly check for archived configuration files + cib: Correctly log short-form xml diffs + cib: Fix remote cib based on TLS + cibadmin: Report errors during sign-off + cli: Do not enabled blackbox for cli tools + cluster: Fix segfault on removing a node + cman: Do not start pacemaker if cman startup fails + cman: Start clvmd and friends from the init script if enabled + Command-line tools should stop after an assertion failure + controld: Use the correct variant of dlm_controld for corosync-2 clusters + cpg: Correctly set the group name length + cpg: Ensure the CPG group is always null-terminated + cpg: Only process one message at a time to allow other priority jobs to be performed + crmd: Correctly observe the configured batch-limit + crmd: Correctly update expected state when the previous DC shuts down + crmd: Correcty update the history cache when recurring ops change their return code + crmd: Don't add node_state to cib, if we have not seen or fenced this node yet + crmd: don't segfault on shutdown when using heartbeat + crmd: Prevent recurring monitors being cancelled due to notify operations + crmd: Reliably detect and act on reprobe operations from the policy engine + crmd: When a peer expectedly shuts down, record the new join and expected states into the cib + crmd: When the DC gracefully shuts down, record the new expected state into the cib + crm_attribute: Do not swallow hostname lookup failures + crm_mon: Do not display duplicates of failed actions + crm_mon: Reduce flickering in interactive mode + crm_resource: Observe --master modifier for --move + crm_resource: Provide a meaningful error if --master is used for primitives and groups + fencing: Allow fencing for node after topology entries are deleted + fencing: Apply correct score to the resource of group + fencing: Ignore changes to non-fencing resources + fencing: Observe pcmk_host_list during automatic unfencing + fencing: Put all fencing agent processes into their own process group + fencing: Wait until all possible replies are recieved before continuing with unverified devices + ipc: Compress msgs based on client's actual max send size + ipc: Have the ipc server enforce a minimum buffer size all clients must use. + iso8601: Prevent dates from jumping backwards a day in some timezones + lrmd: Correctly calculate metadata for the 'service' class + lrmd: Correctly cancel monitor actions for lsb/systemd/service resources on cleaning up + mcp: Remove LSB hints that instruct chkconfig to start pacemaker at boot time + mcp: Some distros complain when LSB scripts do not include Default-Start/Stop directives + pengine: Allow fencing of baremetal remote nodes + pengine: cl#5186 - Avoid running rsc on two nodes when node is fenced during migration + pengine: Correctly account for the location preferences of things colocated with a group + pengine: Correctly handle demotion of grouped masters that are partially demoted + pengine: Disable container node probes due to constraint conflicts + pengine: Do not allow colocation with blocked clone instances + pengine: Do not re-allocate clone instances that are blocked in the Stopped state + pengine: Do not restart resources that depend on unmanaged resources + pengine: Force record pending for migrate_to actions + pengine: Location constraints with role=Started should prevent masters from running at all + pengine: Order demote/promote of resources on remote nodes to happen only once the connection is up + pengine: Properly handle orphaned multistate resources living on remote-nodes + pengine: Properly shutdown orphaned remote connection resources + pengine: Recover unexpectedly running container nodes. + remote: Add support for ipv6 into pacemaker_remote daemon + remote: Handle endian changes between client and server and improve forward compatibility + services: Fixes segfault associated with cancelling in-flight recurring operations. + services: Reset the scheduling policy and priority for lrmd's children without replying on SCHED_RESET_ON_FORK * Fri Jul 26 2013 Andrew Beekhof Pacemaker-1.1.10-1 - Update source tarball to revision: ab2e209 - Changesets: 602 - Diff: 143 files changed, 8162 insertions(+), 5159 deletions(-) - Features added since Pacemaker-1.1.9 + Core: Convert all exit codes to positive errno values + crm_error: Add the ability to list and print error symbols + crm_resource: Allow individual resources to be reprobed + crm_resource: Allow options to be set recursively + crm_resource: Implement --ban for moving resources away from nodes and --clear (replaces --unmove) + crm_resource: Support OCF tracing when using --force-(check|start|stop) + PE: Allow active nodes in our current membership to be fenced without quorum + PE: Suppress meaningless IDs when displaying anonymous clone status + Turn off auto-respawning of systemd services when the cluster starts them + Bug cl#5128 - pengine: Support maintenance mode for a single node - Changes since Pacemaker-1.1.9 + crmd: cib: stonithd: Memory leaks resolved and improved use of glib reference counting + attrd: Fixes deleted attributes during dc election + Bug cf#5153 - Correctly display clone failcounts in crm_mon + Bug cl#5133 - pengine: Correctly observe on-fail=block for failed demote operation + Bug cl#5148 - legacy: Correctly remove a node that used to have a different nodeid + Bug cl#5151 - Ensure node names are consistently compared without case + Bug cl#5152 - crmd: Correctly clean up fenced nodes during membership changes + Bug cl#5154 - Do not expire failures when on-fail=block is present + Bug cl#5155 - pengine: Block the stop of resources if any depending resource is unmanaged + Bug cl#5157 - Allow migration in the absence of some colocation constraints + Bug cl#5161 - crmd: Prevent memory leak in operation cache + Bug cl#5164 - crmd: Fixes crash when using pacemaker-remote + Bug cl#5164 - pengine: Fixes segfault when calculating transition with remote-nodes. + Bug cl#5167 - crm_mon: Only print "stopped" node list for incomplete clone sets + Bug cl#5168 - Prevent clones from being bounced around the cluster due to location constraints + Bug cl#5170 - Correctly support on-fail=block for clones + cib: Correctly read back archived configurations if the primary is corrupted + cib: The result is not valid when diffs fail to apply cleanly for CLI tools + cib: Restore the ability to embed comments in the configuration + cluster: Detect and warn about node names with capitals + cman: Do not pretend we know the state of nodes we've never seen + cman: Do not unconditionally start cman if it is already running + cman: Support non-blocking CPG calls + Core: Ensure the blackbox is saved on abnormal program termination + corosync: Detect the loss of members for which we only know the nodeid + corosync: Do not pretend we know the state of nodes we've never seen + corosync: Ensure removed peers are erased from all caches + corosync: Nodes that can persist in sending CPG messages must be alive afterall + crmd: Do not get stuck in S_POLICY_ENGINE if a node we couldn't fence returns + crmd: Do not update fail-count and last-failure for old failures + crmd: Ensure all membership operations can complete while trying to cancel a transition + crmd: Ensure operations for cleaned up resources don't block recovery + crmd: Ensure we return to a stable state if there have been too many fencing failures + crmd: Initiate node shutdown if another node claims to have successfully fenced us + crmd: Prevent messages for remote crmd clients from being relayed to wrong daemons + crmd: Properly handle recurring monitor operations for remote-node agent + crmd: Store last-run and last-rc-change for all operations + crm_mon: Ensure stale pid files are updated when a new process is started + crm_report: Correctly collect logs when 'uname -n' reports fully qualified names + fencing: Fail the operation once all peers have been exhausted + fencing: Restore the ability to manually confirm that fencing completed + ipc: Allow unpriviliged clients to clean up after server failures + ipc: Restore the ability for members of the haclient group to connect to the cluster + legacy: Support "crm_node --remove" with a node name for corosync plugin (bnc#805278) + lrmd: Default to the upstream location for resource agent scratch directory + lrmd: Pass errors from lsb metadata generation back to the caller + pengine: Correctly handle resources that recover before we operate on them + pengine: Delete the old resource state on every node whenever the resource type is changed + pengine: Detect constraints with inappropriate actions (ie. promote for a clone) + pengine: Ensure per-node resource parameters are used during probes + pengine: If fencing is unavailable or disabled, block further recovery for resources that fail to stop + pengine: Implement the rest of get_timet_now() and rename to get_effective_time + pengine: Re-initiate _active_ recurring monitors that previously failed but have timed out + remote: Workaround for inconsistent tls handshake behavior between gnutls versions + systemd: Ensure we get shut down correctly by systemd + systemd: Reload systemd after adding/removing override files for cluster services + xml: Check for and replace non-printing characters with their octal equivalent while exporting xml text + xml: Prevent lockups by setting a more reliable buffer allocation strategy * Fri Mar 08 2013 Andrew Beekhof Pacemaker-1.1.9-1 - Update source tarball to revision: 7e42d77 - Statistics: Changesets: 731 Diff: 1301 files changed, 92909 insertions(+), 57455 deletions(-) - Features added in Pacemaker-1.1.9 + corosync: Allow cman and corosync 2.0 nodes to use a name other than uname() + corosync: Use queues to avoid blocking when sending CPG messages + ipc: Compress messages that exceed the configured IPC message limit + ipc: Use queues to prevent slow clients from blocking the server + ipc: Use shared memory by default + lrmd: Support nagios remote monitoring + lrmd: Pacemaker Remote Daemon for extending pacemaker functionality outside corosync cluster. + pengine: Check for master/slave resources that are not OCF agents + pengine: Support a 'requires' resource meta-attribute for controlling whether it needs quorum, fencing or nothing + pengine: Support for resource container + pengine: Support resources that require unfencing before start - Changes since Pacemaker-1.1.8 + attrd: Correctly handle deletion of non-existant attributes + Bug cl#5135 - Improved detection of the active cluster type + Bug rhbz#913093 - Use crm_node instead of uname + cib: Avoid use-after-free by correctly support cib_no_children for non-xpath queries + cib: Correctly process XML diff's involving element removal + cib: Performance improvements for non-DC nodes + cib: Prevent error message by correctly handling peer replies + cib: Prevent ordering changes when applying xml diffs + cib: Remove text nodes from cib replace operations + cluster: Detect node name collisions in corosync + cluster: Preserve corosync membership state when matching node name/id entries + cman: Force fenced to terminate on shutdown + cman: Ignore qdisk 'nodes' + core: Drop per-user core directories + corosync: Avoid errors when closing failed connections + corosync: Ensure peer state is preserved when matching names to nodeids + corosync: Clean up CMAP connections after querying node name + corosync: Correctly detect corosync 2.0 clusters even if we don't have permission to access it + crmd: Bug cl#5144 - Do not updated the expected status of failed nodes + crmd: Correctly determin if cluster disconnection was abnormal + crmd: Correctly relay messages for remote clients (bnc#805626, bnc#804704) + crmd: Correctly stall the FSA when waiting for additional inputs + crmd: Detect and recover when we are evicted from CPG + crmd: Differentiate between a node that is up and coming up in peer_update_callback() + crmd: Have cib operation timeouts scale with node count + crmd: Improved continue/wait logic in do_dc_join_finalize() + crmd: Prevent election storms caused by getrusage() values being too close + crmd: Prevent timeouts when performing pacemaker level membership negotiation + crmd: Prevent use-after-free of fsa_message_queue during exit + crmd: Store all current actions when stalling the FSA + crm_mon: Do not try to render a blank cib and indicate the previous output is now stale + crm_mon: Fixes crm_mon crash when using snmp traps. + crm_mon: Look for the correct error codes when applying configuration updates + crm_report: Ensure policy engine logs are found + crm_report: Fix node list detection + crm_resource: Have crm_resource generate a valid transition key when sending resource commands to the crmd + date/time: Bug cl#5118 - Correctly convert seconds-since-epoch to the current time + fencing: Attempt to provide more information that just 'generic error' for failed actions + fencing: Correctly record completed but previously unknown fencing operations + fencing: Correctly terminate when all device options have been exhausted + fencing: cov#739453 - String not null terminated + fencing: Do not merge new fencing requests with stale ones from dead nodes + fencing: Do not start fencing until entire device topology is found or query results timeout. + fencing: Do not wait for the query timeout if all replies have arrived + fencing: Fix passing of parameters from CMAN containing '=' + fencing: Fix non-comparison when sorting devices by priority + fencing: On failure, only try a topology device once from the remote level. + fencing: Only try peers for non-topology based operations once + fencing: Retry stonith device for duration of action's timeout period. + heartbeat: Remove incorrect assert during cluster connect + ipc: Bug cl#5110 - Prevent 100% CPU usage when looking for synchronous replies + ipc: Use 50k as the default compression threshold + legacy: Prevent assertion failure on routing ais messages (bnc#805626) + legacy: Re-enable logging from the pacemaker plugin + legacy: Relax the 'active' check for plugin based clusters to avoid false negatives + legacy: Skip peer process check if the process list is empty in crm_is_corosync_peer_active() + mcp: Only define HA_DEBUGLOG to avoid agent calls to ocf_log printing everything twice + mcp: Re-attach to existing pacemaker components when mcp fails + pengine: Any location constraint for the slave role applies to all roles + pengine: Avoid leaking memory when cleaning up failcounts and using containers + pengine: Bug cl#5101 - Ensure stop order is preserved for partially active groups + pengine: Bug cl#5140 - Allow set members to be stopped when the subseqent set has require-all=false + pengine: Bug cl#5143 - Prevent shuffling of anonymous master/slave instances + pengine: Bug rhbz#880249 - Ensure orphan masters are demoted before being stopped + pengine: Bug rhbz#880249 - Teach the PE how to recover masters into primitives + pengine: cl#5025 - Automatically clear failcount for start/monitor failures after resource parameters change + pengine: cl#5099 - Probe operation uses the timeout value from the minimum interval monitor by default (#bnc776386) + pengine: cl#5111 - When clone/master child rsc has on-fail=stop, insure all children stop on failure. + pengine: cl#5142 - Do not delete orphaned children of an anonymous clone + pengine: Correctly unpack active anonymous clones + pengine: Ensure previous migrations are closed out before attempting another one + pengine: Introducing the whitebox container resources feature + pengine: Prevent double-free for cloned primitive from template + pengine: Process rsc_ticket dependencies earlier for correctly allocating resources (bnc#802307) + pengine: Remove special cases for fencing resources + pengine: rhbz#902459 - Remove rsc node status for orphan resources + systemd: Gracefully handle unexpected DBus return types + Replace the use of the insecure mktemp(3) with mkstemp(3) * Thu Sep 20 2012 Andrew Beekhof Pacemaker-1.1.8-1 - Update source tarball to revision: 1a5341f - Statistics: Changesets: 1019 Diff: 2107 files changed, 117258 insertions(+), 73606 deletions(-) - All APIs have been cleaned up and reduced to essentials - Pacemaker now includes a replacement lrmd that supports systemd and upstart agents - Config and state files (cib.xml, PE inputs and core files) have moved to new locations - The crm shell has become a separate project and no longer included with Pacemaker - All daemons/tools now have a unified set of error codes based on errno.h (see crm_error) - Changes since Pacemaker-1.1.7 + Core: Bug cl#5032 - Rewrite the iso8601 date handling code + Core: Correctly extract the version details from a diff + Core: Log blackbox contents, if enabled, when an error occurs + Core: Only LOG_NOTICE and higher are sent to syslog + Core: Replace use of IPC from clplumbing with IPC from libqb + Core: SIGUSR1 now enables blackbox logging, SIGTRAP to write out + Core: Support a blackbox for additional logging detail after crashes/errors + Promote support for advanced fencing logic to the stable schema + Promote support for node starting scores to the stable schema + Promote support for service and systemd to the stable schema + attrd: Differentiate between updating all our attributes and everybody updating all theirs too + attrd: Have single-shot clients wait for an ack before disconnecting + cib: cl#5026 - Synced cib updates should not return until the cpg broadcast is complete. + corosync: Detect when the first corosync has not yet formed and handle it gracefully + corosync: Obtain a full list of configured nodes, including their names, when we connect to the quorum API + corosync: Obtain a node name from DNS if one was not already known + corosync: Populate the cib nodelist from corosync if available + corosync: Use the CFG API and DNS to determine node names if not configured in corosync.conf + crmd: Block after 10 failed fencing attempts for a node + crmd: cl#5051 - Fixes file leak in PE ipc connection initialization. + crmd: cl#5053 - Fixes fail-count not being updated properly. + crmd: cl#5057 - Restart sub-systems correctly (bnc#755671) + crmd: cl#5068 - Fixes crm_node -R option so it works with corosync 2.0 + crmd: Correctly re-establish failed attrd connections + crmd: Detect when the quorum API isn't configured for corosync 2.0 + crmd: Do not overwrite any configured node type (eg. quorum node) + crmd: Enable use of new lrmd daemon and client library in crmd. + crmd: Overhaul the way node state is recorded and updated in the CIB + fencing: Bug rhbz#853537 - Prevent use-of-NULL when the cib libraries are not available + fencing: cl#5073 - Add 'off' as an valid value for stonith-action option. + fencing: cl#5092 - Always timeout stonith operations if timeout period expires. + fencing: cl#5093 - Stonith per device timeout option + fencing: Clean up if we detect a failed connection + fencing: Delegate complex self fencing requests - we wont be around to see it to completion + fencing: Ensure all peers are notified of complex fencing op completion + fencing: Fix passing of fence_legacy parameters containing '=' + fencing: Gracefully handle metadata requests for unknown agents + fencing: Return cached dynamic target list for busy devices. + fencing: rhbz#801355 - Abort transition on DC when external fencing operation is detected + fencing: rhbz#801355 - Merge fence requests for identical operations already in progress. + fencing: rhbz#801355 - Report fencing operations external of pacemaker to cib + fencing: Specify the action to perform using action= instead of the older option= + fencing: Stop building fake metadata for broken agents + fencing: Tolerate agents that report empty metadata in the admin tool + mcp: Correctly retry the connection to corosync on failure + mcp: Do not shut down IPC until the last client exits + mcp: Prevent use-after-free when running against corosync 1.x + pengine: Bug cl#5059 - Use the correct action's status when calculating required actions for interleaved clones + pengine: Bypass online/offline checking resource detection for ping/quorum nodes + pengine: cl#5044 - migrate_to no longer requires load_stopped for avoiding possible transition loop + pengine: cl#5069 - Honor 'on-fail=ignore' even when operation is disabled. + pengine: cl#5070 - Allow influence of promotion score when multistate rsc is left hand of colocation + pengine: cl#5072 - Fixes monitor op stopping after rsc promotion. + pengine: cl#5072 - Fixes pengine regression test failures + pengine: Correctly set the status for nodes not intended to run Pacemaker + pengine: Do not append instance numbers to anonymous clones + pengine: Fix failcount expiration + pengine: Fix memory leaks found by valgrind + pengine: Fix use-after-free and use-of-NULL errors detected by coverity + pengine: Fixes use of colocation scores other than +/- INFINITY + pengine: Improve detection of rejoining nodes + pengine: Prevent use-of-NULL when tracing is enabled + pengine: Stonith resources are allowed to start even if their probes haven't completed on partially active nodes + services: New class called 'service' which expands to the correct (LSB/systemd/upstart) standard + services: Support Asynchronous systemd/upstart actions + Tools: crm_shadow - Bug cl#5062 - Correctly set argv[0] when forking a shell process + Tools: crm_report: Always include system logs (if we can find them) * Wed Mar 28 2012 Andrew Beekhof Pacemaker-1.1.7-1 - Update source tarball to revision: bc7ff2c - Statistics: Changesets: 513 Diff: 1171 files changed, 90472 insertions(+), 19368 deletions(-) - Changes since Pacemaker-1.1.6.1 + ais: Prepare for corosync versions using IPC from libqb + cib: Correctly shutdown in the presence of peers without relying on timers + cib: Don't halt disk writes if the previous digest is missing + cib: Determine when there are no peers to respond to our shutdown request and exit + cib: Ensure no additional messages are processed after we begin terminating + Cluster: Hook up the callbacks to the corosync quorum notifications + Core: basename() may modify its input, do not pass in a constant + Core: Bug cl#5016 - Prevent failures in recurring ops from being lost + Core: Bug rhbz#800054 - Correctly retrieve heartbeat uuids + Core: Correctly determine when an XML file should be decompressed + Core: Correctly track the length of a string without reading from uninitialzied memory (valgrind) + Core: Ensure signals are handled eventually in the absense of timer sources or IPC messages + Core: Prevent use-of-NULL in crm_update_peer() + Core: Strip text nodes from on disk xml files + Core: Support libqb for logging + corosync: Consistently set the correct uuid with get_node_uuid() + Corosync: Correctly disconnect from corosync variants + Corosync: Correctly extract the node id from membership udpates + corosync: Correctly infer lost members from the quorum API + Corosync: Default to using the nodeid as the node's uuid (instead of uname) + corosync: Ensure we catch nodes that leave the membership, even if the ringid doesn't change + corosync: Hook up CPG membership + corosync: Relax a development assert and gracefully handle the error condition + corosync: Remove deprecated member of the CFG API + corosync: Treat CS_ERR_QUEUE_FULL the same as CS_ERR_TRY_AGAIN + corosync: Unset the process list when nodes dissappear on us + crmd: Also purge fencing results when we enter S_NOT_DC + crmd: Bug cl#5015 - Remove the failed operation as well as the resulting fail-count and last-failure attributes + crmd: Correctly determine when a node can suicide with fencing + crmd: Election - perform the age comparison only once + crmd: Fast-track shutdown if we couldn't request it via attrd + crmd: Leave it up to the PE to decide which ops can/cannot be reload + crmd: Prevent use-after-free when calling delete_resource due to CRM_OP_REPROBE + crmd: Supply format arguments in the correct order + fencing: Add missing format parameter + fencing: Add the fencing topology section to the 1.1 configuration schema + fencing: fence_legacy - Drop spurilous host argument from status query + fencing: fence_legacy - Ensure port is available as an environment variable when calling monitor + fencing: fence_pcmk - don't block if nothing is specified on stdin + fencing: Fix log format error + fencing: Fix segfault caused by passing garbage to dlsym() + fencing: Fix use-of-NULL in process_remote_stonith_query() + fencing: Fix use-of-NULL when listing installed devices + fencing: Implement support for advanced fencing topologies: eg. kdump || (network && disk) || power + fencing: More gracefully handle failed 'list' operations for devices that only support a single connection + fencing: Prevent duplicate free when listing devices + fencing: Prevent uninitialized pointers being passed to free + fencing: Prevent use-after-free, we may need the query result for subsequent operations + fencing: Provide enough data to construct an entry in the node's fencing history + fencing: Standardize on /one/ method for clients to request members be fenced + fencing: Supress errors when listing all registered devices + mcp: corosync_cfg_state_track was removed from the corosync API, luckily we didnt use it for anything + mcp: Do not specify a WorkingDirectory in the systemd unit file - startup fails if its not available + mcp: Set the HA_quorum_type env variable consistently with our corosync plugin + mcp: Shut down if one of our child processes can/should not be respawned + pengine: Bug cl#5000 - Ensure ordering is preserved when depending on partial sets + pengine: Bug cl#5028 - Unmanaged services should block shutdown unless in maintenance mode + pengine: Bug cl#5038 - Prevent restart of anonymous clones when clone-max decreases + pengine: Bug cl#5007 - Fixes use of colocation constraints with multi-state resources + pengine: Bug cl#5014 - Prevent asymmetrical order constraints from causing resource stops + pengine: Bug cl#5000 - Implements ability to create rsc_order constraint sets such that A can start after B or C has started. + pengine: Correctly migrate a resource that has just migrated + pengine: Correct return from error path + pengine: Detect reloads of previously migrated resources + pengine: Ensure post-migration stop actions occur before node shutdown + pengine: Log as loudly as possible when we cannot shut down a cluster node + pengine: Reload of a resource no longer causes a restart of dependent resources + pengine: Support limiting the number of concurrent live migrations + pengine: Support referencing templates in constraints + pengine: Support of referencing resource templates in resource sets + pengine: Support to make tickets standby for relinquishing tickets gracefully + stonith: A "start" operation of a stonith resource does a "monitor" on the device beyond registering it + stonith: Bug rhbz#745526 - Ensure stonith_admin actually gets called by fence_pcmk + Stonith: Ensure all nodes receive and deliver notifications of the manual override + stonith: Fix the stonith timeout issue (cl#5009, bnc#727498) + Stonith: Implement a manual override for when nodes are known to be safely off + Tools: Bug cl#5003 - Prevent use-after-free in crm_simlate + Tools: crm_mon - Support to display tickets (based on Yuusuke Iida's work) + Tools: crm_simulate - Support to grant/revoke/standby/activate tickets from the new ticket state section + Tools: Implement crm_node functionality for native corosync + Fix a number of potential problems reported by coverity * Wed Aug 31 2011 Andrew Beekhof 1.1.6-1 - Update source tarball to revision: 676e5f25aa46 tip - Statistics: Changesets: 376 Diff: 1761 files changed, 36259 insertions(+), 140578 deletions(-) - Changes since Pacemaker-1.1.5 + ais: check for retryable errors when dispatching AIS messages + ais: Correctly disconnect from Corosync and Cman based clusters + ais: Followup to previous patch - Ensure we drain the corosync queue of messages when Glib tells us there is input + ais: Handle IPC error before checking for NULL data (bnc#702907) + cib: Check the validation version before adding the originator details of a CIB change + cib: Remove disconnected remote connections from mainloop + cman: Correctly override existing fenced operations + cman: Dequeue all the cman emitted events and not only the first one leaving the others in the event's queue. + cman: Don't call fenced_join and fenced_leave when notifying cman of a fencing event. + cman: We need to run the crmd as root for CMAN so that we can ACK fencing operations + Core: Cancelled and pending operations do not count as failed + Core: Ensure there is sufficient space for EOS when building short-form option strings + Core: Fix variable expansion in pkg-config files + Core: Partial revert of accidental commit in previous patch + Core: Use dlopen to load heartbeat libraries on-demand + crmd: Bug lf#2509 - Watch for config option changes from the CIB even if we're not the DC + crmd: Bug lf#2528 - Introduce a slight delay when creating a transition to allow attrd time to perform its updates + crmd: Bug lf#2559 - Fail actions that were scheduled for a failed/fenced node + crmd: Bug lf#2584 - Allow nodes to fence themselves if they're the last one standing + crmd: Bug lf#2632 - Correctly handle nodes that return faster than stonith + crmd: Cancel timers for actions that were pending on dead nodes + crmd: Catch fence operations that claim to succeed but did not really + crmd: Do not wait for actions that were pending on dead nodes + crmd: Ensure we do not attempt to perform action on failed nodes + crmd: Prevent use-of-NULL by g_hash_table_iter_next() + crmd: Recurring actions shouldn't cause the last non-recurring action to be forgotten + crmd: Store only the last and last failed operation in the CIB + mcp: dirname() modifies the input path - pass in a copy of the logfile path + mcp: Enable stack detection logic instead of forcing 'corosync' + mcp: Fix spelling mistake in systemd service script that prevents shutdown + mcp: Shut down if corosync becomes unavailable + mcp: systemd control file is now functional + pengine: Before migrating an utilization-using resource to a node, take off the load which will no longer run there (lf#2599, bnc#695440) + pengine: Before migrating an utilization-using resource to a node, take off the load which will no longer run there (regression tests) (lf#2599, bnc#695440) + pengine: Bug lf#2574 - Prevent shuffling by choosing the correct clone instance to stop + pengine: Bug lf#2575 - Use uname for migration variables, id is a UUID on heartbeat + pengine: Bug lf#2581 - Avoid group restart when clone (re)starts on an unrelated node + pengine: Bug lf#2613, lf#2619 - Group migration after failures and non-default utilization policies + pengine: Bug suse#707150 - Prevent services being active if dependencies on clones are not satisfied + pengine: Correctly recognise which recurring operations are currently active + pengine: Demote from Master does not clear previous errors + pengine: Ensure restarts due to definition changes cause the start action to be re-issued not probes + pengine: Ensure role is preserved for unmanaged resources + pengine: Ensure unmanaged resources have the correct role set so the correct monitor operation is chosen + pengine: Fix memory leak for re-allocated resources reported by valgrind + pengine: Implement cluster ticket and deadman + pengine: Implement resource template + pengine: Correctly determine the state of multi-state resources with a partial operation history + pengine: Only allocate master/slave resources once + pengine: Partial revert of 'Minor code cleanup CS: cf6bca32376c On: 2011-08-15' + pengine: Resolve memory leak reported by valgrind + pengine: Restore the ability to save inputs to disk + Shell: implement -w,--wait option to wait for the transition to finish + Shell: repair template list command + Shell: set of commands to examine logs, reports, etc + Stonith: Consolidate pcmk_host_map into run_stonith_agent so that it is applied consistently + Stonith: Deprecate pcmk_arg_map for the saner pcmk_host_argument + Stonith: Fix use-of-NULL by g_hash_table_lookup + Stonith: Improved pcmk_host_map parsing + Stonith: Prevent use-of-NULL by g_hash_table_lookup + Stonith: Prevent use-of-NULL when no Linux-HA stonith agents are present + stonith: Add missing entries to stonith_error2string() + Stonith: Correctly finish sending agent options if the initial write is interrupted + stonith: Correctly handle synchronous calls + stonith: Coverity - Correctly construct result list for the query API call + stonith: Coverity - Remove badly constructed memory allocation from the query API call + stonith: Ensure completed operations are recorded as such in the history + Stonith: Ensure device parameters are passed to the daemon during registration + stonith: Fix use-of-NULL in stonith_api_device_list() + stonith: stonith_admin - Prevent use of uninitialized pointer by --history command + Tools: Bug lf#2528 - Make progress when attrd_updater is called repeatedly within the dampen interval but with the same value + Tools: crm_report - Correctly extract data from the local node + Tools: crm_report - Remove newlines when detecting the node list + Tools: crm_report - Repair the ability to extract data from the local machine + Tools: crm_report - Report on all detected backtraces * Fri Feb 11 2011 Andrew Beekhof 1.1.5-1 - Update source tarball to revision: baad6636a053 - Statistics: Changesets: 184 Diff: 605 files changed, 46103 insertions(+), 26417 deletions(-) - Changes since Pacemaker-1.1.4 + Add the ability to delegate sub-sections of the cluster to non-root users via ACLs Needs to be enabled at compile time, not enabled by default. + ais: Bug lf#2550 - Report failed processes immediately + Core: Prevent recently introduced use-after-free in replace_xml_child() + Core: Reinstate the logic that skips past non-XML_ELEMENT_NODE children + Core: Remove extra calls to xmlCleanupParser resulting in use-after-free + Core: Repair reference to child-of-child after removal of xml_child_iter_filter from get_message_xml() + crmd: Bug lf#2545 - Ensure notify variables are accurate for stop operations + crmd: Cancel recurring operations while we're still connected to the lrmd + crmd: Reschedule the PE_START action if its not already running when we try to use it + crmd: Update failcount for failed promote and demote operations + pengine: Bug lf#2445 - Avoid relying on stickness for stable clone placement + pengine: Bug lf#2445 - Do not override configured clone stickiness values + pengine: Bug lf#2493 - Don't imply colocation requirements when applying ordering constraints with clones + pengine: Bug lf#2495 - Prevent segfault by validating the contents of ordering sets + pengine: Bug lf#2508 - Correctly reconstruct the status of anonymous cloned groups + pengine: Bug lf#2518 - Avoid spamming the logs with errors for orphan resources + pengine: Bug lf#2544 - Prevent unstable clone placement by factoring in the current node's score before all others + pengine: Bug lf#2554 - target-role alone is not sufficient to promote resources + pengine: Correct target_rc for probes of inactive resources (fix regression introduced by cs:ac3f03006e95) + pengine: Ensure that fencing has completed for stop actions on stonith-dependent resources (lf#2551) + pengine: Only update the node's promotion score if the resource is active there + pengine: Only use the promotion score from the current clone instance + pengine: Prevent use-of-NULL resulting from variable shadowing spotted by Coverity + pengine: Prevent use-of-NULL when there is status for an undefined node + pengine: Prevet use-after-free resulting from unintended recursion when chosing a node to promote master/slave resources + Shell: don't create empty optional sections (bnc#665131) + Stonith: Teach stonith_admin to automagically obtain the current node attributes for the target from the CIB + tools: Bug lf#2527 - Prevent use-of-NULL in crm_simulate + Tools: Prevent crm_resource commands from being lost due to the use of cib_scope_local * Wed Oct 20 2010 Andrew Beekhof 1.1.4-1 - Update source tarball to revision: 75406c3eb2c1 tip - Statistics: Changesets: 169 Diff: 772 files changed, 56172 insertions(+), 39309 deletions(-) - Changes since Pacemaker-1.1.3 + Italian translation of Clusters from Scratch + Significant performance enhancements to the Policy Engine and CIB + cib: Bug lf#2506 - Don't remove client's when notifications fail, they might just be too big + cib: Drop invalid/failed connections from the client hashtable + cib: Ensure all diffs sent to peers have sufficient ordering information + cib: Ensure non-change diffs can preserve the ordering on the other side + cib: Fix the feature set check + cib: Include version information on our synthesised diffs when nothing changed + cib: Optimize the way we detect group/set ordering changes - 15% speedup + cib: Prevent false detection of config updates with the new diff format + cib: Reduce unnecessary copying when comparing xml objects + cib: Repair the processing of updates sent from peer nodes + cib: Revert part of a recent commit that purged still valid connections + cib: The feature set version check is only valid if the current value is non-NULL + Core: Actually removing diff markers is necessary + Core: Bug lf#2506 - Drop the compression limit because Heartbeat's IPC code sucks + Core: Cache Relax-NG schemas - profiling indicates many cycles are wasted needlessly re-parsing them + Core: Correctly compare against crm_log_level in the logging macros + Core: Correctly extract the version details from a diff + Core: Correctly hook up the RNG schema cache + Core: Correctly use lazy_xml_sort() for v2 digests + Core: Don't compress large payload elements unless we're approaching message limits + Core: Don't insert empty ID tags when applying diffs + Core: Enable the improve v2 digests + Core: Ensure ordering is preserved when applying diffs + Core: Fix the CRM_CHECK macro + Core: Modify the v2 digest algorithm so that some fields are sorted + Core: Prevent use-after-free when creating a CIB update for a timed out action + Core: Prevent use-of-NULL when cleaning up RelaxNG data structures + Core: Provide significant performance improvements by implementing versioned diffs and digests + crmd: All pending operations should be recorded, even recurring ones with high start delays + crmd: Don't abort transitions when probes are completed on a node + crmd: Don't hide stop events that time out - allowing faster recovery in the presence of overloaded hosts + crmd: Ensure the CIB is always writable on the DC by removing a timing hole + crmd: Include the correct transition details for timed out operations + crmd: Prevent use of NULL by making copies of the operation's hash table + crmd: There's no need to check the cib version from the 'added' part of diff updates + crmd: Use the supplied timeout for stop actions + mcp: Ensure valgrind is able to log its output somewhere + mcp: Use 99/01 for the start/stop sequence to avoid problems with services (such as libvirtd) started by init - Patch from Vladislav Bogdanov + pengine: Ensure fencing of the DC preceeds the STONITH_DONE operation + pengine: Fix memory leak introduced as part of the conversion to GHashTables + pengine: Fix memory leak when processing completed migration actions + pengine: Fix typo leading to use-of-NULL in the new ordering code + pengine: Free memory in recently introduced helper function + pengine: lf#2478 - Implement improved handling and recovery of atomic resource migrations + pengine: Obtain massive speedup by prepending to the list of ordering constraints (which can grow quite large) + pengine: Optimize the logic for deciding which non-grouped anonymous clone instances to probe for + pengine: Prevent clones from being stopped because resources colocated with them cannot be active + pengine: Try to ensure atomic migration ops occur within a single transition + pengine: Use hashtables instead of linked lists for performance sensitive datastructures + pengine: Use the original digest algorithm for parameter lists + stonith: cleanup children on timeout in fence_legacy + Stonith: Fix two memory leaks + Tools: crm_shadow - Avoid replacing the entire configuration (including status) * Tue Sep 21 2010 Andrew Beekhof 1.1.3-1 - Update source tarball to revision: e3bb31c56244 tip - Statistics: Changesets: 352 Diff: 481 files changed, 14130 insertions(+), 11156 deletions(-) - Changes since Pacemaker-1.1.2.1 + ais: Bug lf#2401 - Improved processing when the peer crmd processes join/leave + ais: Correct the logic for conecting to plugin based clusters + ais: Do not supply a process list in mcp-mode + ais: Drop support for whitetank in the 1.1 release series + ais: Get an initial dump of the node membership when connecting to quorum-based clusters + ais: Guard against saturated cpg connections + ais: Handle CS_ERR_TRY_AGAIN in more cases + ais: Move the code for finding uid before the fork so that the child does no logging + ais: Never allow quorum plugins to affect connection to the pacemaker plugin + ais: Sign everyone up for peer process updates, not just the crmd + ais: The cluster type needs to be set before initializing classic openais connections + cib: Also free query result for xpath operations that return more than one hit + cib: Attempt to resolve memory corruption when forking a child to write the cib to disk + cib: Correctly free memory when writing out the cib to disk + cib: Fix the application of unversioned diffs + cib: Remove old developmental error logging + cib: Restructure the 'valid peer' check for deciding which instructions to ignore + cman: Correctly process membership/quorum changes from the pcmk plugin. Allow other message types through untouched + cman: Filter directed messages not intended for us + cman: Grab the initial membership when we connect + cman: Keep the list of peer processes up-to-date + cman: Make sure our common hooks are called after a cman membership update + cman: Make sure we can compile without cman present + cman: Populate sender details for cpg messages + cman: Update the ringid for cman based clusters + Core: Correctly unpack HA_Messages containing multiple entries with the same name + Core: crm_count_member() should only track nodes that have the full stack up + Core: New developmental logging system inspired by the kernel and a PoC from Lars Ellenberg + crmd: All nodes should see status updates, not just he DC + crmd: Allow non-DC nodes to clear failcounts too + crmd: Base DC election on process relative uptime + crmd: Bug lf#2439 - cancel_op() can also return HA_RSCBUSY + crmd: Bug lf#2439 - Handle asynchronous notification of resource deletion events + crmd: Bug lf#2458 - Ensure stop actions always have the relevant resource attributes + crmd: Disable age as a criteria for cman based clusters, its not reliable enough + crmd: Ensure we activate the DC timer if we detect an alternate DC + crmd: Factor the nanosecond component of process uptime in elections + crmd: Fix assertion failure when performing async resource failures + crmd: Fix handling of async resource deletion results + crmd: Include the action for crm graph operations + crmd: Make sure the membership cache is accurate after a sucessful fencing operation + crmd: Make sure we always poke the FSA after a transition to clear any TE_HALT actions + crmd: Offer crm-level membership once the peer starts the crmd process + crmd: Only need to request quorum update for plugin based clusters + crmd: Prevent assertion failure for stop actions resulting from cs: 3c0bc17c6daf + crmd: Prevent everyone from loosing DC elections by correctly initializing all relevant variables + crmd: Prevent segmentation fault + crmd: several fixes for async resource delete (thanks to beekhof) + crmd: Use the correct define/size for lrm resource IDs + Introduce two new cluster types 'cman' and 'corosync', replaces 'quorum_provider' concept + mcp: Add missing headers when built without heartbeat support + mcp: Correctly initialize the string containing the list of active daemons + mcp: Fix macro expansion in init script + mcp: Fix the expansion of the pid file in the init script + mcp: Handle CS_ERR_TRY_AGAIN when connecting to libcfg + mcp: Make sure we can compile the mcp without cman present + mcp: New master control process for (re)spawning pacemaker daemons + mcp: Read config early so we can re-initialize logging asap if daemonizing + mcp: Rename the mcp binary to pacemakerd and create a 'pacemaker' init script + mcp: Resend our process list after every CPG change + mcp: Tell chkconfig we need to shut down early on + pengine: Avoid creating invalid ordering constraints for probes that are not needed + pengine: Bug lf#1959 - Fail unmanaged resources should not prevent other services from shutting down + pengine: Bug lf#2422 - Ordering dependencies on partially active groups not observed properly + pengine: Bug lf#2424 - Use notify oepration definition if it exists in the configuration + pengine: Bug lf#2433 - No services should be stopped until probes finish + pengine: Bug lf#2453 - Enforce clone ordering in the absense of colocation constraints + pengine: Bug lf#2476 - Repair on-fail=block for groups and primitive resources + pengine: Correctly detect when there is a real failcount that expired and needs to be cleared + pengine: Correctly handle pseudo action creation + pengine: Correctly order clone startup after group/clone start + pengine: Correct use-after-free introduced in the prior patch + pengine: Do not demote resources because something that requires it can not run + pengine: Fix colocation for interleaved clones + pengine: Fix colocation with partially active groups + pengine: Fix potential use-after-free defect from coverity + pengine: Fix previous merge + pengine: Fix use-after-free in order_actions() reported by valgrind + pengine: Make the current data set a global variable so it does not need to be passed around everywhere + pengine: Prevent endless loop when looking for operation definitions in the configuration + pengine: Prevent segfault by ensuring the arguments to do_calculations() are initialized + pengine: Rewrite the ordering constraint logic to be simplicity, clarity and maintainability + pengine: Wait until stonith is available, do not fall back to shutdown for nodes requesting termination + Resolve coverity RESOURCE_LEAK defects + Shell: Complete the transition to using crm_attribute instead of crm_failcount and crm_standby + stonith: Advertise stonith-ng options in the metadata + stonith: Bug lf#2461 - Prevent segfault by not looking up operations if the hashtable has not been initialized yet + stonith: Bug lf#2473 - Add the timeout at the top level where the daemon is looking for it + Stonith: Bug lf#2473 - Ensure stonith operations complete within the timeout and are terminated if they run too long + stonith: Bug lf#2473 - Ensure timeouts are included for fencing operations + stonith: Bug lf#2473 - Gracefully handle remote operations that arrive late (after we have done notifications) + stonith: Correctly parse pcmk_host_list parameters that appear on a single line + stonith: Map poweron/poweroff back to on/off expected by the stonith tool from cluster-glue + stonith: pass the configuration to the stonith program via environment variables (bnc#620781) + Stonith: Use the timeout specified by the user + Support starting plugin-based Pacemaker clusters with the MCP as well + Tools: Bug lf#2456 - Fix assertion failure in crm_resource + tools: crm_node - Repair the ability to connect to openais based clusters + tools: crm_node - Use the correct short option for --cman + tools: crm_report - corosync.conf wont necessarily contain the text 'pacemaker' anymore + Tools: crm_simulate - Fix use-after-free in when terminating + tools: crm_simulate - Resolve coverity USE_AFTER_FREE defect + Tools: Drop the 'pingd' daemon and resource agent in favor of ocf:pacemaker:ping + Tools: Fix recently introduced use-of-NULL + Tools: Fix use-after-free defects from coverity * Wed May 12 2010 Andrew Beekhof 1.1.2-1 - Update source tarball to revision: c25c972a25cc tip - Statistics: Changesets: 339 Diff: 708 files changed, 37918 insertions(+), 10584 deletions(-) - Changes since Pacemaker-1.1.1 + ais: Do not count votes from offline nodes and calculate current votes before sending quorum data + ais: Ensure the list of active processes sent to clients is always up-to-date + ais: Look for the correct conf variable for turning on file logging + ais: Need to find a better and thread-safe way to set core_uses_pid. Disable for now. + ais: Use the threadsafe version of getpwnam + Core: Bump the feature set due to the new failcount expiry feature + Core: fix memory leaks exposed by valgrind + Core: Bug lf#2414 - Prevent use-after-free reported by valgrind when doing xpath based deletions + crmd: Bug lf#2414 - Prevent use-after-free of the PE connection after it dies + crmd: Bug lf#2414 - Prevent use-after-free of the stonith-ng connection + crmd: Bug lf#2401 - Improved detection of partially active peers + crmd: Bug lf#2379 - Ensure the cluster terminates when the PE is not available + crmd: Do not allow the target_rc to be misused by resource agents + crmd: Do not ignore action timeouts based on FSA state + crmd: Ensure we don't get stuck in S_PENDING if we lose an election to someone that never talks to us again + crmd: Fix memory leaks exposed by valgrind + crmd: Remove race condition that could lead to multiple instances of a clone being active on a machine + crmd: Send erase_status_tag() calls to the local CIB when the DC is fenced, since there is no DC to accept them + crmd: Use global fencing notifications to prevent secondary fencing operations of the DC + pengine: Bug lf#2317 - Avoid needless restart of primitive depending on a clone + pengine: Bug lf#2361 - Ensure clones observe mandatory ordering constraints if the LHS is unrunnable + pengine: Bug lf#2383 - Combine failcounts for all instances of an anonymous clone on a host + pengine: Bug lf#2384 - Fix intra-set colocation and ordering + pengine: Bug lf#2403 - Enforce mandatory promotion (colocation) constraints + pengine: Bug lf#2412 - Correctly find clone instances by their prefix + pengine: Do not be so quick to pull the trigger on nodes that are coming up + pengine: Fix memory leaks exposed by valgrind + pengine: Rewrite native_merge_weights() to avoid Fix use-after-free + Shell: Bug bnc#590035 - always reload status if working with the cluster + Shell: Bug bnc#592762 - Default to using the status section from the live CIB + Shell: Bug lf#2315 - edit multiple meta_attributes sets in resource management + Shell: Bug lf#2221 - enable comments + Shell: Bug bnc#580492 - implement new cibstatus interface and commands + Shell: Bug bnc#585471 - new cibstatus import command + Shell: check timeouts also against the default-action-timeout property + Shell: new configure filter command + Tools: crm_mon - fix memory leaks exposed by valgrind * Tue Feb 16 2010 Andrew Beekhof - 1.1.1-1 - First public release of Pacemaker 1.1 - Package reference documentation in a doc subpackage - Move cts into a subpackage so that it can be easily consumed by others - Update source tarball to revision: 17d9cd4ee29f + New stonith daemon that supports global notifications + Service placement influenced by the physical resources + A new tool for simulating failures and the cluster’s reaction to them + Ability to serialize an otherwise unrelated a set of resource actions (eg. Xen migrations) * Mon Jan 18 2010 Andrew Beekhof - 1.0.7-1 - Update source tarball to revision: 2eed906f43e9 (stable-1.0) tip - Statistics: Changesets: 193 Diff: 220 files changed, 15933 insertions(+), 8782 deletions(-) - Changes since 1.0.5-4 + pengine: Bug 2213 - Ensure groups process location constraints so that clone-node-max works for cloned groups + pengine: Bug lf#2153 - non-clones should not restart when clones stop/start on other nodes + pengine: Bug lf#2209 - Clone ordering should be able to prevent startup of dependent clones + pengine: Bug lf#2216 - Correctly identify the state of anonymous clones when deciding when to probe + pengine: Bug lf#2225 - Operations that require fencing should wait for 'stonith_complete' not 'all_stopped'. + pengine: Bug lf#2225 - Prevent clone peers from stopping while another is instance is (potentially) being fenced + pengine: Correctly anti-colocate with a group + pengine: Correctly unpack ordering constraints for resource sets to avoid graph loops + Tools: crm: load help from crm_cli.txt + Tools: crm: resource sets (bnc#550923) + Tools: crm: support for comments (LF 2221) + Tools: crm: support for description attribute in resources/operations (bnc#548690) + Tools: hb2openais: add EVMS2 CSM processing (and other changes) (bnc#548093) + Tools: hb2openais: do not allow empty rules, clones, or groups (LF 2215) + Tools: hb2openais: refuse to convert pure EVMS volumes + cib: Ensure the loop for login message terminates + cib: Finally fix reliability of receiving large messages over remote plaintext connections + cib: Fix remote notifications + cib: For remote connections, default to CRM_DAEMON_USER since thats the only one that the cib can validate the password for using PAM + cib: Remote plaintext - Retry sending parts of the message that did not fit the first time + crmd: Ensure batch-limit is correctly enforced + crmd: Ensure we have the latest status after a transition abort + (bnc#547579,547582): Tools: crm: status section editing support + shell: Add allow-migrate as allowed meta-attribute (bnc#539968) + Medium: Build: Do not automatically add -L/lib, it could cause 64-bit arches to break + Medium: pengine: Bug lf#2206 - rsc_order constraints always use score at the top level + Medium: pengine: Only complain about target-role=master for non m/s resources + Medium: pengine: Prevent non-multistate resources from being promoted through target-role + Medium: pengine: Provide a default action for resource-set ordering + Medium: pengine: Silently fix requires=fencing for stonith resources so that it can be set in op_defaults + Medium: Tools: Bug lf#2286 - Allow the shell to accept template parameters on the command line + Medium: Tools: Bug lf#2307 - Provide a way to determin the nodeid of past cluster members + Medium: Tools: crm: add update method to template apply (LF 2289) + Medium: Tools: crm: direct RA interface for ocf class resource agents (LF 2270) + Medium: Tools: crm: direct RA interface for stonith class resource agents (LF 2270) + Medium: Tools: crm: do not add score which does not exist + Medium: Tools: crm: do not consider warnings as errors (LF 2274) + Medium: Tools: crm: do not remove sets which contain id-ref attribute (LF 2304) + Medium: Tools: crm: drop empty attributes elements + Medium: Tools: crm: exclude locations when testing for pathological constraints (LF 2300) + Medium: Tools: crm: fix exit code on single shot commands + Medium: Tools: crm: fix node delete (LF 2305) + Medium: Tools: crm: implement -F (--force) option + Medium: Tools: crm: rename status to cibstatus (LF 2236) + Medium: Tools: crm: revisit configure commit + Medium: Tools: crm: stay in crm if user specified level only (LF 2286) + Medium: Tools: crm: verify changes on exit from the configure level + Medium: ais: Some clients such as gfs_controld want a cluster name, allow one to be specified in corosync.conf + Medium: cib: Clean up logic for receiving remote messages + Medium: cib: Create valid notification control messages + Medium: cib: Indicate where the remote connection came from + Medium: cib: Send password prompt to stderr so that stdout can be redirected + Medium: cts: Fix rsh handling when stdout is not required + Medium: doc: Fill in the section on removing a node from an AIS-based cluster + Medium: doc: Update the docs to reflect the 0.6/1.0 rolling upgrade problem + Medium: doc: Use Publican for docbook based documentation + Medium: fencing: stonithd: add metadata for stonithd instance attributes (and support in the shell) + Medium: fencing: stonithd: ignore case when comparing host names (LF 2292) + Medium: tools: Make crm_mon functional with remote connections + Medium: xml: Add stopped as a supported role for operations + Medium: xml: Bug bnc#552713 - Treat node unames as text fields not IDs + Medium: xml: Bug lf#2215 - Create an always-true expression for empty rules when upgrading from 0.6 * Thu Oct 29 2009 Andrew Beekhof - 1.0.5-4 - Include the fixes from CoroSync integration testing - Move the resource templates - they are not documentation - Ensure documentation is placed in a standard location - Exclude documentation that is included elsewhere in the package - Update the tarball from upstream to version ee19d8e83c2a + cib: Correctly clean up when both plaintext and tls remote ports are requested + pengine: Bug bnc#515172 - Provide better defaults for lt(e) and gt(e) comparisions + pengine: Bug lf#2197 - Allow master instances placemaker to be influenced by colocation constraints + pengine: Make sure promote/demote pseudo actions are created correctly + pengine: Prevent target-role from promoting more than master-max instances + ais: Bug lf#2199 - Prevent expected-quorum-votes from being populated with garbage + ais: Prevent deadlock - don't try to release IPC message if the connection failed + cib: For validation errors, send back the full CIB so the client can display the errors + cib: Prevent use-after-free for remote plaintext connections + crmd: Bug lf#2201 - Prevent use-of-NULL when running heartbeat * Wed Oct 13 2009 Andrew Beekhof - 1.0.5-3 - Update the tarball from upstream to version 38cd629e5c3c + Core: Bug lf#2169 - Allow dtd/schema validation to be disabled + pengine: Bug lf#2106 - Not all anonymous clone children are restarted after configuration change + pengine: Bug lf#2170 - stop-all-resources option had no effect + pengine: Bug lf#2171 - Prevent groups from starting if they depend on a complex resource which can not + pengine: Disable resource management if stonith-enabled=true and no stonith resources are defined + pengine: do not include master score if it would prevent allocation + ais: Avoid excessive load by checking for dead children every 1s (instead of 100ms) + ais: Bug rh#525589 - Prevent shutdown deadlocks when running on CoroSync + ais: Gracefully handle changes to the AIS nodeid + crmd: Bug bnc#527530 - Wait for the transition to complete before leaving S_TRANSITION_ENGINE + crmd: Prevent use-after-free with LOG_DEBUG_3 + Medium: xml: Mask the "symmetrical" attribute on rsc_colocation constraints (bnc#540672) + Medium (bnc#520707): Tools: crm: new templates ocfs2 and clvm + Medium: Build: Invert the disable ais/heartbeat logic so that --without (ais|heartbeat) is available to rpmbuild + Medium: pengine: Bug lf#2178 - Indicate unmanaged clones + Medium: pengine: Bug lf#2180 - Include node information for all failed ops + Medium: pengine: Bug lf#2189 - Incorrect error message when unpacking simple ordering constraint + Medium: pengine: Correctly log resources that would like to start but can not + Medium: pengine: Stop ptest from logging to syslog + Medium: ais: Include version details in plugin name + Medium: crmd: Requery the resource metadata after every start operation * Fri Aug 21 2009 Tomas Mraz - 1.0.5-2.1 - rebuilt with new openssl * Wed Aug 19 2009 Andrew Beekhof - 1.0.5-2 - Add versioned perl dependency as specified by https://fedoraproject.org/wiki/Packaging/Perl#Packages_that_link_to_libperl - No longer remove RPATH data, it prevents us finding libperl.so and no other libraries were being hardcoded - Compile in support for heartbeat - Conditionally add heartbeat-devel and corosynclib-devel to the -devel requirements depending on which stacks are supported * Mon Aug 17 2009 Andrew Beekhof - 1.0.5-1 - Add dependency on resource-agents - Use the version of the configure macro that supplies --prefix, --libdir, etc - Update the tarball from upstream to version 462f1569a437 (Pacemaker 1.0.5 final) + Tools: crm_resource - Advertise --move instead of --migrate + Medium: Extra: New node connectivity RA that uses system ping and attrd_updater + Medium: crmd: Note that dc-deadtime can be used to mask the brokeness of some switches * Tue Aug 11 2009 Ville Skyttä - 1.0.5-0.7.c9120a53a6ae.hg - Use bzipped upstream tarball. * Wed Jul 29 2009 Andrew Beekhof - 1.0.5-0.6.c9120a53a6ae.hg - Add back missing build auto* dependencies - Minor cleanups to the install directive * Tue Jul 28 2009 Andrew Beekhof - 1.0.5-0.5.c9120a53a6ae.hg - Add a leading zero to the revision when alphatag is used * Tue Jul 28 2009 Andrew Beekhof - 1.0.5-0.4.c9120a53a6ae.hg - Incorporate the feedback from the cluster-glue review - Realistically, the version is a 1.0.5 pre-release - Use the global directive instead of define for variables - Use the haclient/hacluster group/user instead of daemon - Use the _configure macro - Fix install dependencies * Fri Jul 24 2009 Andrew Beekhof - 1.0.4-3 - Initial Fedora checkin - Include an AUTHORS and license file in each package - Change the library package name to pacemaker-libs to be more Fedora compliant - Remove execute permissions from xml related files - Reference the new cluster-glue devel package name - Update the tarball from upstream to version c9120a53a6ae + pengine: Only prevent migration if the clone dependency is stopping/starting on the target node + pengine: Bug 2160 - Don't shuffle clones due to colocation + pengine: New implementation of the resource migration (not stop/start) logic + Medium: Tools: crm_resource - Prevent use-of-NULL by requiring a resource name for the -A and -a options + Medium: pengine: Prevent use-of-NULL in find_first_action() * Tue Jul 14 2009 Andrew Beekhof - 1.0.4-2 - Reference authors from the project AUTHORS file instead of listing in description - Change Source0 to reference the Mercurial repo - Cleaned up the summaries and descriptions - Incorporate the results of Fedora package self-review * Thu Jun 04 2009 Andrew Beekhof - 1.0.4-1 - Update source tarball to revision: 1d87d3e0fc7f (stable-1.0) - Statistics: Changesets: 209 Diff: 266 files changed, 12010 insertions(+), 8276 deletions(-) - Changes since Pacemaker-1.0.3 + (bnc#488291): ais: do not rely on byte endianness on ptr cast + (bnc#507255): Tools: crm: delete rsc/op_defaults (these meta_attributes are killing me) + (bnc#507255): Tools: crm: import properly rsc/op_defaults + (LF 2114): Tools: crm: add support for operation instance attributes + ais: Bug lf#2126 - Messages replies cannot be routed to transient clients + ais: Fix compilation for the latest Corosync API (v1719) + attrd: Do not perform all updates as complete refreshes + cib: Fix huge memory leak affecting heartbeat-based clusters + Core: Allow xpath queries to match attributes + Core: Generate the help text directly from a tool options struct + Core: Handle differences in 0.6 messaging format + crmd: Bug lf#2120 - All transient node attribute updates need to go via attrd + crmd: Correctly calculate how long an FSA action took to avoid spamming the logs with errors + crmd: Fix another large memory leak affecting Heartbeat based clusters + lha: Restore compatibility with older versions + pengine: Bug bnc#495687 - Filesystem is not notified of successful STONITH under some conditions + pengine: Make running a cluster with STONITH enabled but no STONITH resources an error and provide details on resolutions + pengine: Prevent use-ofNULL when using resource ordering sets + pengine: Provide inter-notification ordering guarantees + pengine: Rewrite the notification code to be understanable and extendable + Tools: attrd - Prevent race condition resulting in the cluster forgetting the node wishes to shut down + Tools: crm: regression tests + Tools: crm_mon - Fix smtp notifications + Tools: crm_resource - Repair the ability to query meta attributes + Low Build: Bug lf#2105 - Debian package should contain pacemaker doc and crm templates + Medium (bnc#507255): Tools: crm: handle empty rsc/op_defaults properly + Medium (bnc#507255): Tools: crm: use the right obj_type when creating objects from xml nodes + Medium (LF 2107): Tools: crm: revisit exit codes in configure + Medium: cib: Do not bother validating updates that only affect the status section + Medium: Core: Include supported stacks in version information + Medium: crmd: Record in the CIB, the cluster infrastructure being used + Medium: cts: Do not combine crm_standby arguments - the wrapper can not process them + Medium: cts: Fix the CIBAusdit class + Medium: Extra: Refresh showscores script from Dominik + Medium: pengine: Build a statically linked version of ptest + Medium: pengine: Correctly log the actions for resources that are being recovered + Medium: pengine: Correctly log the occurrence of promotion events + Medium: pengine: Implememt node health based on a patch from Mark Hamzy + Medium: Tools: Add examples to help text outputs + Medium: Tools: crm: catch syntax errors for configure load + Medium: Tools: crm: implement erasing nodes in configure erase + Medium: Tools: crm: work with parents only when managing xml objects + Medium: Tools: crm_mon - Add option to run custom notification program on resource operations (Patch by Dominik Klein) + Medium: Tools: crm_resource - Allow --cleanup to function on complex resources and cluster-wide + Medium: Tools: haresource2cib.py - Patch from horms to fix conversion error + Medium: Tools: Include stack information in crm_mon output + Medium: Tools: Two new options (--stack,--constraints) to crm_resource for querying how a resource is configured * Wed Apr 08 2009 Andrew Beekhof - 1.0.3-1 - Update source tarball to revision: b133b3f19797 (stable-1.0) tip - Statistics: Changesets: 383 Diff: 329 files changed, 15471 insertions(+), 15119 deletions(-) - Changes since Pacemaker-1.0.2 + Added tag SLE11-HAE-GMC for changeset 9196be9830c2 + ais plugin: Fix quorum calculation (bnc#487003) + ais: Another memory fix leak in error path + ais: Bug bnc#482847, bnc#482905 - Force a clean exit of OpenAIS once Pacemaker has finished unloading + ais: Bug bnc#486858 - Fix update_member() to prevent spamming clients with membership events containing no changes + ais: Centralize all quorum calculations in the ais plugin and allow expected votes to be configured int he cib + ais: Correctly handle a return value of zero from openais_dispatch_recv() + ais: Disable logging to a file + ais: Fix memory leak in error path + ais: IPC messages are only in scope until a response is sent + All signal handlers used with CL_SIGNAL() need to be as minimal as possible + cib: Bug bnc#482885 - Simplify CIB disk-writes to prevent data loss. Required a change to the backup filename format + cib: crmd: Revert part of 9782ab035003. Complex shutdown routines need G_main_add_SignalHandler to avoid race coditions + crm: Avoid infinite loop during crm configure edit (bnc#480327) + crmd: Avoid a race condition by waiting for the attrd update to trigger a transition automatically + crmd: Bug bnc#480977 - Prevent extra, partial, shutdown when a node restarts too quickly + crmd: Bug bnc#480977 - Prevent extra, partial, shutdown when a node restarts too quickly (verified) + crmd: Bug bnc#489063 - Ensure the DC is always unset after we 'lose' an election + crmd: Bug BSC#479543 - Correctly find the migration source for timed out migrate_from actions + crmd: Call crm_peer_init() before we start the FSA - prevents a race condition when used with Heartbeat + crmd: Erasing the status section should not be forced to the local node + crmd: Fix memory leak in cib notication processing code + crmd: Fix memory leak in transition graph processing + crmd: Fix memory leaks found by valgrind + crmd: More memory leaks fixes found by valgrind + fencing: stonithd: is_heartbeat_cluster is a no-no if there is no heartbeat support + pengine: Bug bnc#466788 - Exclude nodes that can not run resources + pengine: Bug bnc#466788 - Make colocation based on node attributes work + pengine: Bug BNC#478687 - Do not crash when clone-max is 0 + pengine: Bug bnc#488721 - Fix id-ref expansion for clones, the doc-root for clone children is not the cib root + pengine: Bug bnc#490418 - Correctly determine node state for nodes wishing to be terminated + pengine: Bug LF#2087 - Correctly parse the state of anonymous clones that have multiple instances on a given node + pengine: Bug lf#2089 - Meta attributes are not inherited by clone children + pengine: Bug lf#2091 - Correctly restart modified resources that were found active by a probe + pengine: Bug lf#2094 - Fix probe ordering for cloned groups + pengine: Bug LF:2075 - Fix large pingd memory leaks + pengine: Correctly attach orphaned clone children to their parent + pengine: Correctly handle terminate node attributes that are set to the output from time() + pengine: Ensure orphaned clone members are hooked up to the parent when clone-max=0 + pengine: Fix memory leak in LogActions + pengine: Fix the determination of whether a group is active + pengine: Look up the correct promotion preference for anonymous masters + pengine: Simplify handling of start failures by changing the default migration-threshold to INFINITY + pengine: The ordered option for clones no longer causes extra start/stop operations + RA: Bug bnc#490641 - Shut down dlm_controld with -TERM instead of -KILL + RA: pingd: Set default ping interval to 1 instead of 0 seconds + Resources: pingd - Correctly tell the ping daemon to shut down + Tools: Bug bnc#483365 - Ensure the command from cluster_test includes a value for --log-facility + Tools: cli: fix and improve delete command + Tools: crm: add and implement templates + Tools: crm: add support for command aliases and some common commands (i.e. cd,exit) + Tools: crm: create top configuration nodes if they are missing + Tools: crm: fix parsing attributes for rules (broken by the previous changeset) + Tools: crm: new ra set of commands + Tools: crm: resource agents information management + Tools: crm: rsc/op_defaults + Tools: crm: support for no value attribute in nvpairs + Tools: crm: the new configure monitor command + Tools: crm: the new configure node command + Tools: crm_mon - Prevent use-of-NULL when summarizing an orphan + Tools: hb2openais: create clvmd clone for respawn evmsd in ha.cf + Tools: hb2openais: fix a serious recursion bug in xml node processing + Tools: hb2openais: fix ocfs2 processing + Tools: pingd - prevent double free of getaddrinfo() output in error path + Tools: The default re-ping interval for pingd should be 1s not 1ms + Medium (bnc#479049): Tools: crm: add validation of resource type for the configure primitive command + Medium (bnc#479050): Tools: crm: add help for RA parameters in tab completion + Medium (bnc#479050): Tools: crm: add tab completion for primitive params/meta/op + Medium (bnc#479050): Tools: crm: reimplement cluster properties completion + Medium (bnc#486968): Tools: crm: listnodes function requires no parameters (do not mix completion with other stuff) + Medium: ais: Remove the ugly hack for dampening AIS membership changes + Medium: cib: Fix memory leaks by using mainloop_add_signal + Medium: cib: Move more logging to the debug level (was info) + Medium: cib: Overhaul the processing of synchronous replies + Medium: Core: Add library functions for instructing the cluster to terminate nodes + Medium: crmd: Add new expected-quorum-votes option + Medium: crmd: Allow up to 5 retires when an attrd update fails + Medium: crmd: Automatically detect and use new values for crm_config options + Medium: crmd: Bug bnc#490426 - Escalated shutdowns stall when there are pending resource operations + Medium: crmd: Clean up and optimize the DC election algorithm + Medium: crmd: Fix memory leak in shutdown + Medium: crmd: Fix memory leaks spotted by Valgrind + Medium: crmd: Ignore join messages from hosts other than our DC + Medium: crmd: Limit the scope of resource updates to the status section + Medium: crmd: Prevent the crmd from being respawned if its told to shut down when it did not ask to be + Medium: crmd: Re-check the election status after membership events + Medium: crmd: Send resource updates via the local CIB during elections + Medium: pengine: Bug bnc#491441 - crm_mon does not display operations returning 'uninstalled' correctly + Medium: pengine: Bug lf#2101 - For location constraints, role=Slave is equivalent to role=Started + Medium: pengine: Clean up the API - removed ->children() and renamed ->find_child() to fine_rsc() + Medium: pengine: Compress the display of healthy anonymous clones + Medium: pengine: Correctly log the actions for resources that are being recovered + Medium: pengine: Determin a promotion score for complex resources + Medium: pengine: Ensure clones always have a value for globally-unique + Medium: pengine: Prevent orphan clones from being allocated + Medium: RA: controld: Return proper exit code for stop op. + Medium: Tools: Bug bnc#482558 - Fix logging test in cluster_test + Medium: Tools: Bug bnc#482828 - Fix quoting in cluster_test logging setup + Medium: Tools: Bug bnc#482840 - Include directory path to CTSlab.py + Medium: Tools: crm: add more user input checks + Medium: Tools: crm: do not check resource status of we are working with a shadow + Medium: Tools: crm: fix id-refs and allow reference to top objects (i.e. primitive) + Medium: Tools: crm: ignore comments in the CIB + Medium: Tools: crm: multiple column output would not work with small lists + Medium: Tools: crm: refuse to delete running resources + Medium: Tools: crm: rudimentary if-else for templates + Medium: Tools: crm: Start/stop clones via target-role. + Medium: Tools: crm_mon - Compress the node status for healthy and offline nodes + Medium: Tools: crm_shadow - Return 0/cib_ok when --create-empty succeeds + Medium: Tools: crm_shadow - Support -e, the short form of --create-empty + Medium: Tools: Make attrd quieter + Medium: Tools: pingd - Avoid using various clplumbing functions as they seem to leak + Medium: Tools: Reduce pingd logging * Mon Feb 16 2009 Andrew Beekhof - 1.0.2-1 - Update source tarball to revision: d232d19daeb9 (stable-1.0) tip - Statistics: Changesets: 441 Diff: 639 files changed, 20871 insertions(+), 21594 deletions(-) - Changes since Pacemaker-1.0.1 + (bnc#450815): Tools: crm cli: do not generate id for the operations tag + ais: Add support for the new AIS IPC layer + ais: Always set header.error to the correct default: SA_AIS_OK + ais: Bug BNC#456243 - Ensure the membership cache always contains an entry for the local node + ais: Bug BNC:456208 - Prevent deadlocks by not logging in the child process before exec() + ais: By default, disable supprt for the WIP openais IPC patch + ais: Detect and handle situations where ais and the crm disagree on the node name + ais: Ensure crm_peer_seq is updated after a membership update + ais: Make sure all IPC header fields are set to sane defaults + ais: Repair and streamline service load now that whitetank startup functions correctly + build: create and install doc files + cib: Allow clients without mainloop to connect to the cib + cib: CID:18 - Fix use-of-NULL in cib_perform_op + cib: CID:18 - Repair errors introduced in b5a18704477b - Fix use-of-NULL in cib_perform_op + cib: Ensure diffs contain the correct values of admin_epoch + cib: Fix four moderately sized memory leaks detected by Valgrind + Core: CID:10 - Prevent indexing into an array of schemas with a negative value + Core: CID:13 - Fix memory leak in log_data_element + Core: CID:15 - Fix memory leak in crm_get_peer + Core: CID:6 - Fix use-of-NULL in copy_ha_msg_input + Core: Fix crash in the membership code preventing node shutdown + Core: Fix more memory leaks foudn by valgrind + Core: Prevent unterminated strings after decompression + crmd: Bug BNC:467995 - Delay marking STONITH operations complete until STONITH tells us so + crmd: Bug LF:1962 - Do not NACK peers because they are not (yet) in our membership. Just ignore them. + crmd: Bug LF:2010 - Ensure fencing cib updates create the node_state entry if needed to preent re-fencing during cluster startup + crmd: Correctly handle reconnections to attrd + crmd: Ensure updates for lost migrate operations indicate which node it tried to migrating to + crmd: If there are no nodes to finalize, start an election. + crmd: If there are no nodes to welcome, start an election. + crmd: Prevent node attribute loss by detecting attrd disconnections immediately + crmd: Prevent node re-probe loops by ensuring mandatory actions always complete + pengine: Bug 2005 - Fix startup ordering of cloned stonith groups + pengine: Bug 2006 - Correctly reprobe cloned groups + pengine: Bug BNC:465484 - Fix the no-quorum-policy=suicide option + pengine: Bug LF:1996 - Correctly process disabled monitor operations + pengine: CID:19 - Fix use-of-NULL in determine_online_status + pengine: Clones now default to globally-unique=false + pengine: Correctly calculate the number of available nodes for the clone to use + pengine: Only shoot online nodes with no-quorum-policy=suicide + pengine: Prevent on-fail settings being ignored after a resource is successfully stopped + pengine: Prevent use-of-NULL for failed migrate actions in process_rsc_state() + pengine: Remove an optimization for the terminate node attribute that caused the cluster to block indefinitly + pengine: Repar the ability to colocate based on node attributes other than uname + pengine: Start the correct monitor operation for unmanaged masters + stonith: CID:3 - Fix another case of exceptionally poor error handling by the original stonith developers + stonith: CID:5 - Checking for NULL and then dereferencing it anyway is an interesting approach to error handling + stonithd: Sending IPC to the cluster is a privileged operation + stonithd: wrong checks for shmid (0 is a valid id) + Tools: attrd - Correctly determine when an attribute has stopped changing and should be committed to the CIB + Tools: Bug 2003 - pingd does not correctly detect failures when the interface is down + Tools: Bug 2003 - pingd does not correctly handle node-down events on multi-NIC systems + Tools: Bug 2021 - pingd does not detect sequence wrapping correctly, incorrectly reports nodes offline + Tools: Bug BNC:468066 - Do not use the result of uname() when its no longer in scope + Tools: Bug BNC:473265 - crm_resource -L dumps core + Tools: Bug LF:2001 - Transient node attributes should be set via attrd + Tools: Bug LF:2036 - crm_resource cannot set/get parameters for cloned resources + Tools: Bug LF:2046 - Node attribute updates are lost because attrd can take too long to start + Tools: Cause the correct clone instance to be failed with crm_resource -F + Tools: cluster_test - Allow the user to select a stack and fix CTS invocation + Tools: crm cli: allow rename only if the resource is stopped + Tools: crm cli: catch system errors on file operations + Tools: crm cli: completion for ids in configure + Tools: crm cli: drop '-rsc' from attributes for order constraint + Tools: crm cli: exit with an appropriate exit code + Tools: crm cli: fix wrong order of action and resource in order constraint + Tools: crm cli: fox wrong exit code + Tools: crm cli: improve handling of cib attributes + Tools: crm cli: new command: configure rename + Tools: crm cli: new command: configure upgrade + Tools: crm cli: new command: node delete + Tools: crm cli: prevent key errors on missing cib attributes + Tools: crm cli: print long help for help topics + Tools: crm cli: return on syntax error when parsing score + Tools: crm cli: rsc_location can be without nvpairs + Tools: crm cli: short node preference location constraint + Tools: crm cli: sometimes, on errors, level would change on single shot use + Tools: crm cli: syntax: drop a bunch of commas (remains of help tables conversion) + Tools: crm cli: verify user input for sanity + Tools: crm: find expressions within rules (do not always skip xml nodes due to used id) + Tools: crm_master should not define a set id now that attrd is used. Defining one can break lookups + Tools: crm_mon Use the OID assigned to the project by IANA for SNMP traps + Medium (bnc#445622): Tools: crm cli: improve the node show command and drop node status + Medium (LF 2009): stonithd: improve timeouts for remote fencing + Medium: ais: Allow dead peers to be removed from membership calculations + Medium: ais: Pass node deletion events on to clients + Medium: ais: Sanitize ipc usage + Medium: ais: Supply the node uname in addtion to the id + Medium: Build: Clean up configure to ensure NON_FATAL_CFLAGS is consistent with CFLAGS (ie. includes -g) + Medium: Build: Install cluster_test + Medium: Build: Use more restrictive CFLAGS and fix the resulting errors + Medium: cib: CID:20 - Fix potential use-after-free in cib_native_signon + Medium: Core: Bug BNC:474727 - Set a maximum time to wait for IPC messages + Medium: Core: CID:12 - Fix memory leak in decode_transition_magic error path + Medium: Core: CID:14 - Fix memory leak in calculate_xml_digest error path + Medium: Core: CID:16 - Fix memory leak in date_to_string error path + Medium: Core: Try to track down the cause of XML parsing errors + Medium: crmd: Bug BNC:472473 - Do not wait excessive amounts of time for lost actions + Medium: crmd: Bug BNC:472473 - Reduce the transition timeout to action_timeout+network_delay + Medium: crmd: Do not fast-track the processing of LRM refreshes when there are pending actions. + Medium: crmd: do_dc_join_filter_offer - Check the 'join' message is for the current instance before deciding to NACK peers + Medium: crmd: Find option values without having to do a config upgrade + Medium: crmd: Implement shutdown using a transient node attribute + Medium: crmd: Update the crmd options to use dashes instead of underscores + Medium: cts: Add 'cluster reattach' to the suite of automated regression tests + Medium: cts: cluster_test - Make some usability enhancements + Medium: CTS: cluster_test - suggest a valid port number + Medium: CTS: Fix python import order + Medium: cts: Implement an automated SplitBrain test + Medium: CTS: Remove references to deleted classes + Medium: Extra: Resources - Use HA_VARRUN instead of HA_RSCTMP for state files as Heartbeat removes HA_RSCTMP at startup + Medium: HB: Bug 1933 - Fake crmd_client_status_callback() calls because HB does not provide them for already running processes + Medium: pengine: CID:17 - Fix memory leak in find_actions_by_task error path + Medium: pengine: CID:7,8 - Prevent hypothetical use-of-NULL in LogActions + Medium: pengine: Defer logging the actions performed on a resource until we have processed ordering constraints + Medium: pengine: Remove the symmetrical attribute of colocation constraints + Medium: Resources: pingd - fix the meta defaults + Medium: Resources: Stateful - Add missing meta defaults + Medium: stonithd: exit if we the pid file cannot be locked + Medium: Tools: Allow attrd clients to specify the ID the attribute should be created with + Medium: Tools: attrd - Allow attribute updates to be performed from a hosts peer + Medium: Tools: Bug LF:1994 - Clean up crm_verify return codes + Medium: Tools: Change the pingd defaults to ping hosts once every second (instead of 5 times every 10 seconds) + Medium: Tools: cibmin - Detect resource operations with a view to providing email/snmp/cim notification + Medium: Tools: crm cli: add back symmetrical for order constraints + Medium: Tools: crm cli: generate role in location when converting from xml + Medium: Tools: crm cli: handle shlex exceptions + Medium: Tools: crm cli: keep order of help topics + Medium: Tools: crm cli: refine completion for ids in configure + Medium: Tools: crm cli: replace inf with INFINITY + Medium: Tools: crm cli: streamline cib load and parsing + Medium: Tools: crm cli: supply provider only for ocf class primitives + Medium: Tools: crm_mon - Add support for sending mail notifications of resource events + Medium: Tools: crm_mon - Include the DC version in status summary + Medium: Tools: crm_mon - Sanitize startup and option processing + Medium: Tools: crm_mon - switch to event-driven updates and add support for sending snmp traps + Medium: Tools: crm_shadow - Replace the --locate option with the saner --edit + Medium: Tools: hb2openais: do not remove Evmsd resources, but replace them with clvmd + Medium: Tools: hb2openais: replace crmadmin with crm_mon + Medium: Tools: hb2openais: replace the lsb class with ocf for o2cb + Medium: Tools: hb2openais: reuse code + Medium: Tools: LF:2029 - Display an error if crm_resource is used to reset the operation history of non-primitive resources + Medium: Tools: Make pingd resilient to attrd failures + Medium: Tools: pingd - fix the command line switches + Medium: Tools: Rename ccm_tool to crm_node * Tue Nov 18 2008 Andrew Beekhof - 1.0.1-1 - Update source tarball to revision: 6fc5ce8302ab (stable-1.0) tip - Statistics: Changesets: 170 Diff: 816 files changed, 7633 insertions(+), 6286 deletions(-) - Changes since Pacemaker-1.0.1 + ais: Allow the crmd to get callbacks whenever a node state changes + ais: Create an option for starting the mgmtd daemon automatically + ais: Ensure HA_RSCTMP exists for use by resource agents + ais: Hook up the openais.conf config logging options + ais: Zero out the PID of disconnecting clients + cib: Ensure global updates cause a disk write when appropriate + Core: Add an extra snaity check to getXpathResults() to prevent segfaults + Core: Do not redefine __FUNCTION__ unnecessarily + Core: Repair the ability to have comments in the configuration + crmd: Bug:1975 - crmd should wait indefinitely for stonith operations to complete + crmd: Ensure PE processing does not occur for all error cases in do_pe_invoke_callback + crmd: Requests to the CIB should cause any prior PE calculations to be ignored + heartbeat: Wait for membership 'up' events before removing stale node status data + pengine: Bug LF:1988 - Ensure recurring operations always have the correct target-rc set + pengine: Bug LF:1988 - For unmanaged resources we need to skip the usual can_run_resources() checks + pengine: Ensure the terminate node attribute is handled correctly + pengine: Fix optional colocation + pengine: Improve up the detection of 'new' nodes joining the cluster + pengine: Prevent assert failures in master_color() by ensuring unmanaged masters are always reallocated to their current location + Tools: crm cli: parser: return False on syntax error and None for comments + Tools: crm cli: unify template and edit commands + Tools: crm_shadow - Show more line number information after validation failures + Tools: hb2openais: add option to upgrade the CIB to v3.0 + Tools: hb2openais: add U option to getopts and update usage + Tools: hb2openais: backup improved and multiple fixes + Tools: hb2openais: fix class/provider reversal + Tools: hb2openais: fix testing + Tools: hb2openais: move the CIB update to the end + Tools: hb2openais: update logging and set logfile appropriately + Tools: LF:1969 - Attrd never sets any properties in the cib + Tools: Make attrd functional on OpenAIS + Medium: ais: Hook up the options for specifying the expected number of nodes and total quorum votes + Medium: ais: Look for pacemaker options inside the service block with 'name: pacemaker' instead of creating an addtional configuration block + Medium: ais: Provide better feedback when nodes change nodeids (in openais.conf) + Medium: cib: Always store cib contents on disk with num_updates=0 + Medium: cib: Ensure remote access ports are cleaned up on shutdown + Medium: crmd: Detect deleted resource operations automatically + Medium: crmd: Erase a nodes resource operations and transient attributes after a successful STONITH + Medium: crmd: Find a more appropriate place to update quorum and refresh attrd attributes + Medium: crmd: Fix the handling of unexpected PE exits to ensure the current CIB is stored + Medium: crmd: Fix the recording of pending operations in the CIB + Medium: crmd: Initiate an attrd refresh _after_ the status section has been fully repopulated + Medium: crmd: Only the DC should update quorum in an openais cluster + Medium: Ensure meta attributes are used consistantly + Medium: pengine: Allow group and clone level resource attributes + Medium: pengine: Bug N:437719 - Ensure scores from colocated resources count when allocating groups + Medium: pengine: Prevent lsb scripts from being used in globally unique clones + Medium: pengine: Make a best-effort guess at a migration threshold for people with 0.6 configs + Medium: Resources: controld - ensure we are part of a clone with globally_unique=false + Medium: Tools: attrd - Automatically refresh all attributes after a CIB replace operation + Medium: Tools: Bug LF:1985 - crm_mon - Correctly process failed cib queries to allow reconnection after cluster restarts + Medium: Tools: Bug LF:1987 - crm_verify incorrectly warns of configuration upgrades for the most recent version + Medium: Tools: crm (bnc#441028): check for key error in attributes management + Medium: Tools: crm_mon - display the meaning of the operation rc code instead of the status + Medium: Tools: crm_mon - Fix the display of timing data + Medium: Tools: crm_verify - check that we are being asked to validate a complete config + Medium: xml: Relax the restriction on the contents of rsc_locaiton.node * Thu Oct 16 2008 Andrew Beekhof - 1.0.0-1 - Update source tarball to revision: 388654dfef8f tip - Statistics: Changesets: 261 Diff: 3021 files changed, 244985 insertions(+), 111596 deletions(-) - Changes since f805e1b30103 + add the crm cli program + ais: Move the service id definition to a common location and make sure it is always used + build: rename hb2openais.sh to .in and replace paths with vars + cib: Implement --create for crm_shadow + cib: Remove dead files + Core: Allow the expected number of quorum votes to be configrable + Core: cl_malloc and friends were removed from Heartbeat + Core: Only call xmlCleanupParser() if we parsed anything. Doing so unconditionally seems to cause a segfault + hb2openais.sh: improve pingd handling; several bugs fixed + hb2openais: fix clone creation; replace EVMS strings + new hb2openais.sh conversion script + pengine: Bug LF:1950 - Ensure the current values for all notification variables are always set (even if empty) + pengine: Bug LF:1955 - Ensure unmanaged masters are unconditionally repromoted to ensure they are monitored correctly. + pengine: Bug LF:1955 - Fix another case of filtering causing unmanaged master failures + pengine: Bug LF:1955 - Umanaged mode prevents master resources from being allocated correctly + pengine: Bug N:420538 - Anit-colocation caused a positive node preference + pengine: Correctly handle unmanaged resources to prevent them from being started elsewhere + pengine: crm_resource - Fix the --migrate command + pengine: MAke stonith-enabled default to true and warn if no STONITH resources are found + pengine: Make sure orphaned clone children are created correctly + pengine: Monitors for unmanaged resources do not need to wait for start/promote/demote actions to complete + stonithd (LF 1951): fix remote stonith operations + stonithd: fix handling of timeouts + stonithd: fix logic for stonith resource priorities + stonithd: implement the fence-timeout instance attribute + stonithd: initialize value before reading fence-timeout + stonithd: set timeouts for fencing ops to the timeout of the start op + stonithd: stonith rsc priorities (new feature) + Tools: Add hb2openais - a tool for upgrading a Heartbeat cluster to use OpenAIS instead + Tools: crm_verify - clean up the upgrade logic to prevent crash on invalid configurations + Tools: Make pingd functional on Linux + Update version numbers for 1.0 candidates + Medium: ais: Add support for a synchronous call to retrieve the nodes nodeid + Medium: ais: Use the agreed service number + Medium: Build: Reliably detect heartbeat libraries during configure + Medium: Build: Supply prototypes for libreplace functions when needed + Medium: Build: Teach configure how to find corosync + Medium: Core: Provide better feedback if Pacemaker is started by a stack it does not support + Medium: crmd: Avoid calling GHashTable functions with NULL + Medium: crmd: Delay raising I_ERROR when the PE exits until we have had a chance to save the current CIB + Medium: crmd: Hook up the stonith-timeout option to stonithd + Medium: crmd: Prevent potential use-of-NULL in global_timer_callback + Medium: crmd: Rationalize the logging of graph aborts + Medium: pengine: Add a stonith_timeout option and remove new options that are better set in rsc_defaults + Medium: pengine: Allow external entities to ask for a node to be shot by creating a terminate=true transient node attribute + Medium: pengine: Bug LF:1950 - Notifications do not contain all documented resource state fields + Medium: pengine: Bug N:417585 - Do not restart group children whos individual score drops below zero + Medium: pengine: Detect clients that disconnect before receiving their reply + Medium: pengine: Implement a true maintenance mode + Medium: pengine: Implement on-fail=standby for NTT. Derived from a patch by Satomi TANIGUCHI + Medium: pengine: Print the correct message when stonith is disabled + Medium: pengine: ptest - check the input is valid before proceeding + Medium: pengine: Revert group stickiness to the 'old way' + Medium: pengine: Use the correct attribute for action 'requires' (was prereq) + Medium: stonithd: Fix compilation without full heartbeat install + Medium: stonithd: exit with better code on empty host list + Medium: tools: Add a new regression test for CLI tools + Medium: tools: crm_resource - return with non-zero when a resource migration command is invalid + Medium: tools: crm_shadow - Allow the admin to start with an empty CIB (and no cluster connection) + Medium: xml: pacemaker-0.7 is now an alias for the 1.0 schema * Mon Sep 22 2008 Andrew Beekhof - 0.7.3-1 - Update source tarball to revision: 33e677ab7764+ tip - Statistics: Changesets: 133 Diff: 89 files changed, 7492 insertions(+), 1125 deletions(-) - Changes since f805e1b30103 + Tools: add the crm cli program + Core: cl_malloc and friends were removed from Heartbeat + Core: Only call xmlCleanupParser() if we parsed anything. Doing so unconditionally seems to cause a segfault + new hb2openais.sh conversion script + pengine: Bug LF:1950 - Ensure the current values for all notification variables are always set (even if empty) + pengine: Bug LF:1955 - Ensure unmanaged masters are unconditionally repromoted to ensure they are monitored correctly. + pengine: Bug LF:1955 - Fix another case of filtering causing unmanaged master failures + pengine: Bug LF:1955 - Umanaged mode prevents master resources from being allocated correctly + pengine: Bug N:420538 - Anit-colocation caused a positive node preference + pengine: Correctly handle unmanaged resources to prevent them from being started elsewhere + pengine: crm_resource - Fix the --migrate command + pengine: MAke stonith-enabled default to true and warn if no STONITH resources are found + pengine: Make sure orphaned clone children are created correctly + pengine: Monitors for unmanaged resources do not need to wait for start/promote/demote actions to complete + stonithd (LF 1951): fix remote stonith operations + Tools: crm_verify - clean up the upgrade logic to prevent crash on invalid configurations + Medium: ais: Add support for a synchronous call to retrieve the nodes nodeid + Medium: ais: Use the agreed service number + Medium: pengine: Allow external entities to ask for a node to be shot by creating a terminate=true transient node attribute + Medium: pengine: Bug LF:1950 - Notifications do not contain all documented resource state fields + Medium: pengine: Bug N:417585 - Do not restart group children whos individual score drops below zero + Medium: pengine: Implement a true maintenance mode + Medium: pengine: Print the correct message when stonith is disabled + Medium: stonithd: exit with better code on empty host list + Medium: xml: pacemaker-0.7 is now an alias for the 1.0 schema * Wed Aug 20 2008 Andrew Beekhof - 0.7.1-1 - Update source tarball to revision: f805e1b30103+ tip - Statistics: Changesets: 184 Diff: 513 files changed, 43408 insertions(+), 43783 deletions(-) - Changes since 0.7.0-19 + Fix compilation when GNUTLS isn't found + admin: Fix use-after-free in crm_mon + Build: Remove testing code that prevented heartbeat-only builds + cib: Use single quotes so that the xpath queries for nvpairs will succeed + crmd: Always connect to stonithd when the TE starts and ensure we notice if it dies + crmd: Correctly handle a dead PE process + crmd: Make sure async-failures cause the failcount to be incremented + pengine: Bug LF:1941 - Handle failed clone instance probes when clone-max < #nodes + pengine: Parse resource ordering sets correctly + pengine: Prevent use-of-NULL - order->rsc_rh will not always be non-NULL + pengine: Unpack colocation sets correctly + Tools: crm_mon - Prevent use-of-NULL for orphaned resources + Medium: ais: Add support for a synchronous call to retrieve the nodes nodeid + Medium: ais: Allow transient clients to receive membership updates + Medium: ais: Avoid double-free in error path + Medium: ais: Include in the mebership nodes for which we have not determined their hostname + Medium: ais: Spawn the PE from the ais plugin instead of the crmd + Medium: cib: By default, new configurations use the latest schema + Medium: cib: Clean up the CIB if it was already disconnected + Medium: cib: Only increment num_updates if something actually changed + Medium: cib: Prevent use-after-free in client after abnormal termination of the CIB + Medium: Core: Fix memory leak in xpath searches + Medium: Core: Get more details regarding parser errors + Medium: Core: Repair expand_plus_plus - do not call char2score on unexpanded values + Medium: Core: Switch to the libxml2 parser - its significantly faster + Medium: Core: Use a libxml2 library function for xml -> text conversion + Medium: crmd: Asynchronous failure actions have no parameters + Medium: crmd: Avoid calling glib functions with NULL + Medium: crmd: Do not allow an election to promote a node from S_STARTING + Medium: crmd: Do not vote if we have not completed the local startup + Medium: crmd: Fix te_update_diff() now that get_object_root() functions differently + Medium: crmd: Fix the lrmd xpath expressions to not contain quotes + Medium: crmd: If we get a join offer during an election, better restart the election + Medium: crmd: No further processing is needed when using the LRMs API call for failing resources + Medium: crmd: Only update have-quorum if the value changed + Medium: crmd: Repair the input validation logic in do_te_invoke + Medium: cts: CIBs can no longer contain comments + Medium: cts: Enable a bunch of tests that were incorrectly disabled + Medium: cts: The libxml2 parser wont allow v1 resources to use integers as parameter names + Medium: Do not use the cluster UID and GID directly. Look them up based on the configured value of HA_CCMUSER + Medium: Fix compilation when heartbeat is not supported + Medium: pengine: Allow groups to be involved in optional ordering constraints + Medium: pengine: Allow sets of operations to be reused by multiple resources + Medium: pengine: Bug LF:1941 - Mark extra clone instances as orphans and do not show inactive ones + Medium: pengine: Determin the correct migration-threshold during resource expansion + Medium: pengine: Implement no-quorum-policy=suicide (FATE #303619) + Medium: pengine: Clean up resources after stopping old copies of the PE + Medium: pengine: Teach the PE how to stop old copies of itself + Medium: Tools: Backport hb_report updates + Medium: Tools: cib_shadow - On create, spawn a new shell with CIB_shadow and PS1 set accordingly + Medium: Tools: Rename cib_shadow to crm_shadow * Fri Jul 18 2008 Andrew Beekhof - 0.7.0-19 - Update source tarball to revision: 007c3a1c50f5 (unstable) tip - Statistics: Changesets: 108 Diff: 216 files changed, 4632 insertions(+), 4173 deletions(-) - Changes added since unstable-0.7 + admin: Fix use-after-free in crm_mon + ais: Change the tag for the ais plugin to "pacemaker" (used in openais.conf) + ais: Log terminated processes as an error + cib: Performance - Reorganize things to avoid calculating the XML diff twice + pengine: Bug LF:1941 - Handle failed clone instance probes when clone-max < #nodes + pengine: Fix memory leak in action2xml + pengine: Make OCF_ERR_ARGS a node-level error rather than a cluster-level one + pengine: Properly handle clones that are not installed on all nodes + Medium: admin: cibadmin - Show any validation errors if the upgrade failed + Medium: admin: cib_shadow - Implement --locate to display the underlying filename + Medium: admin: cib_shadow - Implement a --diff option + Medium: admin: cib_shadow - Implement a --switch option + Medium: admin: crm_resource - create more compact constraints that do not use lifetime (which is deprecated) + Medium: ais: Approximate born_on for OpenAIS based clusters + Medium: cib: Remove do_id_check, it is a poor substitute for ID validation by a schema + Medium: cib: Skip construction of pre-notify messages if no-one wants one + Medium: Core: Attempt to streamline some key functions to increase performance + Medium: Core: Clean up XML parser after validation + Medium: crmd: Detect and optimize the CRMs behavior when processing diffs of an LRM refresh + Medium: Fix memory leaks when resetting the name of an XML object + Medium: pengine: Prefer the current location if it is one of a group of nodes with the same (highest) score * Wed Jun 25 2008 Andrew Beekhof - 0.7.0-1 - Update source tarball to revision: bde0c7db74fb tip - Statistics: Changesets: 439 Diff: 676 files changed, 41310 insertions(+), 52071 deletions(-) - Changes added since stable-0.6 + A new tool for setting up and invoking CTS + Admin: All tools now use --node (-N) for specifying node unames + Admin: All tools now use --xml-file (-x) and --xml-text (-X) for specifying where to find XML blobs + cib: Cleanup the API - remove redundant input fields + cib: Implement CIB_shadow - a facility for making and testing changes before uploading them to the cluster + cib: Make registering per-op callbacks an API call and renamed (for clarity) the API call for requesting notifications + Core: Add a facility for automatically upgrading old configurations + Core: Adopt libxml2 as the XML processing library - all external clients need to be recompiled + Core: Allow sending TLS messages larger than the MTU + Core: Fix parsing of time-only ISO dates + Core: Smarter handling of XML values containing quotes + Core: XML memory corruption - catch, and handle, cases where we are overwriting an attribute value with itself + Core: The xml ID type does not allow UUIDs that start with a number + Core: Implement XPath based versions of query/delete/replace/modify + Core: Remove some HA2.0.(3,4) compatibility code + crmd: Overhaul the detection of nodes that are starting vs. failed + pengine: Bug LF:1459 - Allow failures to expire + pengine: Have the PE do non-persistent configuration upgrades before performing calculations + pengine: Replace failure-stickiness with a simple 'migration-threshold' + tengine: Simplify the design by folding the tengine process into the crmd + Medium: Admin: Bug LF:1438 - Allow the list of all/active resource operations to be queried by crm_resource + Medium: Admin: Bug LF:1708 - crm_resource should print a warning if an attribute is already set as a meta attribute + Medium: Admin: Bug LF:1883 - crm_mon should display fail-count and operation history + Medium: Admin: Bug LF:1883 - crm_mon should display operation timing data + Medium: Admin: Bug N:371785 - crm_resource -C does not also clean up fail-count attributes + Medium: Admin: crm_mon - include timing data for failed actions + Medium: ais: Read options from the environment since objdb is not completely usable yet + Medium: cib: Add sections for op_defaults and rsc_defaults + Medium: cib: Better matching notification callbacks (for detecting duplicates and removal) + Medium: cib: Bug LF:1348 - Allow rules and attribute sets to be referenced for use in other objects + Medium: cib: BUG LF:1918 - By default, all cib calls now timeout after 30s + Medium: cib: Detect updates that decrease the version tuple + Medium: cib: Implement a client-side operation timeout - Requires LHA update + Medium: cib: Implement callbacks and async notifications for remote connections + Medium: cib: Make cib->cmds->update() an alias for modify at the API level (also implemented in cibadmin) + Medium: cib: Mark the CIB as disconnected if the IPC connection is terminated + Medium: cib: New call option 'cib_can_create' which can be passed to modify actions - allows the object to be created if it does not exist yet + Medium: cib: Reimplement get|set|delete attributes using XPath + Medium: cib: Remove some useless parts of the API + Medium: cib: Remove the 'attributes' scaffolding from the new format + Medium: cib: Implement the ability for clients to connect to remote servers + Medium: Core: Add support for validating xml against RelaxNG schemas + Medium: Core: Allow more than one item to be modified/deleted in XPath based operations + Medium: Core: Fix the sort_pairs function for creating sorted xml objects + Medium: Core: iso8601 - Implement subtract_duration and fix subtract_time + Medium: Core: Reduce the amount of xml copying + Medium: Core: Support value='value+=N' XML updates (in addtion to value='value++') + Medium: crmd: Add support for lrm_ops->fail_rsc if its available + Medium: crmd: HB - watch link status for node leaving events + Medium: crmd: Bug LF:1924 - Improved handling of lrmd disconnects and shutdowns + Medium: crmd: Do not wait for actions with a start_delay over 5 minutes. Confirm them immediately + Medium: pengine: Bug LF:1328 - Do not fencing nodes in clusters without managed resources + Medium: pengine: Bug LF:1461 - Give transient node attributes (in ) preference over persistent ones (in ) + Medium: pengine: Bug LF:1884, Bug LF:1885 - Implement N:M ordering and colocation constraints + Medium: pengine: Bug LF:1886 - Create a resource and operation 'defaults' config section + Medium: pengine: Bug LF:1892 - Allow recurring actions to be triggered at known times + Medium: pengine: Bug LF:1926 - Probes should complete before stop actions are invoked + Medium: pengine: Fix the standby when its set as a transient attribute + Medium: pengine: Implement a global 'stop-all-resources' option + Medium: pengine: Implement cibpipe, a tool for performing/simulating config changes "offline" + Medium: pengine: We do not allow colocation with specific clone instances + Medium: Tools: pingd - Implement a stack-independent version of pingd + Medium: xml: Ship an xslt for upgrading from 0.6 to 0.7 * Thu Jun 19 2008 Andrew Beekhof - 0.6.5-1 - Update source tarball to revision: b9fe723d1ac5 tip - Statistics: Changesets: 48 Diff: 37 files changed, 1204 insertions(+), 234 deletions(-) - Changes since Pacemaker-0.6.4 + Admin: Repair the ability to delete failcounts + ais: Audit IPC handling between the AIS plugin and CRM processes + ais: Have the plugin create needed /var/lib directories + ais: Make sure the sync and async connections are assigned correctly (not swapped) + cib: Correctly detect configuration changes - num_updates does not count + pengine: Apply stickiness values to the whole group, not the individual resources + pengine: Bug N:385265 - Ensure groups are migrated instead of remaining partially active on the current node + pengine: Bug N:396293 - Enforce mandatory group restarts due to ordering constraints + pengine: Correctly recover master instances found active on more than one node + pengine: Fix memory leaks reported by Valgrind + Medium: Admin: crm_mon - Misc improvements from Satomi Taniguchi + Medium: Bug LF:1900 - Resource stickiness should not allow placement in asynchronous clusters + Medium: crmd: Ensure joins are completed promptly when a node taking part dies + Medium: pengine: Avoid clone instance shuffling in more cases + Medium: pengine: Bug LF:1906 - Remove an optimization in native_merge_weights() causing group scores to behave eratically + Medium: pengine: Make use of target_rc data to correctly process resource operations + Medium: pengine: Prevent a possible use of NULL in sort_clone_instance() + Medium: tengine: Include target rc in the transition key - used to correctly determin operation failure * Thu May 22 2008 Andrew Beekhof - 0.6.4-1 - Update source tarball to revision: 226d8e356924 tip - Statistics: Changesets: 55 Diff: 199 files changed, 7103 insertions(+), 12378 deletions(-) - Changes since Pacemaker-0.6.3 + crmd: Bug LF:1881 LF:1882 - Overhaul the logic for operation cancelation and deletion + crmd: Bug LF:1894 - Make sure cancelled recurring operations are cleaned out from the CIB + pengine: Bug N:387749 - Colocation with clones causes unnecessary clone instance shuffling + pengine: Ensure 'master' monitor actions are cancelled _before_ we demote the resource + pengine: Fix assert failure leading to core dump - make sure variable is properly initialized + pengine: Make sure 'slave' monitoring happens after the resource has been demoted + pengine: Prevent failure stickiness underflows (where too many failures become a _positive_ preference) + Medium: Admin: crm_mon - Only complain if the output file could not be opened + Medium: Common: filter_action_parameters - enable legacy handling only for older versions + Medium: pengine: Bug N:385265 - The failure stickiness of group children is ignored until it reaches -INFINITY + Medium: pengine: Implement master and clone colocation by exlcuding nodes rather than setting ones score to INFINITY (similar to cs: 756afc42dc51) + Medium: tengine: Bug LF:1875 - Correctly find actions to cancel when their node leaves the cluster * Wed Apr 23 2008 Andrew Beekhof - 0.6.3-1 - Update source tarball to revision: fd8904c9bc67 tip - Statistics: Changesets: 117 Diff: 354 files changed, 19094 insertions(+), 11338 deletions(-) - Changes since Pacemaker-0.6.2 + Admin: Bug LF:1848 - crm_resource - Pass set name and id to delete_resource_attr() in the correct order + Build: SNMP has been moved to the management/pygui project + crmd: Bug LF1837 - Unmanaged resources prevent crmd from shutting down + crmd: Prevent use-after-free in lrm interface code (Patch based on work by Keisuke MORI) + pengine: Allow the cluster to make progress by not retrying failed demote actions + pengine: Anti-colocation with slave should not prevent master colocation + pengine: Bug LF 1768 - Wait more often for STONITH ops to complete before starting resources + pengine: Bug LF1836 - Allow is-managed-default=false to be overridden by individual resources + pengine: Bug LF185 - Prevent pointless master/slave instance shuffling by ignoring the master-pref of stopped instances + pengine: Bug N-191176 - Implement interleaved ordering for clone-to-clone scenarios + pengine: Bug N-347004 - Ensure clone notifications are always sent when an instance is stopped/started + pengine: Bug N-347004 - Include notification ordering is correct for interleaved clones + pengine: Bug PM-11 - Directly link probe_complete to starting clone instances + pengine: Bug PM1 - Fix setting failcounts when applied to complex resources + pengine: Bug PM12, LF1648 - Extensive revision of group ordering + pengine: Bug PM7 - Ensure masters are always demoted before they are stopped + pengine: Create probes after allocation to allow smarter handling of anonymous clones + pengine: Do not prioritize clone instances that must be moved + pengine: Fix error in previous commit that allowed more than the required number of masters to be promoted + pengine: Group start ordering fixes + pengine: Implement promote/demote ordering for cloned groups + tengine: Repair failcount updates + tengine: Use the correct offset when updating failcount + Medium: Admin: Add a summary output that can be easily parsed by CTS for audit purposes + Medium: Build: Make configure fail if bz2 or libxml2 are not present + Medium: Build: Re-instate a better default for LCRSODIR + Medium: CIB: Bug LF-1861 - Filter irrelvant error status from synchronous CIB clients + Medium: Core: Bug 1849 - Invalid conversion of ordinal leap year to gregorian date + Medium: Core: Drop compatibility code for 2.0.4 and 2.0.5 clusters + Medium: crmd: Bug LF-1860 - Automatically cancel recurring ops before demote and promote operations (not only stops) + Medium: crmd: Save the current CIB contents if we detect the PE crashed + Medium: pengine: Bug LF:1866 - Fix version check when applying compatibility handling for failed start operations + Medium: pengine: Bug LF:1866 - Restore the ability to have start failures not be fatal + Medium: pengine: Bug PM1 - Failcount applies to all instances of non-unique clone + Medium: pengine: Correctly set the state of partially active master/slave groups + Medium: pengine: Do not claim to be stopping an already stopped orphan + Medium: pengine: Ensure implies_left ordering constraints are always effective + Medium: pengine: Indicate each resources 'promotion' score + Medium: pengine: Prevent a possible use-of-NULL + Medium: pengine: Reprocess the current action if it changed (so that any prior dependencies are updated) + Medium: tengine: Bug LF-1859 - Wait for fail-count updates to complete before terminating the transition + Medium: tengine: Bug LF:1859 - Do not abort graphs due to our own failcount updates + Medium: tengine: Bug LF:1859 - Prevent the TE from interupting itself * Thu Feb 14 2008 Andrew Beekhof - 0.6.2-1 - Update source tarball to revision: 28b1a8c1868b tip - Statistics: Changesets: 11 Diff: 7 files changed, 58 insertions(+), 18 deletions(-) - Changes since Pacemaker-0.6.1 + haresources2cib.py: set default-action-timeout to the default (20s) + haresources2cib.py: update ra parameters lists + Medium: SNMP: Allow the snmp subagent to be built (patch from MATSUDA, Daiki) + Medium: Tools: Make sure the autoconf variables in haresources2cib are expanded * Tue Feb 12 2008 Andrew Beekhof - 0.6.1-1 - Update source tarball to revision: e7152d1be933 tip - Statistics: Changesets: 25 Diff: 37 files changed, 1323 insertions(+), 227 deletions(-) - Changes since Pacemaker-0.6.0 + CIB: Ensure changes to top-level attributes (like admin_epoch) cause a disk write + CIB: Ensure the archived file hits the disk before returning + CIB: Repair the ability to do 'atomic increment' updates (value="value++") + crmd: Bug #7 - Connecting to the crmd immediately after startup causes use-of-NULL + Medium: CIB: Mask cib_diff_resync results from the caller - they do not need to know + Medium: crmd: Delay starting the IPC server until we are fully functional + Medium: CTS: Fix the startup patterns + Medium: pengine: Bug 1820 - Allow the first resource in a group to be migrated + Medium: pengine: Bug 1820 - Check the colocation dependencies of resources to be migrated * Mon Jan 14 2008 Andrew Beekhof - 0.6.0-1 - This is the first release of the Pacemaker Cluster Resource Manager formerly part of Heartbeat. - For those looking for the GUI, mgmtd, CIM or TSA components, they are now found in the new pacemaker-pygui project. Build dependencies prevent them from being included in Heartbeat (since the built-in CRM is no longer supported) and, being non-core components, are not included with Pacemaker. - Update source tarball to revision: c94b92d550cf - Statistics: Changesets: 347 Diff: 2272 files changed, 132508 insertions(+), 305991 deletions(-) - Test hardware: + 6-node vmware cluster (sles10-sp1/256MB/vmware stonith) on a single host (opensuse10.3/2GB/2.66GHz Quad Core2) + 7-node EMC Centera cluster (sles10/512MB/2GHz Xeon/ssh stonith) - Notes: Heartbeat Stack + All testing was performed with STONITH enabled + The CRM was enabled using the "crm respawn" directive - Notes: OpenAIS Stack + This release contains a preview of support for the OpenAIS cluster stack + The current release of the OpenAIS project is missing two important patches that we require. OpenAIS packages containing these patches are available for most major distributions at: http://download.opensuse.org/repositories/server:/ha-clustering + The OpenAIS stack is not currently recommended for use in clusters that have shared data as STONITH support is not yet implimented + pingd is not yet available for use with the OpenAIS stack + 3 significant OpenAIS issues were found during testing of 4 and 6 node clusters. We are activly working together with the OpenAIS project to get these resolved. - Pending bugs encountered during testing: + OpenAIS #1736 - Openais membership took 20s to stabilize + Heartbeat #1750 - ipc_bufpool_update: magic number in head does not match + OpenAIS #1793 - Assertion failure in memb_state_gather_enter() + OpenAIS #1796 - Cluster message corruption - Changes since Heartbeat-2.1.2-24 + Add OpenAIS support + Admin: crm_uuid - Look in the right place for Heartbeat UUID files + admin: Exit and indicate a problem if the crmd exits while crmadmin is performing a query + cib: Fix CIB_OP_UPDATE calls that modify the whole CIB + cib: Fix compilation when supporting the heartbeat stack + cib: Fix memory leaks caused by the switch to get_message_xml() + cib: HA_VALGRIND_ENABLED needs to be set _and_ set to 1|yes|true + cib: Use get_message_xml() in preference to cl_get_struct() + cib: Use the return value from call to write() in cib_send_plaintext() + Core: ccm nodes can legitimately have a node id of 0 + Core: Fix peer-process tracking for the Heartbeat stack + Core: Heartbeat does not send status notifications for nodes that were already part of the cluster. Fake them instead + CRM: Add children to HA_Messages such that the field name matches F_XML_TAGNAME + crm: Adopt a more flexible appraoch to enabling Valgrind + crm: Fix compilation when bzip2 is not installed + CRM: Future-proof get_message_xml() + crmd: Filter election responses based on time not FSA state + crmd: Handle all possible peer states in crmd_ha_status_callback() + crmd: Make sure the current date/time is set - prevents use-of-NULL when evaluating rules + crmd: Relax an assertion regrading ccm membership instances + crmd: Use (node->processes&crm_proc_ais) to accurately update the CIB after replace operations + crmd: Heartbeat: Accurately record peer client status + pengine: Bug 1777 - Allow colocation with a resource in the Stopped state + pengine: Bug 1822 - Prevent use-of-NULL in PromoteRsc() + pengine: Implement three recovery policies based on op_status and op_rc + pengine: Parse fail-count correctly (it may be set to ININFITY) + pengine: Prevent graph-loop when stonith agents need to be moved around before a STONITH op + pengine: Prevent graph-loops when two operations have the same name+interval + tengine: Cancel active timers when destroying graphs + tengine: Ensure failcount is set correctly for failed stops/starts + tengine: Update failcount for oeprations that time out + Medium: admin: Prevent hang in crm_mon -1 when there is no cib connection - Patch from Junko IKEDA + Medium: cib: Require --force|-f when performing potentially dangerous commands with cibadmin + Medium: cib: Tweak the shutdown code + Medium: Common: Only count peer processes of active nodes + Medium: Core: Create generic cluster sign-in method + Medium: core: Fix compilation when Heartbeat support is disabled + Medium: Core: General cleanup for supporting two stacks + Medium: Core: iso6601 - Support parsing of time-only strings + Medium: core: Isolate more code that is only needed when SUPPORT_HEARTBEAT is enabled + Medium: crm: Improved logging of errors in the XML parser + Medium: crmd: Fix potential use-of-NULL in string comparison + Medium: crmd: Reimpliment syncronizing of CIB queries and updates when invoking the PE + Medium: crm_mon: Indicate when a node is both in standby mode and offline + Medium: pengine: Bug 1822 - Do not try an promote groups if not all of it is active + Medium: pengine: on_fail=nothing is an alias for 'ignore' not 'restart' + Medium: pengine: Prevent a potential use-of-NULL in cron_range_satisfied() + snmp subagent: fix a problem on displaying an unmanaged group + snmp subagent: use the syslog setting + snmp: v2 support (thanks to Keisuke MORI) + snmp_subagent - made it not complain about some things if shutting down diff --git a/doc/Clusters_from_Scratch/pot/Author_Group.pot b/doc/Clusters_from_Scratch/pot/Author_Group.pot index 078e45daed..82963b7dd2 100644 --- a/doc/Clusters_from_Scratch/pot/Author_Group.pot +++ b/doc/Clusters_from_Scratch/pot/Author_Group.pot @@ -1,64 +1,64 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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: firstname #, no-c-format msgid "Andrew" msgstr "" #. Tag: surname #, no-c-format msgid "Beekhof" msgstr "" #. Tag: orgname #, no-c-format msgid "Red Hat" msgstr "" #. Tag: contrib #, no-c-format msgid "Primary author" msgstr "" #. Tag: firstname #, no-c-format msgid "Raoul" msgstr "" #. Tag: surname #, no-c-format msgid "Scarazzini" msgstr "" #. Tag: contrib #, no-c-format msgid "Italian translation" msgstr "" #. Tag: firstname #, no-c-format msgid "Dan" msgstr "" #. Tag: surname #, no-c-format msgid "Frîncu" msgstr "" #. Tag: contrib #, no-c-format msgid "Romanian translation" msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Book_Info.pot b/doc/Clusters_from_Scratch/pot/Book_Info.pot index 2e5b57f4f5..059d4534e9 100644 --- a/doc/Clusters_from_Scratch/pot/Book_Info.pot +++ b/doc/Clusters_from_Scratch/pot/Book_Info.pot @@ -1,69 +1,69 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Clusters from Scratch" msgstr "" #. Tag: subtitle #, no-c-format msgid "Step-by-Step Instructions for Building Your First High-Availability Cluster" msgstr "" #. Tag: productname #, no-c-format msgid "Pacemaker" msgstr "" #. Tag: para #, no-c-format msgid "The purpose of this document is to provide a start-to-finish guide to building an example active/passive cluster with Pacemaker and show how it can be converted to an active/active one." msgstr "" #. Tag: para #, no-c-format msgid "The example cluster will use:" msgstr "" #. Tag: para #, no-c-format msgid "&DISTRO; &DISTRO_VERSION; as the host operating system" msgstr "" #. Tag: para #, no-c-format msgid "Corosync to provide messaging and membership services," msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker to perform resource management," msgstr "" #. Tag: para #, no-c-format msgid "DRBD as a cost-effective alternative to shared storage," msgstr "" #. Tag: para #, no-c-format msgid "GFS2 as the cluster filesystem (in active/active mode)" msgstr "" #. Tag: para #, no-c-format msgid "Given the graphical nature of the install process, a number of screenshots are included. However the guide is primarily composed of commands, the reasons for executing them and their expected outputs." msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Preface.pot b/doc/Clusters_from_Scratch/pot/Preface.pot index eb70fb6c89..f84c72b747 100644 --- a/doc/Clusters_from_Scratch/pot/Preface.pot +++ b/doc/Clusters_from_Scratch/pot/Preface.pot @@ -1,19 +1,19 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Preface" msgstr "" diff --git a/doc/Clusters_from_Scratch/pot/Revision_History.pot b/doc/Clusters_from_Scratch/pot/Revision_History.pot index a3dc415ba8..7f577ac31b 100644 --- a/doc/Clusters_from_Scratch/pot/Revision_History.pot +++ b/doc/Clusters_from_Scratch/pot/Revision_History.pot @@ -1,109 +1,109 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Revision History" msgstr "" #. Tag: firstname #, no-c-format msgid "Andrew" msgstr "" #. Tag: surname #, no-c-format msgid "Beekhof" msgstr "" #. Tag: member #, no-c-format msgid "Import from Pages.app" msgstr "" #. Tag: firstname #, no-c-format msgid "Raoul" msgstr "" #. Tag: surname #, no-c-format msgid "Scarazzini" msgstr "" #. Tag: member #, no-c-format msgid "Italian translation" msgstr "" #. Tag: member #, no-c-format msgid "Updated for Fedora 13" msgstr "" #. Tag: member #, no-c-format msgid "Update the GFS2 section to use CMAN" msgstr "" #. Tag: member #, no-c-format msgid "Generate docbook content from asciidoc sources" msgstr "" #. Tag: member #, no-c-format msgid "Updated for Fedora 17" msgstr "" #. Tag: firstname #, no-c-format msgid "David" msgstr "" #. Tag: surname #, no-c-format msgid "Vossel" msgstr "" #. Tag: member #, no-c-format msgid "Updated for pcs" msgstr "" #. Tag: firstname #, no-c-format msgid "Ken" msgstr "" #. Tag: surname #, no-c-format msgid "Gaillot" msgstr "" #. Tag: member #, no-c-format msgid "Updated for Fedora 21" msgstr "" #. Tag: member #, no-c-format msgid "Minor corrections, plus use include file for intro" msgstr "" #. Tag: member #, no-c-format msgid "Update for CentOS 7.1 and leaving firewalld/SELinux enabled" msgstr "" diff --git a/doc/Pacemaker_Development/pot/Author_Group.pot b/doc/Pacemaker_Development/pot/Author_Group.pot index 5ed5c168d1..4c66589225 100644 --- a/doc/Pacemaker_Development/pot/Author_Group.pot +++ b/doc/Pacemaker_Development/pot/Author_Group.pot @@ -1,44 +1,44 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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: firstname #, no-c-format msgid "Andrew" msgstr "" #. Tag: surname #, no-c-format msgid "Beekhof" msgstr "" #. Tag: orgname #, no-c-format msgid "Red Hat" msgstr "" #. Tag: contrib #, no-c-format msgid "Co-author" msgstr "" #. Tag: firstname #, no-c-format msgid "Ken" msgstr "" #. Tag: surname #, no-c-format msgid "Gaillot" msgstr "" diff --git a/doc/Pacemaker_Development/pot/Book_Info.pot b/doc/Pacemaker_Development/pot/Book_Info.pot index d508f920ea..c994d01a2f 100644 --- a/doc/Pacemaker_Development/pot/Book_Info.pot +++ b/doc/Pacemaker_Development/pot/Book_Info.pot @@ -1,29 +1,29 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Pacemaker Development" msgstr "" #. Tag: subtitle #, no-c-format msgid "Working with the Pacemaker Code Base" msgstr "" #. Tag: para #, no-c-format msgid "This document has guidelines and tips for developers interested in editing Pacemaker source code and submitting changes for inclusion in the project." msgstr "" diff --git a/doc/Pacemaker_Development/pot/Ch-Coding.pot b/doc/Pacemaker_Development/pot/Ch-Coding.pot index ddd5d8e2dc..d1716d820e 100644 --- a/doc/Pacemaker_Development/pot/Ch-Coding.pot +++ b/doc/Pacemaker_Development/pot/Ch-Coding.pot @@ -1,276 +1,276 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "C Coding Guidelines" msgstr "" #. Tag: para #, no-c-format msgid "" msgstr "" #. Tag: title #, no-c-format msgid "C Boilerplate" msgstr "" #. Tag: para #, no-c-format msgid " Cboilerplate boilerplate licensingC boilerplate C boilerplate " msgstr "" #. Tag: para #, no-c-format msgid "Every C file should start like this:" msgstr "" #. Tag: programlisting #, no-c-format msgid "/*\n" " * Copyright (C) <YYYY[-YYYY]> Andrew Beekhof <andrew@beekhof.net>\n" " *\n" " * This source code is licensed under <LICENSE> WITHOUT ANY WARRANTY.\n" " */" msgstr "" #. Tag: para #, no-c-format msgid "<YYYY> is the year the code was originally created (it is the most important date for copyright purposes, as it establishes priority and the point from which expiration is calculated). If the code is modified in later years, add -YYYY with the most recent year of modification." msgstr "" #. Tag: para #, no-c-format msgid "<LICENSE> should follow the policy set forth in the COPYING file, generally one of \"GNU General Public License version 2 or later (GPLv2+)\" or \"GNU Lesser General Public License version 2.1 or later (LGPLv2.1+)\"." msgstr "" #. Tag: title #, no-c-format msgid "Formatting" msgstr "" #. Tag: title #, no-c-format msgid "Whitespace" msgstr "" #. Tag: para #, no-c-format msgid " Cwhitespace whitespace " msgstr "" #. Tag: para #, no-c-format msgid "Indentation must be 4 spaces, no tabs." msgstr "" #. Tag: para #, no-c-format msgid "Do not leave trailing whitespace." msgstr "" #. Tag: title #, no-c-format msgid "Line Length" msgstr "" #. Tag: para #, no-c-format msgid "Lines should be no longer than 80 characters unless limiting line length significantly impacts readability." msgstr "" #. Tag: title #, no-c-format msgid "Pointers" msgstr "" #. Tag: para #, no-c-format msgid " Cpointers pointers " msgstr "" #. Tag: para #, no-c-format msgid "The * goes by the variable name, not the type:" msgstr "" #. Tag: programlisting #, no-c-format msgid "char *foo;" msgstr "" #. Tag: para #, no-c-format msgid "Use a space before the * and after the closing parenthesis in a cast:" msgstr "" #. Tag: programlisting #, no-c-format msgid "char *foo = (char *) bar;" msgstr "" #. Tag: title #, no-c-format msgid "Functions" msgstr "" #. Tag: para #, no-c-format msgid " Cfunctions functions " msgstr "" #. Tag: para #, no-c-format msgid "In the function definition, put the return type on its own line, and place the opening brace by itself on a line:" msgstr "" #. Tag: programlisting #, no-c-format msgid "static int\n" "foo(void)\n" "{" msgstr "" #. Tag: para #, no-c-format msgid "For functions with enough arguments that they must break to the next line, align arguments with the first argument:" msgstr "" #. Tag: programlisting #, no-c-format msgid "static int\n" "function_name(int bar, const char *a, const char *b,\n" " const char *c, const char *d)\n" "{" msgstr "" #. Tag: para #, no-c-format msgid "If a function name gets really long, start the arguments on their own line with 8 spaces of indentation:" msgstr "" #. Tag: programlisting #, no-c-format msgid "static int\n" "really_really_long_function_name_this_is_getting_silly_now(\n" " int bar, const char *a, const char *b,\n" " const char *c, const char *d)\n" "{" msgstr "" #. Tag: title #, no-c-format msgid "Control Statements (if, else, while, for, switch)" msgstr "" #. Tag: para #, no-c-format msgid "The keyword is followed by one space, then left parenthesis without space, condition, right parenthesis, space, opening bracket on the same line. else and else if are on the same line with the ending brace and opening brace, separated by a space:" msgstr "" #. Tag: programlisting #, no-c-format msgid "if (condition1) {\n" " statement1;\n" "} else if (condition2) {\n" " statement2;\n" "} else {\n" " statement3;\n" "}" msgstr "" #. Tag: para #, no-c-format msgid "In a switch statement, case is indented one level, and the body of each case is indented by another level. The opening brace is on the same line as switch." msgstr "" #. Tag: programlisting #, no-c-format msgid "switch (expression) {\n" " case 0:\n" " command1;\n" " break;\n" " case 1:\n" " command2;\n" " break;\n" " default:\n" " command3;\n" "}" msgstr "" #. Tag: title #, no-c-format msgid "Operators" msgstr "" #. Tag: para #, no-c-format msgid " Coperators operators " msgstr "" #. Tag: para #, no-c-format msgid "Operators have spaces from both sides. Do not rely on operator precedence; use parentheses when mixing operators with different priority." msgstr "" #. Tag: para #, no-c-format msgid "No space is used after opening parenthesis and before closing parenthesis." msgstr "" #. Tag: programlisting #, no-c-format msgid "x = a + b - (c * d);" msgstr "" #. Tag: title #, no-c-format msgid "Naming Conventions" msgstr "" #. Tag: para #, no-c-format msgid " Cnaming naming " msgstr "" #. Tag: para #, no-c-format msgid "Any exposed symbols in libraries (non-static function names, type names, etc.) must begin with a prefix appropriate to the library, for example, crm_, pe_, st_, lrm_." msgstr "" #. Tag: title #, no-c-format msgid "vim Settings" msgstr "" #. Tag: para #, no-c-format msgid " vim " msgstr "" #. Tag: para #, no-c-format msgid "Developers who use vim to edit source code can add the following settings to their ~/.vimrc file to follow Pacemaker C coding guidelines:" msgstr "" #. Tag: screen #, no-c-format msgid "\" follow Pacemaker coding guidelines when editing C source code files\n" "filetype plugin indent on\n" "au FileType c setlocal expandtab tabstop=4 softtabstop=4 shiftwidth=4 textwidth=80\n" "autocmd BufNewFile,BufRead *.h set filetype=c\n" "let c_space_errors = 1" msgstr "" diff --git a/doc/Pacemaker_Development/pot/Ch-FAQ.pot b/doc/Pacemaker_Development/pot/Ch-FAQ.pot index 97aa3ec375..fda0b2f70b 100644 --- a/doc/Pacemaker_Development/pot/Ch-FAQ.pot +++ b/doc/Pacemaker_Development/pot/Ch-FAQ.pot @@ -1,139 +1,139 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Frequently Asked Questions" msgstr "" #. Tag: para #, no-c-format msgid "Who is this document intended for?" msgstr "" #. Tag: para #, no-c-format msgid "Anyone who wishes to read and/or edit the Pacemaker source code. Casual contributors should feel free to read just this FAQ, and consult other sections as needed." msgstr "" #. Tag: para #, no-c-format msgid "Where is the source code for Pacemaker?" msgstr "" #. Tag: para #, no-c-format msgid " downloads source code gitGitHub GitHub The source code for Pacemaker is kept on GitHub, as are all software projects under the ClusterLabs umbrella. Pacemaker uses Git for source code management. If you are a Git newbie, the gittutorial(7) man page is an excellent starting point. If you’re familiar with using Git from the command line, you can create a local copy of the Pacemaker source code with: git clone https://github.com/ClusterLabs/pacemaker.git pacemaker" msgstr "" #. Tag: para #, no-c-format msgid "What are the different Git branches and repositories used for?" msgstr "" #. Tag: para #, no-c-format msgid " branches " msgstr "" #. Tag: para #, no-c-format msgid "The master branch is the primary branch used for development." msgstr "" #. Tag: para #, no-c-format msgid "The 1.1 branch contains the latest official release, and normally does not receive any changes. During the release cycle, it will contain release candidates for the next official release, and will receive only bug fixes." msgstr "" #. Tag: para #, no-c-format msgid "The 1.0 repository is a frozen snapshot of the 1.0 release series, and is no longer developed." msgstr "" #. Tag: para #, no-c-format msgid "Messages will be posted to the developers@clusterlabs.org mailing list during the release cycle, with instructions about which branches to use when submitting requests." msgstr "" #. Tag: para #, no-c-format msgid "How do I build from the source code?" msgstr "" #. Tag: para #, no-c-format msgid "See INSTALL.md in the main checkout directory." msgstr "" #. Tag: para #, no-c-format msgid "What coding style should I follow?" msgstr "" #. Tag: para #, no-c-format msgid "You’ll be mostly fine if you simply follow the example of existing code. When unsure, see the relevant section of this document for language-specific recommendations. Pacemaker has grown and evolved organically over many years, so you will see much code that doesn’t conform to the current guidelines. We discourage making changes solely to bring code into conformance, as any change requires developer time for review and opens the possibility of adding bugs. However, new code should follow the guidelines, and it is fine to bring lines of older code into conformance when modifying that code for other reasons." msgstr "" #. Tag: para #, no-c-format msgid "How should I format my Git commit messages?" msgstr "" #. Tag: para #, no-c-format msgid " gitcommit messages commit messages See existing examples in the git log. The first line should look like change-type: affected-code: explanation where change-type can be Fix or Bug for most bug fixes, Feature for new features, Log for changes to log messages or handling, Doc for changes to documentation or comments, or Test for changes in CTS and regression tests. You will sometimes see Low, Med (or Mid) and High used instead for bug fixes, to indicate the severity. The important thing is that only commits with Feature, Fix, Bug, or High will automatically be included in the change log for the next release. The affected-code is the name of the component(s) being changed, for example, crmd or libcrmcommon (it’s more free-form, so don’t sweat getting it exact). The explanation briefly describes the change. The git project recommends the entire summary line stay under 50 characters, but more is fine if needed for clarity. Except for the most simple and obvious of changes, the summary should be followed by a blank line and then a longer explanation of why the change was made." msgstr "" #. Tag: para #, no-c-format msgid "How can I test my changes?" msgstr "" #. Tag: para #, no-c-format msgid "Most importantly, Pacemaker has regression tests for most major components; these will automatically be run for any pull requests submitted through GitHub. Additionally, Pacemaker’s Cluster Test Suite (CTS) can be used to set up a test cluster and run a wide variety of complex tests. This document will have more detail on testing in the future." msgstr "" #. Tag: para #, no-c-format msgid "What is Pacemaker’s license?" msgstr "" #. Tag: para #, no-c-format msgid " licensing Except where noted otherwise in the file itself, the source code for all Pacemaker programs is licensed under version 2 or later of the GNU General Public License (GPLv2+), its headers and libraries under version 2.1 or later of the less restrictive GNU Lesser General Public License (LGPLv2.1+), its documentation under version 4.0 or later of the Creative Commons Attribution-ShareAlike International Public License (CC-BY-SA), and its init scripts under the Revised BSD license. If you find any deviations from this policy, or wish to inquire about alternate licensing arrangements, please e-mail andrew@beekhof.net. Licensing issues are also discussed on the ClusterLabs wiki." msgstr "" #. Tag: para #, no-c-format msgid "How can I contribute my changes to the project?" msgstr "" #. Tag: para #, no-c-format msgid "Contributions of bug fixes or new features are very much appreciated! Patches can be submitted as pull requests via GitHub (the preferred method, due to its excellent features), or e-mailed to the developers@clusterlabs.org mailing list as an attachment in a format Git can import." msgstr "" #. Tag: para #, no-c-format msgid "What if I still have questions?" msgstr "" #. Tag: para #, no-c-format msgid " mailing lists Ask on the developers@clusterlabs.org mailing list for development-related questions, or on the users@clusterlabs.org mailing list for general questions about using Pacemaker. Developers often also hang out on freenode’s #clusterlabs IRC channel." msgstr "" diff --git a/doc/Pacemaker_Development/pot/Ch-Python.pot b/doc/Pacemaker_Development/pot/Ch-Python.pot index 54b56171d9..6d40d89b9b 100644 --- a/doc/Pacemaker_Development/pot/Ch-Python.pot +++ b/doc/Pacemaker_Development/pot/Ch-Python.pot @@ -1,297 +1,297 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Python Coding Guidelines" msgstr "" #. Tag: para #, no-c-format msgid "" msgstr "" #. Tag: title #, no-c-format msgid "Python Boilerplate" msgstr "" #. Tag: para #, no-c-format msgid " Pythonboilerplate boilerplate licensingPython boilerplate Python boilerplate " msgstr "" #. Tag: para #, no-c-format msgid "Every Python file should start like this:" msgstr "" #. Tag: programlisting #, no-c-format msgid "[<SHEBANG>]\n" "\"\"\" <BRIEF-DESCRIPTION>\n" "\"\"\"\n" "\n" "# Pacemaker targets compatibility with Python 2.6+ and 3.2+\n" "from __future__ import print_function, unicode_literals, absolute_import, division\n" "\n" "__copyright__ = \"Copyright (C) <YYYY[-YYYY]> Andrew Beekhof <andrew@beekhof.net>\"\n" "__license__ = \"<LICENSE> WITHOUT ANY WARRANTY\"" msgstr "" #. Tag: para #, no-c-format msgid "If the file is meant to be directly executed, the first line (<SHEBANG>) should be #!/usr/bin/python. If it is meant to be imported, omit this line." msgstr "" #. Tag: para #, no-c-format msgid "<BRIEF-DESCRIPTION> is obviously a brief description of the file’s purpose. The string may contain any other information typically used in a Python file docstring." msgstr "" #. Tag: para #, no-c-format msgid "The import statement is discussed further in ." msgstr "" #. Tag: para #, no-c-format msgid "<YYYY> is the year the code was originally created (it is the most important date for copyright purposes, as it establishes priority and the point from which expiration is calculated). If the code is modified in later years, add -YYYY with the most recent year of modification." msgstr "" #. Tag: para #, no-c-format msgid "<LICENSE> should follow the policy set forth in the COPYING file, generally one of \"GNU General Public License version 2 or later (GPLv2+)\" or \"GNU Lesser General Public License version 2.1 or later (LGPLv2.1+)\"." msgstr "" #. Tag: title #, no-c-format msgid "Python Compatibility" msgstr "" #. Tag: para #, no-c-format msgid " Python2 2 Python3 3 Pythonversions versions " msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker targets compatibility with Python 2.6 and later, and Python 3.2 and later. These versions have added features to be more compatible with each other, allowing us to support both the 2 and 3 series with the same code. It is a good idea to test any changes with both Python 2 and 3." msgstr "" #. Tag: title #, no-c-format msgid "Python Future Imports" msgstr "" #. Tag: para #, no-c-format msgid "The future imports used in mean:" msgstr "" #. Tag: para #, no-c-format msgid "All print statements must use parentheses, and printing without a newline is accomplished with the end=' ' parameter rather than a trailing comma." msgstr "" #. Tag: para #, no-c-format msgid "All string literals will be treated as Unicode (the u prefix is unnecessary, and must not be used, because it is not available in Python 3.2)." msgstr "" #. Tag: para #, no-c-format msgid "Local modules must be imported using from . import (rather than just import). To import one item from a local module, use from .modulename import (rather than from modulename import)." msgstr "" #. Tag: para #, no-c-format msgid "Division using / will always return a floating-point result (use // if you want the integer floor instead)." msgstr "" #. Tag: title #, no-c-format msgid "Other Python Compatibility Requirements" msgstr "" #. Tag: para #, no-c-format msgid "When specifying an exception variable, always use as instead of a comma (e.g. except Exception as e or except (TypeError, IOError) as e). Use e.args to access the error arguments (instead of iterating over or subscripting e)." msgstr "" #. Tag: para #, no-c-format msgid "Use in (not has_key()) to determine if a dictionary has a particular key." msgstr "" #. Tag: para #, no-c-format msgid "Always use the I/O functions from the io module rather than the native I/O functions (e.g. io.open() rather than open())." msgstr "" #. Tag: para #, no-c-format msgid "When opening a file, always use the t (text) or b (binary) mode flag." msgstr "" #. Tag: para #, no-c-format msgid "When creating classes, always specify a parent class to ensure that it is a \"new-style\" class (e.g. class Foo(object): rather than class Foo:)" msgstr "" #. Tag: para #, no-c-format msgid "Be aware of the bytes type added in Python 3. Many places where strings are used in Python 2 use bytes or bytearrays in Python 3 (for example, the pipes used with subprocess.Popen()). Code should handle both possibilities." msgstr "" #. Tag: para #, no-c-format msgid "Be aware that the items(), keys(), and values() methods of dictionaries return lists in Python 2 and views in Python 3. In many case, no special handling is required, but if the code needs to use list methods on the result, cast the result to list first." msgstr "" #. Tag: para #, no-c-format msgid "Do not name variables with or as." msgstr "" #. Tag: para #, no-c-format msgid "Do not raise or catch strings as exceptions (e.g. raise \"Bad thing\")." msgstr "" #. Tag: para #, no-c-format msgid "Do not use the cmp parameter of sorting functions (use key instead, if needed) or the __cmp__() method of classes (implement rich comparison methods such as __lt__() instead, if needed)." msgstr "" #. Tag: para #, no-c-format msgid "Do not use the buffer type." msgstr "" #. Tag: para #, no-c-format msgid "Do not use features not available in all targeted Python versions. Common examples include:" msgstr "" #. Tag: para #, no-c-format msgid "The argparse, html, ipaddress, sysconfig, and UserDict modules" msgstr "" #. Tag: para #, no-c-format msgid "The collections.OrderedDict class" msgstr "" #. Tag: para #, no-c-format msgid "The subprocess.run() function" msgstr "" #. Tag: para #, no-c-format msgid "The subprocess.DEVNULL constant" msgstr "" #. Tag: para #, no-c-format msgid "subprocess module-specific exceptions" msgstr "" #. Tag: para #, no-c-format msgid "Set literals ({1, 2, 3})" msgstr "" #. Tag: title #, no-c-format msgid "Python Usages to Avoid" msgstr "" #. Tag: para #, no-c-format msgid "Avoid the following if possible, otherwise research the compatibility issues involved (hacky workarounds are often available):" msgstr "" #. Tag: para #, no-c-format msgid "long integers" msgstr "" #. Tag: para #, no-c-format msgid "octal integer literals" msgstr "" #. Tag: para #, no-c-format msgid "mixed binary and string data in one data file or variable" msgstr "" #. Tag: para #, no-c-format msgid "metaclasses" msgstr "" #. Tag: para #, no-c-format msgid "locale.strcoll and locale.strxfrm" msgstr "" #. Tag: para #, no-c-format msgid "the configparser and ConfigParser modules" msgstr "" #. Tag: para #, no-c-format msgid "importing compatibility modules such as six (so we don’t have to add them to Pacemaker’s dependencies)" msgstr "" #. Tag: title #, no-c-format msgid "Formatting Python Code" msgstr "" #. Tag: para #, no-c-format msgid " Pythonformatting formatting " msgstr "" #. Tag: para #, no-c-format msgid "Indentation must be 4 spaces, no tabs." msgstr "" #. Tag: para #, no-c-format msgid "Do not leave trailing whitespace." msgstr "" #. Tag: para #, no-c-format msgid "Lines should be no longer than 80 characters unless limiting line length significantly impacts readability. For Python, this limitation is flexible since breaking a line often impacts readability, but definitely keep it under 120 characters." msgstr "" #. Tag: para #, no-c-format msgid "Where not conflicting with this style guide, it is recommended (but not required) to follow PEP 8." msgstr "" #. Tag: para #, no-c-format msgid "It is recommended (but not required) to format Python code such that pylint --disable=line-too-long,too-many-lines,too-many-instance-attributes,too-many-arguments,too-many-statements produces minimal complaints (even better if you don’t need to disable all those checks)." msgstr "" diff --git a/doc/Pacemaker_Development/pot/Revision_History.pot b/doc/Pacemaker_Development/pot/Revision_History.pot index 0a9aa32f12..66ca5f9801 100644 --- a/doc/Pacemaker_Development/pot/Revision_History.pot +++ b/doc/Pacemaker_Development/pot/Revision_History.pot @@ -1,39 +1,39 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Revision History" msgstr "" #. Tag: firstname #, no-c-format msgid "Ken" msgstr "" #. Tag: surname #, no-c-format msgid "Gaillot" msgstr "" #. Tag: member #, no-c-format msgid "Convert coding guidelines and developer FAQ to Publican document" msgstr "" #. Tag: member #, no-c-format msgid "Add Python coding guidelines, and more about licensing" msgstr "" diff --git a/doc/Pacemaker_Explained/en-US/Book_Info.xml b/doc/Pacemaker_Explained/en-US/Book_Info.xml index ae4f45a6a3..0d9d73c5ca 100644 --- a/doc/Pacemaker_Explained/en-US/Book_Info.xml +++ b/doc/Pacemaker_Explained/en-US/Book_Info.xml @@ -1,35 +1,35 @@ Configuration Explained An A-Z guide to Pacemaker's Configuration Options Pacemaker 1.1 - 9 + 10 0 The purpose of this document is to definitively explain the concepts used to configure Pacemaker. To achieve this, it will focus exclusively on the XML syntax used to configure Pacemaker's Cluster Information Base (CIB). diff --git a/doc/Pacemaker_Explained/en-US/Ch-Advanced-Resources.txt b/doc/Pacemaker_Explained/en-US/Ch-Advanced-Resources.txt index e9846c06c6..46a291ba8b 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Advanced-Resources.txt +++ b/doc/Pacemaker_Explained/en-US/Ch-Advanced-Resources.txt @@ -1,1522 +1,1522 @@ = Advanced Resource Types = [[group-resources]] == Groups - A Syntactic Shortcut == indexterm:[Group Resources] indexterm:[Resource,Groups] One of the most common elements of a cluster is a set of resources that need to be located together, start sequentially, and stop in the reverse order. To simplify this configuration, we support the concept of groups. .A group of two primitive resources ====== [source,XML] ------- ------- ====== Although the example above contains only two resources, there is no limit to the number of resources a group can contain. The example is also sufficient to explain the fundamental properties of a group: * Resources are started in the order they appear in (+Public-IP+ first, then +Email+) * Resources are stopped in the reverse order to which they appear in (+Email+ first, then +Public-IP+) If a resource in the group can't run anywhere, then nothing after that is allowed to run, too. * If +Public-IP+ can't run anywhere, neither can +Email+; * but if +Email+ can't run anywhere, this does not affect +Public-IP+ in any way The group above is logically equivalent to writing: .How the cluster sees a group resource ====== [source,XML] ------- ------- ====== Obviously as the group grows bigger, the reduced configuration effort can become significant. Another (typical) example of a group is a DRBD volume, the filesystem mount, an IP address, and an application that uses them. === Group Properties === .Properties of a Group Resource [width="95%",cols="3m,5<",options="header",align="center"] |========================================================= |Field |Description |id |A unique name for the group indexterm:[id,Group Resource Property] indexterm:[Resource,Group Property,id] |========================================================= === Group Options === Groups inherit the +priority+, +target-role+, and +is-managed+ properties from primitive resources. See <> for information about those properties. === Group Instance Attributes === Groups have no instance attributes. However, any that are set for the group object will be inherited by the group's children. === Group Contents === Groups may only contain a collection of cluster resources (see <>). To refer to a child of a group resource, just use the child's +id+ instead of the group's. === Group Constraints === Although it is possible to reference a group's children in constraints, it is usually preferable to reference the group itself. .Some constraints involving groups ====== [source,XML] ------- ------- ====== === Group Stickiness === indexterm:[resource-stickiness,Groups] Stickiness, the measure of how much a resource wants to stay where it is, is additive in groups. Every active resource of the group will contribute its stickiness value to the group's total. So if the default +resource-stickiness+ is 100, and a group has seven members, five of which are active, then the group as a whole will prefer its current location with a score of 500. [[s-resource-clone]] == Clones - Resources That Get Active on Multiple Hosts == indexterm:[Clone Resources] indexterm:[Resource,Clones] Clones were initially conceived as a convenient way to start multiple instances of an IP address resource and have them distributed throughout the cluster for load balancing. They have turned out to quite useful for a number of purposes including integrating with the Distributed Lock Manager (used by many cluster filesystems), the fencing subsystem, and OCFS2. You can clone any resource, provided the resource agent supports it. Three types of cloned resources exist: * Anonymous * Globally unique * Stateful 'Anonymous' clones are the simplest. These behave completely identically everywhere they are running. Because of this, there can be only one copy of an anonymous clone active per machine. 'Globally unique' clones are distinct entities. A copy of the clone running on one machine is not equivalent to another instance on another node, nor would any two copies on the same node be equivalent. 'Stateful' clones are covered later in <>. .A clone of an LSB resource ====== [source,XML] ------- ------- ====== === Clone Properties === .Properties of a Clone Resource [width="95%",cols="3m,5<",options="header",align="center"] |========================================================= |Field |Description |id |A unique name for the clone indexterm:[id,Clone Property] indexterm:[Clone,Property,id] |========================================================= === Clone Options === Options inherited from <> resources: +priority, target-role, is-managed+ .Clone-specific configuration options [width="95%",cols="1m,1,3<",options="header",align="center"] |========================================================= |Field |Default |Description |clone-max |number of nodes in cluster |How many copies of the resource to start indexterm:[clone-max,Clone Option] indexterm:[Clone,Option,clone-max] |clone-node-max |1 |How many copies of the resource can be started on a single node indexterm:[clone-node-max,Clone Option] indexterm:[Clone,Option,clone-node-max] |clone-min |1 |Require at least this number of clone instances to be runnable before allowing resources depending on the clone to be runnable '(since 1.1.14)' indexterm:[clone-min,Clone Option] indexterm:[Clone,Option,clone-min] |notify |true |When stopping or starting a copy of the clone, tell all the other copies beforehand and again when the action was successful. Allowed values: +false+, +true+ indexterm:[notify,Clone Option] indexterm:[Clone,Option,notify] |globally-unique |false |Does each copy of the clone perform a different function? Allowed values: +false+, +true+ indexterm:[globally-unique,Clone Option] indexterm:[Clone,Option,globally-unique] |ordered |false |Should the copies be started in series (instead of in parallel)? Allowed values: +false+, +true+ indexterm:[ordered,Clone Option] indexterm:[Clone,Option,ordered] |interleave |false |If this clone depends on another clone via an ordering constraint, is it allowed to start after the local instance of the other clone starts, rather than wait for all instances of the other clone to start? Allowed values: +false+, +true+ indexterm:[interleave,Clone Option] indexterm:[Clone,Option,interleave] |========================================================= === Clone Instance Attributes === Clones have no instance attributes; however, any that are set here will be inherited by the clone's children. === Clone Contents === Clones must contain exactly one primitive or group resource. [WARNING] You should never reference the name of a clone's child. If you think you need to do this, you probably need to re-evaluate your design. === Clone Constraints === In most cases, a clone will have a single copy on each active cluster node. If this is not the case, you can indicate which nodes the cluster should preferentially assign copies to with resource location constraints. These constraints are written no differently from those for primitive resources except that the clone's +id+ is used. .Some constraints involving clones ====== [source,XML] ------- ------- ====== Ordering constraints behave slightly differently for clones. In the example above, +apache-stats+ will wait until all copies of +apache-clone+ that need to be started have done so before being started itself. Only if _no_ copies can be started will +apache-stats+ be prevented from being active. Additionally, the clone will wait for +apache-stats+ to be stopped before stopping itself. Colocation of a primitive or group resource with a clone means that the resource can run on any machine with an active copy of the clone. The cluster will choose a copy based on where the clone is running and the resource's own location preferences. Colocation between clones is also possible. If one clone +A+ is colocated with another clone +B+, the set of allowed locations for +A+ is limited to nodes on which +B+ is (or will be) active. Placement is then performed normally. [[s-clone-stickiness]] === Clone Stickiness === indexterm:[resource-stickiness,Clones] To achieve a stable allocation pattern, clones are slightly sticky by default. If no value for +resource-stickiness+ is provided, the clone will use a value of 1. Being a small value, it causes minimal disturbance to the score calculations of other resources but is enough to prevent Pacemaker from needlessly moving copies around the cluster. [NOTE] ==== For globally unique clones, this may result in multiple instances of the clone staying on a single node, even after another eligible node becomes active (for example, after being put into standby mode then made active again). If you do not want this behavior, specify a +resource-stickiness+ of 0 for the clone temporarily and let the cluster adjust, then set it back to 1 if you want the default behavior to apply again. ==== === Clone Resource Agent Requirements === Any resource can be used as an anonymous clone, as it requires no additional support from the resource agent. Whether it makes sense to do so depends on your resource and its resource agent. Globally unique clones do require some additional support in the resource agent. In particular, it must only respond with +$\{OCF_SUCCESS}+ if the node has that exact instance active. All other probes for instances of the clone should result in +$\{OCF_NOT_RUNNING}+ (or one of the other OCF error codes if they are failed). Individual instances of a clone are identified by appending a colon and a numerical offset, e.g. +apache:2+. Resource agents can find out how many copies there are by examining the +OCF_RESKEY_CRM_meta_clone_max+ environment variable and which copy it is by examining +OCF_RESKEY_CRM_meta_clone+. The resource agent must not make any assumptions (based on +OCF_RESKEY_CRM_meta_clone+) about which numerical instances are active. In particular, the list of active copies will not always be an unbroken sequence, nor always start at 0. ==== Clone Notifications ==== Supporting notifications requires the +notify+ action to be implemented. If supported, the notify action will be passed a number of extra variables which, when combined with additional context, can be used to calculate the current state of the cluster and what is about to happen to it. .Environment variables supplied with Clone notify actions [width="95%",cols="5,3<",options="header",align="center"] |========================================================= |Variable |Description |OCF_RESKEY_CRM_meta_notify_type |Allowed values: +pre+, +post+ indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,type] indexterm:[type,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_operation |Allowed values: +start+, +stop+ indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,operation] indexterm:[operation,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_start_resource |Resources to be started indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,start_resource] indexterm:[start_resource,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_stop_resource |Resources to be stopped indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,stop_resource] indexterm:[stop_resource,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_active_resource |Resources that are running indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,active_resource] indexterm:[active_resource,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_inactive_resource |Resources that are not running indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,inactive_resource] indexterm:[inactive_resource,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_start_uname |Nodes on which resources will be started indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,start_uname] indexterm:[start_uname,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_stop_uname |Nodes on which resources will be stopped indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,stop_uname] indexterm:[stop_uname,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_active_uname |Nodes on which resources are running indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,active_uname] indexterm:[active_uname,Notification Environment Variable] |========================================================= The variables come in pairs, such as +OCF_RESKEY_CRM_meta_notify_start_resource+ and +OCF_RESKEY_CRM_meta_notify_start_uname+ and should be treated as an array of whitespace-separated elements. +OCF_RESKEY_CRM_meta_notify_inactive_resource+ is an exception as the matching +uname+ variable does not exist since inactive resources are not running on any node. Thus in order to indicate that +clone:0+ will be started on +sles-1+, +clone:2+ will be started on +sles-3+, and +clone:3+ will be started on +sles-2+, the cluster would set .Notification variables ====== [source,Bash] ------- OCF_RESKEY_CRM_meta_notify_start_resource="clone:0 clone:2 clone:3" OCF_RESKEY_CRM_meta_notify_start_uname="sles-1 sles-3 sles-2" ------- ====== ==== Proper Interpretation of Notification Environment Variables ==== .Pre-notification (stop): * Active resources: +$OCF_RESKEY_CRM_meta_notify_active_resource+ * Inactive resources: +$OCF_RESKEY_CRM_meta_notify_inactive_resource+ * Resources to be started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources to be stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ .Post-notification (stop) / Pre-notification (start): * Active resources ** +$OCF_RESKEY_CRM_meta_notify_active_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * Inactive resources ** +$OCF_RESKEY_CRM_meta_notify_inactive_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * Resources that were started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources that were stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ .Post-notification (start): * Active resources: ** +$OCF_RESKEY_CRM_meta_notify_active_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Inactive resources: ** +$OCF_RESKEY_CRM_meta_notify_inactive_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources that were started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources that were stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ [[s-resource-multistate]] == Multi-state - Resources That Have Multiple Modes == indexterm:[Multi-state Resources] indexterm:[Resource,Multi-state] Multi-state resources are a specialization of clone resources; please ensure you understand <> before continuing! Multi-state resources allow the instances to be in one of two operating modes (called 'roles'). The roles are called 'master' and 'slave', but can mean whatever you wish them to mean. The only limitation is that when an instance is started, it must come up in the slave role. === Multi-state Properties === .Properties of a Multi-State Resource [width="95%",cols="3m,5<",options="header",align="center"] |========================================================= |Field |Description |id |Your name for the multi-state resource indexterm:[id,Multi-State Property] indexterm:[Multi-State,Property,id] |========================================================= === Multi-state Options === Options inherited from <> resources: +priority+, +target-role+, +is-managed+ Options inherited from <> resources: +clone-max+, +clone-node-max+, +notify+, +globally-unique+, +ordered+, +interleave+ .Multi-state-specific resource configuration options [width="95%",cols="1m,1,3<",options="header",align="center"] |========================================================= |Field |Default |Description |master-max |1 |How many copies of the resource can be promoted to the +master+ role indexterm:[master-max,Multi-State Option] indexterm:[Multi-State,Option,master-max] |master-node-max |1 |How many copies of the resource can be promoted to the +master+ role on a single node indexterm:[master-node-max,Multi-State Option] indexterm:[Multi-State,Option,master-node-max] |========================================================= === Multi-state Instance Attributes === Multi-state resources have no instance attributes; however, any that are set here will be inherited by a master's children. === Multi-state Contents === Masters must contain exactly one primitive or group resource. [WARNING] You should never reference the name of a master's child. If you think you need to do this, you probably need to re-evaluate your design. === Monitoring Multi-State Resources === The usual monitor actions are insufficient to monitor a multi-state resource, because pacemaker needs to verify not only that the resource is active, but also that its actual role matches its intended one. Define two monitoring actions: the usual one will cover the slave role, and an additional one with +role="master"+ will cover the master role. .Monitoring both states of a multi-state resource ====== [source,XML] ------- ------- ====== [IMPORTANT] =========== It is crucial that _every_ monitor operation has a different interval! Pacemaker currently differentiates between operations only by resource and interval; so if (for example) a master/slave resource had the same monitor interval for both roles, Pacemaker would ignore the role when checking the status -- which would cause unexpected return codes, and therefore unnecessary complications. =========== === Multi-state Constraints === In most cases, multi-state resources will have a single copy on each active cluster node. If this is not the case, you can indicate which nodes the cluster should preferentially assign copies to with resource location constraints. These constraints are written no differently from those for primitive resources except that the master's +id+ is used. When considering multi-state resources in constraints, for most purposes it is sufficient to treat them as clones. The exception is that the +first-action+ and/or +then-action+ fields for ordering constraints may be set to +promote+ or +demote+ to constrain the master role, and colocation constraints may contain +rsc-role+ and/or +with-rsc-role+ fields. .Additional colocation constraint options for multi-state resources [width="95%",cols="1m,1,3<",options="header",align="center"] |========================================================= |Field |Default |Description |rsc-role |Started |An additional attribute of colocation constraints that specifies the role that +rsc+ must be in. Allowed values: +Started+, +Master+, +Slave+. indexterm:[rsc-role,Ordering Constraints] indexterm:[Constraints,Ordering,rsc-role] |with-rsc-role |Started |An additional attribute of colocation constraints that specifies the role that +with-rsc+ must be in. Allowed values: +Started+, +Master+, +Slave+. indexterm:[with-rsc-role,Ordering Constraints] indexterm:[Constraints,Ordering,with-rsc-role] |========================================================= .Constraints involving multi-state resources ====== [source,XML] ------- ------- ====== In the example above, +myApp+ will wait until one of the database copies has been started and promoted to master before being started itself on the same node. Only if no copies can be promoted will +myApp+ be prevented from being active. Additionally, the cluster will wait for +myApp+ to be stopped before demoting the database. Colocation of a primitive or group resource with a multi-state resource means that it can run on any machine with an active copy of the multi-state resource that has the specified role (+master+ or +slave+). In the example above, the cluster will choose a location based on where database is running as a +master+, and if there are multiple +master+ instances it will also factor in +myApp+'s own location preferences when deciding which location to choose. Colocation with regular clones and other multi-state resources is also possible. In such cases, the set of allowed locations for the +rsc+ clone is (after role filtering) limited to nodes on which the +with-rsc+ multi-state resource is (or will be) in the specified role. Placement is then performed as normal. ==== Using Multi-state Resources in Colocation Sets ==== .Additional colocation set options relevant to multi-state resources [width="95%",cols="1m,1,6<",options="header",align="center"] |========================================================= |Field |Default |Description |role |Started |The role that 'all members' of the set must be in. Allowed values: +Started+, +Master+, +Slave+. indexterm:[role,Ordering Constraints] indexterm:[Constraints,Ordering,role] |========================================================= In the following example +B+'s master must be located on the same node as +A+'s master. Additionally resources +C+ and +D+ must be located on the same node as +A+'s and +B+'s masters. .Colocate C and D with A's and B's master instances ====== [source,XML] ------- ------- ====== ==== Using Multi-state Resources in Ordering Sets ==== .Additional ordered set options relevant to multi-state resources [width="95%",cols="1m,1,3<",options="header",align="center"] |========================================================= |Field |Default |Description |action |value of +first-action+ |An additional attribute of ordering constraint sets that specifies the action that applies to 'all members' of the set. Allowed values: +start+, +stop+, +promote+, +demote+. indexterm:[action,Ordering Constraints] indexterm:[Constraints,Ordering,action] |========================================================= .Start C and D after first promoting A and B ====== [source,XML] ------- ------- ====== In the above example, +B+ cannot be promoted to a master role until +A+ has been promoted. Additionally, resources +C+ and +D+ must wait until +A+ and +B+ have been promoted before they can start. === Multi-state Stickiness === indexterm:[resource-stickiness,Multi-State] As with regular clones, multi-state resources are slightly sticky by default. See <> for details. [[s-master-scores]] === Which Resource Instance is Promoted === During the start operation, most resource agents should call the `crm_master` utility. This tool automatically detects both the resource and host and should be used to set a preference for being promoted. Based on this, +master-max+, and +master-node-max+, the instance(s) with the highest preference will be promoted. An alternative is to create a location constraint that indicates which nodes are most preferred as masters. .Explicitly preferring node1 to be promoted to master ====== [source,XML] ------- ------- ====== === Requirements for Multi-state Resource Agents === Since multi-state resources are an extension of cloned resources, all the requirements for resource agents that support clones are also requirements for resource agents that support multi-state resources. Additionally, multi-state resources require two extra actions, +demote+ and +promote+, which are responsible for changing the state of the resource. Like +start+ and +stop+, they should return +$\{OCF_SUCCESS}+ if they completed successfully or a relevant error code if they did not. The states can mean whatever you wish, but when the resource is started, it must come up in the mode called +slave+. From there the cluster will decide which instances to promote to +master+. In addition to the clone requirements for monitor actions, agents must also _accurately_ report which state they are in. The cluster relies on the agent to report its status (including role) accurately and does not indicate to the agent what role it currently believes it to be in. .Role implications of OCF return codes [width="95%",cols="1,1<",options="header",align="center"] |========================================================= |Monitor Return Code |Description |OCF_NOT_RUNNING |Stopped indexterm:[Return Code,OCF_NOT_RUNNING] |OCF_SUCCESS |Running (Slave) indexterm:[Return Code,OCF_SUCCESS] |OCF_RUNNING_MASTER |Running (Master) indexterm:[Return Code,OCF_RUNNING_MASTER] |OCF_FAILED_MASTER |Failed (Master) indexterm:[Return Code,OCF_FAILED_MASTER] |Other |Failed (Slave) |========================================================= ==== Multi-state Notifications ==== Like clones, supporting notifications requires the +notify+ action to be implemented. If supported, the notify action will be passed a number of extra variables which, when combined with additional context, can be used to calculate the current state of the cluster and what is about to happen to it. .Environment variables supplied with multi-state notify actions footnote:[Emphasized variables are specific to +Master+ resources, and all behave in the same manner as described for Clone resources.] [width="95%",cols="5,3<",options="header",align="center"] |========================================================= |Variable |Description |OCF_RESKEY_CRM_meta_notify_type |Allowed values: +pre+, +post+ indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,type] indexterm:[type,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_operation |Allowed values: +start+, +stop+ indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,operation] indexterm:[operation,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_active_resource |Resources that are running indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,active_resource] indexterm:[active_resource,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_inactive_resource |Resources that are not running indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,inactive_resource] indexterm:[inactive_resource,Notification Environment Variable] |_OCF_RESKEY_CRM_meta_notify_master_resource_ |Resources that are running in +Master+ mode indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,master_resource] indexterm:[master_resource,Notification Environment Variable] |_OCF_RESKEY_CRM_meta_notify_slave_resource_ |Resources that are running in +Slave+ mode indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,slave_resource] indexterm:[slave_resource,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_start_resource |Resources to be started indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,start_resource] indexterm:[start_resource,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_stop_resource |Resources to be stopped indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,stop_resource] indexterm:[stop_resource,Notification Environment Variable] |_OCF_RESKEY_CRM_meta_notify_promote_resource_ |Resources to be promoted indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,promote_resource] indexterm:[promote_resource,Notification Environment Variable] |_OCF_RESKEY_CRM_meta_notify_demote_resource_ |Resources to be demoted indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,demote_resource] indexterm:[demote_resource,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_start_uname |Nodes on which resources will be started indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,start_uname] indexterm:[start_uname,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_stop_uname |Nodes on which resources will be stopped indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,stop_uname] indexterm:[stop_uname,Notification Environment Variable] |_OCF_RESKEY_CRM_meta_notify_promote_uname_ |Nodes on which resources will be promoted indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,promote_uname] indexterm:[promote_uname,Notification Environment Variable] |_OCF_RESKEY_CRM_meta_notify_demote_uname_ |Nodes on which resources will be demoted indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,demote_uname] indexterm:[demote_uname,Notification Environment Variable] |OCF_RESKEY_CRM_meta_notify_active_uname |Nodes on which resources are running indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,active_uname] indexterm:[active_uname,Notification Environment Variable] |_OCF_RESKEY_CRM_meta_notify_master_uname_ |Nodes on which resources are running in +Master+ mode indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,master_uname] indexterm:[master_uname,Notification Environment Variable] |_OCF_RESKEY_CRM_meta_notify_slave_uname_ |Nodes on which resources are running in +Slave+ mode indexterm:[Environment Variable,OCF_RESKEY_CRM_meta_notify_,slave_uname] indexterm:[slave_uname,Notification Environment Variable] |========================================================= ==== Proper Interpretation of Multi-state Notification Environment Variables ==== .Pre-notification (demote): * +Active+ resources: +$OCF_RESKEY_CRM_meta_notify_active_resource+ * +Master+ resources: +$OCF_RESKEY_CRM_meta_notify_master_resource+ * +Slave+ resources: +$OCF_RESKEY_CRM_meta_notify_slave_resource+ * Inactive resources: +$OCF_RESKEY_CRM_meta_notify_inactive_resource+ * Resources to be started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources to be promoted: +$OCF_RESKEY_CRM_meta_notify_promote_resource+ * Resources to be demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * Resources to be stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ .Post-notification (demote) / Pre-notification (stop): * +Active+ resources: +$OCF_RESKEY_CRM_meta_notify_active_resource+ * +Master+ resources: ** +$OCF_RESKEY_CRM_meta_notify_master_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * +Slave+ resources: +$OCF_RESKEY_CRM_meta_notify_slave_resource+ * Inactive resources: +$OCF_RESKEY_CRM_meta_notify_inactive_resource+ * Resources to be started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources to be promoted: +$OCF_RESKEY_CRM_meta_notify_promote_resource+ * Resources to be demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * Resources to be stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * Resources that were demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ .Post-notification (stop) / Pre-notification (start) * +Active+ resources: ** +$OCF_RESKEY_CRM_meta_notify_active_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * +Master+ resources: ** +$OCF_RESKEY_CRM_meta_notify_master_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * +Slave+ resources: ** +$OCF_RESKEY_CRM_meta_notify_slave_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * Inactive resources: ** +$OCF_RESKEY_CRM_meta_notify_inactive_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * Resources to be started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources to be promoted: +$OCF_RESKEY_CRM_meta_notify_promote_resource+ * Resources to be demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * Resources to be stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * Resources that were demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * Resources that were stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ .Post-notification (start) / Pre-notification (promote) * +Active+ resources: ** +$OCF_RESKEY_CRM_meta_notify_active_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_start_resource+ * +Master+ resources: ** +$OCF_RESKEY_CRM_meta_notify_master_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * +Slave+ resources: ** +$OCF_RESKEY_CRM_meta_notify_slave_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Inactive resources: ** +$OCF_RESKEY_CRM_meta_notify_inactive_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources to be started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources to be promoted: +$OCF_RESKEY_CRM_meta_notify_promote_resource+ * Resources to be demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * Resources to be stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * Resources that were started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources that were demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * Resources that were stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ .Post-notification (promote) * +Active+ resources: ** +$OCF_RESKEY_CRM_meta_notify_active_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_start_resource+ * +Master+ resources: ** +$OCF_RESKEY_CRM_meta_notify_master_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_demote_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_promote_resource+ * +Slave+ resources: ** +$OCF_RESKEY_CRM_meta_notify_slave_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_start_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_promote_resource+ * Inactive resources: ** +$OCF_RESKEY_CRM_meta_notify_inactive_resource+ ** plus +$OCF_RESKEY_CRM_meta_notify_stop_resource+ ** minus +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources to be started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources to be promoted: +$OCF_RESKEY_CRM_meta_notify_promote_resource+ * Resources to be demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * Resources to be stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ * Resources that were started: +$OCF_RESKEY_CRM_meta_notify_start_resource+ * Resources that were promoted: +$OCF_RESKEY_CRM_meta_notify_promote_resource+ * Resources that were demoted: +$OCF_RESKEY_CRM_meta_notify_demote_resource+ * Resources that were stopped: +$OCF_RESKEY_CRM_meta_notify_stop_resource+ [[s-resource-bundle]] == Bundles - Isolated Environments == indexterm:[bundle] indexterm:[Resource,bundle] indexterm:[Docker,bundle] indexterm:[rkt,bundle] Pacemaker supports a special syntax for launching a https://en.wikipedia.org/wiki/Operating-system-level_virtualization[container] with any infrastructure it requires: the 'bundle'. Pacemaker bundles support https://www.docker.com/[Docker] (since version -1.1.17) and https://coreos.com/rkt/[rkt] (coming in version 1.1.18) container +1.1.17) and https://coreos.com/rkt/[rkt] (since version 1.1.18) container technologies. footnote:[Docker is a trademark of Docker, Inc. No endorsement by or association with Docker, Inc. is implied.] .A bundle for a containerized web server ==== [source,XML] ---- ---- ==== === Bundle Properties === .Properties of a Bundle [width="95%",cols="3m,5<",options="header",align="center"] |========================================================= |Field |Description |id |A unique name for the bundle (required) indexterm:[id,bundle] indexterm:[bundle,Property,id] |description |Arbitrary text (not used by Pacemaker) indexterm:[description,bundle] indexterm:[bundle,Property,description] |========================================================= A bundle must contain exactly one ++ or ++ element. === Docker Properties === Before configuring a Docker bundle in Pacemaker, the user must install Docker and supply a fully configured Docker image on every node allowed to run the bundle. Pacemaker will create an implicit +ocf:heartbeat:docker+ resource to manage a bundle's Docker container. The user must ensure that resource agent is installed on every node allowed to run the bundle. .Properties of a Bundle's Docker Element [width="95%",cols="3m,4,5<",options="header",align="center"] |========================================================= |Field |Default |Description |image | |Docker image tag (required) indexterm:[image,Docker] indexterm:[Docker,Property,image] |replicas |Value of +masters+ if that is positive, else 1 |A positive integer specifying the number of container instances to launch indexterm:[replicas,Docker] indexterm:[Docker,Property,replicas] |replicas-per-host |1 |A positive integer specifying the number of container instances allowed to run on a single node indexterm:[replicas-per-host,Docker] indexterm:[Docker,Property,replicas-per-host] |masters |0 |A non-negative integer that, if positive, indicates that the containerized service should be treated as a multistate service, with this many replicas allowed to run the service in the master role indexterm:[masters,Docker] indexterm:[Docker,Property,masters] |network | |If specified, this will be passed to +docker run+ as the https://docs.docker.com/engine/reference/run/#network-settings[network setting] for the Docker container. indexterm:[network,Docker] indexterm:[Docker,Property,network] |run-command |`/usr/sbin/pacemaker_remoted` if bundle contains a +primitive+, otherwise none |This command will be run inside the container when launching it ("PID 1"). If the bundle contains a +primitive+, this command 'must' start pacemaker_remoted (but could, for example, be a script that does other stuff, too). indexterm:[run-command,Docker] indexterm:[Docker,Property,run-command] |options | |Extra command-line options to pass to `docker run` indexterm:[options,Docker] indexterm:[Docker,Property,options] |========================================================= === rkt Properties === Before configuring a rkt bundle in Pacemaker, the user must install rkt and supply a fully configured container image on every node allowed to run the bundle. Pacemaker will create an implicit +ocf:heartbeat:rkt+ resource to manage a bundle's rkt container. The user must ensure that resource agent is installed on every node allowed to run the bundle. .Properties of a Bundle's rkt Element [width="95%",cols="3m,4,5<",options="header",align="center"] |========================================================= |Field |Default |Description |image | |Container image tag (required) indexterm:[image,rkt] indexterm:[rkt,Property,image] |replicas |Value of +masters+ if that is positive, else 1 |A positive integer specifying the number of container instances to launch indexterm:[replicas,rkt] indexterm:[rkt,Property,replicas] |replicas-per-host |1 |A positive integer specifying the number of container instances allowed to run on a single node indexterm:[replicas-per-host,rkt] indexterm:[rkt,Property,replicas-per-host] |masters |0 |A non-negative integer that, if positive, indicates that the containerized service should be treated as a multistate service, with this many replicas allowed to run the service in the master role indexterm:[masters,rkt] indexterm:[rkt,Property,masters] |network | |If specified, this will be passed to +rkt run+ as the network setting for the rkt container. indexterm:[network,rkt] indexterm:[rkt,Property,network] |run-command |`/usr/sbin/pacemaker_remoted` if bundle contains a +primitive+, otherwise none |This command will be run inside the container when launching it ("PID 1"). If the bundle contains a +primitive+, this command 'must' start pacemaker_remoted (but could, for example, be a script that does other stuff, too). indexterm:[run-command,rkt] indexterm:[rkt,Property,run-command] |options | |Extra command-line options to pass to `rkt run` indexterm:[options,rkt] indexterm:[rkt,Property,options] |========================================================= === Bundle Network Properties === A bundle may optionally contain one ++ element. indexterm:[bundle,network] .Properties of a Bundle's Network Element [width="95%",cols="2m,1,4<",options="header",align="center"] |========================================================= |Field |Default |Description |ip-range-start | |If specified, Pacemaker will create an implicit +ocf:heartbeat:IPaddr2+ resource for each container instance, starting with this IP address, using up to +replicas+ sequential addresses. These addresses can be used from the host's network to reach the service inside the container, though it is not visible within the container itself. Only IPv4 addresses are currently supported. indexterm:[ip-range-start,network] indexterm:[network,Property,ip-range-start] |host-netmask |32 |If +ip-range-start+ is specified, the IP addresses are created with this CIDR netmask (as a number of bits). indexterm:[host-netmask,network] indexterm:[network,Property,host-netmask] |host-interface | |If +ip-range-start+ is specified, the IP addresses are created on this host interface (by default, it will be determined from the IP address). indexterm:[host-interface,network] indexterm:[network,Property,host-interface] |control-port |3121 |If the bundle contains a +primitive+, the cluster will use this integer TCP port for communication with Pacemaker Remote inside the container. Changing this is useful when the container is unable to listen on the default port, for example, when the container uses the host's network rather than +ip-range-start+ (in which case +replicas-per-host+ must be 1), or when the bundle may run on a Pacemaker Remote node that is already listening on the default port. Any PCMK_remote_port environment variable set on the host or in the container is ignored for bundle connections. indexterm:[control-port,network] indexterm:[network,Property,control-port] |========================================================= [[s-resource-bundle-note-replica-names]] [NOTE] ==== If +ip-range-start+ is used, Pacemaker will automatically ensure that +/etc/hosts+ inside the containers has entries for each replica and its assigned IP. Replicas are named by the bundle id plus a dash and an integer counter starting with zero. For example, if a bundle named +httpd-bundle+ has +replicas=2+, its containers will be named +httpd-bundle-0+ and +httpd-bundle-1+. ==== Additionally, a ++ element may optionally contain one or more ++ elements. indexterm:[bundle,network,port-mapping] .Properties of a Bundle's Port-Mapping Element [width="95%",cols="2m,1,4<",options="header",align="center"] |========================================================= |Field |Default |Description |id | |A unique name for the port mapping (required) indexterm:[id,port-mapping] indexterm:[port-mapping,Property,id] |port | |If this is specified, connections to this TCP port number on the host network (on the container's assigned IP address, if +ip-range-start+ is specified) will be forwarded to the container network. Exactly one of +port+ or +range+ must be specified in a +port-mapping+. indexterm:[port,port-mapping] indexterm:[port-mapping,Property,port] |internal-port |value of +port+ |If +port+ and this are specified, connections to +port+ on the host's network will be forwarded to this port on the container network. indexterm:[internal-port,port-mapping] indexterm:[port-mapping,Property,internal-port] |range | |If this is specified, connections to these TCP port numbers (expressed as 'first_port'-'last_port') on the host network (on the container's assigned IP address, if +ip-range-start+ is specified) will be forwarded to the same ports in the container network. Exactly one of +port+ or +range+ must be specified in a +port-mapping+. indexterm:[range,port-mapping] indexterm:[port-mapping,Property,range] |========================================================= [NOTE] ==== If the bundle contains a +primitive+, Pacemaker will automatically map the +control-port+, so it is not necessary to specify that port in a +port-mapping+. ==== === Bundle Storage Properties === A bundle may optionally contain one ++ element. A ++ element has no properties of its own, but may contain one or more ++ elements. indexterm:[bundle,storage,storage-mapping] .Properties of a Bundle's Storage-Mapping Element [width="95%",cols="2m,1,4<",options="header",align="center"] |========================================================= |Field |Default |Description |id | |A unique name for the storage mapping (required) indexterm:[id,storage-mapping] indexterm:[storage-mapping,Property,id] |source-dir | |The absolute path on the host's filesystem that will be mapped into the container. Exactly one of +source-dir+ and +source-dir-root+ must be specified in a +storage-mapping+. indexterm:[source-dir,storage-mapping] indexterm:[storage-mapping,Property,source-dir] |source-dir-root | |The start of a path on the host's filesystem that will be mapped into the container, using a different subdirectory on the host for each container instance. The subdirectory will be named the same as the bundle host name, as described in <>. Exactly one of +source-dir+ and +source-dir-root+ must be specified in a +storage-mapping+. indexterm:[source-dir-root,storage-mapping] indexterm:[storage-mapping,Property,source-dir-root] |target-dir | |The path name within the container where the host storage will be mapped (required) indexterm:[target-dir,storage-mapping] indexterm:[storage-mapping,Property,target-dir] |options | |File system mount options to use when mapping the storage indexterm:[options,storage-mapping] indexterm:[storage-mapping,Property,options] |========================================================= [NOTE] ==== Pacemaker does not define the behavior if the source directory does not already exist on the host. However, it is expected that the container technology and/or its resource agent will create the source directory in that case. ==== [NOTE] ==== If the bundle contains a +primitive+, Pacemaker will automatically map the equivalent of +source-dir=/etc/pacemaker/authkey target-dir=/etc/pacemaker/authkey+ and +source-dir-root=/var/log/pacemaker/bundles target-dir=/var/log+ into the container, so it is not necessary to specify those paths in a +storage-mapping+. (If the DC node has the PCMK_authkey_location variable set, that will be used as the source instead of `/etc/pacemaker/authkey`; the value should be identical on all nodes, if used. The user should not set the PCMK_authkey_location environment variable inside the container.) ==== === Bundle Primitive === A bundle may optionally contain one ++ resource (see <>). The primitive may have operations, instance attributes and meta-attributes defined, as usual. If a bundle contains a primitive resource, the container image must include the Pacemaker Remote daemon, and at least one of +ip-range-start+ or +control-port+ must be configured in the bundle. Pacemaker will create an implicit +ocf:pacemaker:remote+ resource for the connection, launch Pacemaker Remote within the container, and monitor and manage the primitive resource via Pacemaker Remote. If the bundle has more than one container instance (replica), the primitive resource will function as an implicit clone (see <>) -- a multistate clone if the bundle has +masters+ greater than zero (see <>). [IMPORTANT] ==== Containers in bundles with a +primitive+ must have an accessible networking environment, so that Pacemaker on the cluster nodes can contact Pacemaker Remote inside the container. For example, the Docker option `--net=none` should not be used with a +primitive+. The default (using a distinct network space inside the container) works in combination with +ip-range-start+. If the Docker option `--net=host` is used (making the container share the host's network space), a unique +control-port+ should be specified for each bundle. Any firewall must allow access to the +control-port+. ==== [[s-bundle-attributes]] === Bundle Node Attributes === If the bundle has a +primitive+, the primitive's resource agent may want to set node attributes such as <>. However, with containers, it is not apparent which node should get the attribute. If the container uses shared storage that is the same no matter which node the container is hosted on, then it is appropriate to use the master score on the bundle node itself. On the other hand, if the container uses storage exported from the underlying host, then it may be more appropriate to use the master score on the underlying host. Since this depends on the particular situation, the +container-attribute-target+ resource meta-attribute allows the user to specify which approach to use. If it is set to +host+, then user-defined node attributes will be checked on the underlying host. If it is anything else, the local node (in this case the bundle node) is used as usual. This only applies to user-defined attributes; the cluster will always check the local node for cluster-defined attributes such as +#uname+. If +container-attribute-target+ is +host+, the cluster will pass additional environment variables to the primitive's resource agent that allow it to set node attributes appropriately: +container_attribute_target+ (identical to the meta-attribute value) and +physical_host+ (the name of the underlying host). [NOTE] ==== It is up to the resource agent to check for the additional variables and use them when setting node attributes. ==== === Bundle Meta-Attributes === Any meta-attribute set on a bundle will be inherited by the bundle's primitive and any resources implicitly created by Pacemaker for the bundle. This includes options such as +priority+, +target-role+, and +is-managed+. See <> for more information. === Limitations of Bundles === Bundle support is considered experimental. Cleaning up a running bundle, or restarting pacemaker while a bundle is unmanaged or the cluster is in maintenance mode, may cause the bundle to fail. The feature is believed to be otherwise production-ready as of version 1.1.18. Bundles may not be cloned or included in groups. This includes the bundle's primitive and any resources implicitly created by Pacemaker for the bundle. Bundles do not have instance attributes, utilization attributes, or operations, though a bundle's primitive may have them. A bundle with a primitive can run on a Pacemaker Remote node only if the bundle uses a distinct +control-port+. Interacting directly with any resource or guest node implicitly created by Pacemaker for the bundle is strongly discouraged and likely to cause problems. diff --git a/doc/Pacemaker_Explained/en-US/Ch-Alerts.txt b/doc/Pacemaker_Explained/en-US/Ch-Alerts.txt index 6185702525..d3d51deff6 100644 --- a/doc/Pacemaker_Explained/en-US/Ch-Alerts.txt +++ b/doc/Pacemaker_Explained/en-US/Ch-Alerts.txt @@ -1,407 +1,406 @@ = Alerts = //// We prefer [[ch-alerts]], but older versions of asciidoc don't deal well with that construct for chapter headings //// anchor:ch-alerts[Chapter 7, Alerts] indexterm:[Resource,Alerts] 'Alerts' (available since Pacemaker 1.1.15) may be configured to take some external action when a cluster event occurs (node failure, resource starting or stopping, etc.). == Alert Agents == As with resource agents, the cluster calls an external program (an 'alert agent') to handle alerts. The cluster passes information about the event to the agent via environment variables. Agents can do anything desired with this information (send an e-mail, log to a file, update a monitoring system, etc.). .Simple alert configuration ===== [source,XML] ----- ----- ===== In the example above, the cluster will call +my-script.sh+ for each event. Multiple alert agents may be configured; the cluster will call all of them for each event. Alert agents will be called only on cluster nodes. They will be called for events involving Pacemaker Remote nodes, but they will never be called _on_ those nodes. == Alert Recipients == Usually alerts are directed towards a recipient. Thus each alert may be additionally configured with one or more recipients. The cluster will call the agent separately for each recipient. .Alert configuration with recipient ===== [source,XML] ----- ----- ===== In the above example, the cluster will call +my-script.sh+ for each event, passing the recipient +some-address+ as an environment variable. The recipient may be anything the alert agent can recognize -- an IP address, an e-mail address, a file name, whatever the particular agent supports. == Alert Meta-Attributes == As with resource agents, meta-attributes can be configured for alert agents to affect how Pacemaker calls them. .Meta-Attributes of an Alert [width="95%",cols="m,1,2 ----- ===== In the above example, the +my-script.sh+ will get called twice for each event, with each call using a 15-second timeout. One call will be passed the recipient +someuser@example.com+ and a timestamp in the format +%D %H:%M+, while the other call will be passed the recipient +otheruser@example.com+ and a timestamp in the format +%c+. == Alert Instance Attributes == As with resource agents, agent-specific configuration values may be configured as instance attributes. These will be passed to the agent as additional environment variables. The number, names and allowed values of these instance attributes are completely up to the particular agent. .Alert configuration with instance attributes ===== [source,XML] ----- ----- ===== == Alert Filters == -'Coming in 1.1.18' - By default, an alert agent will be called for node events, fencing events, and resource events. An agent may choose to ignore certain types of events, but there is still the overhead of calling it for those events. To eliminate that -overhead, you may select which types of events the agent should receive. +overhead, you may select which types of events the agent should receive +(since version 1.1.18). .Alert configuration to receive only node events and fencing events ===== [source,XML] ----- ----- ===== The possible options within + ----- ===== Node attribute alerts are currently considered experimental. Alerts may be limited to attributes set via attrd_updater, and agents may be called multiple times with the same attribute value. == Using the Sample Alert Agents == Pacemaker provides several sample alert agents, installed in +/usr/share/pacemaker/alerts+ by default. While these sample scripts may be copied and used as-is, they are provided mainly as templates to be edited to suit your purposes. See their source code for the full set of instance attributes they support. .Sending cluster events as SNMP traps ===== [source,XML] ----- ----- ===== .Sending cluster events as e-mails ===== [source,XML] ----- ----- ===== == Writing an Alert Agent == .Environment variables passed to alert agents [width="95%",cols="m,2 Revision History 1-0 19 Oct 2009 AndrewBeekhofandrew@beekhof.net Import from Pages.app 2-0 26 Oct 2009 AndrewBeekhofandrew@beekhof.net Cleanup and reformatting of docbook xml complete 3-0 Tue Nov 12 2009 AndrewBeekhofandrew@beekhof.net Split book into chapters and pass validation Re-organize book for use with Publican 4-0 Mon Oct 8 2012 AndrewBeekhofandrew@beekhof.net Converted to asciidoc (which is converted to docbook for use with Publican) 5-0 Mon Feb 23 2015 KenGaillotkgaillot@redhat.com Update for clarity, stylistic consistency and current command-line syntax 6-0 Tue Dec 8 2015 KenGaillotkgaillot@redhat.com Update for Pacemaker 1.1.14 7-0 Tue May 3 2016 KenGaillotkgaillot@redhat.com Update for Pacemaker 1.1.15 7-1 Fri Oct 28 2016 KenGaillotkgaillot@redhat.com Overhaul upgrade documentation, and document node health strategies 8-0 Tue Oct 25 2016 KenGaillotkgaillot@redhat.com Update for Pacemaker 1.1.16 9-0 Tue Jul 11 2017 KenGaillotkgaillot@redhat.com Update for Pacemaker 1.1.17 + + 10-0 + Fri Oct 6 2017 + KenGaillotkgaillot@redhat.com + + + + Update for Pacemaker 1.1.18 + + + + diff --git a/doc/Pacemaker_Explained/pot/Ap-Debug.pot b/doc/Pacemaker_Explained/pot/Ap-Debug.pot index c906a1c151..79bdc2205d 100644 --- a/doc/Pacemaker_Explained/pot/Ap-Debug.pot +++ b/doc/Pacemaker_Explained/pot/Ap-Debug.pot @@ -1,189 +1,189 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Debugging Cluster Startup" msgstr "" #. Tag: title #, no-c-format msgid "Corosync" msgstr "" #. Tag: title #, no-c-format msgid "Prerequisites" msgstr "" #. Tag: title #, no-c-format msgid "Minimum logging configuration" msgstr "" #. Tag: programlisting #, no-c-format msgid "\n" " # /etc/init.d/openais start\n" " \n" " \n" " logging {\n" " to_syslog: yes\n" " syslog_facility: daemon\n" " }\n" " \n" " " msgstr "" #. Tag: caption #, no-c-format msgid "Whatever other logging you have, these two lines are required for Pacemaker clusters" msgstr "" #. Tag: title #, no-c-format msgid "Confirm Corosync Started" msgstr "" #. Tag: title #, no-c-format msgid "Expected output when starting openais" msgstr "" #. Tag: screen #, no-c-format msgid "\n" " # /etc/init.d/openais start\n" " \n" " \n" " Starting Corosync daemon (aisexec): starting... rc=0: OK\n" " \n" " " msgstr "" #. Tag: title #, no-c-format msgid "Expected log messages - startup" msgstr "" #. Tag: screen #, no-c-format msgid "\n" " # grep -e \"openais.*network interface\" -e \"AIS Executive Service\" /var/log/messages\n" " \n" " \n" " Aug 27 16:23:37 test1 openais[26337]: [MAIN ] AIS Executive Service RELEASE 'subrev 1152 version 0.80'\n" " Aug 27 16:23:38 test1 openais[26337]: [MAIN ] AIS Executive Service: started and ready to provide service.\n" " Aug 27 16:23:38 test1 openais[26337]: [TOTEM] The network interface [192.168.9.41] is now up.\n" " \n" " " msgstr "" #. Tag: caption #, no-c-format msgid "The versions may differ, but you should see Corosync indicate it started and sucessfully attached to the machine's network interface" msgstr "" #. Tag: title #, no-c-format msgid "Expected log messages - membership" msgstr "" #. Tag: screen #, no-c-format msgid "\n" " # grep CLM /var/log/messages\n" " \n" " \n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] CLM CONFIGURATION CHANGE\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] New Configuration:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Left:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Joined:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] CLM CONFIGURATION CHANGE\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] New Configuration:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] r(0) ip(192.168.9.41)\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Left:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] Members Joined:\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] r(0) ip(192.168.9.41)\n" " Aug 27 16:53:15 test1 openais[2166]: [CLM ] got nodejoin message 192.168.9.41\n" " \n" " " msgstr "" #. Tag: caption #, no-c-format msgid "The exact messages will differ, but you should see a new membership formed with the real IP address of your node" msgstr "" #. Tag: title #, no-c-format msgid "Checking Pacemaker" msgstr "" #. Tag: para #, no-c-format msgid "Now that we have confirmed that Corosync is functional we can check the rest of the stack." msgstr "" #. Tag: title #, no-c-format msgid "Expected Pacemaker startup logging for Corosync" msgstr "" #. Tag: screen #, no-c-format msgid "\n" " # grep pcmk_plugin_init /var/log/messages\n" " \n" " \n" " Aug 27 16:53:15 test1 openais[2166]: [pcmk ] info: pcmk_plugin_init: CRM: Initialized\n" " Aug 27 16:53:15 test1 openais[2166]: [pcmk ] Logging: Initialized pcmk_plugin_init\n" " Aug 27 16:53:15 test1 openais[2166]: [pcmk ] info: pcmk_plugin_init: Service: 9\n" " Aug 27 16:53:15 test1 openais[2166]: [pcmk ] info: pcmk_plugin_init: Local hostname: test1\n" " \n" " " msgstr "" #. Tag: caption #, no-c-format msgid "If you don't see these messages, or some like them, there is likely a problem finding or loading the pacemaker plugin." msgstr "" #. Tag: title #, no-c-format msgid "Expected process listing on a 64-bit machine" msgstr "" #. Tag: screen #, no-c-format msgid "\n" " # ps axf\n" " \n" " \n" " 3718 ? Ssl 0:05 /usr/sbin/aisexec\n" " 3723 ? SLs 0:00 \\_ /usr/lib64/heartbeat/stonithd\n" " 3724 ? S 0:05 \\_ /usr/lib64/heartbeat/cib\n" " 3725 ? S 0:21 \\_ /usr/lib64/heartbeat/lrmd\n" " 3726 ? S 0:01 \\_ /usr/lib64/heartbeat/attrd\n" " 3727 ? S 0:00 \\_ /usr/lib64/heartbeat/pengine\n" " 3728 ? S 0:01 \\_ /usr/lib64/heartbeat/crmd\n" " \n" " " msgstr "" #. Tag: caption #, no-c-format msgid "On 32-bit systems the exact path may differ, but all the above processes should be listed." msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Author_Group.pot b/doc/Pacemaker_Explained/pot/Author_Group.pot index 269473e450..22b49850dc 100644 --- a/doc/Pacemaker_Explained/pot/Author_Group.pot +++ b/doc/Pacemaker_Explained/pot/Author_Group.pot @@ -1,139 +1,139 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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: firstname #, no-c-format msgid "Andrew" msgstr "" #. Tag: surname #, no-c-format msgid "Beekhof" msgstr "" #. Tag: orgname #, no-c-format msgid "Red Hat" msgstr "" #. Tag: contrib #, no-c-format msgid "Primary author" msgstr "" #. Tag: firstname #, no-c-format msgid "Dan" msgstr "" #. Tag: surname #, no-c-format msgid "Frîncu" msgstr "" #. Tag: contrib #, no-c-format msgid "Romanian translation" msgstr "" #. Tag: firstname #, no-c-format msgid "Philipp" msgstr "" #. Tag: surname #, no-c-format msgid "Marek" msgstr "" #. Tag: orgname #, no-c-format msgid "LINBit" msgstr "" #. Tag: contrib #, no-c-format msgid "Style and formatting updates. Indexing." msgstr "" #. Tag: firstname #, no-c-format msgid "Tanja" msgstr "" #. Tag: surname #, no-c-format msgid "Roth" msgstr "" #. Tag: orgname #, no-c-format msgid "SUSE" msgstr "" #. Tag: contrib #, no-c-format msgid "Utilization chapter" msgstr "" #. Tag: contrib #, no-c-format msgid "Resource Templates chapter" msgstr "" #. Tag: contrib #, no-c-format msgid "Multi-Site Clusters chapter" msgstr "" #. Tag: firstname #, no-c-format msgid "Lars" msgstr "" #. Tag: surname #, no-c-format msgid "Marowsky-Bree" msgstr "" #. Tag: firstname #, no-c-format msgid "Yan" msgstr "" #. Tag: surname #, no-c-format msgid "Gao" msgstr "" #. Tag: firstname #, no-c-format msgid "Thomas" msgstr "" #. Tag: surname #, no-c-format msgid "Schraitle" msgstr "" #. Tag: firstname #, no-c-format msgid "Dejan" msgstr "" #. Tag: surname #, no-c-format msgid "Muhamedagic" msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Book_Info.pot b/doc/Pacemaker_Explained/pot/Book_Info.pot index fcd9d454d2..775016e5af 100644 --- a/doc/Pacemaker_Explained/pot/Book_Info.pot +++ b/doc/Pacemaker_Explained/pot/Book_Info.pot @@ -1,34 +1,34 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Configuration Explained" msgstr "" #. Tag: subtitle #, no-c-format msgid "An A-Z guide to Pacemaker's Configuration Options" msgstr "" #. Tag: productname #, no-c-format msgid "Pacemaker" msgstr "" #. Tag: para #, no-c-format msgid "The purpose of this document is to definitively explain the concepts used to configure Pacemaker. To achieve this, it will focus exclusively on the XML syntax used to configure Pacemaker's Cluster Information Base (CIB)." msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ch-Alerts.pot b/doc/Pacemaker_Explained/pot/Ch-Alerts.pot index dc9d827330..3a363f258c 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Alerts.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Alerts.pot @@ -1,486 +1,578 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Alerts" msgstr "" #. Tag: para #, no-c-format msgid " ResourceAlerts Alerts " msgstr "" #. Tag: para #, no-c-format -msgid "Alerts may be configured to take some external action when a cluster event occurs (node failure, resource starting or stopping, etc.)." +msgid "Alerts (available since Pacemaker 1.1.15) may be configured to take some external action when a cluster event occurs (node failure, resource starting or stopping, etc.)." msgstr "" #. Tag: title #, no-c-format msgid "Alert Agents" msgstr "" #. Tag: para #, no-c-format msgid "As with resource agents, the cluster calls an external program (an alert agent) to handle alerts. The cluster passes information about the event to the agent via environment variables. Agents can do anything desired with this information (send an e-mail, log to a file, update a monitoring system, etc.)." msgstr "" #. Tag: title #, no-c-format msgid "Simple alert configuration" msgstr "" #. Tag: programlisting #, no-c-format msgid "<configuration>\n" " <alerts>\n" " <alert id=\"my-alert\" path=\"/path/to/my-script.sh\" />\n" " </alerts>\n" "</configuration>" msgstr "" #. Tag: para #, no-c-format msgid "In the example above, the cluster will call my-script.sh for each event." msgstr "" #. Tag: para #, no-c-format msgid "Multiple alert agents may be configured; the cluster will call all of them for each event." msgstr "" #. Tag: para #, no-c-format msgid "Alert agents will be called only on cluster nodes. They will be called for events involving Pacemaker Remote nodes, but they will never be called on those nodes." msgstr "" #. Tag: title #, no-c-format msgid "Alert Recipients" msgstr "" #. Tag: para #, no-c-format msgid "Usually alerts are directed towards a recipient. Thus each alert may be additionally configured with one or more recipients. The cluster will call the agent separately for each recipient." msgstr "" #. Tag: title #, no-c-format msgid "Alert configuration with recipient" msgstr "" #. Tag: programlisting #, no-c-format msgid "<configuration>\n" " <alerts>\n" " <alert id=\"my-alert\" path=\"/path/to/my-script.sh\">\n" " <recipient id=\"my-alert-recipient\" value=\"some-address\"/>\n" " </alert>\n" " </alerts>\n" "</configuration>" msgstr "" #. Tag: para #, no-c-format msgid "In the above example, the cluster will call my-script.sh for each event, passing the recipient some-address as an environment variable." msgstr "" #. Tag: para #, no-c-format msgid "The recipient may be anything the alert agent can recognize — an IP address, an e-mail address, a file name, whatever the particular agent supports." msgstr "" #. Tag: title #, no-c-format msgid "Alert Meta-Attributes" msgstr "" #. Tag: para #, no-c-format msgid "As with resource agents, meta-attributes can be configured for alert agents to affect how Pacemaker calls them." msgstr "" #. Tag: title #, no-c-format msgid "Meta-Attributes of an Alert" msgstr "" #. Tag: entry #, no-c-format msgid "Meta-Attribute" msgstr "" #. Tag: entry #, no-c-format msgid "Default" msgstr "" #. Tag: entry #, no-c-format msgid "Description" msgstr "" #. Tag: para #, no-c-format msgid "timestamp-format" msgstr "" #. Tag: para #, no-c-format msgid "%H:%M:%S.%06N" msgstr "" #. Tag: para #, no-c-format msgid "Format the cluster will use when sending the event’s timestamp to the agent. This is a string as used with the date(1) command. AlertOptiontimestamp-format Optiontimestamp-format timestamp-format " msgstr "" #. Tag: para #, no-c-format msgid "timeout" msgstr "" #. Tag: para #, no-c-format msgid "30s" msgstr "" #. Tag: para #, no-c-format msgid "If the alert agent does not complete within this amount of time, it will be terminated. AlertOptiontimeout Optiontimeout timeout " msgstr "" #. Tag: para #, no-c-format msgid "Meta-attributes can be configured per alert agent and/or per recipient." msgstr "" #. Tag: title #, no-c-format msgid "Alert configuration with meta-attributes" msgstr "" #. Tag: programlisting #, no-c-format msgid "<configuration>\n" " <alerts>\n" " <alert id=\"my-alert\" path=\"/path/to/my-script.sh\">\n" " <meta_attributes id=\"my-alert-attributes\">\n" " <nvpair id=\"my-alert-attributes-timeout\" name=\"timeout\"\n" " value=\"15s\"/>\n" " </meta_attributes>\n" " <recipient id=\"my-alert-recipient1\" value=\"someuser@example.com\">\n" " <meta_attributes id=\"my-alert-recipient1-attributes\">\n" " <nvpair id=\"my-alert-recipient1-timestamp-format\"\n" " name=\"timestamp-format\" value=\"%D %H:%M\"/>\n" " </meta_attributes>\n" " </recipient>\n" " <recipient id=\"my-alert-recipient2\" value=\"otheruser@example.com\">\n" " <meta_attributes id=\"my-alert-recipient2-attributes\">\n" " <nvpair id=\"my-alert-recipient2-timestamp-format\"\n" " name=\"timestamp-format\" value=\"%c\"/>\n" " </meta_attributes>\n" " </recipient>\n" " </alert>\n" " </alerts>\n" "</configuration>" msgstr "" #. Tag: para #, no-c-format msgid "In the above example, the my-script.sh will get called twice for each event, with each call using a 15-second timeout. One call will be passed the recipient someuser@example.com and a timestamp in the format %D %H:%M, while the other call will be passed the recipient otheruser@example.com and a timestamp in the format %c." msgstr "" #. Tag: title #, no-c-format msgid "Alert Instance Attributes" msgstr "" #. Tag: para #, no-c-format msgid "As with resource agents, agent-specific configuration values may be configured as instance attributes. These will be passed to the agent as additional environment variables. The number, names and allowed values of these instance attributes are completely up to the particular agent." msgstr "" #. Tag: title #, no-c-format msgid "Alert configuration with instance attributes" msgstr "" #. Tag: programlisting #, no-c-format msgid "<configuration>\n" " <alerts>\n" " <alert id=\"my-alert\" path=\"/path/to/my-script.sh\">\n" " <meta_attributes id=\"my-alert-attributes\">\n" " <nvpair id=\"my-alert-attributes-timeout\" name=\"timeout\"\n" " value=\"15s\"/>\n" " </meta_attributes>\n" " <instance_attributes id=\"my-alert-options\">\n" " <nvpair id=\"my-alert-options-debug\" name=\"debug\" value=\"false\"/>\n" " </instance_attributes>\n" " <recipient id=\"my-alert-recipient1\" value=\"someuser@example.com\"/>\n" " </alert>\n" " </alerts>\n" "</configuration>" msgstr "" +#. Tag: title +#, no-c-format +msgid "Alert Filters" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Coming in 1.1.18" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "By default, an alert agent will be called for node events, fencing events, and resource events. An agent may choose to ignore certain types of events, but there is still the overhead of calling it for those events. To eliminate that overhead, you may select which types of events the agent should receive." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Alert configuration to receive only node events and fencing events" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<configuration>\n" +" <alerts>\n" +" <alert id=\"my-alert\" path=\"/path/to/my-script.sh\">\n" +" <select>\n" +" <select_nodes />\n" +" <select_fencing />\n" +" </select>\n" +" <recipient id=\"my-alert-recipient1\" value=\"someuser@example.com\"/>\n" +" </alert>\n" +" </alerts>\n" +"</configuration>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The possible options within <select> are <select_nodes>, <select_fencing>, <select_resources>, and <select_attributes>." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "With <select_attributes> (the only event type not enabled by default), the agent will receive alerts when a node attribute changes. If you wish the agent to be called only when certain attributes change, you can configure that as well." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Alert configuration to be called when certain node attributes change" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<configuration>\n" +" <alerts>\n" +" <alert id=\"my-alert\" path=\"/path/to/my-script.sh\">\n" +" <select>\n" +" <select_attributes>\n" +" <attribute id=\"alert-standby\" name=\"standby\" />\n" +" <attribute id=\"alert-shutdown\" name=\"shutdown\" />\n" +" </select_attributes>\n" +" </select>\n" +" <recipient id=\"my-alert-recipient1\" value=\"someuser@example.com\"/>\n" +" </alert>\n" +" </alerts>\n" +"</configuration>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Node attribute alerts are currently considered experimental. Alerts may be limited to attributes set via attrd_updater, and agents may be called multiple times with the same attribute value." +msgstr "" + #. Tag: title #, no-c-format msgid "Using the Sample Alert Agents" msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker provides several sample alert agents, installed in /usr/share/pacemaker/alerts by default." msgstr "" #. Tag: para #, no-c-format msgid "While these sample scripts may be copied and used as-is, they are provided mainly as templates to be edited to suit your purposes. See their source code for the full set of instance attributes they support." msgstr "" #. Tag: title #, no-c-format msgid "Sending cluster events as SNMP traps" msgstr "" #. Tag: programlisting #, no-c-format msgid "<configuration>\n" " <alerts>\n" " <alert id=\"snmp_alert\" path=\"/path/to/alert_snmp.sh\">\n" " <instance_attributes id=\"config_for_alert_snmp\">\n" " <nvpair id=\"trap_node_states\" name=\"trap_node_states\" value=\"all\"/>\n" " </instance_attributes>\n" " <meta_attributes id=\"config_for_timestamp\">\n" " <nvpair id=\"ts_fmt\" name=\"timestamp-format\"\n" " value=\"%Y-%m-%d,%H:%M:%S.%01N\"/>\n" " </meta_attributes>\n" " <recipient id=\"snmp_destination\" value=\"192.168.1.2\"/>\n" " </alert>\n" " </alerts>\n" "</configuration>" msgstr "" #. Tag: title #, no-c-format msgid "Sending cluster events as e-mails" msgstr "" #. Tag: programlisting #, no-c-format msgid " <configuration>\n" " <alerts>\n" " <alert id=\"smtp_alert\" path=\"/path/to/alert_smtp.sh\">\n" " <instance_attributes id=\"config_for_alert_smtp\">\n" " <nvpair id=\"email_sender\" name=\"email_sender\"\n" " value=\"donotreply@example.com\"/>\n" " </instance_attributes>\n" " <recipient id=\"smtp_destination\" value=\"admin@example.com\"/>\n" " </alert>\n" " </alerts>\n" " </configuration>" msgstr "" #. Tag: title #, no-c-format msgid "Writing an Alert Agent" msgstr "" #. Tag: title #, no-c-format msgid "Environment variables passed to alert agents" msgstr "" #. Tag: entry #, no-c-format msgid "Environment Variable" msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_kind" msgstr "" #. Tag: para #, no-c-format -msgid "The type of alert (node, fencing, or resource) Environment VariableCRM_alert_kind CRM_alert_kind kind " +msgid "The type of alert (node, fencing, resource, or attribute) Environment VariableCRM_alert_kind CRM_alert_kind kind " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_version" msgstr "" #. Tag: para #, no-c-format msgid "The version of Pacemaker sending the alert Environment VariableCRM_alert_version CRM_alert_version version " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_recipient" msgstr "" #. Tag: para #, no-c-format msgid "The configured recipient Environment VariableCRM_alert_recipient CRM_alert_recipient recipient " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_node_sequence" msgstr "" #. Tag: para #, no-c-format msgid "A sequence number increased whenever an alert is being issued on the local node, which can be used to reference the order in which alerts have been issued by Pacemaker. An alert for an event that happened later in time reliably has a higher sequence number than alerts for earlier events. Be aware that this number has no cluster-wide meaning. Environment VariableCRM_alert_node_sequence CRM_alert_node_sequence sequence " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_timestamp" msgstr "" #. Tag: para #, no-c-format msgid "A timestamp created prior to executing the agent, in the format specified by the timestamp-format meta-attribute. This allows the agent to have a reliable, high-precision time of when the event occurred, regardless of when the agent itself was invoked (which could potentially be delayed due to system load, etc.). Environment VariableCRM_alert_timestamp CRM_alert_timestamp timestamp " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_node" msgstr "" #. Tag: para #, no-c-format msgid "Name of affected node Environment VariableCRM_alert_node CRM_alert_node node " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_desc" msgstr "" #. Tag: para #, no-c-format msgid "Detail about event. For node alerts, this is the node’s current state (member or lost). For fencing alerts, this is a summary of the requested fencing operation, including origin, target, and fencing operation error code, if any. For resource alerts, this is a readable string equivalent of CRM_alert_status. Environment VariableCRM_alert_desc CRM_alert_desc desc " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_nodeid" msgstr "" #. Tag: para #, no-c-format msgid "ID of node whose status changed (provided with node alerts only) Environment VariableCRM_alert_nodeid CRM_alert_nodeid nodeid " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_task" msgstr "" #. Tag: para #, no-c-format msgid "The requested fencing or resource operation (provided with fencing and resource alerts only) Environment VariableCRM_alert_task CRM_alert_task task " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_rc" msgstr "" #. Tag: para #, no-c-format msgid "The numerical return code of the fencing or resource operation (provided with fencing and resource alerts only) Environment VariableCRM_alert_rc CRM_alert_rc rc " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_rsc" msgstr "" #. Tag: para #, no-c-format msgid "The name of the affected resource (resource alerts only) Environment VariableCRM_alert_rsc CRM_alert_rsc rsc " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_interval" msgstr "" #. Tag: para #, no-c-format msgid "The interval of the resource operation (resource alerts only) Environment VariableCRM_alert_interval CRM_alert_interval interval " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_target_rc" msgstr "" #. Tag: para #, no-c-format msgid "The expected numerical return code of the operation (resource alerts only) Environment VariableCRM_alert_target_rc CRM_alert_target_rc target_rc " msgstr "" #. Tag: para #, no-c-format msgid "CRM_alert_status" msgstr "" #. Tag: para #, no-c-format msgid "A numerical code used by Pacemaker to represent the operation result (resource alerts only) Environment VariableCRM_alert_status CRM_alert_status status " msgstr "" +#. Tag: para +#, no-c-format +msgid "CRM_alert_attribute_name" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The name of the node attribute that changed (attribute alerts only) Environment VariableCRM_alert_attribute_name CRM_alert_attribute_name attribute_name " +msgstr "" + +#. Tag: para +#, no-c-format +msgid "CRM_alert_attribute_value" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The new value of the node attribute that changed (attribute alerts only) Environment VariableCRM_alert_attribute_value CRM_alert_attribute_value attribute_value " +msgstr "" + #. Tag: para #, no-c-format msgid "Special concerns when writing alert agents:" msgstr "" #. Tag: para #, no-c-format msgid "Alert agents may be called with no recipient (if none is configured), so the agent must be able to handle this situation, even if it only exits in that case. (Users may modify the configuration in stages, and add a recipient later.)" msgstr "" #. Tag: para #, no-c-format msgid "If more than one recipient is configured for an alert, the alert agent will be called once per recipient. If an agent is not able to run concurrently, it should be configured with only a single recipient. The agent is free, however, to interpret the recipient as a list." msgstr "" #. Tag: para #, no-c-format msgid "When a cluster event occurs, all alerts are fired off at the same time as separate processes. Depending on how many alerts and recipients are configured, and on what is done within the alert agents, a significant load burst may occur. The agent could be written to take this into consideration, for example by queueing resource-intensive actions into some other instance, instead of directly executing them." msgstr "" #. Tag: para #, no-c-format msgid "Alert agents are run as the hacluster user, which has a minimal set of permissions. If an agent requires additional privileges, it is recommended to configure sudo to allow the agent to run the necessary commands as another user with the appropriate privileges." msgstr "" #. Tag: para #, no-c-format msgid "As always, take care to validate and sanitize user-configured parameters, such as CRM_alert_timestamp (whose content is specified by the user-configured timestamp-format), CRM_alert_recipient, and all instance attributes. Mostly this is needed simply to protect against configuration errors, but if some user can modify the CIB without having hacluster-level access to the cluster nodes, it is a potential security concern as well, to avoid the possibility of code injection." msgstr "" #. Tag: para #, no-c-format msgid "The alerts interface is designed to be backward compatible with the external scripts interface used by the ocf:pacemaker:ClusterMon resource, which is now deprecated. To preserve this compatibility, the environment variables passed to alert agents are available prepended with CRM_notify_ as well as CRM_alert_. One break in compatibility is that ClusterMon ran external scripts as the root user, while alert agents are run as the hacluster user." msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ch-Multi-site-Clusters.pot b/doc/Pacemaker_Explained/pot/Ch-Multi-site-Clusters.pot index 78f9f9a3ee..83a796e634 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Multi-site-Clusters.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Multi-site-Clusters.pot @@ -1,458 +1,458 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Multi-Site Clusters and Tickets" msgstr "" #. Tag: para #, no-c-format msgid "Apart from local clusters, Pacemaker also supports multi-site clusters. That means you can have multiple, geographically dispersed sites, each with a local cluster. Failover between these clusters can be coordinated manually by the administrator, or automatically by a higher-level entity called a Cluster Ticket Registry (CTR)." msgstr "" #. Tag: title #, no-c-format msgid "Challenges for Multi-Site Clusters" msgstr "" #. Tag: para #, no-c-format msgid "Typically, multi-site environments are too far apart to support synchronous communication and data replication between the sites. That leads to significant challenges:" msgstr "" #. Tag: para #, no-c-format msgid "How do we make sure that a cluster site is up and running?" msgstr "" #. Tag: para #, no-c-format msgid "How do we make sure that resources are only started once?" msgstr "" #. Tag: para #, no-c-format msgid "How do we make sure that quorum can be reached between the different sites and a split-brain scenario avoided?" msgstr "" #. Tag: para #, no-c-format msgid "How do we manage failover between sites?" msgstr "" #. Tag: para #, no-c-format msgid "How do we deal with high latency in case of resources that need to be stopped?" msgstr "" #. Tag: para #, no-c-format msgid "In the following sections, learn how to meet these challenges." msgstr "" #. Tag: title #, no-c-format msgid "Conceptual Overview" msgstr "" #. Tag: para #, no-c-format msgid "Multi-site clusters can be considered as “overlay” clusters where each cluster site corresponds to a cluster node in a traditional cluster. The overlay cluster can be managed by a CTR in order to guarantee that any cluster resource will be active on no more than one cluster site. This is achieved by using tickets that are treated as failover domain between cluster sites, in case a site should be down." msgstr "" #. Tag: para #, no-c-format msgid "The following sections explain the individual components and mechanisms that were introduced for multi-site clusters in more detail." msgstr "" #. Tag: title #, no-c-format msgid "Ticket" msgstr "" #. Tag: para #, no-c-format msgid "Tickets are, essentially, cluster-wide attributes. A ticket grants the right to run certain resources on a specific cluster site. Resources can be bound to a certain ticket by rsc_ticket constraints. Only if the ticket is available at a site can the respective resources be started there. Vice versa, if the ticket is revoked, the resources depending on that ticket must be stopped." msgstr "" #. Tag: para #, no-c-format msgid "The ticket thus is similar to a site quorum, i.e. the permission to manage/own resources associated with that site. (One can also think of the current have-quorum flag as a special, cluster-wide ticket that is granted in case of node majority.)" msgstr "" #. Tag: para #, no-c-format msgid "Tickets can be granted and revoked either manually by administrators (which could be the default for classic enterprise clusters), or via the automated CTR mechanism described below." msgstr "" #. Tag: para #, no-c-format msgid "A ticket can only be owned by one site at a time. Initially, none of the sites has a ticket. Each ticket must be granted once by the cluster administrator." msgstr "" #. Tag: para #, no-c-format msgid "The presence or absence of tickets for a site is stored in the CIB as a cluster status. With regards to a certain ticket, there are only two states for a site: true (the site has the ticket) or false (the site does not have the ticket). The absence of a certain ticket (during the initial state of the multi-site cluster) is the same as the value false." msgstr "" #. Tag: title #, no-c-format msgid "Dead Man Dependency" msgstr "" #. Tag: para #, no-c-format msgid "A site can only activate resources safely if it can be sure that the other site has deactivated them. However after a ticket is revoked, it can take a long time until all resources depending on that ticket are stopped \"cleanly\", especially in case of cascaded resources. To cut that process short, the concept of a Dead Man Dependency was introduced." msgstr "" #. Tag: para #, no-c-format msgid "If a dead man dependency is in force, if a ticket is revoked from a site, the nodes that are hosting dependent resources are fenced. This considerably speeds up the recovery process of the cluster and makes sure that resources can be migrated more quickly." msgstr "" #. Tag: para #, no-c-format msgid "This can be configured by specifying a loss-policy=\"fence\" in rsc_ticket constraints." msgstr "" #. Tag: title #, no-c-format msgid "Cluster Ticket Registry" msgstr "" #. Tag: para #, no-c-format msgid "A CTR is a coordinated group of network daemons that automatically handles granting, revoking, and timing out tickets (instead of the administrator revoking the ticket somewhere, waiting for everything to stop, and then granting it on the desired site)." msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker does not implement its own CTR, but interoperates with external software designed for that purpose (similar to how resource and fencing agents are not directly part of pacemaker)." msgstr "" #. Tag: para #, no-c-format msgid "Participating clusters run the CTR daemons, which connect to each other, exchange information about their connectivity, and vote on which sites gets which tickets." msgstr "" #. Tag: para #, no-c-format msgid "A ticket is granted to a site only once the CTR is sure that the ticket has been relinquished by the previous owner, implemented via a timer in most scenarios. If a site loses connection to its peers, its tickets time out and recovery occurs. After the connection timeout plus the recovery timeout has passed, the other sites are allowed to re-acquire the ticket and start the resources again." msgstr "" #. Tag: para #, no-c-format msgid "This can also be thought of as a \"quorum server\", except that it is not a single quorum ticket, but several." msgstr "" #. Tag: title #, no-c-format msgid "Configuration Replication" msgstr "" #. Tag: para #, no-c-format msgid "As usual, the CIB is synchronized within each cluster, but it is not synchronized across cluster sites of a multi-site cluster. You have to configure the resources that will be highly available across the multi-site cluster for every site accordingly." msgstr "" #. Tag: title #, no-c-format msgid "Configuring Ticket Dependencies" msgstr "" #. Tag: para #, no-c-format msgid "The rsc_ticket constraint lets you specify the resources depending on a certain ticket. Together with the constraint, you can set a loss-policy that defines what should happen to the respective resources if the ticket is revoked." msgstr "" #. Tag: para #, no-c-format msgid "The attribute loss-policy can have the following values:" msgstr "" #. Tag: para #, no-c-format msgid "fence: Fence the nodes that are running the relevant resources." msgstr "" #. Tag: para #, no-c-format msgid "stop: Stop the relevant resources." msgstr "" #. Tag: para #, no-c-format msgid "freeze: Do nothing to the relevant resources." msgstr "" #. Tag: para #, no-c-format msgid "demote: Demote relevant resources that are running in master mode to slave mode." msgstr "" #. Tag: title #, no-c-format msgid "Constraint that fences node if ticketA is revoked" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_ticket id=\"rsc1-req-ticketA\" rsc=\"rsc1\" ticket=\"ticketA\" loss-policy=\"fence\"/>" msgstr "" #. Tag: para #, no-c-format msgid "The example above creates a constraint with the ID rsc1-req-ticketA. It defines that the resource rsc1 depends on ticketA and that the node running the resource should be fenced if ticketA is revoked." msgstr "" #. Tag: para #, no-c-format msgid "If resource rsc1 were a multi-state resource (i.e. it could run in master or slave mode), you might want to configure that only master mode depends on ticketA. With the following configuration, rsc1 will be demoted to slave mode if ticketA is revoked:" msgstr "" #. Tag: title #, no-c-format msgid "Constraint that demotes rsc1 if ticketA is revoked" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_ticket id=\"rsc1-req-ticketA\" rsc=\"rsc1\" rsc-role=\"Master\" ticket=\"ticketA\" loss-policy=\"demote\"/>" msgstr "" #. Tag: para #, no-c-format msgid "You can create multiple rsc_ticket constraints to let multiple resources depend on the same ticket. However, rsc_ticket also supports resource sets (see ), so one can easily list all the resources in one rsc_ticket constraint instead." msgstr "" #. Tag: title #, no-c-format msgid "Ticket constraint for multiple resources" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_ticket id=\"resources-dep-ticketA\" ticket=\"ticketA\" loss-policy=\"fence\">\n" " <resource_set id=\"resources-dep-ticketA-0\" role=\"Started\">\n" " <resource_ref id=\"rsc1\"/>\n" " <resource_ref id=\"group1\"/>\n" " <resource_ref id=\"clone1\"/>\n" " </resource_set>\n" " <resource_set id=\"resources-dep-ticketA-1\" role=\"Master\">\n" " <resource_ref id=\"ms1\"/>\n" " </resource_set>\n" "</rsc_ticket>" msgstr "" #. Tag: para #, no-c-format msgid "In the example above, there are two resource sets, so we can list resources with different roles in a single rsc_ticket constraint. There’s no dependency between the two resource sets, and there’s no dependency among the resources within a resource set. Each of the resources just depends on ticketA." msgstr "" #. Tag: para #, no-c-format msgid "Referencing resource templates in rsc_ticket constraints, and even referencing them within resource sets, is also supported." msgstr "" #. Tag: para #, no-c-format msgid "If you want other resources to depend on further tickets, create as many constraints as necessary with rsc_ticket." msgstr "" #. Tag: title #, no-c-format msgid "Managing Multi-Site Clusters" msgstr "" #. Tag: title #, no-c-format msgid "Granting and Revoking Tickets Manually" msgstr "" #. Tag: para #, no-c-format msgid "You can grant tickets to sites or revoke them from sites manually. If you want to re-distribute a ticket, you should wait for the dependent resources to stop cleanly at the previous site before you grant the ticket to the new site." msgstr "" #. Tag: para #, no-c-format msgid "Use the crm_ticket command line tool to grant and revoke tickets." msgstr "" #. Tag: para #, no-c-format msgid "To grant a ticket to this site:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_ticket --ticket ticketA --grant" msgstr "" #. Tag: para #, no-c-format msgid "To revoke a ticket from this site:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_ticket --ticket ticketA --revoke" msgstr "" #. Tag: para #, no-c-format msgid "If you are managing tickets manually, use the crm_ticket command with great care, because it cannot check whether the same ticket is already granted elsewhere." msgstr "" #. Tag: title #, no-c-format msgid "Granting and Revoking Tickets via a Cluster Ticket Registry" msgstr "" #. Tag: para #, no-c-format msgid "We will use Booth here as an example of software that can be used with pacemaker as a Cluster Ticket Registry. Booth implements the Raft algorithm to guarantee the distributed consensus among different cluster sites, and manages the ticket distribution (and thus the failover process between sites)." msgstr "" #. Tag: para #, no-c-format msgid "Each of the participating clusters and arbitrators runs the Booth daemon boothd." msgstr "" #. Tag: para #, no-c-format msgid "An arbitrator is the multi-site equivalent of a quorum-only node in a local cluster. If you have a setup with an even number of sites, you need an additional instance to reach consensus about decisions such as failover of resources across sites. In this case, add one or more arbitrators running at additional sites. Arbitrators are single machines that run a booth instance in a special mode. An arbitrator is especially important for a two-site scenario, otherwise there is no way for one site to distinguish between a network failure between it and the other site, and a failure of the other site." msgstr "" #. Tag: para #, no-c-format msgid "The most common multi-site scenario is probably a multi-site cluster with two sites and a single arbitrator on a third site. However, technically, there are no limitations with regards to the number of sites and the number of arbitrators involved." msgstr "" #. Tag: para #, no-c-format msgid "Boothd at each site connects to its peers running at the other sites and exchanges connectivity details. Once a ticket is granted to a site, the booth mechanism will manage the ticket automatically: If the site which holds the ticket is out of service, the booth daemons will vote which of the other sites will get the ticket. To protect against brief connection failures, sites that lose the vote (either explicitly or implicitly by being disconnected from the voting body) need to relinquish the ticket after a time-out. Thus, it is made sure that a ticket will only be re-distributed after it has been relinquished by the previous site. The resources that depend on that ticket will fail over to the new site holding the ticket. The nodes that have run the resources before will be treated according to the loss-policy you set within the rsc_ticket constraint." msgstr "" #. Tag: para #, no-c-format msgid "Before the booth can manage a certain ticket within the multi-site cluster, you initially need to grant it to a site manually via the booth command-line tool. After you have initially granted a ticket to a site, boothd will take over and manage the ticket automatically." msgstr "" #. Tag: para #, no-c-format msgid "The booth command-line tool can be used to grant, list, or revoke tickets and can be run on any machine where boothd is running. If you are managing tickets via Booth, use only booth for manual intervention, not crm_ticket. That ensures the same ticket will only be owned by one cluster site at a time." msgstr "" #. Tag: title #, no-c-format msgid "Booth Requirements" msgstr "" #. Tag: para #, no-c-format msgid "All clusters that will be part of the multi-site cluster must be based on Pacemaker." msgstr "" #. Tag: para #, no-c-format msgid "Booth must be installed on all cluster nodes and on all arbitrators that will be part of the multi-site cluster." msgstr "" #. Tag: para #, no-c-format msgid "Nodes belonging to the same cluster site should be synchronized via NTP. However, time synchronization is not required between the individual cluster sites." msgstr "" #. Tag: title #, no-c-format msgid "General Management of Tickets" msgstr "" #. Tag: para #, no-c-format msgid "Display the information of tickets:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_ticket --info" msgstr "" #. Tag: para #, no-c-format msgid "Or you can monitor them with:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_mon --tickets" msgstr "" #. Tag: para #, no-c-format msgid "Display the rsc_ticket constraints that apply to a ticket:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_ticket --ticket ticketA --constraints" msgstr "" #. Tag: para #, no-c-format msgid "When you want to do maintenance or manual switch-over of a ticket, revoking the ticket would trigger the loss policies. If loss-policy=\"fence\", the dependent resources could not be gracefully stopped/demoted, and other unrelated resources could even be affected." msgstr "" #. Tag: para #, no-c-format msgid "The proper way is making the ticket standby first with:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_ticket --ticket ticketA --standby" msgstr "" #. Tag: para #, no-c-format msgid "Then the dependent resources will be stopped or demoted gracefully without triggering the loss policies." msgstr "" #. Tag: para #, no-c-format msgid "If you have finished the maintenance and want to activate the ticket again, you can run:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_ticket --ticket ticketA --activate" msgstr "" #. Tag: title #, no-c-format msgid "For more information" msgstr "" #. Tag: para #, no-c-format msgid "SUSE’s Geo Clustering quick start" msgstr "" #. Tag: para #, no-c-format msgid "Booth" msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ch-Notifications.pot b/doc/Pacemaker_Explained/pot/Ch-Notifications.pot index 8bf03de422..47164a713a 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Notifications.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Notifications.pot @@ -1,233 +1,233 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Receiving Notification for Cluster Events" msgstr "" #. Tag: para #, no-c-format msgid " ResourceNotification Notification " msgstr "" #. Tag: para #, no-c-format msgid "A Pacemaker cluster is an event-driven system. In this context, an event might be a resource failure or a configuration change, among others." msgstr "" #. Tag: para #, no-c-format msgid "The ocf:pacemaker:ClusterMon resource can monitor the cluster status and trigger alerts on each cluster event. This resource runs crm_mon in the background at regular (configurable) intervals and uses crm_mon capabilities to trigger emails (SMTP), SNMP traps or external programs (via the extra_options parameter)." msgstr "" #. Tag: para #, no-c-format msgid "Depending on your system settings and compilation settings, SNMP or email alerts might be unavailable. Check the output of crm_mon --help to see whether these options are available to you. In any case, executing an external agent will always be available, and you can use this agent to send emails, SNMP traps or whatever action you develop." msgstr "" #. Tag: title #, no-c-format msgid "Configuring SNMP Notifications" msgstr "" #. Tag: para #, no-c-format msgid " ResourceNotificationSNMP NotificationSNMP SNMP " msgstr "" #. Tag: para #, no-c-format msgid "Requires an IP to send SNMP traps to, and an SNMP community string. The Pacemaker MIB is provided with the source, and is typically installed in /usr/share/snmp/mibs/PCMK-MIB.txt." msgstr "" #. Tag: para #, no-c-format msgid "This example uses snmphost.example.com as the SNMP IP and public as the community string:" msgstr "" #. Tag: title #, no-c-format msgid "Configuring ClusterMon to send SNMP traps" msgstr "" #. Tag: programlisting #, no-c-format msgid "<clone id=\"ClusterMon-clone\">\n" " <primitive class=\"ocf\" id=\"ClusterMon-SNMP\" provider=\"pacemaker\" type=\"ClusterMon\">\n" " <instance_attributes id=\"ClusterMon-instance_attributes\">\n" " <nvpair id=\"ClusterMon-instance_attributes-user\" name=\"user\" value=\"root\"/>\n" " <nvpair id=\"ClusterMon-instance_attributes-update\" name=\"update\" value=\"30\"/>\n" " <nvpair id=\"ClusterMon-instance_attributes-extra_options\" name=\"extra_options\" value=\"-S snmphost.example.com -C public\"/>\n" " </instance_attributes>\n" " </primitive>\n" "</clone>" msgstr "" #. Tag: title #, no-c-format msgid "Configuring Email Notifications" msgstr "" #. Tag: para #, no-c-format msgid " ResourceNotificationSMTP NotificationSMTP SMTP " msgstr "" #. Tag: para #, no-c-format msgid "Requires the recipient e-mail address. You can also optionally configure the sender e-mail address, the hostname of the SMTP relay, and a prefix string for the subject line." msgstr "" #. Tag: title #, no-c-format msgid "Configuring ClusterMon to send email alerts" msgstr "" #. Tag: programlisting #, no-c-format msgid "<clone id=\"ClusterMon-clone\">\n" " <primitive class=\"ocf\" id=\"ClusterMon-SMTP\" provider=\"pacemaker\" type=\"ClusterMon\">\n" " <instance_attributes id=\"ClusterMon-instance_attributes\">\n" " <nvpair id=\"ClusterMon-instance_attributes-user\" name=\"user\" value=\"root\"/>\n" " <nvpair id=\"ClusterMon-instance_attributes-update\" name=\"update\" value=\"30\"/>\n" " <nvpair id=\"ClusterMon-instance_attributes-extra_options\" name=\"extra_options\" value=\"-T pacemaker@example.com -F pacemaker@node2.example.com -P PACEMAKER -H mail.example.com\"/>\n" " </instance_attributes>\n" " </primitive>\n" "</clone>" msgstr "" #. Tag: title #, no-c-format msgid "Configuring Notifications via External-Agent" msgstr "" #. Tag: para #, no-c-format msgid "Requires a program (external-agent) to run when resource operations take place, and an external-recipient (IP address, email address, URI). When triggered, the external-agent is fed with dynamically filled environment variables describing precisely the cluster event that occurred. By making smart usage of these variables in your external-agent code, you can trigger any action." msgstr "" #. Tag: title #, no-c-format msgid "Configuring ClusterMon to execute an external-agent" msgstr "" #. Tag: programlisting #, no-c-format msgid "<clone id=\"ClusterMon-clone\">\n" " <primitive class=\"ocf\" id=\"ClusterMon\" provider=\"pacemaker\" type=\"ClusterMon\">\n" " <instance_attributes id=\"ClusterMon-instance_attributes\">\n" " <nvpair id=\"ClusterMon-instance_attributes-user\" name=\"user\" value=\"root\"/>\n" " <nvpair id=\"ClusterMon-instance_attributes-update\" name=\"update\" value=\"30\"/>\n" " <nvpair id=\"ClusterMon-instance_attributes-extra_options\" name=\"extra_options\" value=\"-E /usr/local/bin/example.sh -e 192.168.12.1\"/>\n" " </instance_attributes>\n" " </primitive>\n" "</clone>" msgstr "" #. Tag: title #, no-c-format msgid "Environment Variables Passed to the External Agent" msgstr "" #. Tag: entry #, no-c-format msgid "Environment Variable" msgstr "" #. Tag: entry #, no-c-format msgid "Description" msgstr "" #. Tag: para #, no-c-format msgid "CRM_notify_recipient" msgstr "" #. Tag: para #, no-c-format msgid "The static external-recipient from the resource definition. Environment VariableCRM_notify_recipient CRM_notify_recipient " msgstr "" #. Tag: para #, no-c-format msgid "CRM_notify_node" msgstr "" #. Tag: para #, no-c-format msgid "The node on which the status change happened. Environment VariableCRM_notify_node CRM_notify_node " msgstr "" #. Tag: para #, no-c-format msgid "CRM_notify_rsc" msgstr "" #. Tag: para #, no-c-format msgid "The name of the resource that changed the status. Environment VariableCRM_notify_rsc CRM_notify_rsc " msgstr "" #. Tag: para #, no-c-format msgid "CRM_notify_task" msgstr "" #. Tag: para #, no-c-format msgid "The operation that caused the status change. Environment VariableCRM_notify_task CRM_notify_task " msgstr "" #. Tag: para #, no-c-format msgid "CRM_notify_desc" msgstr "" #. Tag: para #, no-c-format msgid "The textual output relevant error code of the operation (if any) that caused the status change. Environment VariableCRM_notify_desc CRM_notify_desc " msgstr "" #. Tag: para #, no-c-format msgid "CRM_notify_rc" msgstr "" #. Tag: para #, no-c-format msgid "The return code of the operation. Environment VariableCRM_notify_rc CRM_notify_rc " msgstr "" #. Tag: para #, no-c-format msgid "CRM_notify_target_rc" msgstr "" #. Tag: para #, no-c-format msgid "The expected return code of the operation. Environment VariableCRM_notify_target_rc CRM_notify_target_rc " msgstr "" #. Tag: para #, no-c-format msgid "CRM_notify_status" msgstr "" #. Tag: para #, no-c-format msgid "The numerical representation of the status of the operation. Environment VariableCRM_notify_target_rc CRM_notify_target_rc " msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ch-Resource-Templates.pot b/doc/Pacemaker_Explained/pot/Ch-Resource-Templates.pot index ddd7fc9845..5e7dc30c2b 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Resource-Templates.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Resource-Templates.pot @@ -1,317 +1,317 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Resource Templates" msgstr "" #. Tag: para #, no-c-format msgid "If you want to create lots of resources with similar configurations, defining a resource template simplifies the task. Once defined, it can be referenced in primitives or in certain types of constraints." msgstr "" #. Tag: title #, no-c-format msgid "Configuring Resources with Templates" msgstr "" #. Tag: para #, no-c-format msgid "The primitives referencing the template will inherit all meta-attributes, instance attributes, utilization attributes and operations defined in the template. And you can define specific attributes and operations for any of the primitives. If any of these are defined in both the template and the primitive, the values defined in the primitive will take precedence over the ones defined in the template." msgstr "" #. Tag: para #, no-c-format msgid "Hence, resource templates help to reduce the amount of configuration work. If any changes are needed, they can be done to the template definition and will take effect globally in all resource definitions referencing that template." msgstr "" #. Tag: para #, no-c-format msgid "Resource templates have a syntax similar to that of primitives." msgstr "" #. Tag: title #, no-c-format msgid "Resource template for a migratable Xen virtual machine" msgstr "" #. Tag: programlisting #, no-c-format msgid "<template id=\"vm-template\" class=\"ocf\" provider=\"heartbeat\" type=\"Xen\">\n" " <meta_attributes id=\"vm-template-meta_attributes\">\n" " <nvpair id=\"vm-template-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"true\"/>\n" " </meta_attributes>\n" " <utilization id=\"vm-template-utilization\">\n" " <nvpair id=\"vm-template-utilization-memory\" name=\"memory\" value=\"512\"/>\n" " </utilization>\n" " <operations>\n" " <op id=\"vm-template-monitor-15s\" interval=\"15s\" name=\"monitor\" timeout=\"60s\"/>\n" " <op id=\"vm-template-start-0\" interval=\"0\" name=\"start\" timeout=\"60s\"/>\n" " </operations>\n" "</template>" msgstr "" #. Tag: para #, no-c-format msgid "Once you define a resource template, you can use it in primitives by specifying the template property." msgstr "" #. Tag: title #, no-c-format msgid "Xen primitive resource using a resource template" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"vm1\" template=\"vm-template\">\n" " <instance_attributes id=\"vm1-instance_attributes\">\n" " <nvpair id=\"vm1-instance_attributes-name\" name=\"name\" value=\"vm1\"/>\n" " <nvpair id=\"vm1-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm1\"/>\n" " </instance_attributes>\n" "</primitive>" msgstr "" #. Tag: para #, no-c-format msgid "In the example above, the new primitive vm1 will inherit everything from vm-template. For example, the equivalent of the above two examples would be:" msgstr "" #. Tag: title #, no-c-format msgid "Equivalent Xen primitive resource not using a resource template" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"vm1\" class=\"ocf\" provider=\"heartbeat\" type=\"Xen\">\n" " <meta_attributes id=\"vm-template-meta_attributes\">\n" " <nvpair id=\"vm-template-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"true\"/>\n" " </meta_attributes>\n" " <utilization id=\"vm-template-utilization\">\n" " <nvpair id=\"vm-template-utilization-memory\" name=\"memory\" value=\"512\"/>\n" " </utilization>\n" " <operations>\n" " <op id=\"vm-template-monitor-15s\" interval=\"15s\" name=\"monitor\" timeout=\"60s\"/>\n" " <op id=\"vm-template-start-0\" interval=\"0\" name=\"start\" timeout=\"60s\"/>\n" " </operations>\n" " <instance_attributes id=\"vm1-instance_attributes\">\n" " <nvpair id=\"vm1-instance_attributes-name\" name=\"name\" value=\"vm1\"/>\n" " <nvpair id=\"vm1-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm1\"/>\n" " </instance_attributes>\n" "</primitive>" msgstr "" #. Tag: para #, no-c-format msgid "If you want to overwrite some attributes or operations, add them to the particular primitive’s definition." msgstr "" #. Tag: title #, no-c-format msgid "Xen resource overriding template values" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"vm2\" template=\"vm-template\">\n" " <meta_attributes id=\"vm2-meta_attributes\">\n" " <nvpair id=\"vm2-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"false\"/>\n" " </meta_attributes>\n" " <utilization id=\"vm2-utilization\">\n" " <nvpair id=\"vm2-utilization-memory\" name=\"memory\" value=\"1024\"/>\n" " </utilization>\n" " <instance_attributes id=\"vm2-instance_attributes\">\n" " <nvpair id=\"vm2-instance_attributes-name\" name=\"name\" value=\"vm2\"/>\n" " <nvpair id=\"vm2-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm2\"/>\n" " </instance_attributes>\n" " <operations>\n" " <op id=\"vm2-monitor-30s\" interval=\"30s\" name=\"monitor\" timeout=\"120s\"/>\n" " <op id=\"vm2-stop-0\" interval=\"0\" name=\"stop\" timeout=\"60s\"/>\n" " </operations>\n" "</primitive>" msgstr "" #. Tag: para #, no-c-format msgid "In the example above, the new primitive vm2 has special attribute values. Its monitor operation has a longer timeout and interval, and the primitive has an additional stop operation." msgstr "" #. Tag: para #, no-c-format msgid "To see the resulting definition of a resource, run:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_resource --query-xml --resource vm2" msgstr "" #. Tag: para #, no-c-format msgid "To see the raw definition of a resource in the CIB, run:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_resource --query-xml-raw --resource vm2" msgstr "" #. Tag: title #, no-c-format msgid "Referencing Templates in Constraints" msgstr "" #. Tag: para #, no-c-format msgid "A resource template can be referenced in the following types of constraints:" msgstr "" #. Tag: para #, no-c-format msgid "order constraints (see )" msgstr "" #. Tag: para #, no-c-format msgid "colocation constraints (see )" msgstr "" #. Tag: para #, no-c-format msgid "rsc_ticket constraints (for multi-site clusters as described in )" msgstr "" #. Tag: para #, no-c-format msgid "Resource templates referenced in constraints stand for all primitives which are derived from that template. This means, the constraint applies to all primitive resources referencing the resource template. Referencing resource templates in constraints is an alternative to resource sets and can simplify the cluster configuration considerably." msgstr "" #. Tag: para #, no-c-format msgid "For example, given the example templates earlier in this section:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_colocation id=\"vm-template-colo-base-rsc\" rsc=\"vm-template\" rsc-role=\"Started\" with-rsc=\"base-rsc\" score=\"INFINITY\"/>" msgstr "" #. Tag: para #, no-c-format msgid "would colocate all VMs with base-rsc and is the equivalent of the following constraint configuration:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_colocation id=\"vm-colo-base-rsc\" score=\"INFINITY\">\n" " <resource_set id=\"vm-colo-base-rsc-0\" sequential=\"false\" role=\"Started\">\n" " <resource_ref id=\"vm1\"/>\n" " <resource_ref id=\"vm2\"/>\n" " </resource_set>\n" " <resource_set id=\"vm-colo-base-rsc-1\">\n" " <resource_ref id=\"base-rsc\"/>\n" " </resource_set>\n" "</rsc_colocation>" msgstr "" #. Tag: para #, no-c-format msgid "In a colocation constraint, only one template may be referenced from either rsc or with-rsc; the other reference must be a regular resource." msgstr "" #. Tag: title #, no-c-format msgid "Referencing Resource Templates in Sequential Resource Sets" msgstr "" #. Tag: para #, no-c-format msgid "Resource templates can also be referenced in resource sets." msgstr "" #. Tag: para #, no-c-format msgid "For example:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_order id=\"order1\" score=\"INFINITY\">\n" " <resource_set id=\"order1-0\">\n" " <resource_ref id=\"base-rsc\"/>\n" " <resource_ref id=\"vm-template\"/>\n" " <resource_ref id=\"top-rsc\"/>\n" " </resource_set>\n" "</rsc_order>" msgstr "" #. Tag: para #, no-c-format msgid "is the equivalent of the following constraint configuration:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_order id=\"order1\" score=\"INFINITY\">\n" " <resource_set id=\"order1-0\">\n" " <resource_ref id=\"base-rsc\"/>\n" " <resource_ref id=\"vm1\"/>\n" " <resource_ref id=\"vm2\"/>\n" " <resource_ref id=\"top-rsc\"/>\n" " </resource_set>\n" "</rsc_order>" msgstr "" #. Tag: title #, no-c-format msgid "Referencing Resource Templates in Parallel Resource Sets" msgstr "" #. Tag: para #, no-c-format msgid "If the resources referencing the template can run in parallel:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_order id=\"order2\" score=\"INFINITY\">\n" " <resource_set id=\"order2-0\">\n" " <resource_ref id=\"base-rsc\"/>\n" " </resource_set>\n" " <resource_set id=\"order2-1\" sequential=\"false\">\n" " <resource_ref id=\"vm-template\"/>\n" " </resource_set>\n" " <resource_set id=\"order2-2\">\n" " <resource_ref id=\"top-rsc\"/>\n" " </resource_set>\n" "</rsc_order>" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_order id=\"order2\" score=\"INFINITY\">\n" " <resource_set id=\"order2-0\">\n" " <resource_ref id=\"base-rsc\"/>\n" " </resource_set>\n" " <resource_set id=\"order2-1\" sequential=\"false\">\n" " <resource_ref id=\"vm1\"/>\n" " <resource_ref id=\"vm2\"/>\n" " </resource_set>\n" " <resource_set id=\"order2-2\">\n" " <resource_ref id=\"top-rsc\"/>\n" " </resource_set>\n" "</rsc_order>" msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Ch-Resource-Templates.pot b/doc/Pacemaker_Explained/pot/Ch-Reusing-Configuration.pot similarity index 60% copy from doc/Pacemaker_Explained/pot/Ch-Resource-Templates.pot copy to doc/Pacemaker_Explained/pot/Ch-Reusing-Configuration.pot index ddd7fc9845..93e060a84e 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Resource-Templates.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Reusing-Configuration.pot @@ -1,317 +1,505 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Resource Templates" +msgid "Reusing Parts of the Configuration" msgstr "" #. Tag: para #, no-c-format -msgid "If you want to create lots of resources with similar configurations, defining a resource template simplifies the task. Once defined, it can be referenced in primitives or in certain types of constraints." +msgid "Pacemaker provides multiple ways to simplify the configuration XML by reusing parts of it in multiple places." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Besides simplifying the XML, this also allows you to manipulate multiple configuration elements with a single reference." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Reusing Resource Definitions" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "If you want to create lots of resources with similar configurations, defining a resource template simplifies the task. Once defined, it can be referenced in primitives or in certain types of constraints." msgstr "" #. Tag: title #, no-c-format msgid "Configuring Resources with Templates" msgstr "" #. Tag: para #, no-c-format msgid "The primitives referencing the template will inherit all meta-attributes, instance attributes, utilization attributes and operations defined in the template. And you can define specific attributes and operations for any of the primitives. If any of these are defined in both the template and the primitive, the values defined in the primitive will take precedence over the ones defined in the template." msgstr "" #. Tag: para #, no-c-format msgid "Hence, resource templates help to reduce the amount of configuration work. If any changes are needed, they can be done to the template definition and will take effect globally in all resource definitions referencing that template." msgstr "" #. Tag: para #, no-c-format msgid "Resource templates have a syntax similar to that of primitives." msgstr "" #. Tag: title #, no-c-format msgid "Resource template for a migratable Xen virtual machine" msgstr "" #. Tag: programlisting #, no-c-format msgid "<template id=\"vm-template\" class=\"ocf\" provider=\"heartbeat\" type=\"Xen\">\n" " <meta_attributes id=\"vm-template-meta_attributes\">\n" " <nvpair id=\"vm-template-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"true\"/>\n" " </meta_attributes>\n" " <utilization id=\"vm-template-utilization\">\n" " <nvpair id=\"vm-template-utilization-memory\" name=\"memory\" value=\"512\"/>\n" " </utilization>\n" " <operations>\n" " <op id=\"vm-template-monitor-15s\" interval=\"15s\" name=\"monitor\" timeout=\"60s\"/>\n" " <op id=\"vm-template-start-0\" interval=\"0\" name=\"start\" timeout=\"60s\"/>\n" " </operations>\n" "</template>" msgstr "" #. Tag: para #, no-c-format msgid "Once you define a resource template, you can use it in primitives by specifying the template property." msgstr "" #. Tag: title #, no-c-format msgid "Xen primitive resource using a resource template" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"vm1\" template=\"vm-template\">\n" " <instance_attributes id=\"vm1-instance_attributes\">\n" " <nvpair id=\"vm1-instance_attributes-name\" name=\"name\" value=\"vm1\"/>\n" " <nvpair id=\"vm1-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm1\"/>\n" " </instance_attributes>\n" "</primitive>" msgstr "" #. Tag: para #, no-c-format msgid "In the example above, the new primitive vm1 will inherit everything from vm-template. For example, the equivalent of the above two examples would be:" msgstr "" #. Tag: title #, no-c-format msgid "Equivalent Xen primitive resource not using a resource template" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"vm1\" class=\"ocf\" provider=\"heartbeat\" type=\"Xen\">\n" " <meta_attributes id=\"vm-template-meta_attributes\">\n" " <nvpair id=\"vm-template-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"true\"/>\n" " </meta_attributes>\n" " <utilization id=\"vm-template-utilization\">\n" " <nvpair id=\"vm-template-utilization-memory\" name=\"memory\" value=\"512\"/>\n" " </utilization>\n" " <operations>\n" " <op id=\"vm-template-monitor-15s\" interval=\"15s\" name=\"monitor\" timeout=\"60s\"/>\n" " <op id=\"vm-template-start-0\" interval=\"0\" name=\"start\" timeout=\"60s\"/>\n" " </operations>\n" " <instance_attributes id=\"vm1-instance_attributes\">\n" " <nvpair id=\"vm1-instance_attributes-name\" name=\"name\" value=\"vm1\"/>\n" " <nvpair id=\"vm1-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm1\"/>\n" " </instance_attributes>\n" "</primitive>" msgstr "" #. Tag: para #, no-c-format msgid "If you want to overwrite some attributes or operations, add them to the particular primitive’s definition." msgstr "" #. Tag: title #, no-c-format msgid "Xen resource overriding template values" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"vm2\" template=\"vm-template\">\n" " <meta_attributes id=\"vm2-meta_attributes\">\n" " <nvpair id=\"vm2-meta_attributes-allow-migrate\" name=\"allow-migrate\" value=\"false\"/>\n" " </meta_attributes>\n" " <utilization id=\"vm2-utilization\">\n" " <nvpair id=\"vm2-utilization-memory\" name=\"memory\" value=\"1024\"/>\n" " </utilization>\n" " <instance_attributes id=\"vm2-instance_attributes\">\n" " <nvpair id=\"vm2-instance_attributes-name\" name=\"name\" value=\"vm2\"/>\n" " <nvpair id=\"vm2-instance_attributes-xmfile\" name=\"xmfile\" value=\"/etc/xen/shared-vm/vm2\"/>\n" " </instance_attributes>\n" " <operations>\n" " <op id=\"vm2-monitor-30s\" interval=\"30s\" name=\"monitor\" timeout=\"120s\"/>\n" " <op id=\"vm2-stop-0\" interval=\"0\" name=\"stop\" timeout=\"60s\"/>\n" " </operations>\n" "</primitive>" msgstr "" #. Tag: para #, no-c-format msgid "In the example above, the new primitive vm2 has special attribute values. Its monitor operation has a longer timeout and interval, and the primitive has an additional stop operation." msgstr "" #. Tag: para #, no-c-format msgid "To see the resulting definition of a resource, run:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_resource --query-xml --resource vm2" msgstr "" #. Tag: para #, no-c-format msgid "To see the raw definition of a resource in the CIB, run:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_resource --query-xml-raw --resource vm2" msgstr "" #. Tag: title #, no-c-format -msgid "Referencing Templates in Constraints" +msgid "Using Templates in Constraints" msgstr "" #. Tag: para #, no-c-format msgid "A resource template can be referenced in the following types of constraints:" msgstr "" #. Tag: para #, no-c-format msgid "order constraints (see )" msgstr "" #. Tag: para #, no-c-format msgid "colocation constraints (see )" msgstr "" #. Tag: para #, no-c-format msgid "rsc_ticket constraints (for multi-site clusters as described in )" msgstr "" #. Tag: para #, no-c-format msgid "Resource templates referenced in constraints stand for all primitives which are derived from that template. This means, the constraint applies to all primitive resources referencing the resource template. Referencing resource templates in constraints is an alternative to resource sets and can simplify the cluster configuration considerably." msgstr "" #. Tag: para #, no-c-format msgid "For example, given the example templates earlier in this section:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_colocation id=\"vm-template-colo-base-rsc\" rsc=\"vm-template\" rsc-role=\"Started\" with-rsc=\"base-rsc\" score=\"INFINITY\"/>" msgstr "" #. Tag: para #, no-c-format msgid "would colocate all VMs with base-rsc and is the equivalent of the following constraint configuration:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_colocation id=\"vm-colo-base-rsc\" score=\"INFINITY\">\n" " <resource_set id=\"vm-colo-base-rsc-0\" sequential=\"false\" role=\"Started\">\n" " <resource_ref id=\"vm1\"/>\n" " <resource_ref id=\"vm2\"/>\n" " </resource_set>\n" " <resource_set id=\"vm-colo-base-rsc-1\">\n" " <resource_ref id=\"base-rsc\"/>\n" " </resource_set>\n" "</rsc_colocation>" msgstr "" #. Tag: para #, no-c-format msgid "In a colocation constraint, only one template may be referenced from either rsc or with-rsc; the other reference must be a regular resource." msgstr "" #. Tag: title #, no-c-format -msgid "Referencing Resource Templates in Sequential Resource Sets" +msgid "Using Templates in Resource Sets" msgstr "" #. Tag: para #, no-c-format msgid "Resource templates can also be referenced in resource sets." msgstr "" #. Tag: para #, no-c-format -msgid "For example:" +msgid "For example, given the example templates earlier in this section, then:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_order id=\"order1\" score=\"INFINITY\">\n" " <resource_set id=\"order1-0\">\n" " <resource_ref id=\"base-rsc\"/>\n" " <resource_ref id=\"vm-template\"/>\n" " <resource_ref id=\"top-rsc\"/>\n" " </resource_set>\n" "</rsc_order>" msgstr "" #. Tag: para #, no-c-format -msgid "is the equivalent of the following constraint configuration:" +msgid "is the equivalent of the following constraint using a sequential resource set:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_order id=\"order1\" score=\"INFINITY\">\n" " <resource_set id=\"order1-0\">\n" " <resource_ref id=\"base-rsc\"/>\n" " <resource_ref id=\"vm1\"/>\n" " <resource_ref id=\"vm2\"/>\n" " <resource_ref id=\"top-rsc\"/>\n" " </resource_set>\n" "</rsc_order>" msgstr "" -#. Tag: title -#, no-c-format -msgid "Referencing Resource Templates in Parallel Resource Sets" -msgstr "" - #. Tag: para #, no-c-format -msgid "If the resources referencing the template can run in parallel:" +msgid "Or, if the resources referencing the template can run in parallel, then:" msgstr "" #. Tag: programlisting #, no-c-format msgid "<rsc_order id=\"order2\" score=\"INFINITY\">\n" " <resource_set id=\"order2-0\">\n" " <resource_ref id=\"base-rsc\"/>\n" " </resource_set>\n" " <resource_set id=\"order2-1\" sequential=\"false\">\n" " <resource_ref id=\"vm-template\"/>\n" " </resource_set>\n" " <resource_set id=\"order2-2\">\n" " <resource_ref id=\"top-rsc\"/>\n" " </resource_set>\n" "</rsc_order>" msgstr "" +#. Tag: para +#, no-c-format +msgid "is the equivalent of the following constraint configuration:" +msgstr "" + #. Tag: programlisting #, no-c-format msgid "<rsc_order id=\"order2\" score=\"INFINITY\">\n" " <resource_set id=\"order2-0\">\n" " <resource_ref id=\"base-rsc\"/>\n" " </resource_set>\n" " <resource_set id=\"order2-1\" sequential=\"false\">\n" " <resource_ref id=\"vm1\"/>\n" " <resource_ref id=\"vm2\"/>\n" " </resource_set>\n" " <resource_set id=\"order2-2\">\n" " <resource_ref id=\"top-rsc\"/>\n" " </resource_set>\n" "</rsc_order>" msgstr "" +#. Tag: title +#, no-c-format +msgid "Reusing Rules, Options and Sets of Operations" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Sometimes a number of constraints need to use the same set of rules, and resources need to set the same options and parameters. To simplify this situation, you can refer to an existing object using an id-ref instead of an id." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "So if for one resource you have" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<rsc_location id=\"WebServer-connectivity\" rsc=\"Webserver\">\n" +" <rule id=\"ping-prefer-rule\" score-attribute=\"pingd\" >\n" +" <expression id=\"ping-prefer\" attribute=\"pingd\" operation=\"defined\"/>\n" +" </rule>\n" +"</rsc_location>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Then instead of duplicating the rule for all your other resources, you can instead specify:" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Referencing rules from other constraints" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<rsc_location id=\"WebDB-connectivity\" rsc=\"WebDB\">\n" +" <rule id-ref=\"ping-prefer-rule\"/>\n" +"</rsc_location>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The cluster will insist that the rule exists somewhere. Attempting to add a reference to a non-existing rule will cause a validation failure, as will attempting to remove a rule that is referenced elsewhere." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The same principle applies for meta_attributes and instance_attributes as illustrated in the example below:" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Referencing attributes, options, and operations from other resources" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<primitive id=\"mySpecialRsc\" class=\"ocf\" type=\"Special\" provider=\"me\">\n" +" <instance_attributes id=\"mySpecialRsc-attrs\" score=\"1\" >\n" +" <nvpair id=\"default-interface\" name=\"interface\" value=\"eth0\"/>\n" +" <nvpair id=\"default-port\" name=\"port\" value=\"9999\"/>\n" +" </instance_attributes>\n" +" <meta_attributes id=\"mySpecialRsc-options\">\n" +" <nvpair id=\"failure-timeout\" name=\"failure-timeout\" value=\"5m\"/>\n" +" <nvpair id=\"migration-threshold\" name=\"migration-threshold\" value=\"1\"/>\n" +" <nvpair id=\"stickiness\" name=\"resource-stickiness\" value=\"0\"/>\n" +" </meta_attributes>\n" +" <operations id=\"health-checks\">\n" +" <op id=\"health-check\" name=\"monitor\" interval=\"60s\"/>\n" +" <op id=\"health-check\" name=\"monitor\" interval=\"30min\"/>\n" +" </operations>\n" +"</primitive>\n" +"<primitive id=\"myOtherlRsc\" class=\"ocf\" type=\"Other\" provider=\"me\">\n" +" <instance_attributes id-ref=\"mySpecialRsc-attrs\"/>\n" +" <meta_attributes id-ref=\"mySpecialRsc-options\"/>\n" +" <operations id-ref=\"health-checks\"/>\n" +"</primitive>" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Tagging Configuration Elements" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Pacemaker allows you to tag any configuration element that has an XML ID." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "The main purpose of tagging is to support higher-level user interface tools; Pacemaker itself only uses tags within constraints. Therefore, what you can do with tags mostly depends on the tools you use." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Configuring Tags" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "A tag is simply a named list of XML IDs." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Tag referencing three resources" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<tags>\n" +" <tag id=\"all-vms\">\n" +" <obj_ref id=\"vm1\"/>\n" +" <obj_ref id=\"vm2\"/>\n" +" <obj_ref id=\"vm3\"/>\n" +" </tag>\n" +"</tags>" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "What you can do with this new tag depends on what your higher-level tools support. For example, a tool might allow you to enable or disable all of the tagged resources at once, or show the status of just the tagged resources." +msgstr "" + +#. Tag: para +#, no-c-format +msgid "A single configuration element can be listed in any number of tags." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Using Tags in Constraints and Resource Sets" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "Pacemaker itself only uses tags in constraints. If you supply a tag name instead of a resource name in any constraint, the constraint will apply to all resources listed in that tag." +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Constraint using a tag" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<rsc_order id=\"order1\" first=\"storage\" then=\"all-vms\" kind=\"Mandatory\" />" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "In the example above, assuming the all-vms tag is defined as in the previous example, the constraint will behave the same as:" +msgstr "" + +#. Tag: title +#, no-c-format +msgid "Equivalent constraints without tags" +msgstr "" + +#. Tag: programlisting +#, no-c-format +msgid "<rsc_order id=\"order1-1\" first=\"storage\" then=\"vm1\" kind=\"Mandatory\" />\n" +"<rsc_order id=\"order1-2\" first=\"storage\" then=\"vm2\" kind=\"Mandatory\" />\n" +"<rsc_order id=\"order1-3\" first=\"storage\" then=\"vm2\" kind=\"Mandatory\" />" +msgstr "" + +#. Tag: para +#, no-c-format +msgid "A tag may be used directly in the constraint, or indirectly by being listed in a resource set used in the constraint. When used in a resource set, an expanded tag will honor the set’s sequential property." +msgstr "" + diff --git a/doc/Pacemaker_Explained/pot/Ch-Utilization.pot b/doc/Pacemaker_Explained/pot/Ch-Utilization.pot index 6f049ab60d..944ada7d9d 100644 --- a/doc/Pacemaker_Explained/pot/Ch-Utilization.pot +++ b/doc/Pacemaker_Explained/pot/Ch-Utilization.pot @@ -1,362 +1,362 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Utilization and Placement Strategy" msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker decides where to place a resource according to the resource allocation scores on every node. The resource will be allocated to the node where the resource has the highest score." msgstr "" #. Tag: para #, no-c-format msgid "If the resource allocation scores on all the nodes are equal, by the default placement strategy, Pacemaker will choose a node with the least number of allocated resources for balancing the load. If the number of resources on each node is equal, the first eligible node listed in the CIB will be chosen to run the resource." msgstr "" #. Tag: para #, no-c-format msgid "Often, in real-world situations, different resources use significantly different proportions of a node’s capacities (memory, I/O, etc.). We cannot balance the load ideally just according to the number of resources allocated to a node. Besides, if resources are placed such that their combined requirements exceed the provided capacity, they may fail to start completely or run with degraded performance." msgstr "" #. Tag: para #, no-c-format msgid "To take these factors into account, Pacemaker allows you to configure:" msgstr "" #. Tag: para #, no-c-format msgid "The capacity a certain node provides." msgstr "" #. Tag: para #, no-c-format msgid "The capacity a certain resource requires." msgstr "" #. Tag: para #, no-c-format msgid "An overall strategy for placement of resources." msgstr "" #. Tag: title #, no-c-format msgid "Utilization attributes" msgstr "" #. Tag: para #, no-c-format msgid "To configure the capacity that a node provides or a resource requires, you can use utilization attributes in node and resource objects. You can name utilization attributes according to your preferences and define as many name/value pairs as your configuration needs. However, the attributes' values must be integers." msgstr "" #. Tag: title #, no-c-format msgid "Specifying CPU and RAM capacities of two nodes" msgstr "" #. Tag: programlisting #, no-c-format msgid "<node id=\"node1\" type=\"normal\" uname=\"node1\">\n" " <utilization id=\"node1-utilization\">\n" " <nvpair id=\"node1-utilization-cpu\" name=\"cpu\" value=\"2\"/>\n" " <nvpair id=\"node1-utilization-memory\" name=\"memory\" value=\"2048\"/>\n" " </utilization>\n" "</node>\n" "<node id=\"node2\" type=\"normal\" uname=\"node2\">\n" " <utilization id=\"node2-utilization\">\n" " <nvpair id=\"node2-utilization-cpu\" name=\"cpu\" value=\"4\"/>\n" " <nvpair id=\"node2-utilization-memory\" name=\"memory\" value=\"4096\"/>\n" " </utilization>\n" "</node>" msgstr "" #. Tag: title #, no-c-format msgid "Specifying CPU and RAM consumed by several resources" msgstr "" #. Tag: programlisting #, no-c-format msgid "<primitive id=\"rsc-small\" class=\"ocf\" provider=\"pacemaker\" type=\"Dummy\">\n" " <utilization id=\"rsc-small-utilization\">\n" " <nvpair id=\"rsc-small-utilization-cpu\" name=\"cpu\" value=\"1\"/>\n" " <nvpair id=\"rsc-small-utilization-memory\" name=\"memory\" value=\"1024\"/>\n" " </utilization>\n" "</primitive>\n" "<primitive id=\"rsc-medium\" class=\"ocf\" provider=\"pacemaker\" type=\"Dummy\">\n" " <utilization id=\"rsc-medium-utilization\">\n" " <nvpair id=\"rsc-medium-utilization-cpu\" name=\"cpu\" value=\"2\"/>\n" " <nvpair id=\"rsc-medium-utilization-memory\" name=\"memory\" value=\"2048\"/>\n" " </utilization>\n" "</primitive>\n" "<primitive id=\"rsc-large\" class=\"ocf\" provider=\"pacemaker\" type=\"Dummy\">\n" " <utilization id=\"rsc-large-utilization\">\n" " <nvpair id=\"rsc-large-utilization-cpu\" name=\"cpu\" value=\"3\"/>\n" " <nvpair id=\"rsc-large-utilization-memory\" name=\"memory\" value=\"3072\"/>\n" " </utilization>\n" "</primitive>" msgstr "" #. Tag: para #, no-c-format msgid "A node is considered eligible for a resource if it has sufficient free capacity to satisfy the resource’s requirements. The nature of the required or provided capacities is completely irrelevant to Pacemaker — it just makes sure that all capacity requirements of a resource are satisfied before placing a resource to a node." msgstr "" #. Tag: title #, no-c-format msgid "Placement Strategy" msgstr "" #. Tag: para #, no-c-format msgid "After you have configured the capacities your nodes provide and the capacities your resources require, you need to set the placement-strategy in the global cluster options, otherwise the capacity configurations have no effect." msgstr "" #. Tag: para #, no-c-format msgid "Four values are available for the placement-strategy:" msgstr "" #. Tag: term #, no-c-format msgid "default" msgstr "" #. Tag: para #, no-c-format msgid "Utilization values are not taken into account at all. Resources are allocated according to allocation scores. If scores are equal, resources are evenly distributed across nodes." msgstr "" #. Tag: term #, no-c-format msgid "utilization" msgstr "" #. Tag: para #, no-c-format msgid "Utilization values are taken into account only when deciding whether a node is considered eligible (i.e. whether it has sufficient free capacity to satisfy the resource’s requirements). Load-balancing is still done based on the number of resources allocated to a node." msgstr "" #. Tag: term #, no-c-format msgid "balanced" msgstr "" #. Tag: para #, no-c-format msgid "Utilization values are taken into account when deciding whether a node is eligible to serve a resource and when load-balancing, so an attempt is made to spread the resources in a way that optimizes resource performance." msgstr "" #. Tag: term #, no-c-format msgid "minimal" msgstr "" #. Tag: para #, no-c-format msgid "Utilization values are taken into account only when deciding whether a node is eligible to serve a resource. For load-balancing, an attempt is made to concentrate the resources on as few nodes as possible, thereby enabling possible power savings on the remaining nodes." msgstr "" #. Tag: para #, no-c-format msgid "Set placement-strategy with crm_attribute:" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_attribute --name placement-strategy --update balanced" msgstr "" #. Tag: para #, no-c-format msgid "Now Pacemaker will ensure the load from your resources will be distributed evenly throughout the cluster, without the need for convoluted sets of colocation constraints." msgstr "" #. Tag: title #, no-c-format msgid "Allocation Details" msgstr "" #. Tag: title #, no-c-format msgid "Which node is preferred to get consumed first when allocating resources?" msgstr "" #. Tag: para #, no-c-format msgid "The node with the highest node weight gets consumed first. Node weight is a score maintained by the cluster to represent node health." msgstr "" #. Tag: para #, no-c-format msgid "If multiple nodes have the same node weight:" msgstr "" #. Tag: para #, no-c-format msgid "If placement-strategy is default or utilization, the node that has the least number of allocated resources gets consumed first." msgstr "" #. Tag: para #, no-c-format msgid "If their numbers of allocated resources are equal, the first eligible node listed in the CIB gets consumed first." msgstr "" #. Tag: para #, no-c-format msgid "If placement-strategy is balanced, the node that has the most free capacity gets consumed first." msgstr "" #. Tag: para #, no-c-format msgid "If the free capacities of the nodes are equal, the node that has the least number of allocated resources gets consumed first." msgstr "" #. Tag: para #, no-c-format msgid "If placement-strategy is minimal, the first eligible node listed in the CIB gets consumed first." msgstr "" #. Tag: title #, no-c-format msgid "Which node has more free capacity?" msgstr "" #. Tag: para #, no-c-format msgid "If only one type of utilization attribute has been defined, free capacity is a simple numeric comparison." msgstr "" #. Tag: para #, no-c-format msgid "If multiple types of utilization attributes have been defined, then the node that is numerically highest in the the most attribute types has the most free capacity. For example:" msgstr "" #. Tag: para #, no-c-format msgid "If nodeA has more free cpus, and nodeB has more free memory, then their free capacities are equal." msgstr "" #. Tag: para #, no-c-format msgid "If nodeA has more free cpus, while nodeB has more free memory and storage, then nodeB has more free capacity." msgstr "" #. Tag: title #, no-c-format msgid "Which resource is preferred to be assigned first?" msgstr "" #. Tag: para #, no-c-format msgid "The resource that has the highest priority (see ) gets allocated first." msgstr "" #. Tag: para #, no-c-format msgid "If their priorities are equal, check whether they are already running. The resource that has the highest score on the node where it’s running gets allocated first, to prevent resource shuffling." msgstr "" #. Tag: para #, no-c-format msgid "If the scores above are equal or the resources are not running, the resource has the highest score on the preferred node gets allocated first." msgstr "" #. Tag: para #, no-c-format msgid "If the scores above are equal, the first runnable resource listed in the CIB gets allocated first." msgstr "" #. Tag: title #, no-c-format msgid "Limitations and Workarounds" msgstr "" #. Tag: para #, no-c-format msgid "The type of problem Pacemaker is dealing with here is known as the knapsack problem and falls into the NP-complete category of computer science problems — a fancy way of saying \"it takes a really long time to solve\"." msgstr "" #. Tag: para #, no-c-format msgid "Clearly in a HA cluster, it’s not acceptable to spend minutes, let alone hours or days, finding an optimal solution while services remain unavailable." msgstr "" #. Tag: para #, no-c-format msgid "So instead of trying to solve the problem completely, Pacemaker uses a best effort algorithm for determining which node should host a particular service. This means it arrives at a solution much faster than traditional linear programming algorithms, but by doing so at the price of leaving some services stopped." msgstr "" #. Tag: para #, no-c-format msgid "In the contrived example at the start of this section:" msgstr "" #. Tag: para #, no-c-format msgid "rsc-small would be allocated to node1" msgstr "" #. Tag: para #, no-c-format msgid "rsc-medium would be allocated to node2" msgstr "" #. Tag: para #, no-c-format msgid "rsc-large would remain inactive" msgstr "" #. Tag: para #, no-c-format msgid "Which is not ideal." msgstr "" #. Tag: para #, no-c-format msgid "There are various approaches to dealing with the limitations of pacemaker’s placement strategy:" msgstr "" #. Tag: term #, no-c-format msgid "Ensure you have sufficient physical capacity." msgstr "" #. Tag: para #, no-c-format msgid "It might sound obvious, but if the physical capacity of your nodes is (close to) maxed out by the cluster under normal conditions, then failover isn’t going to go well. Even without the utilization feature, you’ll start hitting timeouts and getting secondary failures." msgstr "" #. Tag: term #, no-c-format msgid "Build some buffer into the capabilities advertised by the nodes." msgstr "" #. Tag: para #, no-c-format msgid "Advertise slightly more resources than we physically have, on the (usually valid) assumption that a resource will not use 100% of the configured amount of CPU, memory and so forth all the time. This practice is sometimes called overcommit." msgstr "" #. Tag: term #, no-c-format msgid "Specify resource priorities." msgstr "" #. Tag: para #, no-c-format msgid "If the cluster is going to sacrifice services, it should be the ones you care about (comparatively) the least. Ensure that resource priorities are properly set so that your most important resources are scheduled first." msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Pacemaker_Explained.pot b/doc/Pacemaker_Explained/pot/Pacemaker_Explained.pot index bda7be86d5..83087da995 100644 --- a/doc/Pacemaker_Explained/pot/Pacemaker_Explained.pot +++ b/doc/Pacemaker_Explained/pot/Pacemaker_Explained.pot @@ -1,44 +1,44 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Further Reading" msgstr "" #. Tag: para #, no-c-format msgid "Project Website: " msgstr "" #. Tag: para #, no-c-format msgid "Project Documentation: " msgstr "" #. Tag: para #, no-c-format msgid "SUSE High Availibility Guide: " msgstr "" #. Tag: para #, no-c-format msgid "Heartbeat configuration: " msgstr "" #. Tag: para #, no-c-format msgid "Corosync Configuration: " msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Preface.pot b/doc/Pacemaker_Explained/pot/Preface.pot index eb70fb6c89..f84c72b747 100644 --- a/doc/Pacemaker_Explained/pot/Preface.pot +++ b/doc/Pacemaker_Explained/pot/Preface.pot @@ -1,19 +1,19 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Preface" msgstr "" diff --git a/doc/Pacemaker_Explained/pot/Revision_History.pot b/doc/Pacemaker_Explained/pot/Revision_History.pot index eb4f85b805..56bf074103 100644 --- a/doc/Pacemaker_Explained/pot/Revision_History.pot +++ b/doc/Pacemaker_Explained/pot/Revision_History.pot @@ -1,89 +1,99 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Revision History" msgstr "" #. Tag: firstname #, no-c-format msgid "Andrew" msgstr "" #. Tag: surname #, no-c-format msgid "Beekhof" msgstr "" #. Tag: member #, no-c-format msgid "Import from Pages.app" msgstr "" #. Tag: member #, no-c-format msgid "Cleanup and reformatting of docbook xml complete" msgstr "" #. Tag: member #, no-c-format msgid "Split book into chapters and pass validation" msgstr "" #. Tag: member #, no-c-format msgid "Re-organize book for use with Publican" msgstr "" #. Tag: member #, no-c-format msgid "Converted to asciidoc (which is converted to docbook for use with Publican)" msgstr "" #. Tag: firstname #, no-c-format msgid "Ken" msgstr "" #. Tag: surname #, no-c-format msgid "Gaillot" msgstr "" #. Tag: member #, no-c-format msgid "Update for clarity, stylistic consistency and current command-line syntax" msgstr "" #. Tag: member #, no-c-format msgid "Update for Pacemaker 1.1.14" msgstr "" #. Tag: member #, no-c-format msgid "Update for Pacemaker 1.1.15" msgstr "" #. Tag: member #, no-c-format msgid "Overhaul upgrade documentation, and document node health strategies" msgstr "" #. Tag: member #, no-c-format msgid "Update for Pacemaker 1.1.16" msgstr "" +#. Tag: member +#, no-c-format +msgid "Update for Pacemaker 1.1.17" +msgstr "" + +#. Tag: member +#, no-c-format +msgid "Update for Pacemaker 1.1.18" +msgstr "" + diff --git a/doc/Pacemaker_Remote/en-US/Ch-Intro.txt b/doc/Pacemaker_Remote/en-US/Ch-Intro.txt index 06d1ccba89..3b6b0c2da0 100644 --- a/doc/Pacemaker_Remote/en-US/Ch-Intro.txt +++ b/doc/Pacemaker_Remote/en-US/Ch-Intro.txt @@ -1,202 +1,206 @@ = Scaling a Pacemaker Cluster = == Overview == In a basic Pacemaker high-availability cluster,footnote:[See the http://www.clusterlabs.org/doc/[Pacemaker documentation], especially 'Clusters From Scratch' and 'Pacemaker Explained', for basic information about high-availability using Pacemaker] each node runs the full cluster stack of corosync and all Pacemaker components. This allows great flexibility but limits scalability to around 16 nodes. To allow for scalability to dozens or even hundreds of nodes, Pacemaker allows nodes not running the full cluster stack to integrate into the cluster and have the cluster manage their resources as if they were a cluster node. == Terms == cluster node:: A node running the full high-availability stack of corosync and all Pacemaker components. Cluster nodes may run cluster resources, run all Pacemaker command-line tools (`crm_mon`, `crm_resource` and so on), execute fencing actions, count toward cluster quorum, and serve as the cluster's Designated Controller (DC). (((cluster node))) (((node,cluster node))) pacemaker_remote:: A small service daemon that allows a host to be used as a Pacemaker node without running the full cluster stack. Nodes running pacemaker_remote may run cluster resources and most command-line tools, but cannot perform other functions of full cluster nodes such as fencing execution, quorum voting or DC eligibility. The pacemaker_remote daemon is an enhanced version of Pacemaker's local resource management daemon (LRMD). (((pacemaker_remote))) remote node:: A physical host running pacemaker_remote. Remote nodes have a special resource that manages communication with the cluster. This is sometimes referred to as the 'baremetal' case. (((remote node))) (((node,remote node))) guest node:: A virtual host running pacemaker_remote. Guest nodes differ from remote nodes mainly in that the guest node is itself a resource that the cluster manages. (((guest node))) (((node,guest node))) [NOTE] ====== 'Remote' in this document refers to the node not being a part of the underlying corosync cluster. It has nothing to do with physical proximity. Remote nodes and guest nodes are subject to the same latency requirements as cluster nodes, which means they are typically in the same data center. ====== [NOTE] ====== It is important to distinguish the various roles a virtual machine can serve in Pacemaker clusters: * A virtual machine can run the full cluster stack, in which case it is a cluster node and is not itself managed by the cluster. * A virtual machine can be managed by the cluster as a resource, without the cluster having any awareness of the services running inside the virtual machine. The virtual machine is 'opaque' to the cluster. * A virtual machine can be a cluster resource, and run pacemaker_remote to make it a guest node, allowing the cluster to manage services inside it. The virtual machine is 'transparent' to the cluster. ====== == Support in Pacemaker Versions == It is recommended to run Pacemaker 1.1.12 or later when using pacemaker_remote due to important bug fixes. An overview of changes in pacemaker_remote capability by version (aside from bug fixes, which are included in every version): +.1.1.18 +* Support for unfencing remote nodes (useful with "fabric fencing" agents) +* Guest nodes are now probed for resource status before starting resources + .1.1.16 * Support for watchdog-based fencing (sbd) on remote nodes .1.1.15 * If pacemaker_remote is stopped on an active node, it will wait for the cluster to migrate all resources off before exiting, rather than exit immediately and get fenced. .1.1.14 * Resources that create guest nodes can be included in groups * reconnect_interval option for remote nodes .1.1.13 * Support for maintenance mode * Remote nodes can recover without being fenced when the cluster node hosting their connection fails * +#kind+ built-in node attribute for use with rules .1.1.12 * Support for permanent node attributes * Support for migration .1.1.11 * Support for IPv6 * Support for remote nodes * Support for transient node attributes * Support for clusters with mixed endian architectures .1.1.10 * remote-connect-timeout for guest nodes .1.1.9 * Initial version to include pacemaker_remote * Limited to guest nodes in KVM/LXC environments using only IPv4; all nodes' architectures must have same endianness == Guest Nodes == (((guest node))) (((node,guest node))) *"I want a Pacemaker cluster to manage virtual machine resources, but I also want Pacemaker to be able to manage the resources that live within those virtual machines."* Without pacemaker_remote, the possibilities for implementing the above use case have significant limitations: * The cluster stack could be run on the physical hosts only, which loses the ability to monitor resources within the guests. * A separate cluster could be on the virtual guests, which quickly hits scalability issues. * The cluster stack could be run on the guests using the same cluster as the physical hosts, which also hits scalability issues and complicates fencing. With pacemaker_remote: * The physical hosts are cluster nodes (running the full cluster stack). * The virtual machines are guest nodes (running the pacemaker_remote service). Nearly zero configuration is required on the virtual machine. * The cluster stack on the cluster nodes launches the virtual machines and immediately connects to the pacemaker_remote service on them, allowing the virtual machines to integrate into the cluster. The key difference here between the guest nodes and the cluster nodes is that the guest nodes do not run the cluster stack. This means they will never become the DC, initiate fencing actions or participate in quorum voting. On the other hand, this also means that they are not bound to the scalability limits associated with the cluster stack (no 16-node corosync member limits to deal with). That isn't to say that guest nodes can scale indefinitely, but it is known that guest nodes scale horizontally much further than cluster nodes. Other than the quorum limitation, these guest nodes behave just like cluster nodes with respect to resource management. The cluster is fully capable of managing and monitoring resources on each guest node. You can build constraints against guest nodes, put them in standby, or do whatever else you'd expect to be able to do with cluster nodes. They even show up in `crm_mon` output as nodes. To solidify the concept, below is an example that is very similar to an actual deployment we test in our developer environment to verify guest node scalability: * 16 cluster nodes running the full corosync + pacemaker stack * 64 Pacemaker-managed virtual machine resources running pacemaker_remote configured as guest nodes * 64 Pacemaker-managed webserver and database resources configured to run on the 64 guest nodes With this deployment, you would have 64 webservers and databases running on 64 virtual machines on 16 hardware nodes, all of which are managed and monitored by the same Pacemaker deployment. It is known that pacemaker_remote can scale to these lengths and possibly much further depending on the specific scenario. == Remote Nodes == (((remote node))) (((node,remote node))) *"I want my traditional high-availability cluster to scale beyond the limits imposed by the corosync messaging layer."* Ultimately, the primary advantage of remote nodes over cluster nodes is scalability. There are likely some other use cases related to geographically distributed HA clusters that remote nodes may serve a purpose in, but those use cases are not well understood at this point. Like guest nodes, remote nodes will never become the DC, initiate fencing actions or participate in quorum voting. That is not to say, however, that fencing of a remote node works any differently than that of a cluster node. The Pacemaker policy engine understands how to fence remote nodes. As long as a fencing device exists, the cluster is capable of ensuring remote nodes are fenced in the exact same way as cluster nodes. == Expanding the Cluster Stack == With pacemaker_remote, the traditional view of the high-availability stack can be expanded to include a new layer: .Traditional HA Stack image::images/pcmk-ha-cluster-stack.png["Traditional Pacemaker+Corosync Stack",width="17cm",height="9cm",align="center"] .HA Stack With Guest Nodes image::images/pcmk-ha-remote-stack.png["Pacemaker+Corosync Stack With pacemaker_remote",width="20cm",height="10cm",align="center"] diff --git a/doc/Pacemaker_Remote/pot/Author_Group.pot b/doc/Pacemaker_Remote/pot/Author_Group.pot index 85d3f585bc..a6f1fbd132 100644 --- a/doc/Pacemaker_Remote/pot/Author_Group.pot +++ b/doc/Pacemaker_Remote/pot/Author_Group.pot @@ -1,34 +1,34 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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: firstname #, no-c-format msgid "David" msgstr "" #. Tag: surname #, no-c-format msgid "Vossel" msgstr "" #. Tag: orgname #, no-c-format msgid "Red Hat" msgstr "" #. Tag: contrib #, no-c-format msgid "Primary author" msgstr "" diff --git a/doc/Pacemaker_Remote/pot/Book_Info.pot b/doc/Pacemaker_Remote/pot/Book_Info.pot index 23f05227e1..fd3dd34d84 100644 --- a/doc/Pacemaker_Remote/pot/Book_Info.pot +++ b/doc/Pacemaker_Remote/pot/Book_Info.pot @@ -1,74 +1,74 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Pacemaker Remote" msgstr "" #. Tag: subtitle #, no-c-format msgid "Scaling High Availablity Clusters" msgstr "" #. Tag: para #, no-c-format msgid "The document exists as both a reference and deployment guide for the Pacemaker Remote service." msgstr "" #. Tag: para #, no-c-format msgid "The example commands in this document will use:" msgstr "" #. Tag: para #, no-c-format msgid "&DISTRO; &DISTRO_VERSION; as the host operating system" msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker Remote to perform resource management within guest nodes and remote nodes" msgstr "" #. Tag: para #, no-c-format msgid "KVM for virtualization" msgstr "" #. Tag: para #, no-c-format msgid "libvirt to manage guest nodes" msgstr "" #. Tag: para #, no-c-format msgid "Corosync to provide messaging and membership services on cluster nodes" msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker to perform resource management on cluster nodes" msgstr "" #. Tag: para #, no-c-format msgid "pcs as the cluster configuration toolset" msgstr "" #. Tag: para #, no-c-format msgid "The concepts are the same for other distributions, virtualization platforms, toolsets, and messaging layers, and should be easily adaptable." msgstr "" diff --git a/doc/Pacemaker_Remote/pot/Ch-Alternatives.pot b/doc/Pacemaker_Remote/pot/Ch-Alternatives.pot index 3fcbb6f30b..d0f9587009 100644 --- a/doc/Pacemaker_Remote/pot/Ch-Alternatives.pot +++ b/doc/Pacemaker_Remote/pot/Ch-Alternatives.pot @@ -1,109 +1,109 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Alternative Configurations" msgstr "" #. Tag: para #, no-c-format -msgid "These alternative configurations may be appropriate in limited cases, such as a test cluster, but are not the best method in most situations. They are presented here for completeness and as an example of pacemaker’s flexibility to suit your needs." +msgid "These alternative configurations may be appropriate in limited cases, such as a test cluster, but are not the best method in most situations. They are presented here for completeness and as an example of Pacemaker’s flexibility to suit your needs." msgstr "" #. Tag: title #, no-c-format msgid "Virtual Machines as Cluster Nodes" msgstr "" #. Tag: para #, no-c-format -msgid "The preferred use of virtual machines in a pacemaker cluster is as a cluster resource, whether opaque or as a guest node. However, it is possible to run the full cluster stack on a virtual node instead." +msgid "The preferred use of virtual machines in a Pacemaker cluster is as a cluster resource, whether opaque or as a guest node. However, it is possible to run the full cluster stack on a virtual node instead." msgstr "" #. Tag: para #, no-c-format msgid "This is commonly used to set up test environments; a single physical host (that does not participate in the cluster) runs two or more virtual machines, all running the full cluster stack. This can be used to simulate a larger cluster for testing purposes." msgstr "" #. Tag: para #, no-c-format msgid "In a production environment, fencing becomes more complicated, especially if the underlying hosts run any services besides the clustered VMs. If the VMs are not guaranteed a minimum amount of host resources, CPU and I/O contention can cause timing issues for cluster components." msgstr "" #. Tag: para #, no-c-format msgid "Another situation where this approach is sometimes used is when the cluster owner leases the VMs from a provider and does not have direct access to the underlying host. The main concerns in this case are proper fencing (usually via a custom resource agent that communicates with the provider’s APIs) and maintaining a static IP address between reboots, as well as resource contention issues." msgstr "" #. Tag: title #, no-c-format msgid "Virtual Machines as Remote Nodes" msgstr "" #. Tag: para #, no-c-format msgid "Virtual machines may be configured following the process for remote nodes rather than guest nodes (i.e., using an ocf:pacemaker:remote resource rather than letting the cluster manage the VM directly)." msgstr "" #. Tag: para #, no-c-format msgid "This is mainly useful in testing, to use a single physical host to simulate a larger cluster involving remote nodes. Pacemaker’s Cluster Test Suite (CTS) uses this approach to test remote node functionality." msgstr "" #. Tag: title #, no-c-format msgid "Containers as Guest Nodes" msgstr "" #. Tag: para #, no-c-format msgid "Containers,https://en.wikipedia.org/wiki/Operating-system-level_virtualization and in particular Linux containers (LXC) and Docker, have become a popular method of isolating services in a resource-efficient manner." msgstr "" #. Tag: para #, no-c-format -msgid "The preferred means of integrating containers into Pacemaker is as a cluster resource, whether opaque or using Pacemaker’s built-in resource isolation support.Documentation for this support is planned but not yet available." +msgid "The preferred means of integrating containers into Pacemaker is as a cluster resource, whether opaque or using Pacemaker’s bundle resource type." msgstr "" #. Tag: para #, no-c-format msgid "However, it is possible to run pacemaker_remote inside a container, following the process for guest nodes. This is not recommended but can be useful, for example, in testing scenarios, to simulate a large number of guest nodes." msgstr "" #. Tag: para #, no-c-format msgid "The configuration process is very similar to that described for guest nodes using virtual machines. Key differences:" msgstr "" #. Tag: para #, no-c-format msgid "The underlying host must install the libvirt driver for the desired container technology — for example, the libvirt-daemon-lxc package to get the libvirt-lxc driver for LXC containers." msgstr "" #. Tag: para #, no-c-format msgid "Libvirt XML definitions must be generated for the containers. The pacemaker-cts package includes a script for this purpose, /usr/share/pacemaker/tests/cts/lxc_autogen.sh. Run it with the --help option for details on how to use it. It is intended for testing purposes only, and hardcodes various parameters that would need to be set appropriately in real usage. Of course, you can create XML definitions manually, following the appropriate libvirt driver documentation." msgstr "" #. Tag: para #, no-c-format msgid "To share the authentication key, either share the host’s /etc/pacemaker directory with the container, or copy the key into the container’s filesystem." msgstr "" #. Tag: para #, no-c-format msgid "The VirtualDomain resource for a container will need force_stop=\"true\" and an appropriate hypervisor option, for example hypervisor=\"lxc:///\" for LXC containers." msgstr "" diff --git a/doc/Pacemaker_Remote/pot/Ch-Baremetal-Tutorial.pot b/doc/Pacemaker_Remote/pot/Ch-Baremetal-Tutorial.pot index 97e2a2ae11..8d49324bca 100644 --- a/doc/Pacemaker_Remote/pot/Ch-Baremetal-Tutorial.pot +++ b/doc/Pacemaker_Remote/pot/Ch-Baremetal-Tutorial.pot @@ -1,458 +1,458 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Remote Node Walk-through" msgstr "" #. Tag: para #, no-c-format msgid "What this tutorial is: An in-depth walk-through of how to get Pacemaker to integrate a remote node into the cluster as a node capable of running cluster resources." msgstr "" #. Tag: para #, no-c-format msgid "What this tutorial is not: A realistic deployment scenario. The steps shown here are meant to get users familiar with the concept of remote nodes as quickly as possible." msgstr "" #. Tag: para #, no-c-format msgid "This tutorial requires three machines: two to act as cluster nodes, and a third to act as the remote node." msgstr "" #. Tag: title #, no-c-format msgid "Configure Remote Node" msgstr "" #. Tag: title #, no-c-format msgid "Configure Firewall on Remote Node" msgstr "" #. Tag: para #, no-c-format msgid "Allow cluster-related services through the local firewall:" msgstr "" #. Tag: screen #, no-c-format msgid "# firewall-cmd --permanent --add-service=high-availability\n" "success\n" "# firewall-cmd --reload\n" "success" msgstr "" #. Tag: para #, no-c-format msgid "If you are using iptables directly, or some other firewall solution besides firewalld, simply open the following ports, which can be used by various clustering components: TCP ports 2224, 3121, and 21064, and UDP port 5405." msgstr "" #. Tag: para #, no-c-format msgid "If you run into any problems during testing, you might want to disable the firewall and SELinux entirely until you have everything working. This may create significant security issues and should not be performed on machines that will be exposed to the outside world, but may be appropriate during development and testing on a protected host." msgstr "" #. Tag: para #, no-c-format msgid "To disable security measures:" msgstr "" #. Tag: screen #, no-c-format msgid "# setenforce 0\n" "# sed -i.bak \"s/SELINUX=enforcing/SELINUX=permissive/g\" /etc/selinux/config\n" "# systemctl mask firewalld.service\n" "# systemctl stop firewalld.service\n" "# iptables --flush" msgstr "" #. Tag: title #, no-c-format msgid "Configure pacemaker_remote on Remote Node" msgstr "" #. Tag: para #, no-c-format msgid "Install the pacemaker_remote daemon on the remote node." msgstr "" #. Tag: screen #, no-c-format msgid "# yum install -y pacemaker-remote resource-agents pcs" msgstr "" #. Tag: para #, no-c-format msgid "Create a location for the shared authentication key:" msgstr "" #. Tag: screen #, no-c-format msgid "# mkdir -p --mode=0750 /etc/pacemaker\n" "# chgrp haclient /etc/pacemaker" msgstr "" #. Tag: para #, no-c-format msgid "All nodes (both cluster nodes and remote nodes) must have the same authentication key installed for the communication to work correctly. If you already have a key on an existing node, copy it to the new remote node. Otherwise, create a new key, for example:" msgstr "" #. Tag: screen #, no-c-format msgid "# dd if=/dev/urandom of=/etc/pacemaker/authkey bs=4096 count=1" msgstr "" #. Tag: para #, no-c-format msgid "Now start and enable the pacemaker_remote daemon on the remote node." msgstr "" #. Tag: screen #, no-c-format msgid "# systemctl enable pacemaker_remote.service\n" "# systemctl start pacemaker_remote.service" msgstr "" #. Tag: para #, no-c-format msgid "Verify the start is successful." msgstr "" #. Tag: screen #, no-c-format msgid "# systemctl status pacemaker_remote\n" "pacemaker_remote.service - Pacemaker Remote Service\n" " Loaded: loaded (/usr/lib/systemd/system/pacemaker_remote.service; enabled)\n" " Active: active (running) since Fri 2015-08-21 15:21:20 CDT; 20s ago\n" " Main PID: 21273 (pacemaker_remot)\n" " CGroup: /system.slice/pacemaker_remote.service\n" " └─21273 /usr/sbin/pacemaker_remoted\n" "\n" "Aug 21 15:21:20 remote1 systemd[1]: Starting Pacemaker Remote Service...\n" "Aug 21 15:21:20 remote1 systemd[1]: Started Pacemaker Remote Service.\n" "Aug 21 15:21:20 remote1 pacemaker_remoted[21273]: notice: crm_add_logfile: Additional logging available in /var/log/pacemaker.log\n" "Aug 21 15:21:20 remote1 pacemaker_remoted[21273]: notice: lrmd_init_remote_tls_server: Starting a tls listener on port 3121.\n" "Aug 21 15:21:20 remote1 pacemaker_remoted[21273]: notice: bind_and_listen: Listening on address ::" msgstr "" #. Tag: title #, no-c-format msgid "Verify Connection to Remote Node" msgstr "" #. Tag: para #, no-c-format msgid "Before moving forward, it’s worth verifying that the cluster nodes can contact the remote node on port 3121. Here’s a trick you can use. Connect using ssh from each of the cluster nodes. The connection will get destroyed, but how it is destroyed tells you whether it worked or not." msgstr "" #. Tag: para #, no-c-format msgid "First, add the remote node’s hostname (we’re using remote1 in this tutorial) to the cluster nodes' /etc/hosts files if you haven’t already. This is required unless you have DNS set up in a way where remote1’s address can be discovered." msgstr "" #. Tag: para #, no-c-format msgid "Execute the following on each cluster node, replacing the IP address with the actual IP address of the remote node." msgstr "" #. Tag: screen #, no-c-format msgid "# cat << END >> /etc/hosts\n" "192.168.122.10 remote1\n" "END" msgstr "" #. Tag: para #, no-c-format msgid "If running the ssh command on one of the cluster nodes results in this output before disconnecting, the connection works:" msgstr "" #. Tag: screen #, no-c-format msgid "# ssh -p 3121 remote1\n" "ssh_exchange_identification: read: Connection reset by peer" msgstr "" #. Tag: para #, no-c-format msgid "If you see one of these, the connection is not working:" msgstr "" #. Tag: screen #, no-c-format msgid "# ssh -p 3121 remote1\n" "ssh: connect to host remote1 port 3121: No route to host" msgstr "" #. Tag: screen #, no-c-format msgid "# ssh -p 3121 remote1\n" "ssh: connect to host remote1 port 3121: Connection refused" msgstr "" #. Tag: para #, no-c-format msgid "Once you can successfully connect to the remote node from the both cluster nodes, move on to setting up Pacemaker on the cluster nodes." msgstr "" #. Tag: title #, no-c-format msgid "Configure Cluster Nodes" msgstr "" #. Tag: title #, no-c-format msgid "Configure Firewall on Cluster Nodes" msgstr "" #. Tag: para #, no-c-format msgid "On each cluster node, allow cluster-related services through the local firewall, following the same procedure as in ." msgstr "" #. Tag: title #, no-c-format msgid "Install Pacemaker on Cluster Nodes" msgstr "" #. Tag: para #, no-c-format msgid "On the two cluster nodes, install the following packages." msgstr "" #. Tag: screen #, no-c-format msgid "# yum install -y pacemaker corosync pcs resource-agents" msgstr "" #. Tag: title #, no-c-format msgid "Copy Authentication Key to Cluster Nodes" msgstr "" #. Tag: para #, no-c-format msgid "Create a location for the shared authentication key, and copy it from any existing node:" msgstr "" #. Tag: screen #, no-c-format msgid "# mkdir -p --mode=0750 /etc/pacemaker\n" "# chgrp haclient /etc/pacemaker\n" "# scp remote1:/etc/pacemaker/authkey /etc/pacemaker/authkey" msgstr "" #. Tag: title #, no-c-format msgid "Configure Corosync on Cluster Nodes" msgstr "" #. Tag: para #, no-c-format msgid "Corosync handles Pacemaker’s cluster membership and messaging. The corosync config file is located in /etc/corosync/corosync.conf. That config file must be initialized with information about the two cluster nodes before pacemaker can start." msgstr "" #. Tag: para #, no-c-format msgid "To initialize the corosync config file, execute the following pcs command on both nodes, filling in the information in <> with your nodes' information." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs cluster setup --force --local --name mycluster <node1 ip or hostname> <node2 ip or hostname>" msgstr "" #. Tag: title #, no-c-format msgid "Start Pacemaker on Cluster Nodes" msgstr "" #. Tag: para #, no-c-format msgid "Start the cluster stack on both cluster nodes using the following command." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs cluster start" msgstr "" #. Tag: para #, no-c-format msgid "Verify corosync membership" msgstr "" #. Tag: literallayout #, no-c-format msgid "# pcs status corosync\n" "Membership information\n" "----------------------\n" " Nodeid Votes Name\n" " 1 1 node1 (local)" msgstr "" #. Tag: para #, no-c-format msgid "Verify Pacemaker status. At first, the pcs cluster status output will look like this." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs status\n" "Cluster name: mycluster\n" "Last updated: Fri Aug 21 16:14:05 2015\n" "Last change: Fri Aug 21 14:02:14 2015\n" "Stack: corosync\n" "Current DC: NONE\n" "Version: 1.1.12-a14efad\n" "1 Nodes configured, unknown expected votes\n" "0 Resources configured" msgstr "" #. Tag: para #, no-c-format msgid "After about a minute, you should see your two cluster nodes come online." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs status\n" "Cluster name: mycluster\n" "Last updated: Fri Aug 21 16:16:32 2015\n" "Last change: Fri Aug 21 14:02:14 2015\n" "Stack: corosync\n" "Current DC: node1 (1) - partition with quorum\n" "Version: 1.1.12-a14efad\n" "2 Nodes configured\n" "0 Resources configured\n" "\n" "Online: [ node1 node2 ]" msgstr "" #. Tag: para #, no-c-format msgid "For the sake of this tutorial, we are going to disable stonith to avoid having to cover fencing device configuration." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs property set stonith-enabled=false" msgstr "" #. Tag: title #, no-c-format msgid "Integrate Remote Node into Cluster" msgstr "" #. Tag: para #, no-c-format msgid "Integrating a remote node into the cluster is achieved through the creation of a remote node connection resource. The remote node connection resource both establishes the connection to the remote node and defines that the remote node exists. Note that this resource is actually internal to Pacemaker’s crmd component. A metadata file for this resource can be found in the /usr/lib/ocf/resource.d/pacemaker/remote file that describes what options are available, but there is no actual ocf:pacemaker:remote resource agent script that performs any work." msgstr "" #. Tag: para #, no-c-format msgid "Define the remote node connection resource to our remote node, remote1, using the following command on any cluster node." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource create remote1 ocf:pacemaker:remote" msgstr "" #. Tag: para #, no-c-format msgid "That’s it. After a moment you should see the remote node come online." msgstr "" #. Tag: screen #, no-c-format msgid "Cluster name: mycluster\n" "Last updated: Fri Aug 21 17:13:09 2015\n" "Last change: Fri Aug 21 17:02:02 2015\n" "Stack: corosync\n" "Current DC: node1 (1) - partition with quorum\n" "Version: 1.1.12-a14efad\n" "3 Nodes configured\n" "1 Resources configured\n" "\n" "\n" "Online: [ node1 node2 ]\n" "RemoteOnline: [ remote1 ]\n" "\n" "Full list of resources:\n" "\n" " remote1 (ocf::pacemaker:remote): Started node1\n" "\n" "PCSD Status:\n" " node1: Online\n" " node2: Online\n" "\n" "Daemon Status:\n" " corosync: active/disabled\n" " pacemaker: active/disabled\n" " pcsd: active/enabled" msgstr "" #. Tag: title #, no-c-format msgid "Starting Resources on Remote Node" msgstr "" #. Tag: para #, no-c-format msgid "Once the remote node is integrated into the cluster, starting resources on a remote node is the exact same as on cluster nodes. Refer to the Clusters from Scratch document for examples of resource creation." msgstr "" #. Tag: para #, no-c-format msgid "Never involve a remote node connection resource in a resource group, colocation constraint, or order constraint." msgstr "" #. Tag: title #, no-c-format msgid "Fencing Remote Nodes" msgstr "" #. Tag: para #, no-c-format msgid "Remote nodes are fenced the same way as cluster nodes. No special considerations are required. Configure fencing resources for use with remote nodes the same as you would with cluster nodes." msgstr "" #. Tag: para #, no-c-format msgid "Note, however, that remote nodes can never initiate a fencing action. Only cluster nodes are capable of actually executing a fencing operation against another node." msgstr "" #. Tag: title #, no-c-format msgid "Accessing Cluster Tools from a Remote Node" msgstr "" #. Tag: para #, no-c-format msgid "Besides allowing the cluster to manage resources on a remote node, pacemaker_remote has one other trick. The pacemaker_remote daemon allows nearly all the pacemaker tools (crm_resource, crm_mon, crm_attribute, crm_master, etc.) to work on remote nodes natively." msgstr "" #. Tag: para #, no-c-format msgid "Try it: Run crm_mon on the remote node after pacemaker has integrated it into the cluster. These tools just work. These means resource agents such as master/slave resources which need access to tools like crm_master work seamlessly on the remote nodes." msgstr "" #. Tag: para #, no-c-format msgid "Higher-level command shells such as pcs may have partial support on remote nodes, but it is recommended to run them from a cluster node." msgstr "" diff --git a/doc/Pacemaker_Remote/pot/Ch-Example.pot b/doc/Pacemaker_Remote/pot/Ch-Example.pot index 5fd0b61a8f..f27a1eb1c6 100644 --- a/doc/Pacemaker_Remote/pot/Ch-Example.pot +++ b/doc/Pacemaker_Remote/pot/Ch-Example.pot @@ -1,174 +1,174 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Guest Node Quick Example" msgstr "" #. Tag: para #, no-c-format msgid "If you already know how to use Pacemaker, you’ll likely be able to grasp this new concept of guest nodes by reading through this quick example without having to sort through all the detailed walk-through steps. Here are the key configuration ingredients that make this possible using libvirt and KVM virtual guests. These steps strip everything down to the very basics. guest node nodeguest node guest node " msgstr "" #. Tag: title #, no-c-format msgid "Mile-High View of Configuration Steps" msgstr "" #. Tag: para #, no-c-format msgid "Give each virtual machine that will be used as a guest node a static network address and unique hostname." msgstr "" #. Tag: para #, no-c-format msgid "Put the same authentication key with the path /etc/pacemaker/authkey on every cluster node and virtual machine. This secures remote communication." msgstr "" #. Tag: para #, no-c-format msgid "Run this command if you want to make a somewhat random key:" msgstr "" #. Tag: screen #, no-c-format msgid "dd if=/dev/urandom of=/etc/pacemaker/authkey bs=4096 count=1" msgstr "" #. Tag: para #, no-c-format msgid "Install pacemaker_remote on every virtual machine, enabling it to start at boot, and if a local firewall is used, allow the node to accept connections on TCP port 3121." msgstr "" #. Tag: screen #, no-c-format msgid "yum install pacemaker-remote resource-agents\n" "systemctl enable pacemaker_remote\n" "firewall-cmd --add-port 3121/tcp --permanent" msgstr "" #. Tag: para #, no-c-format msgid "If you just want to see this work, you may want to simply disable the local firewall and put SELinux in permissive mode while testing. This creates security risks and should not be done on a production machine exposed to the Internet, but can be appropriate for a protected test machine." msgstr "" #. Tag: para #, no-c-format msgid "Create a Pacemaker resource to launch each virtual machine, using the remote-node meta-attribute to let Pacemaker know this will be a guest node capable of running resources." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource create vm-guest1 VirtualDomain hypervisor=\"qemu:///system\" config=\"vm-guest1.xml\" meta remote-node=\"guest1\"" msgstr "" #. Tag: para #, no-c-format msgid "The above command will create CIB XML similar to the following:" msgstr "" #. Tag: programlisting #, no-c-format msgid " <primitive class=\"ocf\" id=\"vm-guest1\" provider=\"heartbeat\" type=\"VirtualDomain\">\n" " <instance_attributes id=\"vm-guest-instance_attributes\">\n" " <nvpair id=\"vm-guest1-instance_attributes-hypervisor\" name=\"hypervisor\" value=\"qemu:///system\"/>\n" " <nvpair id=\"vm-guest1-instance_attributes-config\" name=\"config\" value=\"guest1.xml\"/>\n" " </instance_attributes>\n" " <operations>\n" " <op id=\"vm-guest1-interval-30s\" interval=\"30s\" name=\"monitor\"/>\n" " </operations>\n" " <meta_attributes id=\"vm-guest1-meta_attributes\">\n" " <nvpair id=\"vm-guest1-meta_attributes-remote-node\" name=\"remote-node\" value=\"guest1\"/>\n" " </meta_attributes>\n" " </primitive>" msgstr "" #. Tag: para #, no-c-format msgid "In the example above, the meta-attribute remote-node=\"guest1\" tells Pacemaker that this resource is a guest node with the hostname guest1. The cluster will attempt to contact the virtual machine’s pacemaker_remote service at the hostname guest1 after it launches." msgstr "" #. Tag: para #, no-c-format msgid "The ID of the resource creating the virtual machine (vm-guest1 in the above example) must be different from the virtual machine’s uname (guest1 in the above example). Pacemaker will create an implicit internal resource for the pacemaker_remote connection to the guest, named with the value of remote-node, so that value cannot be used as the name of any other resource." msgstr "" #. Tag: title #, no-c-format msgid "Using a Guest Node" msgstr "" #. Tag: para #, no-c-format msgid "Guest nodes will show up in crm_mon output as normal:" msgstr "" #. Tag: title #, no-c-format msgid "Example crm_mon output after guest1 is integrated into cluster" msgstr "" #. Tag: screen #, no-c-format msgid "Last updated: Wed Mar 13 13:52:39 2013\n" "Last change: Wed Mar 13 13:25:17 2013 via crmd on node1\n" "Stack: corosync\n" "Current DC: node1 (24815808) - partition with quorum\n" "Version: 1.1.10\n" "2 Nodes configured, unknown expected votes\n" "2 Resources configured.\n" "\n" "Online: [ node1 guest1]\n" "\n" "vm-guest1 (ocf::heartbeat:VirtualDomain): Started node1" msgstr "" #. Tag: para #, no-c-format msgid "Now, you could place a resource, such as a webserver, on guest1:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource create webserver apache params configfile=/etc/httpd/conf/httpd.conf op monitor interval=30s\n" "# pcs constraint location webserver prefers guest1" msgstr "" #. Tag: para #, no-c-format msgid "Now, the crm_mon output would show:" msgstr "" #. Tag: screen #, no-c-format msgid "Last updated: Wed Mar 13 13:52:39 2013\n" "Last change: Wed Mar 13 13:25:17 2013 via crmd on node1\n" "Stack: corosync\n" "Current DC: node1 (24815808) - partition with quorum\n" "Version: 1.1.10\n" "2 Nodes configured, unknown expected votes\n" "2 Resources configured.\n" "\n" "Online: [ node1 guest1]\n" "\n" "vm-guest1 (ocf::heartbeat:VirtualDomain): Started node1\n" "webserver (ocf::heartbeat::apache): Started guest1" msgstr "" #. Tag: para #, no-c-format msgid "It is worth noting that after guest1 is integrated into the cluster, nearly all the Pacemaker command-line tools immediately become available to the guest node. This means things like crm_mon, crm_resource, and crm_attribute will work natively on the guest node, as long as the connection between the guest node and a cluster node exists. This is particularly important for any master/slave resources executing on the guest node that need access to crm_master to set transient attributes." msgstr "" diff --git a/doc/Pacemaker_Remote/pot/Ch-Intro.pot b/doc/Pacemaker_Remote/pot/Ch-Intro.pot index 03f39e7341..dd7ee06b4d 100644 --- a/doc/Pacemaker_Remote/pot/Ch-Intro.pot +++ b/doc/Pacemaker_Remote/pot/Ch-Intro.pot @@ -1,384 +1,379 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Scaling a Pacemaker Cluster" msgstr "" #. Tag: title #, no-c-format msgid "Overview" msgstr "" #. Tag: para #, no-c-format msgid "In a basic Pacemaker high-availability cluster,See the Pacemaker documentation, especially Clusters From Scratch and Pacemaker Explained, for basic information about high-availability using Pacemaker each node runs the full cluster stack of corosync and all Pacemaker components. This allows great flexibility but limits scalability to around 16 nodes." msgstr "" #. Tag: para #, no-c-format msgid "To allow for scalability to dozens or even hundreds of nodes, Pacemaker allows nodes not running the full cluster stack to integrate into the cluster and have the cluster manage their resources as if they were a cluster node." msgstr "" #. Tag: title #, no-c-format msgid "Terms" msgstr "" #. Tag: term #, no-c-format msgid "cluster node" msgstr "" #. Tag: para #, no-c-format msgid "A node running the full high-availability stack of corosync and all Pacemaker components. Cluster nodes may run cluster resources, run all Pacemaker command-line tools (crm_mon, crm_resource and so on), execute fencing actions, count toward cluster quorum, and serve as the cluster’s Designated Controller (DC). cluster node nodecluster node cluster node " msgstr "" #. Tag: term #, no-c-format msgid "pacemaker_remote" msgstr "" #. Tag: para #, no-c-format msgid "A small service daemon that allows a host to be used as a Pacemaker node without running the full cluster stack. Nodes running pacemaker_remote may run cluster resources and most command-line tools, but cannot perform other functions of full cluster nodes such as fencing execution, quorum voting or DC eligibility. The pacemaker_remote daemon is an enhanced version of Pacemaker’s local resource management daemon (LRMD). pacemaker_remote " msgstr "" #. Tag: term #, no-c-format msgid "remote node" msgstr "" #. Tag: para #, no-c-format msgid "A physical host running pacemaker_remote. Remote nodes have a special resource that manages communication with the cluster. This is sometimes referred to as the baremetal case. remote node noderemote node remote node " msgstr "" #. Tag: term #, no-c-format msgid "guest node" msgstr "" #. Tag: para #, no-c-format msgid "A virtual host running pacemaker_remote. Guest nodes differ from remote nodes mainly in that the guest node is itself a resource that the cluster manages. guest node nodeguest node guest node " msgstr "" #. Tag: para #, no-c-format msgid "Remote in this document refers to the node not being a part of the underlying corosync cluster. It has nothing to do with physical proximity. Remote nodes and guest nodes are subject to the same latency requirements as cluster nodes, which means they are typically in the same data center." msgstr "" #. Tag: para #, no-c-format msgid "It is important to distinguish the various roles a virtual machine can serve in Pacemaker clusters:" msgstr "" #. Tag: para #, no-c-format msgid "A virtual machine can run the full cluster stack, in which case it is a cluster node and is not itself managed by the cluster." msgstr "" #. Tag: para #, no-c-format msgid "A virtual machine can be managed by the cluster as a resource, without the cluster having any awareness of the services running inside the virtual machine. The virtual machine is opaque to the cluster." msgstr "" #. Tag: para #, no-c-format msgid "A virtual machine can be a cluster resource, and run pacemaker_remote to make it a guest node, allowing the cluster to manage services inside it. The virtual machine is transparent to the cluster." msgstr "" #. Tag: title #, no-c-format msgid "Support in Pacemaker Versions" msgstr "" #. Tag: para #, no-c-format msgid "It is recommended to run Pacemaker 1.1.12 or later when using pacemaker_remote due to important bug fixes. An overview of changes in pacemaker_remote capability by version (aside from bug fixes, which are included in every version):" msgstr "" #. Tag: title #, no-c-format msgid "1.1.16" msgstr "" #. Tag: para #, no-c-format msgid "Support for watchdog-based fencing (sbd) on remote nodes" msgstr "" #. Tag: title #, no-c-format msgid "1.1.15" msgstr "" #. Tag: para #, no-c-format msgid "If pacemaker_remote is stopped on an active node, it will wait for the cluster to migrate all resources off before exiting, rather than exit immediately and get fenced." msgstr "" #. Tag: title #, no-c-format msgid "1.1.14" msgstr "" #. Tag: para #, no-c-format msgid "Resources that create guest nodes can be included in groups" msgstr "" #. Tag: para #, no-c-format msgid "reconnect_interval option for remote nodes" msgstr "" #. Tag: title #, no-c-format msgid "1.1.13" msgstr "" #. Tag: para #, no-c-format msgid "Support for maintenance mode" msgstr "" #. Tag: para #, no-c-format msgid "Remote nodes can recover without being fenced when the cluster node hosting their connection fails" msgstr "" -#. Tag: para -#, no-c-format -msgid "Running pacemaker_remote within LXC environments is deprecated due to newly added Pacemaker support for isolated resources" -msgstr "" - #. Tag: para #, no-c-format msgid "#kind built-in node attribute for use with rules" msgstr "" #. Tag: title #, no-c-format msgid "1.1.12" msgstr "" #. Tag: para #, no-c-format msgid "Support for permanent node attributes" msgstr "" #. Tag: para #, no-c-format msgid "Support for migration" msgstr "" #. Tag: title #, no-c-format msgid "1.1.11" msgstr "" #. Tag: para #, no-c-format msgid "Support for IPv6" msgstr "" #. Tag: para #, no-c-format msgid "Support for remote nodes" msgstr "" #. Tag: para #, no-c-format msgid "Support for transient node attributes" msgstr "" #. Tag: para #, no-c-format msgid "Support for clusters with mixed endian architectures" msgstr "" #. Tag: title #, no-c-format msgid "1.1.10" msgstr "" #. Tag: para #, no-c-format msgid "remote-connect-timeout for guest nodes" msgstr "" #. Tag: title #, no-c-format msgid "1.1.9" msgstr "" #. Tag: para #, no-c-format msgid "Initial version to include pacemaker_remote" msgstr "" #. Tag: para #, no-c-format msgid "Limited to guest nodes in KVM/LXC environments using only IPv4; all nodes' architectures must have same endianness" msgstr "" #. Tag: title #, no-c-format msgid "Guest Nodes" msgstr "" #. Tag: para #, no-c-format msgid " guest node nodeguest node guest node " msgstr "" #. Tag: para #, no-c-format msgid "\"I want a Pacemaker cluster to manage virtual machine resources, but I also want Pacemaker to be able to manage the resources that live within those virtual machines.\"" msgstr "" #. Tag: para #, no-c-format msgid "Without pacemaker_remote, the possibilities for implementing the above use case have significant limitations:" msgstr "" #. Tag: para #, no-c-format msgid "The cluster stack could be run on the physical hosts only, which loses the ability to monitor resources within the guests." msgstr "" #. Tag: para #, no-c-format msgid "A separate cluster could be on the virtual guests, which quickly hits scalability issues." msgstr "" #. Tag: para #, no-c-format msgid "The cluster stack could be run on the guests using the same cluster as the physical hosts, which also hits scalability issues and complicates fencing." msgstr "" #. Tag: para #, no-c-format msgid "With pacemaker_remote:" msgstr "" #. Tag: para #, no-c-format msgid "The physical hosts are cluster nodes (running the full cluster stack)." msgstr "" #. Tag: para #, no-c-format msgid "The virtual machines are guest nodes (running the pacemaker_remote service). Nearly zero configuration is required on the virtual machine." msgstr "" #. Tag: para #, no-c-format msgid "The cluster stack on the cluster nodes launches the virtual machines and immediately connects to the pacemaker_remote service on them, allowing the virtual machines to integrate into the cluster." msgstr "" #. Tag: para #, no-c-format msgid "The key difference here between the guest nodes and the cluster nodes is that the guest nodes do not run the cluster stack. This means they will never become the DC, initiate fencing actions or participate in quorum voting." msgstr "" #. Tag: para #, no-c-format msgid "On the other hand, this also means that they are not bound to the scalability limits associated with the cluster stack (no 16-node corosync member limits to deal with). That isn’t to say that guest nodes can scale indefinitely, but it is known that guest nodes scale horizontally much further than cluster nodes." msgstr "" #. Tag: para #, no-c-format msgid "Other than the quorum limitation, these guest nodes behave just like cluster nodes with respect to resource management. The cluster is fully capable of managing and monitoring resources on each guest node. You can build constraints against guest nodes, put them in standby, or do whatever else you’d expect to be able to do with cluster nodes. They even show up in crm_mon output as nodes." msgstr "" #. Tag: para #, no-c-format msgid "To solidify the concept, below is an example that is very similar to an actual deployment we test in our developer environment to verify guest node scalability:" msgstr "" #. Tag: para #, no-c-format msgid "16 cluster nodes running the full corosync + pacemaker stack" msgstr "" #. Tag: para #, no-c-format msgid "64 Pacemaker-managed virtual machine resources running pacemaker_remote configured as guest nodes" msgstr "" #. Tag: para #, no-c-format msgid "64 Pacemaker-managed webserver and database resources configured to run on the 64 guest nodes" msgstr "" #. Tag: para #, no-c-format msgid "With this deployment, you would have 64 webservers and databases running on 64 virtual machines on 16 hardware nodes, all of which are managed and monitored by the same Pacemaker deployment. It is known that pacemaker_remote can scale to these lengths and possibly much further depending on the specific scenario." msgstr "" #. Tag: title #, no-c-format msgid "Remote Nodes" msgstr "" #. Tag: para #, no-c-format msgid " remote node noderemote node remote node " msgstr "" #. Tag: para #, no-c-format msgid "\"I want my traditional high-availability cluster to scale beyond the limits imposed by the corosync messaging layer.\"" msgstr "" #. Tag: para #, no-c-format msgid "Ultimately, the primary advantage of remote nodes over cluster nodes is scalability. There are likely some other use cases related to geographically distributed HA clusters that remote nodes may serve a purpose in, but those use cases are not well understood at this point." msgstr "" #. Tag: para #, no-c-format msgid "Like guest nodes, remote nodes will never become the DC, initiate fencing actions or participate in quorum voting." msgstr "" #. Tag: para #, no-c-format msgid "That is not to say, however, that fencing of a remote node works any differently than that of a cluster node. The Pacemaker policy engine understands how to fence remote nodes. As long as a fencing device exists, the cluster is capable of ensuring remote nodes are fenced in the exact same way as cluster nodes." msgstr "" #. Tag: title #, no-c-format msgid "Expanding the Cluster Stack" msgstr "" #. Tag: para #, no-c-format msgid "With pacemaker_remote, the traditional view of the high-availability stack can be expanded to include a new layer:" msgstr "" #. Tag: title #, no-c-format msgid "Traditional HA Stack" msgstr "" #. Tag: title #, no-c-format msgid "HA Stack With Guest Nodes" msgstr "" diff --git a/doc/Pacemaker_Remote/pot/Ch-KVM-Tutorial.pot b/doc/Pacemaker_Remote/pot/Ch-KVM-Tutorial.pot index e76f35b752..a20b5674e3 100644 --- a/doc/Pacemaker_Remote/pot/Ch-KVM-Tutorial.pot +++ b/doc/Pacemaker_Remote/pot/Ch-KVM-Tutorial.pot @@ -1,767 +1,767 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Guest Node Walk-through" msgstr "" #. Tag: para #, no-c-format msgid "What this tutorial is: An in-depth walk-through of how to get Pacemaker to manage a KVM guest instance and integrate that guest into the cluster as a guest node." msgstr "" #. Tag: para #, no-c-format msgid "What this tutorial is not: A realistic deployment scenario. The steps shown here are meant to get users familiar with the concept of guest nodes as quickly as possible." msgstr "" #. Tag: title #, no-c-format msgid "Configure the Physical Host" msgstr "" #. Tag: para #, no-c-format msgid "For this example, we will use a single physical host named example-host. A production cluster would likely have multiple physical hosts, in which case you would run the commands here on each one, unless noted otherwise." msgstr "" #. Tag: title #, no-c-format msgid "Configure Firewall on Host" msgstr "" #. Tag: para #, no-c-format msgid "On the physical host, allow cluster-related services through the local firewall:" msgstr "" #. Tag: screen #, no-c-format msgid "# firewall-cmd --permanent --add-service=high-availability\n" "success\n" "# firewall-cmd --reload\n" "success" msgstr "" #. Tag: para #, no-c-format msgid "If you are using iptables directly, or some other firewall solution besides firewalld, simply open the following ports, which can be used by various clustering components: TCP ports 2224, 3121, and 21064, and UDP port 5405." msgstr "" #. Tag: para #, no-c-format msgid "If you run into any problems during testing, you might want to disable the firewall and SELinux entirely until you have everything working. This may create significant security issues and should not be performed on machines that will be exposed to the outside world, but may be appropriate during development and testing on a protected host." msgstr "" #. Tag: para #, no-c-format msgid "To disable security measures:" msgstr "" #. Tag: screen #, no-c-format msgid "[root@pcmk-1 ~]# setenforce 0\n" "[root@pcmk-1 ~]# sed -i.bak \"s/SELINUX=enforcing/SELINUX=permissive/g\" /etc/selinux/config\n" "[root@pcmk-1 ~]# systemctl mask firewalld.service\n" "[root@pcmk-1 ~]# systemctl stop firewalld.service\n" "[root@pcmk-1 ~]# iptables --flush" msgstr "" #. Tag: title #, no-c-format msgid "Install Cluster Software" msgstr "" #. Tag: screen #, no-c-format msgid "# yum install -y pacemaker corosync pcs resource-agents" msgstr "" #. Tag: title #, no-c-format msgid "Configure Corosync" msgstr "" #. Tag: para #, no-c-format msgid "Corosync handles pacemaker’s cluster membership and messaging. The corosync config file is located in /etc/corosync/corosync.conf. That config file must be initialized with information about the cluster nodes before pacemaker can start." msgstr "" #. Tag: para #, no-c-format msgid "To initialize the corosync config file, execute the following pcs command, replacing the cluster name and hostname as desired:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs cluster setup --force --local --name mycluster example-host" msgstr "" #. Tag: para #, no-c-format msgid "If you have multiple physical hosts, you would execute the setup command on only one host, but list all of them at the end of the command." msgstr "" #. Tag: title #, no-c-format msgid "Configure Pacemaker for Remote Node Communication" msgstr "" #. Tag: para #, no-c-format msgid "Create a place to hold an authentication key for use with pacemaker_remote:" msgstr "" #. Tag: screen #, no-c-format msgid "# mkdir -p --mode=0750 /etc/pacemaker\n" "# chgrp haclient /etc/pacemaker" msgstr "" #. Tag: para #, no-c-format msgid "Generate a key:" msgstr "" #. Tag: screen #, no-c-format msgid "# dd if=/dev/urandom of=/etc/pacemaker/authkey bs=4096 count=1" msgstr "" #. Tag: para #, no-c-format msgid "If you have multiple physical hosts, you would generate the key on only one host, and copy it to the same location on all hosts." msgstr "" #. Tag: title #, no-c-format msgid "Verify Cluster Software" msgstr "" #. Tag: para #, no-c-format msgid "Start the cluster" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs cluster start" msgstr "" #. Tag: para #, no-c-format msgid "Verify corosync membership" msgstr "" #. Tag: literallayout #, no-c-format msgid "# pcs status corosync\n" "\n" "Membership information\n" "----------------------\n" " Nodeid Votes Name\n" " 1 1 example-host (local)" msgstr "" #. Tag: para #, no-c-format msgid "Verify pacemaker status. At first, the output will look like this:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs status\n" "Cluster name: mycluster\n" "WARNING: no stonith devices and stonith-enabled is not false\n" "Last updated: Fri Oct 9 15:18:32 2015 Last change: Fri Oct 9 12:42:21 2015 by root via cibadmin on example-host\n" "Stack: corosync\n" "Current DC: NONE\n" "1 node and 0 resources configured\n" "\n" "Node example-host: UNCLEAN (offline)\n" "\n" "Full list of resources:\n" "\n" "\n" "PCSD Status:\n" " example-host: Online\n" "\n" "Daemon Status:\n" " corosync: active/disabled\n" " pacemaker: active/disabled\n" " pcsd: active/enabled" msgstr "" #. Tag: para #, no-c-format msgid "After a short amount of time, you should see your host as a single node in the cluster:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs status\n" "Cluster name: mycluster\n" "WARNING: no stonith devices and stonith-enabled is not false\n" "Last updated: Fri Oct 9 15:20:05 2015 Last change: Fri Oct 9 12:42:21 2015 by root via cibadmin on example-host\n" "Stack: corosync\n" "Current DC: example-host (version 1.1.13-a14efad) - partition WITHOUT quorum\n" "1 node and 0 resources configured\n" "\n" "Online: [ example-host ]\n" "\n" "Full list of resources:\n" "\n" "\n" "PCSD Status:\n" " example-host: Online\n" "\n" "Daemon Status:\n" " corosync: active/disabled\n" " pacemaker: active/disabled\n" " pcsd: active/enabled" msgstr "" #. Tag: title #, no-c-format msgid "Disable STONITH and Quorum" msgstr "" #. Tag: para #, no-c-format msgid "Now, enable the cluster to work without quorum or stonith. This is required for the sake of getting this tutorial to work with a single cluster node." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs property set stonith-enabled=false\n" "# pcs property set no-quorum-policy=ignore" msgstr "" #. Tag: para #, no-c-format msgid "The use of stonith-enabled=false is completely inappropriate for a production cluster. It tells the cluster to simply pretend that failed nodes are safely powered off. Some vendors will refuse to support clusters that have STONITH disabled. We disable STONITH here only to focus the discussion on pacemaker_remote, and to be able to use a single physical host in the example." msgstr "" #. Tag: para #, no-c-format msgid "Now, the status output should look similar to this:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs status\n" "Cluster name: mycluster\n" "Last updated: Fri Oct 9 15:22:49 2015 Last change: Fri Oct 9 15:22:46 2015 by root via cibadmin on example-host\n" "Stack: corosync\n" "Current DC: example-host (version 1.1.13-a14efad) - partition with quorum\n" "1 node and 0 resources configured\n" "\n" "Online: [ example-host ]\n" "\n" "Full list of resources:\n" "\n" "\n" "PCSD Status:\n" " example-host: Online\n" "\n" "Daemon Status:\n" " corosync: active/disabled\n" " pacemaker: active/disabled\n" " pcsd: active/enabled" msgstr "" #. Tag: para #, no-c-format msgid "Go ahead and stop the cluster for now after verifying everything is in order." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs cluster stop --force" msgstr "" #. Tag: title #, no-c-format msgid "Install Virtualization Software" msgstr "" #. Tag: screen #, no-c-format msgid "# yum install -y kvm libvirt qemu-system qemu-kvm bridge-utils virt-manager\n" "# systemctl enable libvirtd.service" msgstr "" #. Tag: para #, no-c-format msgid "Reboot the host." msgstr "" #. Tag: para #, no-c-format msgid "While KVM is used in this example, any virtualization platform with a Pacemaker resource agent can be used to create a guest node. The resource agent needs only to support usual commands (start, stop, etc.); Pacemaker implements the remote-node meta-attribute, independent of the agent." msgstr "" #. Tag: title #, no-c-format msgid "Configure the KVM guest" msgstr "" #. Tag: title #, no-c-format msgid "Create Guest" msgstr "" #. Tag: para #, no-c-format msgid "We will not outline here the installation steps required to create a KVM guest. There are plenty of tutorials available elsewhere that do that. Just be sure to configure the guest with a hostname and a static IP address (as an example here, we will use guest1 and 192.168.122.10)." msgstr "" #. Tag: title #, no-c-format msgid "Configure Firewall on Guest" msgstr "" #. Tag: para #, no-c-format msgid "On each guest, allow cluster-related services through the local firewall, following the same procedure as in ." msgstr "" #. Tag: title #, no-c-format msgid "Verify Connectivity" msgstr "" #. Tag: para #, no-c-format msgid "At this point, you should be able to ping and ssh into guests from hosts, and vice versa." msgstr "" #. Tag: title #, no-c-format msgid "Configure pacemaker_remote" msgstr "" #. Tag: para #, no-c-format msgid "Install pacemaker_remote, and enable it to run at start-up. Here, we also install the pacemaker package; it is not required, but it contains the dummy resource agent that we will use later for testing." msgstr "" #. Tag: screen #, no-c-format msgid "# yum install -y pacemaker pacemaker-remote resource-agents\n" "# systemctl enable pacemaker_remote.service" msgstr "" #. Tag: para #, no-c-format msgid "Copy the authentication key from a host:" msgstr "" #. Tag: screen #, no-c-format msgid "# mkdir -p --mode=0750 /etc/pacemaker\n" "# chgrp haclient /etc/pacemaker\n" "# scp root@example-host:/etc/pacemaker/authkey /etc/pacemaker" msgstr "" #. Tag: para #, no-c-format msgid "Start pacemaker_remote, and verify the start was successful:" msgstr "" #. Tag: screen #, no-c-format msgid "# systemctl start pacemaker_remote\n" "# systemctl status pacemaker_remote\n" "\n" " pacemaker_remote.service - Pacemaker Remote Service\n" " Loaded: loaded (/usr/lib/systemd/system/pacemaker_remote.service; enabled)\n" " Active: active (running) since Thu 2013-03-14 18:24:04 EDT; 2min 8s ago\n" " Main PID: 1233 (pacemaker_remot)\n" " CGroup: name=systemd:/system/pacemaker_remote.service\n" " └─1233 /usr/sbin/pacemaker_remoted\n" "\n" " Mar 14 18:24:04 guest1 systemd[1]: Starting Pacemaker Remote Service...\n" " Mar 14 18:24:04 guest1 systemd[1]: Started Pacemaker Remote Service.\n" " Mar 14 18:24:04 guest1 pacemaker_remoted[1233]: notice: lrmd_init_remote_tls_server: Starting a tls listener on port 3121." msgstr "" #. Tag: title #, no-c-format msgid "Verify Host Connection to Guest" msgstr "" #. Tag: para #, no-c-format msgid "Before moving forward, it’s worth verifying that the host can contact the guest on port 3121. Here’s a trick you can use. Connect using ssh from the host. The connection will get destroyed, but how it is destroyed tells you whether it worked or not." msgstr "" #. Tag: para #, no-c-format msgid "First add guest1 to the host machine’s /etc/hosts file if you haven’t already. This is required unless you have DNS setup in a way where guest1’s address can be discovered." msgstr "" #. Tag: screen #, no-c-format msgid "# cat << END >> /etc/hosts\n" "192.168.122.10 guest1\n" "END" msgstr "" #. Tag: para #, no-c-format msgid "If running the ssh command on one of the cluster nodes results in this output before disconnecting, the connection works:" msgstr "" #. Tag: screen #, no-c-format msgid "# ssh -p 3121 guest1\n" "ssh_exchange_identification: read: Connection reset by peer" msgstr "" #. Tag: para #, no-c-format msgid "If you see one of these, the connection is not working:" msgstr "" #. Tag: screen #, no-c-format msgid "# ssh -p 3121 guest1\n" "ssh: connect to host guest1 port 3121: No route to host" msgstr "" #. Tag: screen #, no-c-format msgid "# ssh -p 3121 guest1\n" "ssh: connect to host guest1 port 3121: Connection refused" msgstr "" #. Tag: para #, no-c-format msgid "Once you can successfully connect to the guest from the host, shutdown the guest. Pacemaker will be managing the virtual machine from this point forward." msgstr "" #. Tag: title #, no-c-format msgid "Integrate Guest into Cluster" msgstr "" #. Tag: para #, no-c-format msgid "Now the fun part, integrating the virtual machine you’ve just created into the cluster. It is incredibly simple." msgstr "" #. Tag: title #, no-c-format msgid "Start the Cluster" msgstr "" #. Tag: para #, no-c-format msgid "On the host, start pacemaker." msgstr "" #. Tag: para #, no-c-format msgid "Wait for the host to become the DC. The output of pcs status should look as it did in ." msgstr "" #. Tag: title #, no-c-format msgid "Integrate as Guest Node" msgstr "" #. Tag: para #, no-c-format msgid "If you didn’t already do this earlier in the verify host to guest connection section, add the KVM guest’s IP address to the host’s /etc/hosts file so we can connect by hostname. For this example:" msgstr "" #. Tag: para #, no-c-format msgid "We will use the VirtualDomain resource agent for the management of the virtual machine. This agent requires the virtual machine’s XML config to be dumped to a file on disk. To do this, pick out the name of the virtual machine you just created from the output of this list." msgstr "" #. Tag: literallayout #, no-c-format msgid "# virsh list --all\n" " Id Name State\n" "----------------------------------------------------\n" " - guest1 shut off" msgstr "" #. Tag: para #, no-c-format msgid "In my case I named it guest1. Dump the xml to a file somewhere on the host using the following command." msgstr "" #. Tag: screen #, no-c-format msgid "# virsh dumpxml guest1 > /etc/pacemaker/guest1.xml" msgstr "" #. Tag: para #, no-c-format msgid "Now just register the resource with pacemaker and you’re set!" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource create vm-guest1 VirtualDomain hypervisor=\"qemu:///system\" \\\n" " config=\"/etc/pacemaker/guest1.xml\" meta remote-node=guest1" msgstr "" #. Tag: para #, no-c-format msgid "This example puts the guest XML under /etc/pacemaker because the permissions and SELinux labeling should not need any changes. If you run into trouble with this or any step, try disabling SELinux with setenforce 0. If it works after that, see SELinux documentation for how to troubleshoot, if you wish to reenable SELinux." msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker will automatically monitor pacemaker_remote connections for failure, so it is not necessary to create a recurring monitor on the VirtualDomain resource." msgstr "" #. Tag: para #, no-c-format msgid "Once the vm-guest1 resource is started you will see guest1 appear in the pcs status output as a node. The final pcs status output should look something like this." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs status\n" "Cluster name: mycluster\n" "Last updated: Fri Oct 9 18:00:45 2015 Last change: Fri Oct 9 17:53:44 2015 by root via crm_resource on example-host\n" "Stack: corosync\n" "Current DC: example-host (version 1.1.13-a14efad) - partition with quorum\n" "2 nodes and 2 resources configured\n" "\n" "Online: [ example-host ]\n" "GuestOnline: [ guest1@example-host ]\n" "\n" "Full list of resources:\n" "\n" " vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host\n" "\n" "PCSD Status:\n" " example-host: Online\n" "\n" "Daemon Status:\n" " corosync: active/disabled\n" " pacemaker: active/disabled\n" " pcsd: active/enabled" msgstr "" #. Tag: title #, no-c-format msgid "Starting Resources on KVM Guest" msgstr "" #. Tag: para #, no-c-format msgid "The commands below demonstrate how resources can be executed on both the guest node and the cluster node." msgstr "" #. Tag: para #, no-c-format msgid "Create a few Dummy resources. Dummy resources are real resource agents used just for testing purposes. They actually execute on the host they are assigned to just like an apache server or database would, except their execution just means a file was created. When the resource is stopped, that the file it created is removed." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource create FAKE1 ocf:pacemaker:Dummy\n" "# pcs resource create FAKE2 ocf:pacemaker:Dummy\n" "# pcs resource create FAKE3 ocf:pacemaker:Dummy\n" "# pcs resource create FAKE4 ocf:pacemaker:Dummy\n" "# pcs resource create FAKE5 ocf:pacemaker:Dummy" msgstr "" #. Tag: para #, no-c-format msgid "Now check your pcs status output. In the resource section, you should see something like the following, where some of the resources started on the cluster node, and some started on the guest node." msgstr "" #. Tag: screen #, no-c-format msgid "Full list of resources:\n" "\n" " vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host\n" " FAKE1 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE2 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE3 (ocf::pacemaker:Dummy): Started example-host\n" " FAKE4 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE5 (ocf::pacemaker:Dummy): Started example-host" msgstr "" #. Tag: para #, no-c-format msgid "The guest node, guest1, reacts just like any other node in the cluster. For example, pick out a resource that is running on your cluster node. For my purposes, I am picking FAKE3 from the output above. We can force FAKE3 to run on guest1 in the exact same way we would any other node." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs constraint location FAKE3 prefers guest1" msgstr "" #. Tag: para #, no-c-format msgid "Now, looking at the bottom of the pcs status output you’ll see FAKE3 is on guest1." msgstr "" #. Tag: screen #, no-c-format msgid "Full list of resources:\n" "\n" " vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host\n" " FAKE1 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE2 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE3 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE4 (ocf::pacemaker:Dummy): Started example-host\n" " FAKE5 (ocf::pacemaker:Dummy): Started example-host" msgstr "" #. Tag: title #, no-c-format msgid "Testing Recovery and Fencing" msgstr "" #. Tag: para #, no-c-format msgid "Pacemaker’s policy engine is smart enough to know fencing guest nodes associated with a virtual machine means shutting off/rebooting the virtual machine. No special configuration is necessary to make this happen. If you are interested in testing this functionality out, trying stopping the guest’s pacemaker_remote daemon. This would be equivalent of abruptly terminating a cluster node’s corosync membership without properly shutting it down." msgstr "" #. Tag: para #, no-c-format msgid "ssh into the guest and run this command." msgstr "" #. Tag: screen #, no-c-format msgid "# kill -9 `pidof pacemaker_remoted`" msgstr "" #. Tag: para #, no-c-format msgid "Within a few seconds, your pcs status output will show a monitor failure, and the guest1 node will not be shown while it is being recovered." msgstr "" #. Tag: screen #, no-c-format msgid "# pcs status\n" "Cluster name: mycluster\n" "Last updated: Fri Oct 9 18:08:35 2015 Last change: Fri Oct 9 18:07:00 2015 by root via cibadmin on example-host\n" "Stack: corosync\n" "Current DC: example-host (version 1.1.13-a14efad) - partition with quorum\n" "2 nodes and 7 resources configured\n" "\n" "Online: [ example-host ]\n" "\n" "Full list of resources:\n" "\n" " vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host\n" " FAKE1 (ocf::pacemaker:Dummy): Stopped\n" " FAKE2 (ocf::pacemaker:Dummy): Stopped\n" " FAKE3 (ocf::pacemaker:Dummy): Stopped\n" " FAKE4 (ocf::pacemaker:Dummy): Started example-host\n" " FAKE5 (ocf::pacemaker:Dummy): Started example-host\n" "\n" "Failed Actions:\n" "* guest1_monitor_30000 on example-host 'unknown error' (1): call=8, status=Error, exitreason='none',\n" " last-rc-change='Fri Oct 9 18:08:29 2015', queued=0ms, exec=0ms\n" "\n" "\n" "PCSD Status:\n" " example-host: Online\n" "\n" "Daemon Status:\n" " corosync: active/disabled\n" " pacemaker: active/disabled\n" " pcsd: active/enabled" msgstr "" #. Tag: para #, no-c-format msgid "A guest node involves two resources: the one you explicitly configured creates the guest, and Pacemaker creates an implicit resource for the pacemaker_remote connection, which will be named the same as the value of the remote-node attribute of the explicit resource. When we killed pacemaker_remote, it is the implicit resource that failed, which is why the failed action starts with guest1 and not vm-guest1." msgstr "" #. Tag: para #, no-c-format msgid "Once recovery of the guest is complete, you’ll see it automatically get re-integrated into the cluster. The final pcs status output should look something like this." msgstr "" #. Tag: screen #, no-c-format msgid "Cluster name: mycluster\n" "Last updated: Fri Oct 9 18:18:30 2015 Last change: Fri Oct 9 18:07:00 2015 by root via cibadmin on example-host\n" "Stack: corosync\n" "Current DC: example-host (version 1.1.13-a14efad) - partition with quorum\n" "2 nodes and 7 resources configured\n" "\n" "Online: [ example-host ]\n" "GuestOnline: [ guest1@example-host ]\n" "\n" "Full list of resources:\n" "\n" " vm-guest1 (ocf::heartbeat:VirtualDomain): Started example-host\n" " FAKE1 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE2 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE3 (ocf::pacemaker:Dummy): Started guest1\n" " FAKE4 (ocf::pacemaker:Dummy): Started example-host\n" " FAKE5 (ocf::pacemaker:Dummy): Started example-host\n" "\n" "Failed Actions:\n" "* guest1_monitor_30000 on example-host 'unknown error' (1): call=8, status=Error, exitreason='none',\n" " last-rc-change='Fri Oct 9 18:08:29 2015', queued=0ms, exec=0ms\n" "\n" "\n" "PCSD Status:\n" " example-host: Online\n" "\n" "Daemon Status:\n" " corosync: active/disabled\n" " pacemaker: active/disabled\n" " pcsd: active/enabled" msgstr "" #. Tag: para #, no-c-format msgid "Normally, once you’ve investigated and addressed a failed action, you can clear the failure. However Pacemaker does not yet support cleanup for the implicitly created connection resource while the explicit resource is active. If you want to clear the failed action from the status output, stop the guest resource before clearing it. For example:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource disable vm-guest1 --wait\n" "# pcs resource cleanup guest1\n" "# pcs resource enable vm-guest1" msgstr "" #. Tag: title #, no-c-format msgid "Accessing Cluster Tools from Guest Node" msgstr "" #. Tag: para #, no-c-format msgid "Besides allowing the cluster to manage resources on a guest node, pacemaker_remote has one other trick. The pacemaker_remote daemon allows nearly all the pacemaker tools (crm_resource, crm_mon, crm_attribute, crm_master, etc.) to work on guest nodes natively." msgstr "" #. Tag: para #, no-c-format msgid "Try it: Run crm_mon on the guest after pacemaker has integrated the guest node into the cluster. These tools just work. This means resource agents such as master/slave resources which need access to tools like crm_master work seamlessly on the guest nodes." msgstr "" #. Tag: para #, no-c-format msgid "Higher-level command shells such as pcs may have partial support on guest nodes, but it is recommended to run them from a cluster node." msgstr "" diff --git a/doc/Pacemaker_Remote/pot/Ch-Options.pot b/doc/Pacemaker_Remote/pot/Ch-Options.pot index 052ae16850..77a04cde59 100644 --- a/doc/Pacemaker_Remote/pot/Ch-Options.pot +++ b/doc/Pacemaker_Remote/pot/Ch-Options.pot @@ -1,232 +1,232 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Configuration Explained" msgstr "" #. Tag: para #, no-c-format msgid "The walk-through examples use some of these options, but don’t explain exactly what they mean or do. This section is meant to be the go-to resource for all the options available for configuring pacemaker_remote-based nodes. configuration " msgstr "" #. Tag: title #, no-c-format msgid "Resource Meta-Attributes for Guest Nodes" msgstr "" #. Tag: para #, no-c-format msgid "When configuring a virtual machine as a guest node, the virtual machine is created using one of the usual resource agents for that purpose (for example, ocf:heartbeat:VirtualDomain or ocf:heartbeat:Xen), with additional metadata parameters." msgstr "" #. Tag: para #, no-c-format msgid "No restrictions are enforced on what agents may be used to create a guest node, but obviously the agent must create a distinct environment capable of running the pacemaker_remote daemon and cluster resources. An additional requirement is that fencing the host running the guest node resource must be sufficient for ensuring the guest node is stopped. This means, for example, that not all hypervisors supported by VirtualDomain may be used to create guest nodes; if the guest can survive the hypervisor being fenced, it may not be used as a guest node." msgstr "" #. Tag: para #, no-c-format msgid "Below are the metadata options available to enable a resource as a guest node and define its connection parameters." msgstr "" #. Tag: title #, no-c-format msgid "Meta-attributes for configuring VM resources as guest nodes" msgstr "" #. Tag: entry #, no-c-format msgid "Option" msgstr "" #. Tag: entry #, no-c-format msgid "Default" msgstr "" #. Tag: entry #, no-c-format msgid "Description" msgstr "" #. Tag: para #, no-c-format msgid "remote-node" msgstr "" #. Tag: para #, no-c-format msgid "none" msgstr "" #. Tag: para #, no-c-format msgid "The node name of the guest node this resource defines. This both enables the resource as a guest node and defines the unique name used to identify the guest node. If no other parameters are set, this value will also be assumed as the hostname to use when connecting to pacemaker_remote on the VM. This value must not overlap with any resource or node IDs." msgstr "" #. Tag: para #, no-c-format msgid "remote-port" msgstr "" #. Tag: para #, no-c-format msgid "3121" msgstr "" #. Tag: para #, no-c-format msgid "The port on the virtual machine that the cluster will use to connect to pacemaker_remote." msgstr "" #. Tag: para #, no-c-format msgid "remote-addr" msgstr "" #. Tag: para #, no-c-format msgid "value of remote-node" msgstr "" #. Tag: para #, no-c-format msgid "The IP address or hostname to use when connecting to pacemaker_remote on the VM." msgstr "" #. Tag: para #, no-c-format msgid "remote-connect-timeout" msgstr "" #. Tag: para #, no-c-format msgid "60s" msgstr "" #. Tag: para #, no-c-format msgid "How long before a pending guest connection will time out." msgstr "" #. Tag: title #, no-c-format msgid "Connection Resources for Remote Nodes" msgstr "" #. Tag: para #, no-c-format msgid "A remote node is defined by a connection resource. That connection resource has instance attributes that define where the remote node is located on the network and how to communicate with it." msgstr "" #. Tag: para #, no-c-format msgid "Descriptions of these instance attributes can be retrieved using the following pcs command:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource describe remote\n" "ocf:pacemaker:remote - remote resource agent\n" "\n" "Resource options:\n" " server: Server location to connect to. This can be an ip address or hostname.\n" " port: tcp port to connect to.\n" " reconnect_interval: Interval in seconds at which Pacemaker will attempt to\n" " reconnect to a remote node after an active connection to\n" " the remote node has been severed. When this value is\n" " nonzero, Pacemaker will retry the connection\n" " indefinitely, at the specified interval. As with any\n" " time-based actions, this is not guaranteed to be checked\n" " more frequently than the value of the\n" " cluster-recheck-interval cluster option." msgstr "" #. Tag: para #, no-c-format msgid "When defining a remote node’s connection resource, it is common and recommended to name the connection resource the same as the remote node’s hostname. By default, if no server option is provided, the cluster will attempt to contact the remote node using the resource name as the hostname." msgstr "" #. Tag: para #, no-c-format msgid "Example defining a remote node with the hostname remote1:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource create remote1 remote" msgstr "" #. Tag: para #, no-c-format msgid "Example defining a remote node to connect to a specific IP address and port:" msgstr "" #. Tag: screen #, no-c-format msgid "# pcs resource create remote1 remote server=192.168.122.200 port=8938" msgstr "" #. Tag: title #, no-c-format msgid "Environment Variables for Daemon Start-up" msgstr "" #. Tag: para #, no-c-format msgid "Authentication and encryption of the connection between cluster nodes and nodes running pacemaker_remote is achieved using with TLS-PSK encryption/authentication over TCP (port 3121 by default). This means that both the cluster node and remote node must share the same private key. By default, this key is placed at /etc/pacemaker/authkey on each node." msgstr "" #. Tag: para #, no-c-format msgid "You can change the default port and/or key location for Pacemaker and pacemaker_remote via environment variables. How these variables are set varies by OS, but usually they are set in the /etc/sysconfig/pacemaker or /etc/default/pacemaker file." msgstr "" #. Tag: screen #, no-c-format msgid "#==#==# Pacemaker Remote\n" "# Use a custom directory for finding the authkey.\n" "PCMK_authkey_location=/etc/pacemaker/authkey\n" "#\n" "# Specify a custom port for Pacemaker Remote connections\n" "PCMK_remote_port=3121" msgstr "" #. Tag: title #, no-c-format msgid "Removing Remote Nodes and Guest Nodes" msgstr "" #. Tag: para #, no-c-format msgid "If the resource creating a guest node, or the ocf:pacemaker:remote resource creating a connection to a remote node, is removed from the configuration, the affected node will continue to show up in output as an offline node." msgstr "" #. Tag: para #, no-c-format msgid "If you want to get rid of that output, run (replacing $NODE_NAME appropriately):" msgstr "" #. Tag: screen #, no-c-format msgid "# crm_node --force --remove $NODE_NAME" msgstr "" #. Tag: para #, no-c-format msgid "Be absolutely sure that there are no references to the node’s resource in the configuration before running the above command." msgstr "" diff --git a/doc/Pacemaker_Remote/pot/Revision_History.pot b/doc/Pacemaker_Remote/pot/Revision_History.pot index 33e99ff95f..e5aef3b9b2 100644 --- a/doc/Pacemaker_Remote/pot/Revision_History.pot +++ b/doc/Pacemaker_Remote/pot/Revision_History.pot @@ -1,74 +1,74 @@ # # AUTHOR , YEAR. # msgid "" msgstr "" "Project-Id-Version: 0\n" -"POT-Creation-Date: 2017-05-08 11:19-0500\n" -"PO-Revision-Date: 2017-05-08 11:19-0500\n" +"POT-Creation-Date: 2017-10-06 19:59-0500\n" +"PO-Revision-Date: 2017-10-06 19:59-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 "Revision History" msgstr "" #. Tag: firstname #, no-c-format msgid "David" msgstr "" #. Tag: surname #, no-c-format msgid "Vossel" msgstr "" #. Tag: member #, no-c-format msgid "Import from Pages.app" msgstr "" #. Tag: member #, no-c-format msgid "Added Future Features Section" msgstr "" #. Tag: member #, no-c-format msgid "Added Baremetal remote-node feature documentation" msgstr "" #. Tag: firstname #, no-c-format msgid "Ken" msgstr "" #. Tag: surname #, no-c-format msgid "Gaillot" msgstr "" #. Tag: member #, no-c-format msgid "Targeted CentOS 7.1 and Pacemaker 1.1.12+, updated for current terminology and practice" msgstr "" #. Tag: member #, no-c-format msgid "Updated for Pacemaker 1.1.14" msgstr "" #. Tag: member #, no-c-format msgid "Updated for Pacemaker 1.1.15" msgstr "" #. Tag: member #, no-c-format msgid "Updated for Pacemaker 1.1.16" msgstr "" diff --git a/lib/cib/Makefile.am b/lib/cib/Makefile.am index 086b5af451..25219dbbd1 100644 --- a/lib/cib/Makefile.am +++ b/lib/cib/Makefile.am @@ -1,36 +1,36 @@ # # Copyright (C) 2004 Andrew Beekhof # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. # include $(top_srcdir)/Makefile.common ## libraries lib_LTLIBRARIES = libcib.la ## SOURCES libcib_la_SOURCES = cib_ops.c cib_utils.c cib_client.c cib_native.c cib_attrs.c libcib_la_SOURCES += cib_file.c cib_remote.c -libcib_la_LDFLAGS = -version-info 5:3:1 +libcib_la_LDFLAGS = -version-info 5:4:1 libcib_la_CPPFLAGS = -I$(top_srcdir) $(AM_CPPFLAGS) libcib_la_CFLAGS = $(CFLAGS_HARDENED_LIB) libcib_la_LDFLAGS += $(LDFLAGS_HARDENED_LIB) libcib_la_LIBADD = $(CRYPTOLIB) $(top_builddir)/lib/pengine/libpe_rules.la $(top_builddir)/lib/common/libcrmcommon.la clean-generic: rm -f *.log *.debug *.xml *~ diff --git a/lib/cluster/Makefile.am b/lib/cluster/Makefile.am index 58cb5d13f3..7865785fc1 100644 --- a/lib/cluster/Makefile.am +++ b/lib/cluster/Makefile.am @@ -1,45 +1,45 @@ # # Copyright (C) 2004 Andrew Beekhof # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. # include $(top_srcdir)/Makefile.common ## libraries lib_LTLIBRARIES = libcrmcluster.la -libcrmcluster_la_LDFLAGS = -version-info 7:0:3 +libcrmcluster_la_LDFLAGS = -version-info 7:1:3 libcrmcluster_la_CFLAGS = $(CFLAGS_HARDENED_LIB) libcrmcluster_la_LDFLAGS += $(LDFLAGS_HARDENED_LIB) libcrmcluster_la_LIBADD = $(top_builddir)/lib/common/libcrmcommon.la $(top_builddir)/lib/fencing/libstonithd.la $(CLUSTERLIBS) libcrmcluster_la_SOURCES = election.c cluster.c membership.c if BUILD_CS_SUPPORT libcrmcluster_la_SOURCES += cpg.c if BUILD_CS_PLUGIN libcrmcluster_la_SOURCES += legacy.c else libcrmcluster_la_SOURCES += corosync.c endif endif if BUILD_HEARTBEAT_SUPPORT libcrmcluster_la_SOURCES += heartbeat.c #libcrmcluster_la_LIBADD += -ldl endif clean-generic: rm -f *.log *.debug *.xml *~ diff --git a/lib/common/Makefile.am b/lib/common/Makefile.am index 77e50d5f94..30427625ed 100644 --- a/lib/common/Makefile.am +++ b/lib/common/Makefile.am @@ -1,50 +1,50 @@ # # Copyright (C) 2004 Andrew Beekhof # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. # include $(top_srcdir)/Makefile.common AM_CPPFLAGS += -I$(top_builddir)/lib/gnu -I$(top_srcdir)/lib/gnu ## libraries lib_LTLIBRARIES = libcrmcommon.la # Can't use -Wcast-qual here because glib insists on pretending things are const # when they're not and thus we need the crm_element_value_const() hack # s390 needs -fPIC # s390-suse-linux/bin/ld: .libs/ipc.o: relocation R_390_PC32DBL against `__stack_chk_fail@@GLIBC_2.4' can not be used when making a shared object; recompile with -fPIC CFLAGS = $(CFLAGS_COPY:-Wcast-qual=) -fPIC -libcrmcommon_la_LDFLAGS = -version-info 10:0:7 +libcrmcommon_la_LDFLAGS = -version-info 11:0:8 libcrmcommon_la_CFLAGS = $(CFLAGS_HARDENED_LIB) libcrmcommon_la_LDFLAGS += $(LDFLAGS_HARDENED_LIB) libcrmcommon_la_LIBADD = @LIBADD_DL@ $(GNUTLSLIBS) libcrmcommon_la_SOURCES = compat.c digest.c ipc.c io.c procfs.c utils.c xml.c \ iso8601.c remote.c mainloop.c logging.c watchdog.c \ schemas.c strings.c xpath.c attrd_client.c alerts.c \ operations.c if BUILD_CIBSECRETS libcrmcommon_la_SOURCES += cib_secrets.c endif libcrmcommon_la_SOURCES += $(top_builddir)/lib/gnu/md5.c clean-generic: rm -f *.log *.debug *.xml *~ diff --git a/lib/fencing/Makefile.am b/lib/fencing/Makefile.am index 73e7b6b6fb..da1ec37b8f 100644 --- a/lib/fencing/Makefile.am +++ b/lib/fencing/Makefile.am @@ -1,29 +1,29 @@ # File: Makefile.am # Author: Sun Jiang Dong # Copyright (c) 2004 International Business Machines # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. # include $(top_srcdir)/Makefile.common lib_LTLIBRARIES = libstonithd.la -libstonithd_la_LDFLAGS = -version-info 4:3:2 +libstonithd_la_LDFLAGS = -version-info 4:4:2 libstonithd_la_CFLAGS = $(CFLAGS_HARDENED_LIB) libstonithd_la_LDFLAGS += $(LDFLAGS_HARDENED_LIB) libstonithd_la_LIBADD = $(top_builddir)/lib/common/libcrmcommon.la libstonithd_la_SOURCES = st_client.c diff --git a/lib/lrmd/Makefile.am b/lib/lrmd/Makefile.am index 2cfb1bb088..8e5e4761b4 100644 --- a/lib/lrmd/Makefile.am +++ b/lib/lrmd/Makefile.am @@ -1,29 +1,29 @@ # Copyright (c) 2012 David Vossel # # This library is free software; you can redistribute it and/or # modify it under the terms of the GNU Lesser General Public # License as published by the Free Software Foundation; either # version 2.1 of the License, or (at your option) any later version. # # This library is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU # Lesser General Public License for more details. # # You should have received a copy of the GNU Lesser General Public # License along with this library; if not, write to the Free Software # Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA # include $(top_srcdir)/Makefile.common lib_LTLIBRARIES = liblrmd.la -liblrmd_la_LDFLAGS = -version-info 5:0:4 +liblrmd_la_LDFLAGS = -version-info 6:0:5 liblrmd_la_CFLAGS = $(CFLAGS_HARDENED_LIB) liblrmd_la_LDFLAGS += $(LDFLAGS_HARDENED_LIB) liblrmd_la_LIBADD = $(top_builddir)/lib/common/libcrmcommon.la \ $(top_builddir)/lib/services/libcrmservice.la \ $(top_builddir)/lib/fencing/libstonithd.la liblrmd_la_SOURCES = lrmd_client.c proxy_common.c lrmd_alerts.c diff --git a/lib/pengine/Makefile.am b/lib/pengine/Makefile.am index ad2c7ae60f..8aceccc707 100644 --- a/lib/pengine/Makefile.am +++ b/lib/pengine/Makefile.am @@ -1,44 +1,44 @@ # # Copyright (C) 2004 Andrew Beekhof # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. # include $(top_srcdir)/Makefile.common ## libraries lib_LTLIBRARIES = libpe_rules.la libpe_status.la ## SOURCES noinst_HEADERS = unpack.h variant.h -libpe_rules_la_LDFLAGS = -version-info 4:0:2 +libpe_rules_la_LDFLAGS = -version-info 5:0:3 libpe_rules_la_CFLAGS = $(CFLAGS_HARDENED_LIB) libpe_rules_la_LDFLAGS += $(LDFLAGS_HARDENED_LIB) libpe_rules_la_LIBADD = $(top_builddir)/lib/common/libcrmcommon.la libpe_rules_la_SOURCES = rules.c rules_alerts.c common.c -libpe_status_la_LDFLAGS = -version-info 13:0:3 +libpe_status_la_LDFLAGS = -version-info 14:0:4 libpe_status_la_CFLAGS = $(CFLAGS_HARDENED_LIB) libpe_status_la_LDFLAGS += $(LDFLAGS_HARDENED_LIB) libpe_status_la_LIBADD = @CURSESLIBS@ $(top_builddir)/lib/common/libcrmcommon.la libpe_status_la_SOURCES = status.c unpack.c utils.c complex.c native.c container.c \ group.c clone.c rules.c common.c failcounts.c remote.c clean-generic: rm -f *.log *.debug *~ diff --git a/lib/services/Makefile.am b/lib/services/Makefile.am index 7134ab122e..a416f1369e 100644 --- a/lib/services/Makefile.am +++ b/lib/services/Makefile.am @@ -1,44 +1,44 @@ # Copyright (c) 2012 David Vossel # # This library is free software; you can redistribute it and/or # modify it under the terms of the GNU Lesser General Public # License as published by the Free Software Foundation; either # version 2.1 of the License, or (at your option) any later version. # # This library is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU # Lesser General Public License for more details. # # You should have received a copy of the GNU Lesser General Public # License along with this library; if not, write to the Free Software # Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA # # MAINTAINERCLEANFILES = Makefile.in AM_CPPFLAGS = -I$(top_srcdir)/include lib_LTLIBRARIES = libcrmservice.la noinst_HEADERS = pcmk-dbus.h upstart.h systemd.h services_private.h -libcrmservice_la_LDFLAGS = -version-info 5:0:2 +libcrmservice_la_LDFLAGS = -version-info 6:0:3 libcrmservice_la_CPPFLAGS = -DOCF_ROOT_DIR=\"@OCF_ROOT_DIR@\" $(AM_CPPFLAGS) libcrmservice_la_CFLAGS = $(GIO_CFLAGS) libcrmservice_la_CFLAGS += $(CFLAGS_HARDENED_LIB) libcrmservice_la_LDFLAGS += $(LDFLAGS_HARDENED_LIB) libcrmservice_la_LIBADD = $(GIO_LIBS) $(top_builddir)/lib/common/libcrmcommon.la $(DBUS_LIBS) libcrmservice_la_SOURCES = services.c services_linux.c if BUILD_DBUS libcrmservice_la_SOURCES += dbus.c endif if BUILD_UPSTART libcrmservice_la_SOURCES += upstart.c endif if BUILD_SYSTEMD libcrmservice_la_SOURCES += systemd.c endif diff --git a/lib/transition/Makefile.am b/lib/transition/Makefile.am index f42450125c..304837edf6 100644 --- a/lib/transition/Makefile.am +++ b/lib/transition/Makefile.am @@ -1,35 +1,35 @@ # # Copyright (C) 2004 Andrew Beekhof # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. # include $(top_srcdir)/Makefile.common ## libraries lib_LTLIBRARIES = libtransitioner.la ## SOURCES -libtransitioner_la_LDFLAGS = -version-info 2:7:0 +libtransitioner_la_LDFLAGS = -version-info 3:0:1 libtransitioner_la_CPPFLAGS = -I$(top_builddir) $(AM_CPPFLAGS) libtransitioner_la_CFLAGS = $(CFLAGS_HARDENED_LIB) libtransitioner_la_LDFLAGS += $(LDFLAGS_HARDENED_LIB) libtransitioner_la_LIBADD = $(top_builddir)/lib/common/libcrmcommon.la libtransitioner_la_SOURCES = unpack.c graph.c utils.c clean-generic: rm -f *~ diff --git a/pacemaker.spec.in b/pacemaker.spec.in index 642af7411e..6152601e3b 100644 --- a/pacemaker.spec.in +++ b/pacemaker.spec.in @@ -1,796 +1,796 @@ # Globals and defines to control package behavior (configure these as desired) ## User and group to use for nonprivileged services %global uname hacluster %global gname haclient ## Where to install Pacemaker documentation %global pcmk_docdir %{_docdir}/%{name} ## GitHub entity that distributes source (for ease of using a fork) %global github_owner ClusterLabs ## Upstream pacemaker version, and its package version (specversion ## can be incremented to build packages reliably considered "newer" ## than previously built packages with the same pcmkversion) -%global pcmkversion 1.1.17 +%global pcmkversion 1.1.18 %global specversion 1 ## Upstream commit (or git tag, such as "Pacemaker-" plus the ## {pcmkversion} macro for an official release) to use for this package %global commit HEAD ## Since git v2.11, the extent of abbreviation is autoscaled by default ## (used to be constant of 7), so we need to convey it for non-tags, too. %global commit_abbrev 7 # Define globals for convenient use later ## Workaround to use parentheses in other globals %global lparen ( %global rparen ) ## Short version of git commit %define shortcommit %(c=%{commit}; case ${c} in Pacemaker-*%{rparen} echo ${c:10};; *%{rparen} echo ${c:0:%{commit_abbrev}};; esac) ## Whether this is a tagged release %define tag_release %([ %{commit} != Pacemaker-%{shortcommit} ]; echo $?) ## Whether this is a release candidate (in case of a tagged release) %define pre_release %([ "%{tag_release}" -eq 0 ] || { case "%{shortcommit}" in *-rc[[:digit:]]*%{rparen} false;; esac; }; echo $?) ## Turn off auto-compilation of python files outside site-packages directory, ## so that the -libs-devel package is multilib-compliant (no *.py[co] files) %global __os_install_post %(echo '%{__os_install_post}' | { sed -e 's!/usr/lib[^[:space:]]*/brp-python-bytecompile[[:space:]].*$!!g'; }) ## Heuristic used to infer bleeding-edge deployments that are ## less likely to have working versions of the documentation tools %define bleeding %(test ! -e /etc/yum.repos.d/fedora-rawhide.repo; echo $?) ## Corosync version %define cs_version %(pkg-config corosync --modversion 2>/dev/null | awk -F . '{print $1}') ## Where to install python site libraries (currently, this uses the unversioned ## python_sitearch macro to get the default system python, but at some point, ## we should explicitly choose python2_sitearch or python3_sitearch -- or both) %define py_site %{?python_sitearch}%{!?python_sitearch:%( python -c 'from distutils.sysconfig import get_python_lib as gpl; print(gpl(1))' 2>/dev/null)} ## Whether this platform defaults to using CMAN %define cman_native (0%{?el6} || (0%{?fedora} > 0 && 0%{?fedora} < 17)) ## Whether this platform defaults to using systemd as an init system ## (needs to be evaluated prior to BuildRequires being enumerated and ## installed as it's intended to conditionally select some of these, and ## for that there are only few indicators with varying reliability: ## - presence of systemd-defined macros (when building in a full-fledged ## environment, which is not the case with ordinary mock-based builds) ## - systemd-aware rpm as manifested with the presence of particular ## macro (rpm itself will trivially always be present when building) ## - existence of /usr/lib/os-release file, which is something heavily ## propagated by systemd project ## - when not good enough, there's always a possibility to check ## particular distro-specific macros (incl. version comparison) %define systemd_native (%{?_unitdir:1}%{?!_unitdir:0}%{nil \ } || %{?__transaction_systemd_inhibit:1}%{?!__transaction_systemd_inhibit:0}%{nil \ } || %(test -f /usr/lib/os-release; test $? -ne 0; echo $?)) # Definitions for backward compatibility with older RPM versions ## Ensure the license macro behaves consistently (older RPM will otherwise ## overwrite it once it encounters "License:"). Courtesy Jason Tibbitts: ## https://pkgs.fedoraproject.org/cgit/rpms/epel-rpm-macros.git/tree/macros.zzz-epel?h=el6&id=e1adcb77 %if !%{defined _licensedir} %define description %{lua: rpm.define("license %doc") print("%description") } %endif # Define conditionals so that "rpmbuild --with " and # "rpmbuild --without " can enable and disable specific features ## Add option to enable support for stonith/external fencing agents %bcond_with stonithd ## Add option to create binaries suitable for use with profiling tools %bcond_with profiling ## Add option to create binaries with coverage analysis %bcond_with coverage ## Add option to skip generating documentation ## (the build tools aren't available everywhere) %bcond_without doc ## Add option to prefix package version with "0." ## (so later "official" packages will be considered updates) %bcond_with pre_release ## Add option to ship Upstart job files %bcond_with upstart_job ## Add option to turn off CMAN support on CMAN-native platforms %bcond_without cman ## Add option to turn off hardening of libraries and daemon executables %bcond_without hardening # Keep sane profiling data if requested %if %{with profiling} ## Disable -debuginfo package and stripping binaries/libraries %define debug_package %{nil} %endif # Define the release version # (do not look at externally enforced pre-release flag for tagged releases # as only -rc tags, captured with the second condition, implies that then) %if (!%{tag_release} && %{with pre_release}) || 0%{pre_release} %if 0%{pre_release} %define pcmk_release 0.%{specversion}.%(s=%{shortcommit}; echo ${s: -3}) %else %define pcmk_release 0.%{specversion}.%{shortcommit}.git %endif %else %if 0%{tag_release} %define pcmk_release %{specversion} %else %define pcmk_release %{specversion}.%{shortcommit}.git %endif %endif Name: pacemaker Summary: Scalable High-Availability cluster resource manager Version: %{pcmkversion} Release: %{pcmk_release}%{?dist} %if %{defined _unitdir} License: GPLv2+ and LGPLv2+ %else # initscript is Revised BSD License: GPLv2+ and LGPLv2+ and BSD %endif Url: http://www.clusterlabs.org Group: System Environment/Daemons # Hint: use "spectool -s 0 pacemaker.spec" (rpmdevtools) to check the final URL: # https://github.com/ClusterLabs/pacemaker/archive/e91769e5a39f5cb2f7b097d3c612368f0530535e/pacemaker-e91769e.tar.gz Source0: https://github.com/%{github_owner}/%{name}/archive/%{commit}/%{name}-%{shortcommit}.tar.gz BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XXXXXX) AutoReqProv: on Requires: resource-agents Requires: %{name}-libs = %{version}-%{release} Requires: %{name}-cluster-libs = %{version}-%{release} Requires: %{name}-cli = %{version}-%{release} %if %{defined systemd_requires} %systemd_requires %endif # Pacemaker targets compatibility with python 2.6+ and 3.2+ Requires: python >= 2.6 BuildRequires: python-devel >= 2.6 # Pacemaker requires a minimum libqb functionality Requires: libqb >= 0.13.0 BuildRequires: libqb-devel >= 0.13.0 # Basics required for the build (even if usually satisfied through other BRs) BuildRequires: coreutils findutils grep sed # Required for core functionality BuildRequires: automake autoconf libtool pkgconfig libtool-ltdl-devel ## version lower bound for: G_GNUC_INTERNAL BuildRequires: pkgconfig(glib-2.0) >= 2.6 BuildRequires: libxml2-devel libxslt-devel libuuid-devel BuildRequires: bzip2-devel pam-devel # Required for agent_config.h which specifies the correct scratch directory BuildRequires: resource-agents # Enables optional functionality BuildRequires: ncurses-devel docbook-style-xsl BuildRequires: bison byacc flex help2man gnutls-devel pkgconfig(dbus-1) %if %{systemd_native} BuildRequires: pkgconfig(systemd) %endif %if %{with cman} && %{cman_native} BuildRequires: clusterlib-devel # pacemaker initscript: cman initscript, fence_tool (+ some soft-dependencies) # "post" scriptlet: ccs_update_schema Requires: cman %endif Requires: corosync BuildRequires: corosynclib-devel %if %{with stonithd} BuildRequires: cluster-glue-libs-devel %endif ## (note no avoiding effect when building through non-customized mock) %if !%{bleeding} %if %{with doc} BuildRequires: publican inkscape asciidoc %endif %endif %description Pacemaker is an advanced, scalable High-Availability cluster resource manager for Corosync, CMAN and/or Linux-HA. It supports more than 16 node clusters with significant capabilities for managing resources and dependencies. It will run scripts at initialization, when machines go up or down, when related resources fail and can be configured to periodically check resource health. Available rpmbuild rebuild options: --with(out) : cman coverage doc stonithd hardening pre_release profiling upstart_job %package cli License: GPLv2+ and LGPLv2+ Summary: Command line tools for controlling Pacemaker clusters Group: System Environment/Daemons Requires: %{name}-libs = %{version}-%{release} Requires: perl-TimeDate %description cli Pacemaker is an advanced, scalable High-Availability cluster resource manager for Corosync, CMAN and/or Linux-HA. The %{name}-cli package contains command line tools that can be used to query and control the cluster from machines that may, or may not, be part of the cluster. %package -n %{name}-libs License: GPLv2+ and LGPLv2+ Summary: Core Pacemaker libraries Group: System Environment/Daemons %description -n %{name}-libs Pacemaker is an advanced, scalable High-Availability cluster resource manager for Corosync, CMAN and/or Linux-HA. The %{name}-libs package contains shared libraries needed for cluster nodes and those just running the CLI tools. %package -n %{name}-cluster-libs License: GPLv2+ and LGPLv2+ Summary: Cluster Libraries used by Pacemaker Group: System Environment/Daemons Requires: %{name}-libs = %{version}-%{release} %description -n %{name}-cluster-libs Pacemaker is an advanced, scalable High-Availability cluster resource manager for Corosync, CMAN and/or Linux-HA. The %{name}-cluster-libs package contains cluster-aware shared libraries needed for nodes that will form part of the cluster nodes. %package remote %if %{defined _unitdir} License: GPLv2+ and LGPLv2+ %else # initscript is Revised BSD License: GPLv2+ and LGPLv2+ and BSD %endif Summary: Pacemaker remote daemon for non-cluster nodes Group: System Environment/Daemons Requires: %{name}-libs = %{version}-%{release} Requires: %{name}-cli = %{version}-%{release} Requires: resource-agents %if %{defined systemd_requires} %systemd_requires %endif %description remote Pacemaker is an advanced, scalable High-Availability cluster resource manager for Corosync, CMAN and/or Linux-HA. The %{name}-remote package contains the Pacemaker Remote daemon which is capable of extending pacemaker functionality to remote nodes not running the full corosync/cluster stack. %package -n %{name}-libs-devel License: GPLv2+ and LGPLv2+ Summary: Pacemaker development package Group: Development/Libraries Requires: %{name}-cts = %{version}-%{release} Requires: %{name}-libs = %{version}-%{release} Requires: %{name}-cluster-libs = %{version}-%{release} Requires: libtool-ltdl-devel libqb-devel libuuid-devel Requires: libxml2-devel libxslt-devel bzip2-devel glib2-devel Requires: corosynclib-devel %description -n %{name}-libs-devel Pacemaker is an advanced, scalable High-Availability cluster resource manager for Corosync, CMAN and/or Linux-HA. The %{name}-libs-devel package contains headers and shared libraries for developing tools for Pacemaker. # NOTE: can be noarch if lrmd_test is moved to another subpackage %package cts License: GPLv2+ and LGPLv2+ Summary: Test framework for cluster-related technologies like Pacemaker Group: System Environment/Daemons Requires: python >= 2.6 Requires: %{name}-libs = %{version}-%{release} # systemd python bindings are separate package in some distros %if %{defined systemd_requires} %if 0%{?fedora} > 22 Requires: python2-systemd %else %if 0%{?fedora} > 20 || 0%{?rhel} > 6 Requires: systemd-python %endif %endif %endif %description cts Test framework for cluster-related technologies like Pacemaker %package doc License: CC-BY-SA Summary: Documentation for Pacemaker Group: Documentation %description doc Documentation for Pacemaker. Pacemaker is an advanced, scalable High-Availability cluster resource manager for Corosync, CMAN and/or Linux-HA. %prep %setup -q -n %{name}-%{commit} # Force the local time # # 'git' sets the file date to the date of the last commit. # This can result in files having been created in the future # when building on machines in timezones 'behind' the one the # commit occurred in - which seriously confuses 'make' find . -exec touch \{\} \; %build # Early versions of autotools (e.g. RHEL <= 5) do not support --docdir export docdir=%{pcmk_docdir} export systemdunitdir=%{?_unitdir}%{?!_unitdir:no} %if %{with hardening} # prefer distro-provided hardening flags in case they are defined # through _hardening_{c,ld}flags macros, configure script will # use its own defaults otherwise; if such hardenings are completely # undesired, rpmbuild using "--without hardening" # (or "--define '_without_hardening 1'") export CFLAGS_HARDENED_EXE="%{?_hardening_cflags}" export CFLAGS_HARDENED_LIB="%{?_hardening_cflags}" export LDFLAGS_HARDENED_EXE="%{?_hardening_ldflags}" export LDFLAGS_HARDENED_LIB="%{?_hardening_ldflags}" %endif ./autogen.sh %{configure} \ %{?with_profiling: --with-profiling} \ %{?with_coverage: --with-coverage} \ %{!?with_cman: --without-cman} \ --without-heartbeat \ %{!?with_doc: --with-brand=} \ %{!?with_hardening: --disable-hardening} \ --with-initdir=%{_initrddir} \ --localstatedir=%{_var} \ --with-version=%{version}-%{release} %if 0%{?suse_version} >= 1200 # Fedora handles rpath removal automagically sed -i 's|^hardcode_libdir_flag_spec=.*|hardcode_libdir_flag_spec=""|g' libtool sed -i 's|^runpath_var=LD_RUN_PATH|runpath_var=DIE_RPATH_DIE|g' libtool %endif make %{_smp_mflags} V=1 all %check { pengine/regression.sh --run one-or-more-unrunnnable-instances \ && tools/regression.sh \ && touch .CHECKED } 2>&1 | sed 's/[fF]ail/faiil/g' # prevent false positives in rpmlint [ -f .CHECKED ] && rm -f -- .CHECKED || false %install rm -rf %{buildroot} make DESTDIR=%{buildroot} docdir=%{pcmk_docdir} V=1 install mkdir -p ${RPM_BUILD_ROOT}%{_sysconfdir}/sysconfig install -m 644 mcp/pacemaker.sysconfig ${RPM_BUILD_ROOT}%{_sysconfdir}/sysconfig/pacemaker install -m 644 tools/crm_mon.sysconfig ${RPM_BUILD_ROOT}%{_sysconfdir}/sysconfig/crm_mon %if %{with upstart_job} mkdir -p ${RPM_BUILD_ROOT}%{_sysconfdir}/init install -m 644 mcp/pacemaker.upstart ${RPM_BUILD_ROOT}%{_sysconfdir}/init/pacemaker.conf install -m 644 mcp/pacemaker.combined.upstart ${RPM_BUILD_ROOT}%{_sysconfdir}/init/pacemaker.combined.conf install -m 644 tools/crm_mon.upstart ${RPM_BUILD_ROOT}%{_sysconfdir}/init/crm_mon.conf %endif %if %{defined _unitdir} mkdir -p ${RPM_BUILD_ROOT}%{_localstatedir}/lib/rpm-state/%{name} %endif # Scripts that should be executable chmod a+x %{buildroot}/%{_datadir}/pacemaker/tests/cts/CTSlab.py # These are not actually scripts find %{buildroot} -name '*.xml' -type f -print0 | xargs -0 chmod a-x # Don't package static libs find %{buildroot} -name '*.a' -type f -print0 | xargs -0 rm -f find %{buildroot} -name '*.la' -type f -print0 | xargs -0 rm -f # Do not package these either rm -f %{buildroot}/%{_libdir}/service_crm.so # Don't ship init scripts for systemd based platforms %if %{defined _unitdir} rm -f %{buildroot}/%{_initrddir}/pacemaker rm -f %{buildroot}/%{_initrddir}/pacemaker_remote %endif # Don't ship fence_pcmk where it has no use %if %{without cman} rm -f %{buildroot}/%{_sbindir}/fence_pcmk %endif %if %{with coverage} GCOV_BASE=%{buildroot}/%{_var}/lib/pacemaker/gcov mkdir -p $GCOV_BASE find . -name '*.gcno' -type f | while read F ; do D=`dirname $F` mkdir -p ${GCOV_BASE}/$D cp $F ${GCOV_BASE}/$D done %endif %clean rm -rf %{buildroot} %post %if %{defined _unitdir} %systemd_post pacemaker.service %else /sbin/chkconfig --add pacemaker || : %if %{with cman} && %{cman_native} # make fence_pcmk in cluster.conf valid instantly otherwise tools like ccs may # choke (until schema gets auto-regenerated on the next start of cluster), # per the protocol shared with other packages contributing to cluster.rng /usr/sbin/ccs_update_schema >/dev/null 2>&1 || : %endif %endif %preun %if %{defined _unitdir} %systemd_preun pacemaker.service %else /sbin/service pacemaker stop >/dev/null 2>&1 || : if [ $1 -eq 0 ]; then # Package removal, not upgrade /sbin/chkconfig --del pacemaker || : fi %endif %postun %if %{defined _unitdir} %systemd_postun_with_restart pacemaker.service %endif %pre remote %if %{defined _unitdir} # Stop the service before anything is touched, and remember to restart # it as one of the last actions (compared to using systemd_postun_with_restart, # this avoids suicide when sbd is in use) systemctl --quiet is-active pacemaker_remote if [ $? -eq 0 ] ; then mkdir -p %{_localstatedir}/lib/rpm-state/%{name} touch %{_localstatedir}/lib/rpm-state/%{name}/restart_pacemaker_remote systemctl stop pacemaker_remote >/dev/null 2>&1 else rm -f %{_localstatedir}/lib/rpm-state/%{name}/restart_pacemaker_remote fi %endif %post remote %if %{defined _unitdir} %systemd_post pacemaker_remote.service %else /sbin/chkconfig --add pacemaker_remote || : %endif %preun remote %if %{defined _unitdir} %systemd_preun pacemaker_remote.service %else /sbin/service pacemaker_remote stop >/dev/null 2>&1 || : if [ $1 -eq 0 ]; then # Package removal, not upgrade /sbin/chkconfig --del pacemaker_remote || : fi %endif %postun remote %if %{defined _unitdir} # This next line is a no-op, because we stopped the service earlier, but # we leave it here because it allows us to revert to the standard behavior # in the future if desired %systemd_postun_with_restart pacemaker_remote.service # Explicitly take care of removing the flag-file(s) upon final removal if [ $1 -eq 0 ] ; then rm -f %{_localstatedir}/lib/rpm-state/%{name}/restart_pacemaker_remote fi %endif %posttrans remote %if %{defined _unitdir} if [ -e %{_localstatedir}/lib/rpm-state/%{name}/restart_pacemaker_remote ] ; then systemctl start pacemaker_remote >/dev/null 2>&1 rm -f %{_localstatedir}/lib/rpm-state/%{name}/restart_pacemaker_remote fi %endif %post cli %if %{defined _unitdir} %systemd_post crm_mon.service %endif %preun cli %if %{defined _unitdir} %systemd_preun crm_mon.service %endif %postun cli %if %{defined _unitdir} %systemd_postun_with_restart crm_mon.service %endif %pre -n %{name}-libs getent group %{gname} >/dev/null || groupadd -r %{gname} -g 189 getent passwd %{uname} >/dev/null || useradd -r -g %{gname} -u 189 -s /sbin/nologin -c "cluster user" %{uname} exit 0 %post -n %{name}-libs -p /sbin/ldconfig %postun -n %{name}-libs -p /sbin/ldconfig %post -n %{name}-cluster-libs -p /sbin/ldconfig %postun -n %{name}-cluster-libs -p /sbin/ldconfig %files ########################################################### %defattr(-,root,root) %config(noreplace) %{_sysconfdir}/sysconfig/pacemaker %{_sbindir}/pacemakerd %if %{defined _unitdir} %{_unitdir}/pacemaker.service %else %{_initrddir}/pacemaker %endif %exclude %{_libexecdir}/pacemaker/lrmd_test %exclude %{_sbindir}/pacemaker_remoted %{_libexecdir}/pacemaker/* %{_sbindir}/crm_attribute %{_sbindir}/crm_master %{_sbindir}/crm_node %{_sbindir}/fence_legacy %if %{with cman} %{_sbindir}/fence_pcmk %endif %{_sbindir}/stonith_admin %doc %{_mandir}/man7/crmd.* %doc %{_mandir}/man7/pengine.* %doc %{_mandir}/man7/stonithd.* %if %{without cman} || !%{cman_native} %doc %{_mandir}/man7/ocf_pacemaker_controld.* %endif %doc %{_mandir}/man7/ocf_pacemaker_o2cb.* %doc %{_mandir}/man7/ocf_pacemaker_remote.* %doc %{_mandir}/man8/crm_attribute.* %doc %{_mandir}/man8/crm_node.* %doc %{_mandir}/man8/crm_master.* %if %{with cman} %doc %{_mandir}/man8/fence_pcmk.* %endif %doc %{_mandir}/man8/fence_legacy.* %doc %{_mandir}/man8/pacemakerd.* %doc %{_mandir}/man8/stonith_admin.* %doc %{_datadir}/pacemaker/alerts %license licenses/GPLv2 %doc COPYING %doc ChangeLog %dir %attr (750, %{uname}, %{gname}) %{_var}/lib/pacemaker/cib %dir %attr (750, %{uname}, %{gname}) %{_var}/lib/pacemaker/pengine %if %{without cman} || !%{cman_native} /usr/lib/ocf/resource.d/pacemaker/controld %endif /usr/lib/ocf/resource.d/pacemaker/o2cb /usr/lib/ocf/resource.d/pacemaker/remote /usr/lib/ocf/resource.d/.isolation %if "%{?cs_version}" != "UNKNOWN" %if 0%{?cs_version} < 2 %{_libexecdir}/lcrso/pacemaker.lcrso %endif %endif %if %{with upstart_job} %config(noreplace) %{_sysconfdir}/init/pacemaker.conf %config(noreplace) %{_sysconfdir}/init/pacemaker.combined.conf %endif %files cli %defattr(-,root,root) %config(noreplace) %{_sysconfdir}/logrotate.d/pacemaker %config(noreplace) %{_sysconfdir}/sysconfig/crm_mon %if %{defined _unitdir} %{_unitdir}/crm_mon.service %endif %if %{with upstart_job} %config(noreplace) %{_sysconfdir}/init/crm_mon.conf %endif %{_sbindir}/attrd_updater %{_sbindir}/cibadmin %{_sbindir}/crm_diff %{_sbindir}/crm_error %{_sbindir}/crm_failcount %{_sbindir}/crm_mon %{_sbindir}/crm_resource %{_sbindir}/crm_standby %{_sbindir}/crm_verify %{_sbindir}/crmadmin %{_sbindir}/iso8601 %{_sbindir}/crm_shadow %{_sbindir}/crm_simulate %{_sbindir}/crm_report %{_sbindir}/crm_ticket %exclude %{_datadir}/pacemaker/alerts %exclude %{_datadir}/pacemaker/tests %{_datadir}/pacemaker %{_datadir}/snmp/mibs/PCMK-MIB.txt %exclude /usr/lib/ocf/resource.d/pacemaker/controld %exclude /usr/lib/ocf/resource.d/pacemaker/o2cb %exclude /usr/lib/ocf/resource.d/pacemaker/remote %dir /usr/lib/ocf %dir /usr/lib/ocf/resource.d /usr/lib/ocf/resource.d/pacemaker %doc %{_mandir}/man7/* %exclude %{_mandir}/man7/crmd.* %exclude %{_mandir}/man7/pengine.* %exclude %{_mandir}/man7/stonithd.* %exclude %{_mandir}/man7/ocf_pacemaker_controld.* %exclude %{_mandir}/man7/ocf_pacemaker_o2cb.* %exclude %{_mandir}/man7/ocf_pacemaker_remote.* %doc %{_mandir}/man8/* %exclude %{_mandir}/man8/crm_attribute.* %exclude %{_mandir}/man8/crm_node.* %exclude %{_mandir}/man8/crm_master.* %exclude %{_mandir}/man8/fence_pcmk.* %exclude %{_mandir}/man8/fence_legacy.* %exclude %{_mandir}/man8/pacemakerd.* %exclude %{_mandir}/man8/pacemaker_remoted.* %exclude %{_mandir}/man8/stonith_admin.* %license licenses/GPLv2 %doc COPYING %doc ChangeLog %dir %attr (750, %{uname}, %{gname}) %{_var}/lib/pacemaker %dir %attr (750, %{uname}, %{gname}) %{_var}/lib/pacemaker/blackbox %dir %attr (750, %{uname}, %{gname}) %{_var}/lib/pacemaker/cores %files -n %{name}-libs %defattr(-,root,root) %{_libdir}/libcib.so.* %{_libdir}/liblrmd.so.* %{_libdir}/libcrmservice.so.* %{_libdir}/libcrmcommon.so.* %{_libdir}/libpe_status.so.* %{_libdir}/libpe_rules.so.* %{_libdir}/libpengine.so.* %{_libdir}/libstonithd.so.* %{_libdir}/libtransitioner.so.* %license licenses/LGPLv2.1 %doc COPYING %doc ChangeLog %files -n %{name}-cluster-libs %defattr(-,root,root) %{_libdir}/libcrmcluster.so.* %license licenses/LGPLv2.1 %doc COPYING %doc ChangeLog %files remote %defattr(-,root,root) %config(noreplace) %{_sysconfdir}/sysconfig/pacemaker %if %{defined _unitdir} # state directory is shared between the subpackets # let rpm take care of removing it once it isn't # referenced anymore and empty %ghost %dir %{_localstatedir}/lib/rpm-state/%{name} %{_unitdir}/pacemaker_remote.service %else %{_initrddir}/pacemaker_remote %endif %{_sbindir}/pacemaker_remoted %{_mandir}/man8/pacemaker_remoted.* %license licenses/GPLv2 %doc COPYING %doc ChangeLog %files doc %defattr(-,root,root) %doc %{pcmk_docdir} %license licenses/CC-BY-SA-4.0 %files cts %defattr(-,root,root) %{py_site}/cts %{_datadir}/pacemaker/tests/cts %{_libexecdir}/pacemaker/lrmd_test %license licenses/GPLv2 %doc COPYING %doc ChangeLog %files -n %{name}-libs-devel %defattr(-,root,root) %exclude %{_datadir}/pacemaker/tests/cts %{_datadir}/pacemaker/tests %{_includedir}/pacemaker %{_libdir}/*.so %if %{with coverage} %{_var}/lib/pacemaker/gcov %endif %{_libdir}/pkgconfig/*.pc %license licenses/LGPLv2.1 %doc COPYING %doc ChangeLog %changelog diff --git a/pengine/Makefile.am b/pengine/Makefile.am index 5eaf2be2d8..e997454faf 100644 --- a/pengine/Makefile.am +++ b/pengine/Makefile.am @@ -1,90 +1,90 @@ # # Copyright (C) 2004 Andrew Beekhof # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. # include $(top_srcdir)/Makefile.common AM_CPPFLAGS += -I$(top_builddir) -I$(top_srcdir) halibdir = $(CRM_DAEMON_DIR) PE_TESTS = $(wildcard test10/*.scores) testdir = $(datadir)/$(PACKAGE)/tests/pengine test_SCRIPTS = regression.sh test_DATA = regression.core.sh test10dir = $(datadir)/$(PACKAGE)/tests/pengine/test10 test10_DATA = $(PE_TESTS) $(PE_TESTS:%.scores=%.xml) $(PE_TESTS:%.scores=%.exp) $(PE_TESTS:%.scores=%.dot) $(PE_TESTS:%.scores=%.summary) $(wildcard test10/*.stderr) beekhof: echo $(shell ls -1 test10/*.xml) #TESTS = test10/*.xml TESTS = test10/bug-rh-1097457.xml TEST_EXTENSIONS = .xml XML_LOG_COMPILER = ./regression.sh AM_XML_LOG_FLAGS = -V --run #LOG_COMPILER = #AM_LOG_FLAGS = -V COMMONLIBS = $(top_builddir)/lib/common/libcrmcommon.la \ $(top_builddir)/lib/pengine/libpe_status.la \ libpengine.la ## libraries lib_LTLIBRARIES = libpengine.la ## binary progs halib_PROGRAMS = pengine if BUILD_XML_HELP man7_MANS = pengine.7 endif ## SOURCES noinst_HEADERS = allocate.h notif.h utils.h pengine.h -libpengine_la_LDFLAGS = -version-info 13:0:3 +libpengine_la_LDFLAGS = -version-info 14:0:4 libpengine_la_CFLAGS = $(CFLAGS_HARDENED_LIB) libpengine_la_LDFLAGS += $(LDFLAGS_HARDENED_LIB) libpengine_la_LIBADD = $(top_builddir)/lib/pengine/libpe_status.la \ $(top_builddir)/lib/cib/libcib.la # -L$(top_builddir)/lib/pils -lpils -export-dynamic -module -avoid-version libpengine_la_SOURCES = pengine.c allocate.c notif.c utils.c constraints.c libpengine_la_SOURCES += native.c group.c clone.c master.c graph.c utilization.c container.c pengine_CFLAGS = $(CFLAGS_HARDENED_EXE) pengine_LDFLAGS = $(LDFLAGS_HARDENED_EXE) pengine_LDADD = $(top_builddir)/lib/cib/libcib.la $(COMMONLIBS) # libcib for get_object_root() # $(top_builddir)/lib/hbclient/libhbclient.la pengine_SOURCES = main.c install-exec-local: $(mkinstalldirs) $(DESTDIR)/$(PE_STATE_DIR) -chown $(CRM_DAEMON_USER) $(DESTDIR)/$(PE_STATE_DIR) -chgrp $(CRM_DAEMON_GROUP) $(DESTDIR)/$(PE_STATE_DIR) -chmod 750 $(DESTDIR)/$(PE_STATE_DIR) uninstall-local: clean-local: rm -f test10/*.pe.* $(man7_MANS) diff --git a/version.m4 b/version.m4 index 8492bd495d..3f75ce3f90 100644 --- a/version.m4 +++ b/version.m4 @@ -1,2 +1,2 @@ -m4_define([VERSION_NUMBER], [1.1.17]) +m4_define([VERSION_NUMBER], [1.1.18]) m4_define([PCMK_URL], [http://clusterlabs.org/]) diff --git a/xml/Readme.md b/xml/Readme.md index 82dd9091e3..84d41ffb76 100644 --- a/xml/Readme.md +++ b/xml/Readme.md @@ -1,108 +1,109 @@ # Schema Reference Pacemaker's XML schema has a version of its own, independent of the version of Pacemaker itself. ## Versioned Schema Evolution A versioned schema offers transparent backward and forward compatibility. - It reflects the timeline of schema-backed features (introduction, changes to the syntax, possibly deprecation) through the versioned stable schema increments, while keeping schema versions used by default by older Pacemaker versions untouched. - Pacemaker internally uses the latest stable schema version, and relies on supplemental transformations to promote cluster configurations based on older, incompatible schema versions into the desired form. - It allows experimental features with a possibly unstable configuration interface to be developed using the special `next` version of the schema. ## Mapping Pacemaker Versions to Schema Versions | Pacemaker | Latest Schema | Changed | --------- | ------------- | ---------------------------------------------- +| `1.1.18` | `2.10` | `resources`, `alerts` | `1.1.17` | `2.9` | `resources`, `rule` | `1.1.16` | `2.6` | `constraints` | `1.1.15` | `2.5` | `alerts` | `1.1.14` | `2.4` | `fencing` | `1.1.13` | `2.3` | `constraints` | `1.1.12` | `2.0` | `nodes`, `nvset`, `resources`, `tags` + `acls` | `1.1.8`+ | `1.2` | ## Schema generation Each logical portion of the schema goes into its own RNG file, named like `${base}-${X}.${Y}.rng`. `${base}` identifies the portion of the schema (e.g. constraints, resources); ${X}.${Y} is the latest schema version that contained changes in this portion of the schema. The complete, overall schema, `pacemaker-${X}.${Y}.rng`, is automatically generated from the other files via the Makefile. # Updating schema files # ## Experimental features ## Experimental features go into `${base}-next.rng` where `${base}` is the affected portion of the schema. If such a file does not already exist, create it by copying the most recent `${base}-${X}.${Y}.rng`. Pacemaker will not use the experimental schema by default; the cluster administrator must explicitly set the `validate-with` property appropriately to use it. ## Stable features ## The current stable version is determined at runtime when crm_schema_init() scans the CRM_DTD_DIRECTORY. It will have the form `pacemaker-${X}.${Y}` and the highest `${X}.${Y}` wins. ### Simple Additions When the new syntax is a simple addition to the previous one, create a new entry, incrementing `${Y}`. ### Feature Removal or otherwise Incompatible Changes When the new syntax is not a simple addition to the previous one, create a new entry, incrementing `${X}` and setting `${Y} = 0`. An XSLT file is also required that converts an old syntax to the new one and must be named `upgrade-${Xold}.${Yold}.xsl`. See `xml/upgrade-1.3.xsl` for an example. ### General Procedure 1. Copy the most recent version of `${base}-*.rng` to `${base}-${X}.${Y}.rng` 1. Commit the copy, e.g. `"Low: xml: clone ${base} schema in preparation for changes"`. This way, the actual change will be obvious in the commit history. 1. Modify `${base}-${X}.${Y}.rng` as required. 1. If required, add an XSLT file, and update `xslt_SCRIPTS` in `xml/Makefile.am`. 1. Commit 1. `make -C xml clean; make -C xml all` to rebuild the schemas in the local source directory. 1. The CIB validity regression tests will break after the schema is updated. Run `tools/regression.sh` to get the new output, `diff tools/regression.validity.{out,exp}` to ensure the changes look correct, `cp tools/regression.validity.{out,exp}` to update the expected output, then commit the change. ## Using a New Schema New features will not be available until the cluster administrator: 1. Updates all the nodes 1. Runs the equivalent of `cibadmin --upgrade --force` ## Random Notes From the source directory, run `make -C xml diff` to see the changes in the current schema (compared to the previous ones) and also the pending changes in `pacemaker-next`. Alternatively, if the intention is to grok the overall historical schema evolution, use `make -C xml fulldiff`.