Re: [ClusterLabs] Removing a resource without stopping it

2022-01-31 Thread Ken Gaillot
On Mon, 2022-01-31 at 10:37 +0100, Tomas Jelinek wrote: > Hi, > > The output you posted actually shows the procedure you followed > works. > Orphan resources are running resources which have no configuration > stored in CIB. Usually, they are stopped shortly after they are > removed > from

Re: [ClusterLabs] Removing a resource without stopping it

2022-01-31 Thread Jehan-Guillaume de Rorthais
Hi, On Sat, 29 Jan 2022 16:51:47 -0500 Digimer wrote: > ... > Though going back to the original question, deleting the server from > pacemaker while the VM is left running, is still something I am quite curious > about. As the real resource moved away, meaning it couldn't be stopped locally

Re: [ClusterLabs] Removing a resource without stopping it

2022-01-31 Thread Tomas Jelinek
Hi, The output you posted actually shows the procedure you followed works. Orphan resources are running resources which have no configuration stored in CIB. Usually, they are stopped shortly after they are removed from CIB. If you set stop-orphan-resources to false, pacemaker won't stop

Re: [ClusterLabs] Removing a resource without stopping it

2022-01-29 Thread Digimer
I think I have a working method, though not in the conditions first explained. Though I would love to have feedback on it's sanity. The ultimate goal is to migrate the resource (VM) to a different pacemaker cluster. Setting it to be unmanaged,

Re: [ClusterLabs] Removing a resource without stopping it

2022-01-29 Thread Strahil Nikolov via Users
I know... and the editor stuff can be bypassed, if the approach works. Best Regards,Strahil Nikolov On Sat, Jan 29, 2022 at 15:43, Digimer wrote:On 2022-01-29 03:16, Strahil Nikolov wrote: I think there is pcs cluster edit --scope=resources (based on memory). Can you try to

Re: [ClusterLabs] Removing a resource without stopping it

2022-01-29 Thread Digimer
On 2022-01-29 03:16, Strahil Nikolov wrote: I think there is pcs cluster edit --scope=resources (based on memory). Can you try to delete it from there ? Best Regards, Strahil Nikolov Thanks, but no that

Re: [ClusterLabs] Removing a resource without stopping it

2022-01-29 Thread Strahil Nikolov via Users
I think there is pcs cluster edit --scope=resources (based on memory).Can you try to delete it from there ? Best Regards,Strahil Nikolov On Sat, Jan 29, 2022 at 7:12, Digimer wrote: ___ Manage your subscription:

Re: [ClusterLabs] Removing a resource without stopping it

2022-01-28 Thread Digimer
On 2022-01-29 00:10, Digimer wrote: On 2022-01-28 16:54, Ken Gaillot wrote: On Fri, 2022-01-28 at 16:38 -0500, Digimer wrote: Hi all, I'm trying to figure out how to move a running VM from one pacemaker

Re: [ClusterLabs] Removing a resource without stopping it

2022-01-28 Thread Digimer
On 2022-01-28 16:54, Ken Gaillot wrote: On Fri, 2022-01-28 at 16:38 -0500, Digimer wrote: Hi all, I'm trying to figure out how to move a running VM from one pacemaker cluster to another. I've got the storage and VM live migration sorted, but having

Re: [ClusterLabs] Removing a resource without stopping it

2022-01-28 Thread Digimer
On 2022-01-28 16:54, Ken Gaillot wrote: On Fri, 2022-01-28 at 16:38 -0500, Digimer wrote: Hi all, I'm trying to figure out how to move a running VM from one pacemaker cluster to another. I've got the storage and VM live migration sorted, but having

Re: [ClusterLabs] Removing a resource without stopping it

2022-01-28 Thread Ken Gaillot
On Fri, 2022-01-28 at 16:38 -0500, Digimer wrote: > Hi all, > >I'm trying to figure out how to move a running VM from one > pacemaker > cluster to another. I've got the storage and VM live migration > sorted, > but having trouble with pacemaker. > >I tried unmanaging the resource (the

[ClusterLabs] Removing a resource without stopping it

2022-01-28 Thread Digimer
Hi all,   I'm trying to figure out how to move a running VM from one pacemaker cluster to another. I've got the storage and VM live migration sorted, but having trouble with pacemaker.   I tried unmanaging the resource (the VM), then deleted the resource, and the node got fenced. So I am