@Impact Thanks for pointing that :)
In my defense:
while composing that previous post I searched for the detailed link in the first document and there was no ToC at all. Now I've had a closer look at that page and can see that this was due to...
Hello,
let's assume a 3 node cluster with ceph, node1/node2/node3 being let's say 10.0.0.1/2/3 respectively on external interfaces, and 10.10.10.1/2/3 on internal ones
(ceph+migration on 10.10.10.0/24, 'production' on 10.0.0.0/24).
let's...
Dear members of the Proxmox forum
I'm researching the possibilities of replication of a VM on a standalone Proxmox Virtual Environment Host to a 3 node PVE cluster with CEPH.
For legal reasons, we have to run a VM on a separate physical server...
The strangest thing is when virtualization on a proven Dell platform can't support a cutting-edge system like Proxmox—what’s the point of it all, then? Just a home PC and nothing more?
Oder halt einfach IPv6 verwenden.
Dann kann man auf der Destination sowas einstellen:
Allow all incoming traffic from StaticIPv6PVE to StaticIPv6PBS on Port 8007
Wobei OP von einem Hausanschluss und von 20TB VMs spricht.
Warum lässt du es...
Den Bugfix kann ich bestätigen. Seit Upgrade und Rückstellung der Settings in den Normalbetrieb seit ca. 12 h nun keine Probleme mehr.
Vielen Dank euch :-)
My opinion is that if you really want a properly running cluster with HA enabled, then SFF/USFF machines are mostly a dead end. Either find mini-towers so you can have dual 10GbE, a boot mirror and a some drives for Ceph, or forgo HA and just...
In fact the pve manual recommends not to have a qdevice if you have at least three nodes and an odd number of nodes due to the way corosync handles them:
Don't cluster them but use the DatacenterManager for migrating vms between the nodes and pve-zsnc for replicating via zfs. You will need to start them manually instead of HA though. Alternatively buy two USB-NICs to have a dedicated cluster...
You dont need a qdevice for a 3 node cluster; it will just serve as a 4th vote that doesnt have any consequence since its not a tiebreaker anyway.
The lessons here are well learned, namely:
1. your cluster is only as stable as its network design...
Hello
H730P
H730P is on HBA mode. I think no cache.
Forgive me, but I'm not very experienced: do you think the problem is the controller (I repeat, it's in HBA mode and I can see all the individual disks on the node) or the RAIDZ1?
Best regards
"all_system_memory - 1 GiB" - Wow! I didn't notice that one yet.
This shows how confident the developers are, that release/shrink memory of ARC does really work nowadays :)
Though... I would not bet my cluster on that assumption...
Reviving this because the root cause was never pinned down here, and it is a
one-liner: systemd-networkd.socket is left enabled, and it socket-activates the
service Proxmox deliberately disabled.
pve-container disables networkd in Debian...
Yes, I use the Luckfox Lyra Ultra E with POE.
It is an amazing device that runs 10-15° cooler than my Pi3B+ that I tried before.
It uses <1W idle with the Ubuntu community image supplied also in the official doc.
The Pi3B+ was drawing 3W idle...
Yes, I use the Luckfox Lyra Ultra E with POE.
It is an amazing device that runs 10-15° cooler than my Pi3B+ that I tried before.
It uses <1W idle with the Ubuntu community image supplied also in the official doc.
The Pi3B+ was drawing 3W idle...
Yes, I use the Luckfox Lyra Ultra E with POE.
It is an amazing device that runs 10-15° cooler than my Pi3B+ that I tried before.
It uses <1W idle with the Ubuntu community image supplied also in the official doc.
The Pi3B+ was drawing 3W idle...