pacemaker 1.1.18-2ubuntu1 source package in Ubuntu

Changelog

pacemaker (1.1.18-2ubuntu1) cosmic; urgency=medium

  * Merge with Debian. Remaining changes:
    - d/control: Demote fence-agents to Suggests, avoiding main
      inclusion.
    - debian/patches/pacemaker_is_partof_corosync.patch: Default systemd
      unit hard-requires corosync.
      + Debian disagrees in Debian bug 887563 message 36. We could revert back
        to Debian's behaviour, but keeping the patch in this merge maintains
        existing behaviour for Ubuntu users pending any separate future
        decision.
  * Drop changes:
    - Drop upstreamed patches (dropped in Debian now instead).
    - Refresh d/p/portability-define-EKEYREJECTED-if-necessary.patch: no longer
      needed; dropped in Debian.
    - d/pacemaker.{pre,post}inst flag for corosync: upgrade path no longer
      needed post-Bionic.

pacemaker (1.1.18-2) unstable; urgency=medium

  * [812cda7] Fixup symbols files.
    The Hurd architecture looks strangely irregular.
  * [38d49fe] Simplify autopkgtest script
  * [87f237c] Remove trailing empty line from debian/changelog

pacemaker (1.1.18-1) unstable; urgency=medium

  * [da58a7f] Some overlooked libqb vs new binutils symbol flux
  * [c6b8c8a] New upstream release (1.1.18)
  * [871dcfa] Delete upstreamed patches, refresh the rest
  * [7c9e795] Add post-1.1.18 regression fixes
    https://lists.clusterlabs.org/pipermail/users/2017-December/014227.html
    * 1.1.18 improved scalability by eliminating redundant node attribute
    write-outs. This proved to be too aggressive in one case: when a
    cluster is configured with only IP addresses (no node names) in
    corosync.conf, attribute write-outs can be incorrectly delayed; in the
    worst case, this prevents a node from shutting down due to the shutdown
    attribute not being written.
    * 1.1.18 overhauled unfencing in order to support it on remote nodes.
    (Unfencing is for devices such as fence_scsi that require a fenced node
    to be explicitly re-admitted to the cluster.) This made the faulty
    assumption that the fence devices themselves could operate before
    unfencing happened. As a result, a cluster with unfencing could see
    unnecessary fence device monitoring failures (these do not harm the
    cluster's ability to fence or unfence).
    * 1.1.18 implemented ordering constraints for the new bundle resource
    type. This had a corner case that could lead to an invalid transition.
    As part of the fix for this, we have included a fix for an issue
    discussed in an earlier thread on this list ("pcmk_remote evaluation"),
    so the cluster will always prefer the newest Pacemaker Remote
    connection to a remote node, even if an older (dead) connection has not
    yet timed out.
  * [4d9e29c] Update Standards-Version to 4.1.4 (no changes required)
  * [c77cdf4] Migrate to salsa.debian.org/ha-team
  * [269dcb6] Switch to HTTPS in the Homepage and Source URLs
  * [371288b] Switch to Debhelper compat level 11
  * [c58d652] Replace hand-made control substitution with stock dpkg method.
    Remove the superfluous check_header_deps call as well.
  * [eb76cbd] Update symbols files

 -- Robie Basak <email address hidden>  Tue, 24 Jul 2018 14:12:03 +0100

Upload details

Uploaded by:
Robie Basak on 2018-07-25
Uploaded to:
Cosmic
Original maintainer:
Ubuntu Developers
Architectures:
any all
Section:
admin
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Eoan release on 2019-04-18 main admin
Disco release on 2018-10-30 main admin
Cosmic release on 2018-07-25 main admin

Downloads

File Size SHA-256 Checksum
pacemaker_1.1.18.orig.tar.gz 5.1 MiB a71921c1e2a93c5bed6199fb41464a1cff887be515f4a0ffbc2c92bc98d233af
pacemaker_1.1.18-2ubuntu1.debian.tar.xz 79.4 KiB 4dd53939261f50cf35a614332e3ac133b74a37578a802b4c35dfa21bab1f970a
pacemaker_1.1.18-2ubuntu1.dsc 3.8 KiB 62c145a2b100229ab255d8efaf96084727188bfc257fb12ac27c9fb0679558ab

View changes file

Binary packages built by this source

libcib-dev: cluster resource manager CIB library development

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the headers and other necessary files to build
 applications or libraries that use the Cluster Information Base library.

libcib4: cluster resource manager CIB library

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the Cluster Information Base library.

libcib4-dbgsym: debug symbols for libcib4
libcrmcluster-dev: cluster resource manager cluster library development

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the headers and other necessary files to build
 applications or libraries that use the cluster library.

libcrmcluster4: cluster resource manager cluster library

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the cluster library.

libcrmcluster4-dbgsym: debug symbols for libcrmcluster4
libcrmcommon-dev: cluster resource manager common library development

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the headers and other necessary files to build
 applications or libraries that use the common library.

libcrmcommon3: cluster resource manager common library

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the common library.

libcrmcommon3-dbgsym: debug symbols for libcrmcommon3
libcrmservice-dev: cluster resource manager service library development

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the headers and other necessary files to build
 applications or libraries that use the service library.

libcrmservice3: cluster resource manager service library

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the service library.

libcrmservice3-dbgsym: debug symbols for libcrmservice3
liblrmd-dev: cluster resource manager LRMD library development

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the headers and other necessary files to build
 applications or libraries that use the Local Resource Manager Daemon
 library.

liblrmd1: cluster resource manager LRMD library

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the Local Resource Manager Daemon library.

liblrmd1-dbgsym: debug symbols for liblrmd1
libpe-rules2: cluster resource manager Policy Engine rules library

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the Policy Engine rules library.

libpe-rules2-dbgsym: debug symbols for libpe-rules2
libpe-status10: cluster resource manager Policy Engine status library

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the Policy Engine status library.

libpe-status10-dbgsym: debug symbols for libpe-status10
libpengine-dev: cluster resource manager Policy Engine library development

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the headers and other necessary files to build
 applications or libraries that use the Policy Engine library.

libpengine10: cluster resource manager Policy Engine library

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the Policy Engine library.

libpengine10-dbgsym: debug symbols for libpengine10
libstonithd-dev: cluster resource manager STONITH daemon library development

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the headers and other necessary files to build
 applications or libraries that use the STONITH daemon library.

libstonithd2: cluster resource manager STONITH daemon library

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the STONITH daemon library.

libstonithd2-dbgsym: debug symbols for libstonithd2
libtransitioner2: cluster resource manager transitioner library

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the transitioner library.

libtransitioner2-dbgsym: debug symbols for libtransitioner2
pacemaker: cluster resource manager

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the Pacemaker daemons directly interacting with
 the cluster stack.

pacemaker-cli-utils: cluster resource manager command line utilities

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains those command line utilities of the Pacemaker
 cluster manager which work on remote nodes as well.

pacemaker-cli-utils-dbgsym: debug symbols for pacemaker-cli-utils
pacemaker-common: cluster resource manager common files

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains common infrastructure and data files for the
 Pacemaker daemons and utilities.

pacemaker-dbgsym: debug symbols for pacemaker
pacemaker-doc: cluster resource manager HTML documentation

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains
  * the Pacemaker API documentation generated by Doxygen,
  * the Clusters from Scratch book,
  * the Pacemaker Development book,
  * the Pacemaker Explained book and
  * the Pacemaker Remote book.

pacemaker-remote: cluster resource manager proxy daemon for remote nodes

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains the Pacemaker proxy daemon, which simulates cluster
 services on a node not running the cluster stack. Such "remote" nodes can
 run resources but don't participate in the quorum. This package is
 mutually exclusive with Pacemaker proper.

pacemaker-remote-dbgsym: debug symbols for pacemaker-remote
pacemaker-resource-agents: cluster resource manager general resource agents

 At its core, Pacemaker is a distributed finite state
 machine capable of co-ordinating the startup and recovery of inter-related
 services across a set of machines.
 .
 Pacemaker understands many different resource types (OCF, SYSV, systemd) and
 can accurately model the relationships between them (colocation, ordering).
 .
 It can even use technology such as Docker to automatically isolate the
 resources managed by the cluster.
 .
 This package contains Pacemaker resource agents not requiring access
 to the cluster stack, thus also usable by the remote daemon.