[ClusterLabs] Antw: Re: Concept of a Shared ipaddress/resource for generic applicatons
>>> Ken Gaillot schrieb am 02.12.2019 um 16:50 in Nachricht <49fc68f1249252b912f0ce9f3ed4a3258f23fb7c.ca...@redhat.com>: > On Sat, 2019-11-30 at 18:58 +0300, Andrei Borzenkov wrote: >> 29.11.2019 17:46, Jan Pokorný пишет: >> > "Clone" feature for IPAddr2 is actually sort of an overloading that >> > agent with an alternative functionality -- trivial low-level load >> > balancing. You can ignore that if you don't need any such. >> > >> >> I would say IPaddr2 in clone mode does something similar to >> SharedAddress. > > Just a side note about something that came up recently: > > IPaddr2 cloning utilizes the iptables "clusterip" feature, which has > been deprecated in the Linux kernel since 2015. IPaddr2 cloning > therefore must be considered deprecated as well. (Using it for a single > floating IP is still fully supported.) > > IPaddr2 could be modified to use a newer iptables capability called > "xt_cluster", but someone would have to volunteer to do that as it's > not a priority. Probably while doing so, also provide better documentation (e.g. hardware requirements). I could not get the cluster IP working when I tried several years ago. Maybe it was due to our networking equipment, but actually I never found out why... Regards, Ulrich > -- > Ken Gaillot > > ___ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] pacemaker will not promote a drbd resource
Hi,
I know this kind of problem has been posted numerous times but my google-fu
doesn't seem to gather anything interesting and I'm really stuck.
I have this 2 node cluster with multiple drbd resources in active/passive mode
(only one primary allowed) and every time one primary drbd resource gets in
trouble (I have still to figure out why, I suspect a home-grown LVM backup
cronjob that takes images of Xen VMs living on top of drbd and brings down the
I/O on the primary node) the whole node get fenced and killed by stonith and
the drbd resources on the secondary node don't get promoted to primary, they
just sits there in secondary role.
After failure, the cluster inserts location constraints that forbid the
surviving node to promote the drbd resources:
location drbd-fence-by-handler-r0-ms_drbd_r0 ms_drbd_r0 \
rule $role=Master -inf: #uname ne node1
The drbd resources are all set with:
resource {
disk {
fencing resource-only;
...
}
handlers {
fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
after-resync-target "/usr/lib/drbd/crm-unfence-peer.sh";
...
}
...
so I fail to see why the node with the problematic resource get killed.
I must do something extremely stupid but I can't see it!
The cluster as a run-of-the-mill config with (the Xen VM 'fly' lives on a
volume group on top of the drbd resource )
primitive p_xen_fly Xen \
params xmfile="/etc/xen/fly.cfg" name=fly \
op monitor interval=20s timeout=60s \
op start interval=0 timeout=90s \
op stop interval=0 timeout=90s \
meta migration-threshold=3 failure-timeout=60s target-role=Started
primitive resDRBDr0 ocf:linbit:drbd \
params drbd_resource=r0 unfence_if_all_uptodate=true \
op start interval=0 timeout=300s \
op stop interval=0 timeout=100s \
op monitor interval=29s role=Master timeout=300s \
op monitor interval=31s role=Slave timeout=300s \
meta migration-threshold=3 failure-timeout=120s
primitive p_lvm_vg0 LVM \
params volgrpname=vg0 \
op start timeout=30s interval=0 \
op stop timeout=30s interval=0 \
op monitor timeout=30s interval=10s
ms ms_drbd_r0 resDRBDr0 \
meta master-max=1 master-node-max=1 clone-max=2 clone-node-max=1
notify=true target-role=Master is-managed=true
colocation c_lvm_vg0_on_drbd_r0 inf: p_lvm_vg0 ms_drbd_r0:Master
colocation c_xen_fly_on_lvm_vg0 inf: p_xen_fly p_lvm_vg0
order o_drbd_r0_before_lvm_vg0 Mandatory: ms_drbd_r0:promote p_lvm_vg0:start
order o_lvm_vg0_before_xen_fly Mandatory: p_lvm_vg0 p_xen_fly
Can anyone see something obvious?
Thanks,
jf
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] 2020 Summit is right around the corner!
I pasted my password into fpaste/IRC a month ago. So... ya. :) digimer On 2019-12-02 2:24 p.m., Steven Levine wrote: > I did *not* mean this message to go to the whole list. My profuse apologies. > > I haven't made this rookie mistake in a decade or more. > > Sorry, > > Steven > > - Original Message - > From: "Steven Levine" > To: "Cluster Labs - All topics related to open-source clustering welcomed" > > Sent: Monday, December 2, 2019 1:23:44 PM > Subject: Re: [ClusterLabs] 2020 Summit is right around the corner! > > Ken: > > I plan to be there. I wasn't sure if I needed to let you know specifically. > > I got budget approval last fall when we thought this would happen in > November, but my department asked me to withdraw that request and re-apply > this quarter when the date was changed. And then they told me we had no more > money in the travel budget, so my manager has asked Chris if the budget could > come from his department. > > But I plan to come anyway, even if I have to pay my own way again. It's much > too important to my ability to do my job well for me to miss this if I can > possibly attend. > > Steven > > - Original Message - > From: "Ken Gaillot" > To: users@clusterlabs.org > Sent: Monday, December 2, 2019 12:43:01 PM > Subject: [ClusterLabs] 2020 Summit is right around the corner! > > The 2020 ClusterLabs summit is only two months away! Details are > available at: > > http://plan.alteeve.ca/index.php/HA_Cluster_Summit_2020 > > So far we have responses from Alteeve, Canonical, IBM MQ, NTT, Proxmox, > Red Hat, and SUSE. If anyone else thinks they might attend, please > reply here or email me privately so we can firm up the head count and > finalize planning. > > Thanks, > -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] 2020 Summit is right around the corner!
I did *not* mean this message to go to the whole list. My profuse apologies. I haven't made this rookie mistake in a decade or more. Sorry, Steven - Original Message - From: "Steven Levine" To: "Cluster Labs - All topics related to open-source clustering welcomed" Sent: Monday, December 2, 2019 1:23:44 PM Subject: Re: [ClusterLabs] 2020 Summit is right around the corner! Ken: I plan to be there. I wasn't sure if I needed to let you know specifically. I got budget approval last fall when we thought this would happen in November, but my department asked me to withdraw that request and re-apply this quarter when the date was changed. And then they told me we had no more money in the travel budget, so my manager has asked Chris if the budget could come from his department. But I plan to come anyway, even if I have to pay my own way again. It's much too important to my ability to do my job well for me to miss this if I can possibly attend. Steven - Original Message - From: "Ken Gaillot" To: users@clusterlabs.org Sent: Monday, December 2, 2019 12:43:01 PM Subject: [ClusterLabs] 2020 Summit is right around the corner! The 2020 ClusterLabs summit is only two months away! Details are available at: http://plan.alteeve.ca/index.php/HA_Cluster_Summit_2020 So far we have responses from Alteeve, Canonical, IBM MQ, NTT, Proxmox, Red Hat, and SUSE. If anyone else thinks they might attend, please reply here or email me privately so we can firm up the head count and finalize planning. Thanks, -- Ken Gaillot ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] 2020 Summit is right around the corner!
Ken: I plan to be there. I wasn't sure if I needed to let you know specifically. I got budget approval last fall when we thought this would happen in November, but my department asked me to withdraw that request and re-apply this quarter when the date was changed. And then they told me we had no more money in the travel budget, so my manager has asked Chris if the budget could come from his department. But I plan to come anyway, even if I have to pay my own way again. It's much too important to my ability to do my job well for me to miss this if I can possibly attend. Steven - Original Message - From: "Ken Gaillot" To: users@clusterlabs.org Sent: Monday, December 2, 2019 12:43:01 PM Subject: [ClusterLabs] 2020 Summit is right around the corner! The 2020 ClusterLabs summit is only two months away! Details are available at: http://plan.alteeve.ca/index.php/HA_Cluster_Summit_2020 So far we have responses from Alteeve, Canonical, IBM MQ, NTT, Proxmox, Red Hat, and SUSE. If anyone else thinks they might attend, please reply here or email me privately so we can firm up the head count and finalize planning. Thanks, -- Ken Gaillot ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] 2020 Summit is right around the corner!
The 2020 ClusterLabs summit is only two months away! Details are available at: http://plan.alteeve.ca/index.php/HA_Cluster_Summit_2020 So far we have responses from Alteeve, Canonical, IBM MQ, NTT, Proxmox, Red Hat, and SUSE. If anyone else thinks they might attend, please reply here or email me privately so we can firm up the head count and finalize planning. Thanks, -- Ken Gaillot ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Concept of a Shared ipaddress/resource for generic applicatons
On Sat, 2019-11-30 at 18:58 +0300, Andrei Borzenkov wrote: > 29.11.2019 17:46, Jan Pokorný пишет: > > "Clone" feature for IPAddr2 is actually sort of an overloading that > > agent with an alternative functionality -- trivial low-level load > > balancing. You can ignore that if you don't need any such. > > > > I would say IPaddr2 in clone mode does something similar to > SharedAddress. Just a side note about something that came up recently: IPaddr2 cloning utilizes the iptables "clusterip" feature, which has been deprecated in the Linux kernel since 2015. IPaddr2 cloning therefore must be considered deprecated as well. (Using it for a single floating IP is still fully supported.) IPaddr2 could be modified to use a newer iptables capability called "xt_cluster", but someone would have to volunteer to do that as it's not a priority. -- Ken Gaillot ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
