On Mon, Apr 17, 2023 at 10:48 AM Philip Schiller
wrote:
>
> Hello Andrei,
>
> you wrote:
>
> >>As a workaround you could add dummy clone resource colocated with and
> >>ordered after your DRBD masters and order VM after this clone.
>
> Thanks for the idea. This looks like a good option to solve
Hello Andrei,
you wrote:
As a workaround you could add dummy clone resource colocated with and
ordered after your DRBD masters and order VM after this clone.
Thanks for the idea. This looks like a good option to solve my problem.
I have also researched a little more and came up with an
On 14.04.2023 14:35, Andrei Borzenkov wrote:
On Fri, Apr 14, 2023 at 11:45 AM Philip Schiller
wrote:
I would like to know if the order constraint
is equivalent to: "First promote ms-drbd_fs then start drbd_vm".
No, it is not. It is equivalent to
order drbd_vm_after_drbd_fs Mandatory:
On Fri, Apr 14, 2023 at 2:35 PM Andrei Borzenkov wrote:
>
> As far as I can tell, pacemaker simply does not support migration
> together with demote/promote actions. I don't really know the reasons.
Thinking about it - migrating a resource depending on a master is
simply not possible in the
On Fri, Apr 14, 2023 at 11:45 AM Philip Schiller
wrote:
>
> I would like to know if the order constraint Mandatory: ms-drbd_fs:promote drbd_vm>
> is equivalent to: "First promote ms-drbd_fs then start drbd_vm".
>
No, it is not. It is equivalent to
order drbd_vm_after_drbd_fs Mandatory:
Hello Andrei,
I'm sorry for the confusion. I will try to point everything out more specific.
*>>Andrei Borzenkov*
/>>Thu Apr 13 15:24:38 EDT 2023 /In this Message you tested the behavior of my thread.
OK, I compared CIB and the difference is that non-working case has
explicit "start" action
On Fri, Apr 14, 2023 at 10:25 AM Philip Schiller
wrote:
>
> Thank you very much Andrei,
> this completely solved my problem.
>
I am not sure I understand that (and as you do not quote the previous
posts you are replying to it is not even clear what you are talking
about).
> To point out, when
Thank you very much Andrei,
this completely solved my problem.
To point out, when I use the command:
pcs constraint order promote mas-drbd-jabber pri-vm-jabber
it sets the pri-vm action to start as default -> order
order-mas-drbd-jabber-pri-vm-jabber-mandatory mas-drbd-jabber:promote
On 13.04.2023 22:24, Andrei Borzenkov wrote:
...
order drbd_vm_after_drbd_fs Mandatory: ms-drbd_fs:promote drbd_vm:start
After I added it back I get the same failed "demote" action.
Transition Summary:
* Stop zfs_drbd_storage:0 (ha1 ) due to node
availability
*
On 12.04.2023 15:44, Philip Schiller wrote:
Here are also some Additional some additional information for a failover with
setting the node standby.
Apr 12 12:40:28 s1 pacemaker-controld[1611990]: notice: State transition S_IDLE
-> S_POLICY_ENGINE
Apr 12 12:40:28 s1
On clusterlabs.org i found this little detail:
https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Explained/epub/advanced-options.html
If an otherwise migratable resource depends on another resource via an
ordering constraint, there are special situations in which it will be
restarted rather
Here are also some Additional some additional information for a failover with
setting the node standby.
Apr 12 12:40:28 s1 pacemaker-controld[1611990]: notice: State transition S_IDLE
-> S_POLICY_ENGINE
Apr 12 12:40:28 s1 pacemaker-schedulerd[1611989]: notice: On loss of quorum:
Ignore
Apr
hank you for the reply.
I added the following line to crm configure:
colocation colo_pri-vm-alarmanlage-drbd-jabber_master inf:
pri-vm-jabber:Started mas-drbd-jabber:Master
This doesn't change anything though. Here some output of crm_mon:
Cluster Summary:
* Stack: corosync
* Current DC:
On Wed, 2023-04-12 at 14:04 +0300, Andrei Borzenkov wrote:
> On Wed, Apr 12, 2023 at 1:21 PM Vladislav Bogdanov ok.com> wrote:
> >
> > Hi,
> >
> > Just add a Master role for drbd resource in the colocation. Default
> > is Started (or Slave).
> >
>
> Could you elaborate why it is needed? The
On Wed, Apr 12, 2023 at 1:21 PM Vladislav Bogdanov wrote:
>
> Hi,
>
> Just add a Master role for drbd resource in the colocation. Default is
> Started (or Slave).
>
Could you elaborate why it is needed? The problem is not leaving the
resource on the node with a demoted instance - when the node
Hi,
Just add a Master role for drbd resource in the colocation. Default is
Started (or Slave).
Philip Schiller 12 апреля 2023 г. 11:28:57 написал:
Hi All, I am using a simple two-nodes cluster with Zvol -> DRBD -> Virsh in
primary/primary mode (necessary for live migration). My
Hi All,
I am using a simple two-nodes cluster with Zvol -> DRBD -> Virsh in
primary/primary mode (necessary for live migration). My configuration:
primitive pri-vm-alarmanlage VirtualDomain \
params
17 matches
Mail list logo
