57 posts tagged with "network"

Network Update​

Ouroboros Network​

• We finished high and low level peer sharing design. See Peer Sharing Implementation Plan
• We started working on low-level design of eclipse evasion (work in progress).
• We decided to use peer sharing instead of overloaded and ambiguous gossip term. PR input-output-hk/ouroboros-network#3980
• We fixed technical dept issue input-output-hk/cardano-node#3905 in the simulation testing of diffusion PR input-output-hk/cardano-node#4004
• We deployed all our nodes using our new nix based deployment architecture. When deploying we found an issue in the RTView.

Ouroboros Consensus​

• Recently we found out that the consensus does not log exceptions thrown during intiialisation. This was fixed in PR input-output-hk/ouroboros-network#4015 As part of this pull request we also changed that all exceptions rethrown by the connection handler thread are wrapped in ExceptionInHandler.

Some older items, which were not announced​

• We identified and fixed an issue related to socket activation (socket options where not set for sockets passed through socket activation). PR input-output-hk/cardano-node#3979 This fix will be released in the next cardano-node release.

Cardano Node​

• We extended the NixOs service module so that one can modify socketPath, runtimeDir, databasePath, traceSocketPathAccept, traceSocketPathConnect and stateDir options. PR input-output-hk/cardano-node#4196

IO-Sim​

We resolved a number of issues before release of io-sim on hackage:

• issue input-output-hk/ouroboros-network#2797
• issue input-output-hk/ouroboros-network#2650
• issue input-output-hk/ouroboros-network#3436
• issue input-output-hk/ouroboros-network#2588
• issue input-output-hk/ouroboros-network#2587
• issue input-output-hk/ouroboros-network#2586

See PR #24.

We also improved experience for contributors of io-sim and typed-protocols by adding issue templates:

• PR input-output-hk/io-sim#25

Typed Protocols​

• We pushed a branch which identifies a GHC quirk: coot/typed-protocols-rewrite-StateToken-problem. That's too be resolved in order to push forward review of the redesign in PR input-output-hk/typed-protocols#3.
• As for io-sim, we wrote issue templates: PR input-output-hk/typed-protocols#11

Input Endorsers Simulation​

New features include:

• Histograms of block arrival frequency, for both network (inbound) and CPU (block validation). This is interesting to check that we're not overloading the CPU block validation capacity, or network link capacity. Or alternatively to observe the behaviour in an overload situation if we set the block generation rate high enough.

• Pie chart of utilisation of TCP links. This shows how small a fraction of links are being used at any one time, and shows that once the system "warms up" and is operating stably, most block delivery is ballistic.

• Showing off the new screen layout combinators, that let us put multiple charts, titles etc on screen at once and scale them to whatever screen or video resolution we like without having to tweak numbers (this example is scaled to fit 1080HD video resolution).

The networking team took an active part in the project iteration (PI) planning session, see cardano-node backlog for detailed outcomes.

• We started working on a detailed design / implementation plan for gossip.

• We merged input-output-hk/ouroboros-network#3859 which sets the ouroboros-network repository for the single relay release.

• We identified a bug in the network simulator, which is fixed in the input-output-hk/ouroboros-network#3852. The above PR was reviewed.

• We set the tracing configuration for nodes which we deploy and fixed and identified some deployment hiccups. We identified some bugs in the RT view which were registered by the maintainers. input-output-hk/ouroboros-network-ops#4

• We fixed typos in network-mux library: input-output-hk/ouroboros-network#3921

• For easy of debugging we renamed a trace point: input-output-hk/ouroboros-network#3922

• Duncan iterated on his simulation / visualisation. He also was able to identify and fix a bug in the simulator. The simulation contains 50 nodes. Dashed lines indicate and established connection, while solid lines indicate a TCP connection with fully open TCP window.