Test discovery

[Eknir]

Requirements for isolated testing:

• ability to create an isolated (network ports only available through vpn) temporary cluster of bee nodes where an underlay multiaddress of one node should be used as --bootnode value configuration parameter so that all other nodes connect to it
• ability to monitor the number of established connections for every node, preferably with bee_libp2p_created_connection_count and bee_libp2p_handled_connection_count metrics
• ability to make http calls to bee API endpoint to every node in order to manually test pingpong protocol between nodes
• ability to make http calls to bee Debug API endpoint to every node in order to list connected peers
• ability to completely destroy created cluster

List of bee's underlay multiaddresses can be retrieved by issuing an HTTP call to $IP:$DEBUG_API_PORT/addresses when #44 is merged. An address which is not on a loopback interface should be selected to be provided to other nodes as --bootnode parameter.

Metrics are exposed for prometheus to be collected on $IP:$DEBUG_API_PORT/metrics.

Requirements for public testing:

• two permanent publicly accessible bee nodes (over P2P and API ports) which underlay multiaddresses would be provided to be used as bootnodes while manually testing
• ability to access their Debug API endpoints though vpn

Optional but useful:

• access to tracing data and log messages for every node

cc @svetomir @vandot

[Eknir]

Hi guys, just wondering on the status of this issue? Is there still active work here, is it blocked?

[svetomir]

Discovery is finished. I am closing the ticket.