Re: [ClusterLabs] Colocation constraint for grouping all master-mode stateful resources with important stateless resources

On Mon, 2018-03-26 at 15:42 +, Sam Gardner wrote: > Thanks, Andrei and Alberto. > > Alberto, I will look into the node-constraint parameters, though I > suspect Andrei is correct - my "base" resource is DRBDFS in this > case, and the issue I'm seeing is that a failure in my secondary >

Re: [ClusterLabs] Colocation constraint for grouping all master-mode stateful resources with important stateless resources

>> >> It is possible. Check this thread >> https://lists.clusterlabs.org/pipermail/users/2017-November/006788.html >> > > I do not see how it answers the question. It explains how to use other > criteria than node name for colocating resources, but it does not change > basic fact that colocating

Re: [ClusterLabs] Colocation constraint for grouping all master-mode stateful resources with important stateless resources

Thanks, Andrei and Alberto. Alberto, I will look into the node-constraint parameters, though I suspect Andrei is correct - my "base" resource is DRBDFS in this case, and the issue I'm seeing is that a failure in my secondary resources does not cause the other secondary resources nor the "base"

Re: [ClusterLabs] Colocation constraint for grouping all master-mode stateful resources with important stateless resources

25.03.2018 10:21, Alberto Mijares пишет: > On Sat, Mar 24, 2018 at 2:16 PM, Andrei Borzenkov wrote: >> 23.03.2018 20:42, Sam Gardner пишет: >>> Thanks, Ken. >>> >>> I just want all master-mode resources to be running wherever DRBDFS is >>> running (essentially). If the

Re: [ClusterLabs] Colocation constraint for grouping all master-mode stateful resources with important stateless resources

On Sat, Mar 24, 2018 at 2:16 PM, Andrei Borzenkov wrote: > 23.03.2018 20:42, Sam Gardner пишет: >> Thanks, Ken. >> >> I just want all master-mode resources to be running wherever DRBDFS is >> running (essentially). If the cluster detects that any of the master-mode >>

Re: [ClusterLabs] Colocation constraint for grouping all master-mode stateful resources with important stateless resources

23.03.2018 20:42, Sam Gardner пишет: > Thanks, Ken. > > I just want all master-mode resources to be running wherever DRBDFS is > running (essentially). If the cluster detects that any of the master-mode > resources can't run on the current node (but can run on the other per > ethmon), all

Re: [ClusterLabs] Colocation constraint for grouping all master-mode stateful resources with important stateless resources

The shared-ip resource agents are our own custom RA - they do what we want and the failover mechanism for the single resource works fine as far as I can tell - using conntrackd or some other non-IP master/slave resource would be the same sort of failure that we're running into because the

Re: [ClusterLabs] Colocation constraint for grouping all master-mode stateful resources with important stateless resources

Thanks, Ken. I just want all master-mode resources to be running wherever DRBDFS is running (essentially). If the cluster detects that any of the master-mode resources can't run on the current node (but can run on the other per ethmon), all other master-mode resources as well as DRBDFS should

Re: [ClusterLabs] Colocation constraint for grouping all master-mode stateful resources with important stateless resources

On Tue, 2018-03-20 at 16:34 +, Sam Gardner wrote: > Hi All - > > I've implemented a simple two-node cluster with DRBD and a couple of > network-based Master/Slave resources. > > Using the ethmonitor RA, I set up failover whenever the > Master/Primary node loses link on the specified ethernet

[ClusterLabs] Colocation constraint for grouping all master-mode stateful resources with important stateless resources

Hi All - I've implemented a simple two-node cluster with DRBD and a couple of network-based Master/Slave resources. Using the ethmonitor RA, I set up failover whenever the Master/Primary node loses link on the specified ethernet physical device by constraining the Master role only on nodes