[PVE-User] question regarding quorum/qdevice on raspberry pi for dual-node cluster
devzero at web.de
Thu Feb 20 15:20:48 CET 2020
why would we need a full corosync instance on RPI at all when it's not
supported and Qdevice is the better way for quorum ?
i.e. who is using full corosync on RPI at all and for what besides
i there a real purpose/benefit or does that wiki page simply describe
the "old way to go before qdevice did exist" ?
Am 20.02.20 um 14:56 schrieb Aaron Lauterer:
> That wiki page describes how to set up a full corosync instance on the
> Using one with Qdevice and the corosync-qnetd service installed on it
> is fine. See our documentation for it .
> I updated the warning on the Wiki page to make it clearer why that
> wiki page needs to be considered with care.
> On 2/20/20 1:40 PM, Roland @web.de wrote:
>> on this page https://pve.proxmox.com/wiki/Raspberry_Pi_as_third_node
>> there is told:
>> "Raspberry Pi as third node - This is only suited for testing or homelab
>> use. Never use it in a production environment! Simply use a QDevice!""
>> On https://pve.proxmox.com/wiki/Roadmap for Proxmox 5.4 there is the
>> following announcement:
>> QDevice support via `pvecm`
>> * primarily for small 2-node clusters adding a qdevice can help
>> mitigate the downside of not being able to reboot one node without
>> losing quorum (and thus the ability to make any changes in the
>> cluster) ** Can also help in clusters with a larger even number of
>> nodes by providing a tie-break vote.
>> * Integration into pvecm and PVE stack vastly simplifies adding a
>> qdevice (it was possible manually before as well)
>> my question is why there is information around which looks like
>> discouraging rasperry pi as third node for quorum, i.e. is a raspberry
>> pi with Qdevice (
>> ->https://blog.jenningsga.com/proxmox-keeping-quorum-with-qdevices/ )
>> suitable for production use or not ?
>> pve-user mailing list
>> pve-user at pve.proxmox.com
More information about the pve-user