>
> But that contradicts what is written in [4], quote: "Storage communication
> should never be on the same network as corosync!". I
> understand your motivation to do it the way you did but there has to be
> another way (if what the Wiki tells is true).
>
Sure, but that's the only way I
Hi Kevin,
thanks for explaining your setup. Comments below.
Am 06.02.2017 um 12:57 schrieb Kevin Lemonnier:
>> * How does fencing work in Proxmox (technically)?
>> Due to fencing being based on watchdogs I assume that some piece of
>> software
>> regularly resets the watchdog's clock so
> * How does fencing work in Proxmox (technically)?
> Due to fencing being based on watchdogs I assume that some piece of software
> regularly resets the watchdog's clock so that the node isn't rebooted
> automatically
> by the watchdog. Is this correct? Which software is responsible?
I
Hi,
But this setup is exactly what I'd want to avoid. Imagine you have a VM running
on Node A that needs VLAN 7. With this kind of
setup Proxmox could migrate the VM to Node B or C in case of failure of node A.
But if the VM is put on Node C the VM has no
connectivity to VLAN 7 which is
Hi Alwin,
thanks for your suggestion. Comments below.
Am 04.02.2017 um 12:04 schrieb Alwin Antreich:
[…]
>>
>> What kind of network setup would you recommend?
>
> We also use multiple VLANs on our network. As linux bridges are
> VLAN-aware (bridge-vlan-aware yes), we set the VLAN in the VM
Dear all,
I'm a bit confused by the Wiki pages regarding high availability [1] & [2].
I would appreciate if my questions could be answered. (Searched the mailing list
archive but didn't find threads regarding HA that are new enough to cover v4.x)
* When does a Proxmox cluster become a HA
