Re: [ClusterLabs] resource cloned group colocations

2023-03-02 Thread Andrei Borzenkov
On Thu, Mar 2, 2023 at 4:16 PM Gerald Vogt wrote: > > On 02.03.23 13:51, Klaus Wenninger wrote: > > Now if I stop pacemaker on one of those nodes, e.g. on node ha2, it's > > fine. ip2 will be moved immediately to ha3. Good. > > > > However, if pacemaker on ha2 starts up again, it will

Re: [ClusterLabs] resource cloned group colocations

2023-03-02 Thread Vladislav Bogdanov
On Thu, 2023-03-02 at 08:41 +0100, Gerald Vogt wrote: > Hi, > > I am setting up a mail relay cluster which main purpose is to > maintain > the service ips via IPaddr2 and move them between cluster nodes when > necessary. > > The service ips should only be active on nodes which are running all

Re: [ClusterLabs] resource cloned group colocations

2023-03-02 Thread Gerald Vogt
On 02.03.23 13:51, Klaus Wenninger wrote: Now if I stop pacemaker on one of those nodes, e.g. on node ha2, it's fine. ip2 will be moved immediately to ha3. Good. However, if pacemaker on ha2 starts up again, it will immediately remove ip2 from ha3 and keep it offline, while

Re: [ClusterLabs] resource cloned group colocations

2023-03-02 Thread Klaus Wenninger
On Thu, Mar 2, 2023 at 8:41 AM Gerald Vogt wrote: > Hi, > > I am setting up a mail relay cluster which main purpose is to maintain > the service ips via IPaddr2 and move them between cluster nodes when > necessary. > > The service ips should only be active on nodes which are running all >

[ClusterLabs] resource cloned group colocations

2023-03-01 Thread Gerald Vogt
Hi, I am setting up a mail relay cluster which main purpose is to maintain the service ips via IPaddr2 and move them between cluster nodes when necessary. The service ips should only be active on nodes which are running all necessary mail (systemd) services. So I have set up a resource