Recipe for network testing #1322
Conversation
…cript to distribute nodes to groups based on group percent.
| @@ -0,0 +1,12 @@ | |||
| PARAMS=-w 100 -R 8 -N 20 -n 100 -H 10 --node-template node.json --relay-template relay.json --non-participating-node-template nonPartNode.json | |||
There was a problem hiding this comment.
Do we really need such a big network to conduct a partitioning test ?
I don't really see how the large network would help us getting the answer "does the network recover after partitioning? and after how long ?"
There was a problem hiding this comment.
We can adjust the network to be smaller. The github tickets ask for all 3 scenarios.
There was a problem hiding this comment.
That's true. It's that I just don't want you to get delayed by "deployment issues" that aren't related to the actual test you're trying to conduct.. Having the feedback that it's broken on small network is more valuable than the fact the it's broken on a large network ( and would probably be easier to evaluate )
There was a problem hiding this comment.
OK, we will start testing tomorrow.
netdeploy/remote/deployedNetwork.go
Outdated
|
|
||
| group := strings.TrimSpace(cloudHost.Group) | ||
| if group == "" { | ||
| hostSpec.Group = "default" |
There was a problem hiding this comment.
For backward compatibility, you might want to leave the default as an empty string.
This would force the cloudspec file consumer to populate it with "default" instead of expecting a non-empty string.
( i.e. currently, all cloud-spec files doesn't have this field. )
If you're going to break backward compatibility, please add versioning to the cloud spec file so we can detect that forward.
There was a problem hiding this comment.
Leave default as an empty string.
| # for i in range(10): | ||
| # partition_name = get_partition(ranges) | ||
| # print(i, partition_name) |
| "EnableMetrics": false, | ||
| "MetricsURI": "{{MetricsURI}}", | ||
| "ConfigJSONOverride": "{ \"TxPoolExponentialIncreaseFactor\": 1, \"DNSBootstrapID\": \"<network>.algodev.network\", \"DeadlockDetection\": -1, \"PeerPingPeriodSeconds\": 30, \"BaseLoggerDebugLevel\": 4, \"EnableProfiler\": true }", | ||
| "AltConfigs": [ |
There was a problem hiding this comment.
Removed extra white space.
Added a new recipe for performing network disruption tests.
Summary
Added a new recipe for performing network disruption tests.
Test Plan
Testing using Algonet.