Since heartbeat not supported and abandoned, if we are to implement general resource clustering, we should likely use corosync+pacemaker
Description
Description
Details
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)
Related Objects
Related Objects
Event Timeline
Comment Actions
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
Comment Actions
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.