Devel

devel@lists.kronosnet.org

1 participants
56 discussions

kronosnet v1.6 released
by Fabio M. Di Nitto 19 Dec '18

19 Dec '18

All, We are pleased to announce the general availability of kronosnet v1.6 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. Highlights in this release: * [IMPORTANT] Fix a PMTUd packet size issue when using crypto communications * Fix build with older versions of openssl * Fix a CPU spinning issue when iptables are set incorrectly * Fix a SCTP kernel <-> userland compatibility issue * Minor other fixes across the code and build infrastructure * libnozzle hits the first GA release. There are currently NO supported apps/users for this library but soon(´ish) corosync will add support for it. As this is the first release please be gentle :) Known issues in this release: * libnozzle needs better porting to FreeBSD (even tho it works as-is). 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/users https://lists.kronosnet.org/mailman/listinfo/devel https://lists.kronosnet.org/mailman/listinfo/commits Cheers, The knet developer team

1 0

kronosnet v1.5 released
by Fabio M. Di Nitto 22 Oct '18

22 Oct '18

All, We are pleased to announce the general availability of kronosnet v1.5 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. Highlights in this release: * [IMPORTANT] fix internal loopback link handling * Improved internal threads information for debugging purposes * Fix nss private key handling for odd key sizes * Minor improvements to the test suite * Minor improvements to the build system 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/users https://lists.kronosnet.org/mailman/listinfo/devel https://lists.kronosnet.org/mailman/listinfo/commits Cheers, The knet developer team

1 0

kronosnet v1.4 released
by Fabio M. Di Nitto 07 Aug '18

07 Aug '18

All, We are pleased to announce the general availability of kronosnet v1.4 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. Highlights in this release: * Major logging code cleanup * Reduced amount of locking around non-performance critical areas * Optimized threads startup and shutdown timers 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/users https://lists.kronosnet.org/mailman/listinfo/devel https://lists.kronosnet.org/mailman/listinfo/commits Cheers, The knet developer team

1 0

kronosnet v1.3 released
by Fabio M. Di Nitto 23 Apr '18

23 Apr '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 All, We are pleased to announce the general availability of kronosnet v1.3 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. Highlights in this release: * Fix potential crashes in the crypto code 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/users https://lists.kronosnet.org/mailman/listinfo/devel https://lists.kronosnet.org/mailman/listinfo/commits Cheers, The knet developer team -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJa3XEbAAoJEAgUGcMLQ3qJCBoP/3w58vloZ8ZumNLOTB2HDf4I UazCcASsdPxguqgg3kS7Dn9Rs7XmMkABDUTZk7cu96vBNn5Hx2v86m+UelDegQ3b PJ/hZU9nD7/LKS/xjiL53pZ0go35PxLMDz26GhnUlWhHHYfee96g1JQjPx0Wbb6v 6G/9iFmQAqWWToP/9pujE4FegAXXKckB7VVy/bfJlkNU/I7RSQo/cniJq5Sr+U95 I10YgnaraJkZVVV0LS4oGV006rV0D00+kSEluIflZF3/q7JQujnF8c3J9IltqQsp XtP8SmXJO7Qyg5UfkAoeYyzgVpJfd+FOb4nKG0NZFb6BH5G558L1wBWHsmzniMWr Ih7CVxg2gTKqCPgl+OLHcx856sR3YuNnU5el7xWaN5Q2otzYzpltprZhCFGbVBLO nWVhBtjB1v3kbIoBXcpK89q9CMDsAbIOlwBmeh4Y8oaiHjjHwj557rWM5C2X4g5A bVGSsBWNuR2ux3QFIva0m1BpDJ7qXkkuElTzfiF4d6Hwddqtn0LEeBa/i0KeIzJC YnLK4dDqID/PD3RnueJWLiLSTkO1t58vjWuGapYjUGICKuh7Eu4sb4/sBiPB8jkc e1OI+TVLOxZLB8fG2IKAcZpjCfsC/rPUDUaAHWN6rQIjFxhgN+POlVV86E9zv4Q5 ZBZ02v9eI3Y9CGeEAzV/ =aEP/ -----END PGP SIGNATURE-----

1 0

kronosnet v1.2 released
by Fabio M. Di Nitto 19 Apr '18

19 Apr '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 All, We are pleased to announce the general availability of kronosnet v1.2 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. Highlights in this release: * Fix a potential crash when using external destination handlers * Improve compression level validation by delegating the validation to the external compression library * Improve the build system to accommodate repeatable builds 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/users https://lists.kronosnet.org/mailman/listinfo/devel https://lists.kronosnet.org/mailman/listinfo/commits Cheers, The knet developer team -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJa2ArMAAoJEAgUGcMLQ3qJmZAP/2v8mn4sAsOHOJHnK88K0wym Zka8Tg/ptQFSFSxg82EDXyT47rnRkwVWg+t8sINfKRX3/kPvCZLcGikmjFMKsElt c8pWEs3GmHTEAWcp2I/fppQb2HBsDN6f+QIhwQwjhQidavj8s+Xk11qrY2zfjBXw H3in6X+Mo1BQ9iLfJpaQKT61ogD5/vSmiVq4Wi06vXv120wrA2Yc9nYJ6gtZy3oH Y+lm+E55zdaCcdvDnWqJrq+pjAJ73jpm7hZrbfPeIjO53VZeUoVe2C/5wxnt/6hB 1+oMne5/g6Sn4yjmw0PEVcNRnnBZNqmTvjVT5ELh+7b0Mfj5GmJFjP9VvUXcOoLG gkpG0aPwAXbpttIY15RsaRdFJ+oLSgWW2688TNqguTSHyQ4Q25Y7u1o7P6sRCACi +U7s+8wWqBYK9xWy+haHOhUcSeWzM3IpKGxkMvu29m8Bi0exu8WmHIyHgsymHlxX VNy8wtUZsSz3RsTRBnGHrJaMImhDYArYm70J6zrUUkesrm06uywQ4vd5t1z8+92z 8+COf8gXCTzsiTHG3XItkwMnT2GcoJxQ8hety+7ALwcmt0KathcEtzzxbA9nLede wgvaNiWxi/0/vJwLPDHeyHg8wh6OBCNwbtNZAMJRr7gVTGdWvVDYWYzNJ7rOMN1o RCY1NeZSKnzirsOQzdkv =fRTG -----END PGP SIGNATURE-----

1 0

Re: [kronosnet/kronosnet]
by Fabio M. Di Nitto 24 Mar '18

24 Mar '18

On 3/24/2018 5:45 AM, GitHub wrote: > Branch: refs/tags/v1.90 > Home: https://github.com/kronosnet/kronosnet It turns out that one of the side effects of tag-in-stable-branch, that we clearly didn´t notice before, is that the master branch was still building packages in the v1.0 series that are < than stable branch. I think the same problem would apply when releasing/tagging from master and later on forking the tree, we just need to remember to tag master after stable fork + one commit (perhaps that should be part of the release process). Now that knet is slowly making its way into distributions, we need the master branch rpms/builds to be on higher versions to avoid confusion for package managements, CI and testing. v1.90 is pretty much random, but lower enough to give us space in future to have 1.9x Beta/RC1/RCx.. before a 2.0 GA. Cheers Fabio

1 0

Re: stable1 backporting process
by wferi＠niif.hu 26 Feb '18

26 Feb '18

"Fabio M. Di Nitto" <fdinitto(a)redhat.com> writes: > 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. So, this sounds like the point of stable1-proposed is to have CI, but I can't see why stable1 couldn't be set up the same way. What do I miss? "Fabio M. Di Nitto" <notifications(a)github.com> also writes: > On 2/19/2018 10:43 AM, wferi wrote: > >> I don't really understand the master/stable1/stable1-proposed >> distinction at the moment, because I can't see anything on master >> which isn't 1.1 material, so we could pretty much release 1.1 >> straight from master. > > https://lists.kronosnet.org/pipermail/devel/2018-January/000049.html > > you are right, at the moment master and stable1-* haven´t diverged yet > but they will in future . It's getting an interesting question nearing the 1.1 release. Basically, why complicate history by pretending 1.1 is being developed in parallel with something else? Surely, there'll be a time when some breaking change (not suitable for 1.x) will have already been merged into master and still the need arises to cut a 1.x+1 release. Then we could branch off stable1 from master right before the breaking change and start doing parallel development when we're forced to. Till then, I'd find it perfectly fine to tag new minor releases on the master branch. Is that an oversimplification? -- Regards, Feri

2 3

kronosnet v1.1 released
by Fabio M. Di Nitto 25 Feb '18

25 Feb '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 All, We are pleased to announce the general availability of kronosnet v1.1 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. Highlights in this release: * Fix plugins loader by switching from RPATH to RUNPATH * Man pages are now automatically generated at build time * Better error reporting from crypto plugins * Fix and improve the whole build system * Add support for some older lz4 versions * Fix issue with UDP sockets that could cause knet to spin * Add new API call to run knet unprivileged Known issues in this release: * When configuring compression plugins, the compress_level checks are not always aligned with what the underlying library can really do. This has been discussed over the devel mailing list and will be fixed in libknet 1.2. Only compression advanced users might notice this problem. * Tarballs downloaded directly from github will fail to build (https://github.com/kronosnet/kronosnet/issues/133) please use the official release tarballs or git clone. 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/users https://lists.kronosnet.org/mailman/listinfo/devel https://lists.kronosnet.org/mailman/listinfo/commits Cheers, The knet developer team -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJakkMqAAoJEAgUGcMLQ3qJfEoQALFAOk+znEqv4ogrGeD22VeT OL0ihimnW+lW9RjTe04B0VFPonAKFPZ3NmQ9XngaX+XSyvm6NCujpz9LckPc30WZ MYwD5LJcmeHqHUNfmLTX0wuvkoairiKQNtak26e+6Bt7wfTZ8fzKF3eFKrfJQ8w7 AvBOL8WVzR4v6Jc21/X2IZN1Bn7y2mIJTfnDPwNxFxNi6mfOLkA+OAc9ivjQZADe XPl0sqzBaaRxg9DrI4XgQxkV1sdwQ6elpL/jd+jKiQ8CfX8zOr6FX7SXTpnbwbmS 2OMzWPCXYxSiJUKWGpJtzn9QkHNrTpDiP3mDQ6KCEEt3o/XXSfkFI/bTuvTtuc/n R+ki/KhT2FqU/ZmgDmFQmHn1r7r70c/8i8i2GC1+FVYN63rGlofCroY3KZjvFewY sYLQKXm4zCvR5BZnonpTz2Mf/ISTNzCuaDwxIJKXAO+ksuot8uU54uBiYf4mR/Uu FuSSaNmiLHYqmEjVHF7V8c7gA4az7gYSV77oNP/y6bECxSrVA0NmXAraYzoIwG01 WsPEobZ4UXRYWggTu16G+xP8EpUiyxDtaJsTy/Kgp5qMqY1aRr5s4u7A6k3/M+HH ZdFtr5V2dGlR8cqYbkVt4Uayw2UgAULTeNsTGTPgNl5woboKAkomTkWUnh2pAbey wbPF6bQBtMDasmaPideX =zqHY -----END PGP SIGNATURE-----

1 0

Last call for PR before 1.1 release
by Fabio M. Di Nitto 23 Feb '18

23 Feb '18

All, as subject, I think 1.1 is ready to ship. I am planning to cut a release over the weekend unless anybody has any pending work that needs to merge right away. Cheers Fabio

3 8

compression plugin compress level validation
by Fabio M. Di Nitto 14 Feb '18

14 Feb '18

Hey guys, original discussion started here (for reference): https://github.com/kronosnet/kronosnet/pull/128 int knet_handle_compress(knet_handle_t knet_h, struct knet_handle_compress_cfg *knet_handle_compress_cfg); Where knet_handle_compress_cfg contains int compress_level. As you can see from libknet.h and relative code, we try (too hard) to validate the values for compress_level. Feri had a proper concern about applying incorrect filtering and I agree that it is already becoming complex to maintain a matrix of valid values, per plugin, per plugin-version, and whatever combination. AFAIR all plugins accept an int value for compress_level so from that perspective it shouldn´t be too much of a problem (aka no API/ABI changes). Historically, the reason why I added the validation was lzo2, that presents a rather unusual compress configuration vs all other plugins (as you can see). I think Feri´s suggestion to drop the filter completely might be too much, instead, after thinking a bit, it might be perfectly reason to change the internals of val_level to try and compress a small buffer to test that the value is good. The val_level is used only at configuration time, so it´s not too expensive to compress one small data chunk for validation and it would remove the whole hardcoded filter of different compress_levels. For special plugins like lzo2, I think it´s important we improve the logging at configuration time to make sure users at least warned of supported values (as you can see each values map to a specific lzo2 API call to compress). wdyt? Fabio

3 4

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Devel