[ClusterLabs] kronosnet v1.29 released
All, We are pleased to announce the general availability of kronosnet v1.29 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: * Fix build on armhf * update to latest doxyxml from libqb * Fix FORTIFY source detection * Fix potential overflow in the test suite 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://projects.clusterlabs.org/project/board/86/ (TODO list and activities tracking) https://goo.gl/9ZvkLS (google shared drive with presentations and diagrams) IRC: #kronosnet on Libera https://lists.kronosnet.org/mailman3/postorius/lists/users.lists.kronosnet.org/ https://lists.kronosnet.org/mailman3/postorius/lists/devel.lists.kronosnet.org/ https://lists.kronosnet.org/mailman3/postorius/lists/commits.lists.kronosnet.org/ Cheers, The knet developer team ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.28 released
All, We are pleased to announce the general availability of kronosnet v1.28 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: * Fix build on i686 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://projects.clusterlabs.org/project/board/86/ (TODO list and activities tracking) https://goo.gl/9ZvkLS (google shared drive with presentations and diagrams) IRC: #kronosnet on Libera https://lists.kronosnet.org/mailman3/postorius/lists/users.lists.kronosnet.org/ https://lists.kronosnet.org/mailman3/postorius/lists/devel.lists.kronosnet.org/ https://lists.kronosnet.org/mailman3/postorius/lists/commits.lists.kronosnet.org/ Cheers, The knet developer team ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] [ClusterLabs Developers] kronosnet v1.27 released
This release unfortunately fails to build on i686. I am prepping 1.28 with just the build fix. If you are in a hurry you can grab it here: https://github.com/kronosnet/kronosnet/pull/417/files Cheers Fabio On 26/09/2023 14.43, Fabio M. Di Nitto wrote: All, We are pleased to announce the general availability of kronosnet v1.27 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: * Fix potential startup race condition (corosync use case) * Fix crypto config check * Minor API cleanup * Test suite fixes 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://projects.clusterlabs.org/project/board/86/ (TODO list and activities tracking) https://goo.gl/9ZvkLS (google shared drive with presentations and diagrams) IRC: #kronosnet on Libera https://lists.kronosnet.org/mailman3/postorius/lists/users.lists.kronosnet.org/ https://lists.kronosnet.org/mailman3/postorius/lists/devel.lists.kronosnet.org/ https://lists.kronosnet.org/mailman3/postorius/lists/commits.lists.kronosnet.org/ Cheers, The knet developer team ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/developers ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.27 released
All, We are pleased to announce the general availability of kronosnet v1.27 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: * Fix potential startup race condition (corosync use case) * Fix crypto config check * Minor API cleanup * Test suite fixes 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://projects.clusterlabs.org/project/board/86/ (TODO list and activities tracking) https://goo.gl/9ZvkLS (google shared drive with presentations and diagrams) IRC: #kronosnet on Libera https://lists.kronosnet.org/mailman3/postorius/lists/users.lists.kronosnet.org/ https://lists.kronosnet.org/mailman3/postorius/lists/devel.lists.kronosnet.org/ https://lists.kronosnet.org/mailman3/postorius/lists/commits.lists.kronosnet.org/ Cheers, The knet developer team ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.26 released
All, We are pleased to announce the general availability of kronosnet v1.26 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: * Tx performance improvements by removing unnecessary and expensive memsets * Add log TRACE facility and drop build time logging configuration * Specfile: migrate to SPDX licence format * Fix few minor build issues with the test suite 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://projects.clusterlabs.org/project/board/86/ (TODO list and activities tracking) https://goo.gl/9ZvkLS (google shared drive with presentations and diagrams) IRC: #kronosnet on Libera https://lists.kronosnet.org/mailman3/postorius/lists/users.lists.kronosnet.org/ https://lists.kronosnet.org/mailman3/postorius/lists/devel.lists.kronosnet.org/ https://lists.kronosnet.org/mailman3/postorius/lists/commits.lists.kronosnet.org/ Cheers, The knet developer team ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.25 released
All, We are pleased to announce the general availability of kronosnet v1.25 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: * Fix an important PMTUd issue when node joins a cluster in the presence of a network device that is black-holing packets * Fix handling of PMTUd packets when firewalls are misconfigured on TX * Fix build with gcc-12 * Update doxyxml from libqb * Minor spec, docs, build and typos fixes 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://projects.clusterlabs.org/project/board/86/ (TODO list and activities tracking) https://goo.gl/9ZvkLS (google shared drive with presentations and diagrams) IRC: #kronosnet on Libera https://lists.kronosnet.org/mailman3/postorius/lists/users.lists.kronosnet.org/ https://lists.kronosnet.org/mailman3/postorius/lists/devel.lists.kronosnet.org/ https://lists.kronosnet.org/mailman3/postorius/lists/commits.lists.kronosnet.org/ Cheers, The knet developer team ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] FYI: clusterlabs.org server maintenance window this weekend
Maintenance is completed now. Please let us know if you encounter any issue. Thanks Fabio On 01/11/2022 19.03, Ken Gaillot wrote: Hi everybody, Just FYI, the clusterlabs.org server (including the websites and mailing lists) will be taken down for planned maintenance this weekend. Most likely it will just be a few hours on Saturday, but if there are complications it could be longer. ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Antw: [EXT] Re: Q: About a false negative of storage_mon
On 02/08/2022 14.37, Ulrich Windl wrote: "Fabio M. Di Nitto" schrieb am 02.08.2022 um 14:30 in Nachricht <0b26c097-1e21-3945-24ba-355cd0ccf...@fabbione.net>: Hello Kazunori-san, On 02/08/2022 12.13, 井上和徳 wrote: Hi, Since O_DIRECT is not specified in open() [1], it reads the buffer cache and may result in a false negative. I fear that this possibility increases in environments with large buffer cache and running disk-reading applications such as database. So, I think it's better to specify O_RDONLY|O_DIRECT, but what about it? (in this case, lseek() processing is unnecessary.) I will have to defer to Christine (in CC) to this email on why we didn´t use O_DIRECT. I have a vague recollection that some storage devices didn´t like the O_DIRECT option causing other issues later, but it´s been a while since I touched the code. The thing with O_DIRECT is that a "software block" has to be a multiple of a "hardware block"; i.e: you cannot read a partial block, and the buffer has some alignment requirements. that was it! thanks for refreshing my memory. Fabio # I am ready to create a patch that works with O_DIRECT. Also, I wouldn't mind # a "change to add a new mode of inspection with O_DIRECT # (add a option to storage_mon) while keeping the current inspection process". [1] https://github.com/ClusterLabs/resource-agents/blob/main/tools/storage_mon.c# L47-L90 It might be a very reasonable solution, tho let´s wait for an answer from Chrissie. Cheers Fabio ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Q: About a false negative of storage_mon
Hello Kazunori-san, On 02/08/2022 12.13, 井上和徳 wrote: Hi, Since O_DIRECT is not specified in open() [1], it reads the buffer cache and may result in a false negative. I fear that this possibility increases in environments with large buffer cache and running disk-reading applications such as database. So, I think it's better to specify O_RDONLY|O_DIRECT, but what about it? (in this case, lseek() processing is unnecessary.) I will have to defer to Christine (in CC) to this email on why we didn´t use O_DIRECT. I have a vague recollection that some storage devices didn´t like the O_DIRECT option causing other issues later, but it´s been a while since I touched the code. # I am ready to create a patch that works with O_DIRECT. Also, I wouldn't mind # a "change to add a new mode of inspection with O_DIRECT # (add a option to storage_mon) while keeping the current inspection process". [1] https://github.com/ClusterLabs/resource-agents/blob/main/tools/storage_mon.c#L47-L90 It might be a very reasonable solution, tho let´s wait for an answer from Chrissie. Cheers Fabio ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.24 released
All, We are pleased to announce the general availability of kronosnet v1.24 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: * Fix UDP transport to deal with host unreachable ICMP errors * Fix potential memory corruption in TX thread * Minor build and typos fixes * Rewrite of the test suite to a new set of test macros * Doc: update URLs and move TODO list from trello to https://projects.clusterlabs.org 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://projects.clusterlabs.org/project/board/86/ (TODO list and activities tracking) https://goo.gl/9ZvkLS (google shared drive with presentations and diagrams) IRC: #kronosnet on Libera https://lists.kronosnet.org/mailman3/postorius/lists/users.lists.kronosnet.org/ https://lists.kronosnet.org/mailman3/postorius/lists/devel.lists.kronosnet.org/ https://lists.kronosnet.org/mailman3/postorius/lists/commits.lists.kronosnet.org/ Cheers, The knet developer team ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] [IMPORTANT] CI update
All, CI should be fully functional as of now. If you spot any issue, please let me know as soon as possible. Cheers Fabio On 27/12/2021 15.32, Fabio M. Di Nitto wrote: All, the following repositories default branch have been updated from master to main: https://github.com/kronosnet/kronosnet https://github.com/kronosnet/knet-ansible-ci https://github.com/kronosnet/ci-tools https://github.com/corosync/corosync https://github.com/corosync/corosync-qdevice https://github.com/ClusterLabs/high-laughability https://github.com/ClusterLabs/booth https://github.com/ClusterLabs/anvil https://github.com/ClusterLabs/fence-agents https://github.com/ClusterLabs/pcs https://github.com/ClusterLabs/sbd https://github.com/ClusterLabs/pcs-web-ui https://github.com/ClusterLabs/resource-agents https://github.com/ClusterLabs/pacemaker https://github.com/ClusterLabs/libqb https://github.com/ClusterLabs/anvil-external-deps I have spotted a few GitHub PRs that have been automatically closed by the rename: https://github.com/ClusterLabs/resource-agents/pull/1378 https://github.com/ClusterLabs/fence-agents/pull/244 but there might be more for which I have received no notifications. I can´t re-open those PRs automatically, so please ask the submitter to refresh their tree and propose the PR again. CI is currently in the process of being updated to deal with master->main. Please expect failures for now. An update will follow when CI is back online 100%. Fabio ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/developers ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] [IMPORTANT] Repositories update
All, the following repositories default branch have been updated from master to main: https://github.com/kronosnet/kronosnet https://github.com/kronosnet/knet-ansible-ci https://github.com/kronosnet/ci-tools https://github.com/corosync/corosync https://github.com/corosync/corosync-qdevice https://github.com/ClusterLabs/high-laughability https://github.com/ClusterLabs/booth https://github.com/ClusterLabs/anvil https://github.com/ClusterLabs/fence-agents https://github.com/ClusterLabs/pcs https://github.com/ClusterLabs/sbd https://github.com/ClusterLabs/pcs-web-ui https://github.com/ClusterLabs/resource-agents https://github.com/ClusterLabs/pacemaker https://github.com/ClusterLabs/libqb https://github.com/ClusterLabs/anvil-external-deps I have spotted a few GitHub PRs that have been automatically closed by the rename: https://github.com/ClusterLabs/resource-agents/pull/1378 https://github.com/ClusterLabs/fence-agents/pull/244 but there might be more for which I have received no notifications. I can´t re-open those PRs automatically, so please ask the submitter to refresh their tree and propose the PR again. CI is currently in the process of being updated to deal with master->main. Please expect failures for now. An update will follow when CI is back online 100%. Fabio ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] [ClusterLabs Developers] [IMPORTANT] Upcoming changes to all ClusterLabs, corosync and knet repositories
All, the maintenance is starting now. We will send out updates as we go. Cheers Fabio On 21/12/2021 04.50, Fabio M. Di Nitto wrote: Just a reminder to everyone. Any developers who have an existing checkout of an affected repository will need to run a few trivial commands to update: https://wiki.clusterlabs.org/wiki/How_to_rename_git_default_branch Nothing needs to be done until the ClusterLabs repositories are updated. Cheers Fabio On 16/11/2021 08.43, Fabio M. Di Nitto wrote: All, following the current internet trends, all our github repositories will switch from the "master" branch to "main". This email is not meant to spark any discussion around the merit of those trends or offend anyone, it´s simple and technical and I would like to keep it that way. This is a multiple day transition that will start the 27th of Dec and end hopefully by the 30th of Dec. The repositories change will follow the published guideline from github: https://github.com/github/renaming and this will happen the 27th itself, pretty fast and hopefully painless. Upstream CI is the most affected service by this change. During those days CI will be unavailable or bumpy. Jenkins itself needs to do an internal transition to change the "master" node name, plus all the CI jobs configurations and all the helper scripts. There will be for sure disruptions in CI after the fact (for example all the CI generated repo files will be renamed). Details of those changes will be published after the transition is completed. If you have any external service / scripts relying on CI builds, be ready to adjust. I am not planning to add backward compatibility layers around. Cheers Fabio ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/developers ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/developers ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] [IMPORTANT] Upcoming changes to all ClusterLabs, corosync and knet repositories
Just a reminder to everyone. Any developers who have an existing checkout of an affected repository will need to run a few trivial commands to update: https://wiki.clusterlabs.org/wiki/How_to_rename_git_default_branch Nothing needs to be done until the ClusterLabs repositories are updated. Cheers Fabio On 16/11/2021 08.43, Fabio M. Di Nitto wrote: All, following the current internet trends, all our github repositories will switch from the "master" branch to "main". This email is not meant to spark any discussion around the merit of those trends or offend anyone, it´s simple and technical and I would like to keep it that way. This is a multiple day transition that will start the 27th of Dec and end hopefully by the 30th of Dec. The repositories change will follow the published guideline from github: https://github.com/github/renaming and this will happen the 27th itself, pretty fast and hopefully painless. Upstream CI is the most affected service by this change. During those days CI will be unavailable or bumpy. Jenkins itself needs to do an internal transition to change the "master" node name, plus all the CI jobs configurations and all the helper scripts. There will be for sure disruptions in CI after the fact (for example all the CI generated repo files will be renamed). Details of those changes will be published after the transition is completed. If you have any external service / scripts relying on CI builds, be ready to adjust. I am not planning to add backward compatibility layers around. Cheers Fabio ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/developers ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] [IMPORTANT] Upcoming changes to all ClusterLabs, corosync and knet repositories
All, following the current internet trends, all our github repositories will switch from the "master" branch to "main". This email is not meant to spark any discussion around the merit of those trends or offend anyone, it´s simple and technical and I would like to keep it that way. This is a multiple day transition that will start the 27th of Dec and end hopefully by the 30th of Dec. The repositories change will follow the published guideline from github: https://github.com/github/renaming and this will happen the 27th itself, pretty fast and hopefully painless. Upstream CI is the most affected service by this change. During those days CI will be unavailable or bumpy. Jenkins itself needs to do an internal transition to change the "master" node name, plus all the CI jobs configurations and all the helper scripts. There will be for sure disruptions in CI after the fact (for example all the CI generated repo files will be renamed). Details of those changes will be published after the transition is completed. If you have any external service / scripts relying on CI builds, be ready to adjust. I am not planning to add backward compatibility layers around. Cheers Fabio ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.23 released
All, We are pleased to announce the general availability of kronosnet v1.23. This version contains MAJOR bug fixes and everybody is strongly encouraged to upgrade as soon as possible. The defrag buffer fixes introduced in v1.22, revealed a long standing bug in corosync, 2 serious bugs in knet that have been lurking around for approx 11 years, and one bug in libqb (spotted during testing of the fixes in this release). Please make sure to upgrade all of them as soon as possible. Corosync and libqb releases are happening (or have already happened) as this announcement is being sent out. All our development team would like to thank the Proxmox VE maintainer, Fabian Gruenbichler, for the extremely detailed bug reports, reproducers and collecting all the data from the affected Proxmox VE users, and his dedication over the past month to debug, test and work with us. 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: * [URGENT] Fix packet sequence number initialization race * [URGENT] Fix UDP link down detection when other nodes restart too fast * [minor] Fix nss buffer boundaries * [minor] improved error logs to make it easier to debug improper setups * [minor] improved logging to not drop log messages on socket overload * Fix build with musl/glibc on archlinux * Enhance security build using annocheck / annobin * Minor bug fixes and enhancements in the test suite Known issues in this release: * The long standing SCTP problem with dynamic links (spotted while preparing v1.21) has not been addressed yet. The problem does NOT affect the corosync / High Availability use case. 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 Libera https://lists.kronosnet.org/mailman3/postorius/lists/users.lists.kronosnet.org/ https://lists.kronosnet.org/mailman3/postorius/lists/devel.lists.kronosnet.org/ https://lists.kronosnet.org/mailman3/postorius/lists/commits.lists.kronosnet.org/ Cheers, The knet developer team ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.22 released
All, We are pleased to announce the general availability of kronosnet v1.22. *** This release includes several MAJOR bug fixes and we strongly encourage everyone to update as soon as possible *** 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: * Fix incorrect defrag buffer index that can cause knet to stop processing all traffic under some extreme network conditions (random latency). * Increase defrag buffer size to better deal with extreme network conditions as above. * Do not leak resources if link configuration fails * Major rework of ACL code to match API vs implementation. * Detect incorrect link configuration when mixing static and dynamic links * Fix knet_send_sync API to require a destination filter * Fix knet sockaddr_storage size across the board to deal with newly introduced checks on FreeBSD * Minor docs updates * Major internal test suite fixes Known issues in this release: * Preparation for this release spotted a long standing issue with SCTP transport used in combination with dynamic links. This specific issue has been in the code since SCTP has been introduced. It will be addressed in one of the upcoming releases. The problem does NOT affect the corosync / High Availability use case. 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 ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.21 released
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/users https://lists.kronosnet.org/mailman/listinfo/devel https://lists.kronosnet.org/mailman/listinfo/commits Cheers, The knet developer team ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] [ClusterLabs Developers] fence-agents v4.8.0
On 17/03/2021 14.41, Oyvind Albrigtsen wrote: ClusterLabs is happy to announce fence-agents v4.8.0. The fence-virt repository has been merged into fence-agents, so be sure to give fence_virt, fence_xvm and fence_virtd some additional testing to ensure it doesnt have any issues we havent caught in our initial testing. All, I am about to do some major spring cleaning in fence_virt: - delete plugins that no longer work or build or used: * null-plugin (disabled by default, does nothing) * libvirt-qmf-plugin (disabled by default, does not build, needs porting to qpid-proton) * pacemaker fence (disabled by default, does not build, needs porting to newer versions of pacemaker) - enable cpg plugin by default (it builds fine, might even work) - drop non-modular build (--disable-modules). It´s currently broken and we know of none shipping fence_virt as a single binary. and add a bunch of coverity scan fixes. If there are any objections, please raise your hands now. Cheers Fabio ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Old pcs-0.9.167/0.9.168/0.9.169 package with newer corosync-3.1 and pacemaker-2.1 on RHEL 7.7
Hi, adding the lead developer for pcs, and the pacemaker user devel mailing list. This mailing list is specific to kronosnet development. On 05/02/2021 10.17, RUGINA Szabolcs-Gavril wrote: Hi folks, Thank you for your time and will to help. 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 2.4.3 to 3.1 and pacemaker 1.1.20 to 2.1 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.. In the midtime we found out that we could archive the same setting using crm_attribute --name no-quorum-policy –update stop. My questions are: * Is there a reason that pcs has no build for RHEL 7? I can only answer this question, newer version of pcs needs ruby and python in versions that are not supported on RHEL7 and even if we can build the package, it won´t run. Fabio * Is the crm_attribute the right choice for setting cluster properties and will cover all usecases? * Thank You! BR, Szabolcs ___ Users mailing list us...@lists.kronosnet.org https://lists.kronosnet.org/mailman/listinfo/users ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.20 released
All, We are pleased to announce the general availability of kronosnet v1.20 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: * Fix per link stats collection to be more consistent on RX/TX * Fix coverity scan build error * Remove some dead code * Minor improvements to the test suite 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 ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.x series and future support / development
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 ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.19 released
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/users https://lists.kronosnet.org/mailman/listinfo/devel https://lists.kronosnet.org/mailman/listinfo/commits Cheers, The knet developer team ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.18 released
All, We are pleased to announce the general availability of kronosnet v1.18 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: * Fix libknet soname * Fix doxyxml build 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 ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] kronosnet v1.17 released (don´t use)
Hey all, please hold your horses in packaging 1.17. I just found out that we forgot to bump the soname for libknet (new symbols). I am pushing the fix via CI and a 1.18 release will follow as soon as possible. Cheers Fabio On 7/14/2020 4:03 PM, Fabio M. Di Nitto wrote: 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/users https://lists.kronosnet.org/mailman/listinfo/devel https://lists.kronosnet.org/mailman/listinfo/commits Cheers, The knet developer team ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/developers ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.17 released
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/users https://lists.kronosnet.org/mailman/listinfo/devel https://lists.kronosnet.org/mailman/listinfo/commits Cheers, The knet developer team ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.16 released
All, We are pleased to announce the general availability of kronosnet v1.16 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: * Fix major issue with SCTP when nodes have duplicated IP addresses, for example virtual interfaces to connect to docker or libvirt * Fix build with newest gcc * Minor bug fixes 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 ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.15 released
All, We are pleased to announce the general availability of kronosnet v1.15 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: * Fix major interaction issues between applications gathering statistics and PMTUd. * Fix UDP socket options that could lead to knet not being properly functional * Man pages updates * Minor bug fixes 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 ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.14 released
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/users https://lists.kronosnet.org/mailman/listinfo/devel https://lists.kronosnet.org/mailman/listinfo/commits Cheers, The knet developer team ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.13 released
All, We are pleased to announce the general availability of kronosnet v1.13 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 performances compared to the old network protocol. Highlights in this release: * IMPORTANT/URGENT: fix defrag buffer reclaim logic that could lead knet to deliver corrupted data to the application (corosync or alike). * IMPORTANT/URGENT: fix MTU boundary check on links with very high packet loss and avoid delivering corrupted (short) data to the application. * Optimize reassembly of defrag packets by avoid unnecessary memmoves. * Improvements to the test suite to deal with the above bugs and potentially reduce regressions in future. * Minor stability fixes to the test suite. 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 ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.12 released
All, We are pleased to announce the general availability of kronosnet v1.12 (bug fix release) 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 performances compared to the old network protocol. Highlights in this release: * IMPORTANT: any version prior to 1.12 has a memory corruption bug that could cause knet to crash or hung when the network is not stable for a long period of time. Please see https://github.com/kronosnet/kronosnet/issues/255 for details. If you are unable to upgrade to 1.12, please make sure to cherry pick https://github.com/kronosnet/kronosnet/commit/6a92361c7554c2aa7222d6f868e43704694683c7 (stable branch) into your distribution as soon as possible. * Fixed all coverity scan errors for runtime code. * Fixed latency calculation in some corner cases that could cause internal latency values to spike too high with incorrect values. * Fixed some documentation. * Add support for musl libc 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 signature.asc Description: OpenPGP digital signature ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.11 released
All, We are pleased to announce the general availability of kronosnet v1.11 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 performances compared to the old network protocol. Highlights in this release: * Major bug fixes in the PMTUd code. MTU was not calculated correctly when using crypto and PMTUd would fail due to timeouts when using crypto and systems are overloaded. Thanks to the proxmox community for reporting the issues and testing pre-fixes. * Allow TX and RX threads to flush queues during shutdown to avoid dropping outgoing packets. * Add a new API to allow manual override of PMTUd/MTU. Please use with caution. (NOTE to package maintainers, this also includes a minor soname bump) * Minor internal improvements and bug fixes. 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 ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.10 released
All, We are pleased to announce the general availability of kronosnet v1.10 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 performances compared to the old network protocol. Highlights in this release: * Add support for IP based access lists to filter packets only from known or allowed sources (please be aware of the minor soname change!) * Add support for zstd compression * Update upstream spec file to build rpm * Fix ssl runtime reconfiguration code to be much more robust * Many minor bug fixes * Fixed license headers across the board to be more clear which license applies where 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 ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.9 released
All, We are pleased to announce the general availability of kronosnet v1.9 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: * Reduce minimum crypto key size requirement to 1024bit * Drop libnss 3des support * Lots of man pages improvements and cleanup * Improved UDP error reporting from ICMP error messages 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 ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[ClusterLabs] kronosnet v1.8 released
All, We are pleased to announce the general availability of kronosnet v1.8 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: * Fixed SCTP transport on FreeBSD. * Fixed a potential use-after-free that could lead to a crash when unconfiguring links at runtime. * Fixed a link configuration error that would allow a user to configure, for example, an IPv4 source address and an IPv6 causing knet to spin at 100% of the CPU. * Minor man pages fixes and improvements. * Minor build and test suite fixes. * Minor logging events fixes. 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 ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] [ClusterLabs Developers] Resource Agent language discussion
On 8/11/2015 11:01 AM, Jehan-Guillaume de Rorthais wrote: On Tue, 11 Aug 2015 06:42:37 +0200 Fabio M. Di Nitto fabbi...@fabbione.net wrote: On 8/7/2015 5:14 PM, Jehan-Guillaume de Rorthais wrote: Hi Jan, On Fri, 7 Aug 2015 15:36:57 +0200 Jan Pokorný jpoko...@redhat.com wrote: On 07/08/15 12:09 +0200, Jehan-Guillaume de Rorthais wrote: Now, I would like to discuss about the language used to write a RA in Pacemaker. I never seen discussion or page about this so far. it wasn't in such a heretic :) tone, but I tried to show that it is extremely hard (if not impossible in some instances) to write bullet-proof code in bash (or POSIX shell, for that matter) because it's so cumbersome to move from whitespace-delimited words as a single argument and words as standalone arguments back and forth, connected with quotation-desired/-counterproductive madness (what if one wants to indeed pass quotation marks as legitimate characters within the passed value, etc.) few months back: http://clusterlabs.org/pipermail/users/2015-May/000403.html (even on developers list, but with fewer replies and broken threading: http://clusterlabs.org/pipermail/developers/2015-May/23.html). Thanks for the links and history. You add some more argument to my points :) HINT: I don't want to discuss (neither troll about) what is the best language. I would like to know why **ALL** the RA are written in bash I would expect the original influence were the init scripts (as RAs are mostly just enriched variants to support more flexible configuration and better diagnostics back to the cluster stack), which in turn were born having simplicity and ease of debugging (maintainability) in mind. That sounds legitimate. And bash is still appropriate for some simple RA. But for the same ease of code debugging and maintainability arguments (and many others), complexe RA shouldn't use shell as language. so beside the language you can/want to use, from a development perspective you guys are probably right that in some cases, more complex languages could be a better fit. But you forgot to position yourself as end user and the reason why we currently use bash/shell. first of all, our end user is not necessarily a developer. Most of them are in fact sysadmins and one common that sysadmins have is that they know bash/shell. I understand that. However, most sysadmins know the basics of bash, maybe some advanced bash, to interact with the system. But how many of them are actually doing proper **development** in bash? Use arrays, escape parameters, protects against unwanted globing, use substitutions instead of cut/sed/awk/grep/whatever, check their return code, declare typed variable, mess with their scope, ...? Sysadmins are happy with bash for simple tasks/scripts or just doing sysadmin. When it comes to development, they turn to perl or python nowadays. If they want to open and debug a RA, this is not some sysadmin anymore, this is development. At least, I would expect published RA to be well tested and production ready, not having trivial bug easy to fix. If needs arise to debug a RA, shell is pretty much the only common denominator with our user base. But as a sysadmin who tries to write robust bash script and as a PostgreSQL DBA, if I open the pgsql RA agent, I become a bit nervous. Try to run shellcheck on the pgsql and mysql RA. Proper and robust bash development often require to use syntaxes, features and cautions a lot of people will not be familiar with. Worst, sometime you must stick outside of good practices: consider some optional args to a command you must not quote as instance... It just becomes quickly a headache. So all-in-all, as a sysadmin, watching at some RA code (not all of them) doesn't give me much more confidence about them. And reading the discussions pointed by Jan earlier in this thread confirm this feeling. The other problem i see in using other languages is how they operate under extreme conditions (memory pressure, disk I/O etc). Just for the fun of it, [...] Granted, it´s an incredibly small test et all, but all I am trying to say is that Cluster is supposed to be as reliable as possible under extreme conditions. Ok, I understand this argument. Bash is reliable and lighter, so better fit for extreme condition. But then, I would expect the project to provide a C library as well. I'm not kidding, I understand bash is a good compromise. But as far as I can read the code and debug if needed, whatever the language. Again, this is development tasks. If I pick the PostgreSQL project, the engine can be extended using SQL, PL/PgSQL, python, perl, C, and many other languages (even shell), to add operators, types, functions/procedures, background worker (C only), ... People extending or using external modules are responsible to test and validate them. Sometime, when such a module is really useful, they are swallowed
