Subject: Re: [Rift] Visualization of RIFT and Interop testing

From: Antoni Przygienda <[email-masked]>
Date: Wed, 1 Aug 2018 15:49:36 +0000

Thus spake <[email-masked]<mailto:[email-masked]>>:

Hi Tony,

You might be interesting in this visualization: http://bit.ly/visualize-rift-example<https://urldefense.proofpoint.com/v2/url?u=http-3A__bit.ly_visualize-2Drift-2Dexample&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=maKXfKzgRTpiLitqHnJiww&m=IgUVcrHW3M4GyQcvChLsNiEXiHpQzHkgB5Ne-5bhVgc&s=2XsEry1jsw5miuc1PEqdlH_xk1EFSG-ejazaVrv9c3I&e=>

Prz: Neato, very nice framework you set up  ;-)

Looks like this implementation is shaping up to be perfect for people to initially understand/muck around with RIFT and innovate. And seeing the runtimes, probably good enough for leaf version.

I cross-checked 2 finer points & I see on LIE FSM that the FSM comes up within couple msecs to 2-way on original exchange but not 3-way as it should.  Either I published older version or you omitted something (or I have a bug?)

Your timers may need bit jitter but then the graphs will become much messier ;-)

It is an example output of a tool I build to visualize messages and FSM information for RIFT.  This particular example shows your two_by_to_by_two_ztp.yaml topology.

yupp

This is generated by the visualize_log.py script in https://github.com/brunorijsman/rift-python<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_brunorijsman_rift-2Dpython&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=maKXfKzgRTpiLitqHnJiww&m=IgUVcrHW3M4GyQcvChLsNiEXiHpQzHkgB5Ne-5bhVgc&s=58yru-a7ZoPNNCkWPBx2zzZapVCMvXH3wapG_R3pvSs&e=>

I find it very useful to debug the various FSMs, especially when there’s a large number of nodes.

Each black vertical line represents an entity: either a node (ZTP FSM) or an interface (LIE FSM). The interfaces are grouped together with the node that they belong to.

Red dots are events on the ZTP FSM for a node.

Orange dots are events on the LIE FSM for an interface.

Blue dots and lines are messages.

I plan to enhance it with various knobs and whistles to show more details when you hover over a dot etc.

I find on those tools filtering is the most important thing. Visualization quickly overwhelms our processing capacity for such stuff unless you go towards summarization like PCA but that does nothing for protocol verification.

I’m ready to do interop testing with your code, whenever you are ready. (I have your binary, so I can get started without you.)

Yupp. I’ll ping you of the list. You ran 2x2x2_ztp and got the correct results on miscabling as I saw which is a good first test.

CC to RIFT mailing list. If anyone else wants to join the interop testing with another implementation, let us know.

Where are the brave souls ;-)