Re: [ClusterLabs] Pacemaker for Embedded Systems

On 04/11/2017 12:11 AM, Dimitri Maziuk wrote: > On 04/10/2017 03:58 PM, Chad Cravens wrote: > >> However, we are considering if pacemaker would be a good solution for high >> availability for an embedded control system that integrates with CAN for >> vehicles? > When fencing puts my vehicle in a

Re: [ClusterLabs] Pacemaker for Embedded Systems

On 04/10/2017 03:58 PM, Chad Cravens wrote: > However, we are considering if pacemaker would be a good solution for high > availability for an embedded control system that integrates with CAN for > vehicles? When fencing puts my vehicle in a "known" state, I'd want to be very sure it's the

[ClusterLabs] Pacemaker for Embedded Systems

Hello all: we have implemented large cluster solutions for complex server environments that had databases, application servers, apache web servers and implemented fencing with the IPMI fencing agent. However, we are considering if pacemaker would be a good solution for high availability for an

[ClusterLabs] PSA Ubuntu 16.04 and OCSF2 corruption

Hello, Just opened what I think is a bug with the Ubuntu util-linux package: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1681410 TL;DR The 'fstrim' command is run weekly on all filesystems. If you're using ocfs2 and the same filesystem is mounted on multiple Ubuntu 16.04

Re: [ClusterLabs] Adding a node to the cluster deployed with "Unicast configuration"

Sorry, i lack of the last command, where i took the node out of the CIB. discard my previous question, thanks On Mon, Apr 10, 2017 at 3:11 PM, Alejandro Comisario wrote: > Hi, im reviving this thread because of the following. > > To add new nodes to the cluster, this

Re: [ClusterLabs] Adding a node to the cluster deployed with "Unicast configuration"

Hi, im reviving this thread because of the following. To add new nodes to the cluster, this procedure works like a charm. But to take them out, i've assumed the follwing, whitch didnt worked. * stop corosync/pacemaker on the old node * update all corosync.conf on the cluster and took the old

Re: [ClusterLabs] Can't See Why This Cluster Failed Over

Eric Robinson writes: >> crm configure show xml c_clust19 > > Here is what I am entering using crmsh (version 2.0-1): > > > colocation c_clust19 inf: [ p_mysql_057 p_mysql_092 p_mysql_187 ] > p_vip_clust19 p_fs_clust19 p_lv_on_drbd0 ms_drbd0:Master > order o_clust19

Re: [ClusterLabs] Can't See Why This Cluster Failed Over

> crm configure show xml c_clust19 Here is what I am entering using crmsh (version 2.0-1): colocation c_clust19 inf: [ p_mysql_057 p_mysql_092 p_mysql_187 ] p_vip_clust19 p_fs_clust19 p_lv_on_drbd0 ms_drbd0:Master order o_clust19 inf: ms_drbd0:promote p_lv_on_drbd0 p_fs_clust19 p_vip_clust19