experimenting a bit here. As you build PR for master, please do NOT
create a new PR for stable1. Indicate if the commit qualifies for
stable1 and if we all agree it should be backported, you can or we will
cherry-pick the fix in stable1-proposed branched.
there is a PR open to merge stable1-proposed that will keep running CI
on each cherry-pick backport for now, and we feel the time is ready to
cut 1.1, we will just merge that PR at once.
We are pleased to announce the general availability of kronosnet v1.0
kronosnet (or knet for short) is the new underlying network protocol
for Linux HA components (corosync), that features 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
performances compared to the old network protocol.
The source tarballs can be downloaded here:
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
IRC: #kronosnet on Freenode
Known issues in this release:
* Knet will fail to work on Fedora 26 arm when built with clang. This is
a known issue with clang compiler that is fixed in more recent
versions of clang.
* Knet will fail to build with clang on rhel7 + epel version of clang.
This is a known issue with clang compiler that is fixed in more recent
versions of clang.
* Running the knet test suite with valgrind (make check-memcheck) will
fail with Debian Experimental glibc due to a known bug in valgrind.
* Running the knet test suite with valgrind on FreeBSD is no longer
supported. The valgrind version on FreeBSD is too old and generates
too many false positives. Also, please refer to build-aux/check.mk on
how to use valgrind in combination with knet. Some platforms requires
extra options to work properly.
* If you are planning to develop plugins, please be aware of this issue:
https://github.com/kronosnet/kronosnet/issues/107 . It affects only
The knet developer team