[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/
Re: [ClusterLabs] Finding attributes of a past resource agent invocation
Hi Feri, just to this one... On 03/03/20 15:22 +0100, wf...@niif.hu wrote: > Is there a way to find out what attributes were passed to the OCF > agent in that fateful invocation? AFAIK, not possible after-the-fact, unless you add TRACE_RA=1 as another (real) parameter to the agent and it happens to respond to it (very likely with standard agents from resource-agents project). And even then, logs generated like that will likely get lost when the node is fenced (depends on path/mount particulars). I think that not exposing such details about invocation directly at pacemaker logging level is by design ... safer than to leave the cat out of the bag. Consider that any incidents reported are promptly followed with soliciting the logs, and making the authentication tokens, password and other secrets leaked this way would be bad for general reputation, wouldn't it? (this was also part of the reasoning behind CVE-2019-3885) -- Poki pgpBT4ivPPPXM.pgp Description: PGP signature ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Antw: [EXT] Re: clusterlabs.org upgrade done
On Wed, Mar 04, 2020 at 10:05:50AM +0200, Strahil Nikolov wrote: > Maybe I will be unsubscribed every 10th email instead of every 5th one. AFAICT from the reports, the mail I send to the list might not get delivered, perhaps this is causing the unsubscribe too: 78.46.95.29 2 reject fail fail valentin-vidic.from.hr valentin-vidic.from.hr permerror clusterlabs.org none For DKIM the problem is that list modifies Subject and body so the signature is not valid anymore. The list would need to remove DKIM headers, change the From field to list address and perhaps add DKIM signature of its own. Another options is for the list to stop modifying messages: https://begriffs.com/posts/2018-09-18-dmarc-mailing-list.html For SPF if would be good to add SPF records into DNS for clusterlabs.org domain. -- Valentin ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Antw: [EXT] Re: clusterlabs.org upgrade done
On March 4, 2020 9:50:10 AM GMT+02:00, Ulrich Windl wrote: Valentin Vidic schrieb am >03.03.2020 um >16:52 >in Nachricht ><20449_1583250783_5e5e7d5f_20449_2155_1_20200303155240.ga24...@valentin-vidic.fr > >m.hr>: >> On Sat, Feb 29, 2020 at 03:44:50PM ‑0600, Ken Gaillot wrote: >>> The clusterlabs.org server OS upgrade is (mostly) done. >>> >>> Services are back up, with the exception of some cosmetic issues and >>> the source code continuous integration testing for ClusterLabs >github >>> projects (ci.kronosnet.org). Those will be dealt with at a more >>> reasonable time :) >> >> Regarding the upgrade, perhaps the mailman config for the list should >> be updated to work better with SPF and DKIM checks? > >How do you define "work better"? > >> >> ‑‑ >> Valentin >> ___ >> 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/ Maybe I will be unsubscribed every 10th email instead of every 5th one. Best Regards, Strahil Nikolov ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
