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

PR https://github.com/vyos/vyatta-config-mgmt/pull/7

Still with issues, VyOS 1.4-rolling-202112090318:

vyos@r11-roll# set system config-management commit-archive location sftp://foo:foo@192.168.122.14/
[edit]
vyos@r11-roll# commit
Archiving config...
  sftp://192.168.122.14/ Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python3/dist-packages/vyos/remote.py", line 312, in upload
    urlc(urlstring, *args, **kwargs).upload(local_path)
  File "/usr/lib/python3/dist-packages/vyos/remote.py", line 202, in upload
    with self._establish() as ssh, ssh.open_sftp() as sftp:
  File "/usr/lib/python3/dist-packages/vyos/remote.py", line 189, in _establish
    sock = socket.create_connection((self.hostname, self.port), socket.getdefaulttimeout(), self.source)
  File "/usr/lib/python3.9/socket.py", line 830, in create_connection
    sock.bind(source_address)
TypeError: str, bytes or bytearray expected, not NoneType
[edit]
vyos@r11-roll# 
[edit]

But save is working:

vyos@r11-roll# save sftp://foo:foo@192.168.122.14/
Saving configuration to 'sftp://foo:foo@192.168.122.14/'...
Done
[edit]
vyos@r11-roll#

Accel-PPP uses total number of CPUs / 2 for the number of internal threads. I personally like to have as less CLI commands as possible.

@m.korobeinikov please close if the current solution works for you!

I've checked it and what we have:

@Viacheslav Right, if I will write server-bridge, then OpenVPN will write to log error about "cannot be used together"

@m.korobeinikov - I did not test the backup and fault, but what you said sums it up correctly. Let me know if you need anything on exact re-creation, etc..

Looks like the issue is persistent.
Tested on VyOS 1.3-beta-202112080938
Reboot VyOS (first one, wait for it to load. Then the other one)
'transition-script master' script doesn't start

As I understand it, after the reboot, the following scenarios are running:

Utility function added; it remnains to move 'vyos-config-status' to /run.

@hexes Do I understand correctly that when you set this option you get logs "Options error"?
openvpn-option "--server-bridge 10.1.4.1 255.255.255.0 10.1.4.240 10.1.4.250"

Anyone?

Hey - Thanks for the fix works great. One more thing I noticed, I'm not sure if it's an edge case or considered a "bug".

"VyOS 1.4-rolling-202112081536" : sync-group scripts work well after rebooting.

I've checked this bug on "VyOS 1.3-beta-202112080938", everything is well.
After rebooting scripts(sync-groups) work as needed.

+1

Logic has been changed in keepalived-fifo.py to read in the CLI data (and thus the scripts) the first time they are really needed by a transition.

The displayed error:

Thank you for sharing your information.

For anyone looking for a work around until it is patched this is my workaround. I am just adding a line to restart the service right after bootup in the “/config/scripts/vyos-postconfig-bootup.script” (more info on this file in the command scripting section - Command Scripting — VyOS 1.4.x (sagitta) documentation)

I confirm the bug. After rebooting script doesn't work on sync-groups. It's necessary to reload vrrp to start running the script (After rebooting).
More detail:
https://phabricator.vyos.net/T4041

There is a task with VRRP scripts problem on reboot:

I tested this bug on "vyos-1.3-beta-202112060443".

PR https://github.com/vyos/vyos-1x/pull/1100

BGP/OSPF bfd profile support will be implemented in T4058