Tracker: First Network Test

[alrevuelta]

Coming from these top level requirements this issue aims to break down in lower level requirements, all tasks required to accomplish the First Network Test presented in the issue. If you think any of the tasks have to be further discussed, feel free to open an issue.

Assumptions:

• Only relay protocol is supported
• Only nwaku client is tested
• All nodes are visible to each other.

Tracker: First Network Test

• [x] Hardcoded configuration to spin up two hardcoded nwaku nodes:
  • [x] https://github.com/logos-co/wakurtosis/pull/1
• [x] Configuration to spin up n configurable nwaku nodes.
• [x] Connect nodes at startup, using the RPC API. Edit: Done in #9
• [x] Include prometheus and grafana in the setup, with all config and a dashboard automatically provisioned. Edit: Done in #10
  • [x] https://github.com/logos-co/wakurtosis/pull/5
• [ ] A metrics such as node resource consumption - CPU, bandwidth and memory usage. Edit: Tackled with #76 , completed when integrated with Prometheus.
• [x] Write a first experimental test, eg curl localhost:8003/metrics | grep waku_connected_peers and assert that after some time its >x. Edit: Done in #39
• [x] Allow nodes to use a given nodekey so its peerId is known in advance before starting the node. Edit: Done in #6
• [x] Incorporate discovery via discv5, conneting only small subset of nodes with staticnode(s) or discv5-bootstrap-node(s) and letting the peers discover each other. Done in #99
• [x] Publish (from a random subset of nodes) messages of size s at a rate r. Done in #19
• [ ] Measure reliability, using a seq counter to the message payload.
• [ ] Measure latency using the sender timestamp field.

cc @AlbertoSoutullo @Daimakaimura @LNSD Let me know what you think.

[fryorcraken]

@kaiserd I believe this is mostly complete, right? Shall we ref to the 1k nodes final report here?