That wiki page describes how to set up a full corosync instance on the RPI.
Using one with Qdevice and the corosync-qnetd service installed on it is fine. See our documentation for it [0].
I updated the warning on the Wiki page to make it clearer why that wiki page needs to be considered with care.
[0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_corosync_external_vote_support
On 2/20/20 1:40 PM, Roland @web.de wrote:
hello, 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 ? regards roland _______________________________________________ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
