Re: [ClusterLabs] resource-agents v4.2.0
On Wed, 2018-10-24 at 10:21 +0200, Oyvind Albrigtsen wrote: > ClusterLabs is happy to announce resource-agents v4.2.0. > Source code is available at: > https://github.com/ClusterLabs/resource-agents/releases/tag/v4.2.0 > [snip] > - ocf.py: new Python library and dev guide > I just wanted to highlight the Python library since I think it can make agent development a lot easier in the future, especially as we expand the library with more utilities that are commonly needed when writing agents. Any agents written in Python should (for now at least) be compatible both with Python 2.7+ and Python 3.3+. We still need to expand the CI to actually verify that agents do support these versions, so anyone who would like to help out improving the test setup is more than welcome to do so :) The biggest example of an agent using it that we have now is the azure- events agent [1], so I would recommend anyone interested in working on new agents to take a look at that. For a more compact example, I wrote a version of the Dummy resource agent using the ocf.py library and put it in a gist [2], and then there is a small example in the document describing the library and how to use it [3]. [1]: https://github.com/ClusterLabs/resource-agents/blob/master/heartbe at/azure-events.in [2]: https://gist.github.com/krig/6676d0ae065fd852fac8b445410e1c95 [3]: https://github.com/ClusterLabs/resource-agents/blob/master/doc/dev -guides/writing-python-agents.md Cheers, Kristoffer ___ Users mailing list: Users@clusterlabs.org https://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[ClusterLabs] resource-agents v4.2.0
ClusterLabs is happy to announce resource-agents v4.2.0. Source code is available at: https://github.com/ClusterLabs/resource-agents/releases/tag/v4.2.0 The most significant enhancements in this release are: - new resource agents: - azure-events - aliyun-vpc-move-ip - gcp-pd-move - gcp-vpc-move-ip - gcp-vpc-move-route (improved Python version of gcp-vpc-move-ip) - gcp-vpc-move-vip - openstack-cinder-volume - openstack-floating-ip - openstack-info - podman - sybaseASE - bugfixes and enhancements: - apache: fix return value for silent_status (introduced in the retry PID check mentioned below) - rabbitmq-cluster: fail monitor when node is in minority partition - ZFS: check status without locks when possible - pgsql: fix to avoid failing on masters re-promote - CI: fixes for bash path, strncpy in GCC 8 and missing docbook-style-xsl - CTDB: fix "ctdb_recovery_lock" validation - CTDB: fix incorrect DB corruption reports (ensure health check is run) - Filesystem: support symlink as mountpoint directory - IPaddr2: return OCF_ERR_GENERIC when failing due to IPv4 address collision - LVM-activate: fix for dashes in volume group and logical volume names - LVM-activate: read parameters for stop-action - LVM-activate: return OCF_ERR_CONFIGURED for incorrect vg_access_mode - LVM: added missing dash for activation parameters - SAPDatabase: add info to meta-data - SAPInstance: add monitored services for ENSA2 (bsc#1092384) - SAPInstance: implement reload action to avoid resource restarts after a non-unique parameter has been changed - SAPInstance: improve SAP instance profile detection - SAPInstance: improve stop-action logging - Squid: use ss if netstat is not available - VirtualDomain: add stateless support - VirtualDomain: correctly create logfile and set permissions - Xen: add utilization support for cpu and hv_memory - apache: retry PID check - aws-vpc-move-ip: check routing table during monitor probe action - aws-vpc-move-ip: fix backward-compatibility - aws-vpc-move-ip: use ip utility to check address - awseip: fix allocation_id not found error - awseip: update required IAM role permissions - awsvip: get network-id from metadata - awsvip: improve secondary-private-ip query - configure: add Python path detection - exportfs: fix square bracket stripping in clientspec - findif: improve IPv6 NIC detection - findif: only match lines containing netmasks (for newer iputils) - garbd: support netstat and ss - iSCSITarget: support CHAP authentication for lio-t - ipsec: add tunnel fallback option - ldirectord: add manpage to systemd unit file - lvmlockd: add cmirrord support - mysql: remove obsolete DEBUG_LOG functionality (bsc#1021689) - nfsserver: fix rpcpipefs_dir and nfs_shared_infodir issues - ocf-binaries: use SSH-path detected by configure - ocf.py: new Python library and dev guide - oracle: improve dbopen error - pgsql: create replication slots after promoting master - pgsql: dont change ownership of /dev/null - pgsql: support PostgreSQL 11 or later - portblock: support ss and netstat (partial) - ra-dev-guide: update instructions for GitHub - rabbitmq-cluster: get cluster status from mnesia during monitor - rabbitmq-cluster: retry start when cluster join fails - redis: do not use absolute path in pidof calls - sg_persist: correctly pickup old keys - syslog-ng: add Premium Edition 6 and 7 support - systemd-tmpfiles: configure path with --with-rsctmpdir The full list of changes for resource-agents is available at: https://github.com/ClusterLabs/resource-agents/blob/v4.2.0/ChangeLog Everyone is encouraged to download and test the new release candidate. We do many regression tests and simulations, but we can't cover all possible use cases, so your feedback is important and appreciated. Many thanks to all the contributors to this release. Best, The resource-agents maintainers ___ Users mailing list: Users@clusterlabs.org https://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[ClusterLabs] Antw: About the Pacemaker
>>> "T. Ladd Omar" schrieb am 23.10.2018 um 15:06 in >>> Nachricht : > Hi all, I send this message to get some answers for my questions about > Pacemaker. > 1. In order to cleanup start-failed resources automatically, I add > failure-timeout attribute for resources, however, the common way to trigger > the recovery is by cluster-recheck whose interval is 15min by default. I > wonder how lower value could I set for the cluster-recheck-interval. I had > to let the failed resources recover somewhat quickly while little impact > taken by the more frequent cluster-recheck. I think if your agents fail periodically, and you need to do a periodic cleanup of failed actions, your configuration is not stable enough for production. Also, if you always cleanup failed actions, resources may not move to a good node of one node has a problem. > Or, is there another way to automatically cleanup start-failed resources ? > 2. Is Pacemaker suitable for the Master-Slave model HA ? I had some > productive problems when I use Pacemaker. If only one resource stopped on > one node, should I failover all this node for the whole cluster? If not, > the transactions from the ports on this node may fail for this failure. If > yes, it seems to be big action for just one resource failure. ___ Users mailing list: Users@clusterlabs.org https://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [ClusterLabs] VirtualBox : an improved OCF agent
Hello again, The original script had been posted on VB's forum and it is at Howtos there. I subscribed, tried to reach the original author but got no response so far. For me GPL (eg v2) is ok. Cheers John On 5/10/2018 15:00, users-requ...@clusterlabs.org wrote: Date: Thu, 04 Oct 2018 09:19:55 -0500 From: Ken Gaillot To: Cluster Labs - All topics related to open-source clustering welcomed Subject: Re: [ClusterLabs] VirtualBox : an improved OCF agent Message-ID: <1538662795.4624.6.ca...@redhat.com> Content-Type: text/plain; charset="UTF-8" On Thu, 2018-10-04 at 13:35 +0300, Ioannis Ioannou wrote: Hello to all, This is the first time I use HA on Linux. I'm still learning, and I like? it a lot. I was interested to a active/passive system that can support virtual? machines with live migration. For various reason I prefer VirtualBox as? the hypervisor. I used an existing agent that I found here:? https://forums.virtualbox.org/viewtopic.php?f=7&t=35372, improved it and? I would like to share it. It is now more robust and ocf compliant and supports live migration (aka? teleportation in VBox's terminology). I'm testing it one week now on? Debian Stretch and seems stable enough for production. The assumptions in order to be used: 1) Both nodes should mount the same filesystem, the same time (ie iscsi,? cluster, nfs, and so on). I used glusterfs and works like a charm. I put? VM settings and images on it. 2) Both nodes should have reasonable similar hardware - close enough so? that teleportation can work - check VirtualBox's documentation regarding? teleportation for this. 3) Both VMs should have the same settings- if you put the settings on? the common filesystem as I did, then it is easy: create the VM on one? node, just add it on the other. 4) SSH keys should be exchanged between nodes. You see, migrate_to? should be able to handle both nodes in order live migration? (teleporting) to work. 5) Teleportation works by putting the receiving node listening on a port? - by default 6000. Ensure that the port is correct and accessible from? the other node. Any comments are more than welcomed Cheers John (aka Ioannis) That's awesome. If you can find the original author and get agreement to put it under an open source license, it would be a great addition to the resource-agents package. -- Ken Gaillot ___ Users mailing list: Users@clusterlabs.org https://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
