Page MenuHomeVyOS Platform

New cluster implementation with corosync+pacemaker
Closed, WontfixPublicFEATURE REQUEST

Description

Since heartbeat not supported and abandoned, if we are to implement general resource clustering, we should likely use corosync+pacemaker

Details

Difficulty level
Unknown (require assessment)
Version
-
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Perfectly compatible
Issue type
Feature (new functionality)

Event Timeline

syncer triaged this task as Normal priority.Nov 9 2018, 2:06 PM
syncer renamed this task from Migrated clustering from heartbeat to to Migrated clustering from heartbeat to corosync+pacemaker.Nov 14 2018, 1:20 PM
erkin set Is it a breaking change? to Unspecified (possibly destroys the router).Sep 1 2021, 10:49 AM
erkin set Issue type to Improvement (missing useful functionality).

Not sure if we can migrate all old cluster CLI syntax, but create a new I think we can
Something like:

set cluster corosync name xxx
set cluster corosync resource ip|systemd x.x.x.x
set cluster corosync two-node enable|disable (default enable)
set cluster corosync transport udpu|knet
set cluster corosync node node01 address|name x.x.x.x|node01.local
set cluster corosync node node01 node-id 1
set cluster corosync node node02 adderss|name x.x.x.x|node02.local
set cluster corosync node node02 node-id 2

Or without node "corosync", this is to distinguish from the old syntax

dmbaturin renamed this task from Migrated clustering from heartbeat to corosync+pacemaker to New cluster implementation with corosync+pacemaker.Jan 8 2024, 7:20 PM
dmbaturin lowered the priority of this task from Normal to Wishlist.
dmbaturin updated the task description. (Show Details)
dmbaturin edited projects, added VyOS 1.5 Circinus; removed VyOS 1.4 Sagitta.
dmbaturin changed Is it a breaking change? from Unspecified (possibly destroys the router) to Perfectly compatible.
dmbaturin changed Issue type from Improvement (missing useful functionality) to Feature (new functionality).
Viacheslav claimed this task.

We are not going to do it these days.
There are no reasons to use claster after migration to VRRP.
The cluster was deprecated and deleted. Reopen if it is still relevant.