<div dir="ltr">HI<div><br></div><div>yes, that's what I meant, both resources on the same node.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 11, 2021 at 11:39 AM Ulrich Windl <<a href="mailto:Ulrich.Windl@rz.uni-regensburg.de">Ulrich.Windl@rz.uni-regensburg.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">>>> "Ben .T.George" <<a href="mailto:bentech4you@gmail.com" target="_blank">bentech4you@gmail.com</a>> schrieb am 10.02.2021 um 20:28 in<br>
Nachricht<br>
<<a href="mailto:CA%2BC_GOVfVM10JGYUOueZPateNSOzjbFrHyuyYcWjF8HSJ88snw@mail.gmail.com" target="_blank">CA+C_GOVfVM10JGYUOueZPateNSOzjbFrHyuyYcWjF8HSJ88snw@mail.gmail.com</a>>:<br>
> HI<br>
> <br>
> i have 2 resources and i would like configure in such a way that both<br>
> should always run from same node,<br>
<br>
"from" == "on"?<br>
<br>
see "colocation" constraints.<br>
<br>
> <br>
> also is it safe to give below values for 2 node cluster:<br>
> <br>
> pcs resource defaults migration-threshold=1<br>
> pcs property set no-quorum-policy=ignore<br>
> <br>
> <br>
> below is my pcs config:<br>
> ---------------------------------------------<br>
> Cluster Name: EMS<br>
> Corosync Nodes:<br>
>  <a href="http://zkwemsapp01.example.com" rel="noreferrer" target="_blank">zkwemsapp01.example.com</a> <a href="http://zkwemsapp02.example.com" rel="noreferrer" target="_blank">zkwemsapp02.example.com</a><br>
> Pacemaker Nodes:<br>
>  <a href="http://zkwemsapp01.example.com" rel="noreferrer" target="_blank">zkwemsapp01.example.com</a> <a href="http://zkwemsapp02.example.com" rel="noreferrer" target="_blank">zkwemsapp02.example.com</a><br>
> <br>
> Resources:<br>
>  Group: ems_rg<br>
>   Resource: ems_vip (class=ocf provider=heartbeat type=IPaddr2)<br>
>    Attributes: cidr_netmask=24 ip=10.96.11.39<br>
>    Meta Attrs: resource-stickiness=1<br>
>    Operations: monitor interval=30s (ems_vip-monitor-interval-30s)<br>
>                start interval=0s timeout=20s (ems_vip-start-interval-0s)<br>
>                stop interval=0s timeout=20s (ems_vip-stop-interval-0s)<br>
>   Resource: ems_app (class=systemd type=ems-app)<br>
>    Meta Attrs: resource-stickiness=1<br>
>    Operations: monitor interval=60 timeout=100 (ems_app-monitor-interval-60)<br>
>                start interval=0s timeout=40s (ems_app-start-interval-0s)<br>
>                stop interval=0s timeout=40s (ems_app-stop-interval-0s)<br>
> <br>
> Stonith Devices:<br>
>  Resource: ems_vmware_fence (class=stonith type=fence_vmware_soap)<br>
>   Attributes: ip=10.151.37.110 password=gfghfghfghfghfgh<br>
> pcmk_host_map=zkwemsapp01.example.com:ZKWEMSAPP01;zkwemsapp02.example.com:ZK<br>
> WEMSAPP02<br>
> ssl_insecure=1 username=domain\redhat.fadmin<br>
>   Operations: monitor interval=60s (ems_vmware_fence-monitor-interval-60s)<br>
> Fencing Levels:<br>
>   Target: <a href="http://zkwemsapp01.example.com" rel="noreferrer" target="_blank">zkwemsapp01.example.com</a><br>
>     Level 1 - ems_vmware_fence<br>
>   Target: <a href="http://zkwemsapp02.example.com" rel="noreferrer" target="_blank">zkwemsapp02.example.com</a><br>
>     Level 1 - ems_vmware_fence<br>
> <br>
> Location Constraints:<br>
> Ordering Constraints:<br>
> Colocation Constraints:<br>
> Ticket Constraints:<br>
> <br>
> Alerts:<br>
>  No alerts defined<br>
> <br>
> Resources Defaults:<br>
>  resource-stickiness=1000<br>
> Operations Defaults:<br>
>  No defaults set<br>
> <br>
> Cluster Properties:<br>
>  cluster-infrastructure: corosync<br>
>  cluster-name: EMS<br>
>  dc-version: 2.0.2-3.el8-744a30d655<br>
>  have-watchdog: false<br>
>  last-lrm-refresh: 1612951127<br>
>  symmetric-cluster: true<br>
> <br>
> Quorum:<br>
>   Options:<br>
> ----------------------------------------------<br>
> <br>
> Regards,<br>
> Ben<br>
<br>
<br>
<br>
<br>
</blockquote></div>