cherusk/lindwurm

Ad-Hoc actioned means to analyze, explore, trace and monitor Distributed Systems

lindwurm

Abstract

The Lindwurm is meant as an Ad-Hoc actioned means to analyze, explore, trace and monitor Distributed Systems and their intrinsic complexity.

It's meant to ease or quicken trouble shooting for system experts responsible for mid- to large scale Distributed Systems. Further, it should give insights and a good overview or technicial understanding to responsibles of environments.

Example usage

To check if a certain group of nodes does have cohesion trait on transport level, you would do:

$ lindwurm.py node_group cohesion --t_ports 22,23 -f Tree transport

>>objective: [cohesion]
scaffolding
 ┣━━ suse42_n2
 ┃   ┣━━ 22
 ┃   ┃   ┣━━ connected
 ┃   ┃   ┃   ┣━━ fedora24
 ┃   ┃   ┃   ┗━━ suse42_n1
 ┃   ┃   ┗━━ disjoined
 ┃   ┗━━ 23
 ┃       ┣━━ connected
 ┃       ┗━━ disjoined
 ┃           ┣━━ fedora24
 ┃           ┗━━ suse42_n1
 ┣━━ suse42_n1
 ┃   ┣━━ 22
 ┃   ┃   ┣━━ connected
 ┃   ┃   ┃   ┣━━ fedora24
 ┃   ┃   ┃   ┗━━ suse42_n2
 ┃   ┃   ┗━━ disjoined
 ┃   ┗━━ 23
 ┃       ┣━━ connected
 ┃       ┗━━ disjoined
 ┃           ┣━━ fedora24
 ┃           ┗━━ suse42_n2
 ┗━━ fedora24
     ┣━━ 22
     ┃   ┣━━ connected
     ┃   ┃   ┣━━ suse42_n1
     ┃   ┃   ┗━━ suse42_n2
     ┃   ┗━━ disjoined
     ┗━━ 23
         ┣━━ connected
         ┗━━ disjoined
             ┣━━ suse42_n1
             ┗━━ suse42_n2

The scaffolding is the core node set from which the investigations are run. You can see that e.g. suse42_n2 is connected to fedora24,suse42_n1 via ssh, but not connected to them for service on port 23.