All,
We are pleased to announce the general availability of kronosnet v1.21
kronosnet (or knet for short) is the new underlying network protocol for
Linux HA components (corosync), that features the ability to use
multiple links between nodes, active/active and active/passive link
failover policies, automatic link recovery, FIPS compliant encryption
(nss and/or openssl), automatic PMTUd and in general better performance
compared to the old network protocol.
Highlights in this release:
* Update to openssl 3.0alpha13
* Drop -rpath usage from libknet
* Various libnozzle fixes
* API: validate handles for public api calls to avoid crashes
* Update FreeBSD documentation section
* Test suite improvements to speed up testing
Known issues in this release:
* None
The source tarballs can be downloaded here:
https://www.kronosnet.org/releases/
Upstream resources and contacts:
https://kronosnet.org/https://github.com/kronosnet/kronosnet/https://ci.kronosnet.org/https://trello.com/kronosnet (TODO list and activities tracking)
https://goo.gl/9ZvkLS (google shared drive with presentations and diagrams)
IRC: #kronosnet on Freenode
https://lists.kronosnet.org/mailman/listinfo/usershttps://lists.kronosnet.org/mailman/listinfo/develhttps://lists.kronosnet.org/mailman/listinfo/commits
Cheers,
The knet developer team
Hi folks,
Thank you for your time and patience.
Can anybody help us to find an alternative for "pcs property set" when using the old pcs and the new corosync and pacemaker packages as is written in subject?
Unfortunately I don't see on Jenkins an updated version for pcs for RHEL 7.7/7.9 just for RHEL 8.
We are in the middle of a high pressure because some problems with RHEL HA Cluster/Corosync+Pacemaker/DRBD and we arrived at the point that we upgraded corosync and pacemaker but then our setup gives errors with the command
"pcs property set no-quorum-policy=stop".
The error is:
No such file or directory', 'command': '/usr/libexec/pacemaker/pengine metadata'
Indeed /usr/libexec/pacemaker/pengine does not exists, I assume it is OK, because in the new pacemaker 3.1 the internal structure was changed..
However, can you give me an alternative to set that property in this combination of software?
Thank you!
_______________________________________________________
Szabolcs-Gavril Rugina
Development Information Technologies 1 / Software Engineer
FREQUENTIS ROMÂNIA SRL
Str. Taietura Turcului, Nr. 47,
400221, Cluj-Napoca, Romania
Phone +43-1-81150-7511
Mobile +40-771-483274
Web http://www.frequentis.ro
E-Mail szabolcs.rugina(a)frequentis.com<mailto:szabolcs.rugina@frequentis.com>
Nr. O.R.C./an: J12/957/2009
CUI: RO 25475641
_______________________________________________________
All,
kronosnet (or knet for short) is the new underlying network protocol for
Linux HA components (corosync), that features the ability to use
multiple links between nodes, active/active and active/passive link
failover policies, automatic link recovery, FIPS compliant encryption
(nss and/or openssl), automatic PMTUd and in general better performance
compared to the old network protocol.
After several weeks / months without any major bug reported, starting
with v1.19 release, we are going to lock down the 1.x series to only 2
kind of changes:
* Bug fixes
* Onwire compatibility changes to allow rolling upgrades with the v2.x
series (if necessary at all)
Upstream will continue to support v1.x for at least 12 months after v2.x
will be released (date unknown, no really, we didn't even start the
development).
If you have any amazing ideas on what v2.x should include, please file
issues here:
https://github.com/kronosnet/kronosnet/issues
Or check the current TODO list here:
https://trello.com/kronosnet
Cheers,
The knet developer team
All,
We are pleased to announce the general availability of kronosnet v1.19
kronosnet (or knet for short) is the new underlying network protocol for
Linux HA components (corosync), that features the ability to use
multiple links between nodes, active/active and active/passive link
failover policies, automatic link recovery, FIPS compliant encryption
(nss and/or openssl), automatic PMTUd and in general better performance
compared to the old network protocol.
Highlights in this release:
* Add native support for openssl 3.0 (drop API COMPAT macros).
* Code cleanup of public APIs. Lots of lines of code moved around, no
functional changes.
* Removed kronosnetd unsupported code completely
* Removed unused poc-code from the source tree
* Make sure to initialize epoll events structures
Known issues in this release:
* None
The source tarballs can be downloaded here:
https://www.kronosnet.org/releases/
Upstream resources and contacts:
https://kronosnet.org/https://github.com/kronosnet/kronosnet/https://ci.kronosnet.org/https://trello.com/kronosnet (TODO list and activities tracking)
https://goo.gl/9ZvkLS (google shared drive with presentations and diagrams)
IRC: #kronosnet on Freenode
https://lists.kronosnet.org/mailman/listinfo/usershttps://lists.kronosnet.org/mailman/listinfo/develhttps://lists.kronosnet.org/mailman/listinfo/commits
Cheers,
The knet developer team
All,
We are pleased to announce the general availability of kronosnet v1.17
kronosnet (or knet for short) is the new underlying network protocol for
Linux HA components (corosync), that features the ability to use
multiple links between nodes, active/active and active/passive link
failover policies, automatic link recovery, FIPS compliant encryption
(nss and/or openssl), automatic PMTUd and in general better performance
compared to the old network protocol.
Highlights in this release:
* Add ability to change crypto configuration at runtime without
restarting knet and without packet drop
* Add compatibility support for openssl 3.0
* Add functional testing framework and new test cases
* Minor build fixes
NOTE TO PACKAGERS: please be aware that the functional test suite adds a
considerable amount of time to run via make check or make
check-memcheck. This is expected, and it will increase further more as
more tests will be added.
Known issues in this release:
* None
The source tarballs can be downloaded here:
https://www.kronosnet.org/releases/
Upstream resources and contacts:
https://kronosnet.org/https://github.com/kronosnet/kronosnet/https://ci.kronosnet.org/https://trello.com/kronosnet (TODO list and activities tracking)
https://goo.gl/9ZvkLS (google shared drive with presentations and diagrams)
IRC: #kronosnet on Freenode
https://lists.kronosnet.org/mailman/listinfo/usershttps://lists.kronosnet.org/mailman/listinfo/develhttps://lists.kronosnet.org/mailman/listinfo/commits
Cheers,
The knet developer team
All,
We are pleased to announce the general availability of kronosnet v1.14
kronosnet (or knet for short) is the new underlying network protocol for
Linux HA components (corosync), that features the ability to use
multiple links between nodes, active/active and active/passive link
failover policies, automatic link recovery, FIPS compliant encryption
(nss and/or openssl), automatic PMTUd and in general better performance
compared to the old network protocol.
Highlights in this release:
* [MAJOR] different fixes in managing UDP sockets due to recent kernel
changes.
* [MAJOR] SCTP partial rewrite to make it work with newer kernels and
FreeBSD. FreeBSD users please read the updated README for new sysctl.
The development team will be working to evaluate if it's possible to
avoid this new sysctl.
* Fix internal and external latency calculator to avoid underflows,
incorrect values and be consistent.
* Fix code to deal with mixed (UDP and SCTP) environments.
* Fix common transport code to avoid spinning on EOF messages.
* Minor build fixes (support gcc10, openssl, etc).
Known issues in this release:
* FreeBSD users with SCTP configured should add a new sysctl (see README)
The source tarballs can be downloaded here:
https://www.kronosnet.org/releases/
Upstream resources and contacts:
https://kronosnet.org/https://github.com/kronosnet/kronosnet/https://ci.kronosnet.org/https://trello.com/kronosnet (TODO list and activities tracking)
https://goo.gl/9ZvkLS (google shared drive with presentations and diagrams)
IRC: #kronosnet on Freenode
https://lists.kronosnet.org/mailman/listinfo/usershttps://lists.kronosnet.org/mailman/listinfo/develhttps://lists.kronosnet.org/mailman/listinfo/commits
Cheers,
The knet developer team