Nightly test: syncing a node from scratch

[jakubcech]

Description

Nightly test for a measuring that a node successfully syncs from different sources that we provide.

Motivation

Test that nodes are syncing by various means.

Scenario

Sync from the latest local snapshot file scenario

1. Set up a node with the latest snapshot files from the IOTA db-files site.
2. Check that the node syncs via ZMQ.

Sync from the latest database (without local snapshot files)

1. Set up a node with the latest DB from the IOTA db-files site.
2. Check that the node syncs via ZMQ.

(Last to implement scenario) Sync from an ancient DB

1. Set up a node with a database that is at least X, last coo snapshot days old.
2. Check that the node syncs via ZMQ.
3. If it doesn't sync before the next instance of this nightly test is run then the test failed.

[DyrellC]

@GalRogozinski In each of these test cases, is it expected for the nodes to sync up with the network as a whole? Or just to sync with one another from a set db state? If the former, how do you propose we connect these nodes to other testnet nodes, considering there will need to be a mutual pairing of neighbors? And if not, where do you propose we store/pull the day to day db package that will be used as the benchmark?

[GalRogozinski]

just to sync with one another from a set db state

We can store it in the same s3 bucket. We can also use an existing DB. The point is that we have a constant DB, so that we know that only code changes affected performance.

[DyrellC]

@GalRogozinski @jakubcech
iotaledger-archive/iri-regression-tests#13