Users December 2018

users@lists.kronosnet.org

3 participants
2 discussions

How does kronosnet relate to/compare with Transparent Inter Process Communication (TIPC)

by Jan Pokorný

Hello list, sometimes, usually when surfing semi-randomly, I get to know about things that either resemble deja vu to me, or make me feel that I must have lived in an utter ignorance/tunnel so far. Now, both thing combined: https://en.wikipedia.org/wiki/Transparent_Inter-process_Communication Especially now that I checked the kernel module and userspace utility lurk on my Linux machine without ever being asked :-) $ { eval modinfo\ {-F\ description\ ,-F\ version\ ,-F\ license\ }tipc\; echo; tipc -h; } > TIPC: Transparent Inter Process Communication > 2.0.0 > Dual BSD/GPL > > Transparent Inter-Process Communication Protocol > Usage: tipc [OPTIONS] COMMAND [ARGS] ... > > Options: > -h, --help Print help for last given command > > Commands: > bearer - Show or modify bearers > link - Show or modify links > media - Show or modify media > nametable - Show nametable > node - Show or modify node related parameters > peer - Peer related operations > socket - Show sockets Naturally, I am curious how much of an overlap is there, wether there have been any comparisons/benchmarks conducted, all the these sort of things incl. whether the was an a priori knowledge, perhaps inspirational, about this other project. Kronosnet looks to me more on the pragmatically usable and simple side, buying also better portability and avoiding complexities (I take the plugins more like a "look what we can offload from your application layer" demonstration, yet encryption/auth/integrity protection makes a great deal of sense there) beyond UDP (which fully suffices when combined with corosync), something that TIPC covers as well while providing a lot of other abstractions incl. peer discovery, bells and unicorns (which might be heavy overkill for that use case). Any inputs welcome. -- Jan (Poki)

5 years, 3 months

kronosnet v1.6 released

by Fabio M. Di Nitto

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

5 years, 4 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Users December 2018