From: Alex K <rightkicktech@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Proxmox Fencing
Date: Mon, 5 Jul 2021 15:32:48 +0300 [thread overview]
Message-ID: <CABMULtLwXN+z=QMzGO895S1UVv-LvZVt+V-B7pM7d=q55APR_A@mail.gmail.com> (raw)
In-Reply-To: <mailman.220.1625486801.464.pve-user@lists.proxmox.com>
On Mon, Jul 5, 2021 at 3:06 PM Eneko Lacunza via pve-user <
pve-user@lists.proxmox.com> wrote:
>
>
>
> ---------- Forwarded message ----------
> From: Eneko Lacunza <elacunza@binovo.es>
> To: pve-user@lists.proxmox.com
> Cc:
> Bcc:
> Date: Mon, 5 Jul 2021 14:06:31 +0200
> Subject: Re: [PVE-User] Proxmox Fencing
> Hi Alex,
>
> >> El 5/7/21 a las 13:18, Alex K escribió:
> >>> Hi all,
> >>>
> >>> I'm new to proxmox and trying to setup a 2 + 1 node active/active HA
> >>> cluster on top glusterfs using latest community
> >> pve-manager/6.4-4/337d6701
> >>> (running kernel: 5.4.106-1-pve). The third node is used for gluster
> >>> arbitration and perhaps I have to configure in it a quorum disk also to
> >>> keep quorum in case of a node failure (not clear yet at my mind, still
> >>> reading the docs).
> >> If you have 3 nodes, you want all them in Proxmox cluster for proper
> >> quorum majority. No need for quorum disk that way. (note that I don't
> >> know how gluster works).
> >>
> > Gluser has a similar concept for quorum so as to keep writes on the
> > storage. Hence I am placing a third node in the setup. Due to cost
> > limitations, the third node has minimal specs and is not meant to host
> VMs.
> > It is a mini-PC thats why I did not add it as a proxmox host. I am
> > wondering if it is possible to add it as a proxmox host and put a
> > constraint to avoid VMs migrating into it. In this way I will achieve the
> > required quorum levels without adding a full spec host.
>
> Yes, you can create node-groups in HA groups, and add the desired nodes
> to the group. Then when adding a VM/CT to HA, configure the group there
> too.
>
I see. Thanx for the pointer.
>> I am stuck at the moment at the fencing part of the setup. Reading
> through
> >>> the docs it seems that I have only the option to setup hardware
> watchdog
> >>> fencing. I would expect to be able to use external media such as IPMI,
> >>> iDrac, HP iLO or UPS based power management (APC) though I can't find
> any
> >>> info how these are configured at current version of Proxmox.
> >> Currently by default Proxmox uses a software watchdog. I'm not sure if
> >> hardware watchdog support was introduced, others may help with this.
> >>
> > According to the docs it seems there is hardware watchdog option:
> > https://pve.proxmox.com/pve-docs/chapter-ha-manager.html
> > Q+++
> > hardware watchdog - if not available we fall back to the linux kernel
> > software watchdog (softdog)
> > +++Q
> Never used that, sorry.
> >>> In case of a network partition and not a node hardware issue, how is
> the
> >>> watchdog going to behave? Is a healthy but disconnected node going to
> be
> >>> power cycled? I will soon proceed with testing as soon as I manage to
> >> setup
> >>> fencing though I wanted to better understand this part of fencing.
> >> The node that drops out of quorum will be rebooted. If there where
> >> CM/CTs configured for HA in that node, Proxmox will attempt to restart
> >> them in another node.
> >>
> > So soft-fencing is done from ha-manager? How are the other nodes notified
> > that the rebooted host is indeed rebooted so as to start the HA VMs?
> There is a time delay that allows the fended node time to reboot before
> other nodes take over the HA VMs. It's like 1-2 minutes. The fenced node
> (the one out of the quorum) will reboot in max 60s.
>
OK. I understand that there is a locking mechanism which takes place and
determines the node states.
> Cheers
>
> Eneko Lacunza
> Zuzendari teknikoa | Director técnico
> Binovo IT Human Project
>
> Tel. +34 943 569 206 | https://www.binovo.es
> Astigarragako Bidea, 2 - 2º izda. Oficina 10-11, 20180 Oiartzun
>
> https://www.youtube.com/user/CANALBINOVO
> https://www.linkedin.com/company/37269706/
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Eneko Lacunza via pve-user <pve-user@lists.proxmox.com>
> To: pve-user@lists.proxmox.com
> Cc: Eneko Lacunza <elacunza@binovo.es>
> Bcc:
> Date: Mon, 5 Jul 2021 14:06:31 +0200
> Subject: Re: [PVE-User] Proxmox Fencing
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
prev parent reply other threads:[~2021-07-05 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 11:18 Alex K
[not found] ` <mailman.217.1625484651.464.pve-user@lists.proxmox.com>
2021-07-05 11:49 ` Alex K
[not found] ` <mailman.220.1625486801.464.pve-user@lists.proxmox.com>
2021-07-05 12:32 ` Alex K [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABMULtLwXN+z=QMzGO895S1UVv-LvZVt+V-B7pM7d=q55APR_A@mail.gmail.com' \
--to=rightkicktech@gmail.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox