Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

p2p: network testing and simulation framework #3102

Closed
wants to merge 186 commits into from

Conversation

zelig
Copy link
Contributor

@zelig zelig commented Oct 7, 2016

This substantial PR is the first attempt at a comprehensive devp2p network testing framework.
Allows for mounting protocols over various networks:

simulations and adapters:

  • normal operation: using the rlpx adapter
  • simulated inprocess network
  • multinode local cluster
  • docker driven remote cluster

various msgpipe and messenger abstractions allow for

  • throughput monitoring and aggregate stats
  • simulated bandwidth and connectivity constraints to test fault tolerance
  • latency benchmarking
  • serialised or non-serialised transport for simulated networks

test drivers:

  • peer session exchange: single node and multiple peers: testing of trigger/expect style message exchange scenarios. The primary usecase is to support protocol (or protocol module) unit tests.
  • network session: allows for setting up a network of nodes with parameters (availability, uptime, etc) and test it with node-specific RPC snippets
  • scenario drivers: the same setups and scenarios (described with json) can be used on all network types

@zelig zelig self-assigned this Oct 7, 2016
@zelig zelig force-pushed the network-testing-framework branch 2 times, most recently from b65e03c to 186849d Compare October 10, 2016 16:28
@zelig zelig force-pushed the network-testing-framework branch from 186849d to 15b8c39 Compare October 27, 2016 06:44
@zelig zelig mentioned this pull request Oct 27, 2016
@zelig zelig force-pushed the network-testing-framework branch from 15b8c39 to 7831ecb Compare December 20, 2016 14:10
@fjl fjl changed the base branch from develop to master December 20, 2016 14:27
@fjl
Copy link
Contributor

fjl commented Dec 21, 2016

@zelig please fix build issues and rebase

@GitCop
Copy link

GitCop commented Jan 16, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: ed73d164ca16c939c9785ef532c644a41fbacefa
  • Your commit message body contains a line that is longer than 80 characters

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

1 similar comment
@GitCop
Copy link

GitCop commented Jan 19, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: ed73d164ca16c939c9785ef532c644a41fbacefa
  • Your commit message body contains a line that is longer than 80 characters

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

@cobordism cobordism force-pushed the network-testing-framework branch from 6d3107e to ebf4e2c Compare January 19, 2017 16:08
@GitCop
Copy link

GitCop commented Jan 19, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: ed73d164ca16c939c9785ef532c644a41fbacefa
  • Your commit message body contains a line that is longer than 80 characters

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

2 similar comments
@GitCop
Copy link

GitCop commented Jan 30, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: ed73d164ca16c939c9785ef532c644a41fbacefa
  • Your commit message body contains a line that is longer than 80 characters

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

@GitCop
Copy link

GitCop commented Feb 5, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: ed73d164ca16c939c9785ef532c644a41fbacefa
  • Your commit message body contains a line that is longer than 80 characters

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

@GitCop
Copy link

GitCop commented Feb 5, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: ed73d164ca16c939c9785ef532c644a41fbacefa

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: 682875a

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: ec575525740c4d0a88e9acce01737976cbcb8f57

  • Your commit message body contains a line that is longer than 80 characters

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

@GitCop
Copy link

GitCop commented Feb 8, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: ed73d164ca16c939c9785ef532c644a41fbacefa

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: 682875a

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: ec575525740c4d0a88e9acce01737976cbcb8f57

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: 6c91fbaad5159ae764e9a066538904397f267e96

  • Commits must be prefixed with the package(s) they modify

  • Commit: e13b4e2117e97e488d3c2cbf85766597e019bf8e

  • Commits must be prefixed with the package(s) they modify

  • Commit: 505245f06343b3304c971ee376955ba238fa0b27

  • Commits must be prefixed with the package(s) they modify

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

@zelig zelig force-pushed the network-testing-framework branch from 4ba8b37 to 6ef3cdf Compare February 12, 2017 18:11
@GitCop
Copy link

GitCop commented Feb 12, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: 7d2802d

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: eab6b51

  • Your commit message body contains a line that is longer than 80 characters

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

@zelig zelig force-pushed the network-testing-framework branch from 6ef3cdf to 68c4c3f Compare February 14, 2017 04:50
@GitCop
Copy link

GitCop commented Feb 14, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: 7d2802d

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: eab6b51

  • Your commit message body contains a line that is longer than 80 characters

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

@zelig zelig force-pushed the network-testing-framework branch from 68c4c3f to 98f5fad Compare February 16, 2017 17:34
@GitCop
Copy link

GitCop commented Feb 16, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: 7d2802d

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: eab6b51

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: 98f5fad

  • Commits must be prefixed with the package(s) they modify

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

@zelig
Copy link
Contributor Author

zelig commented Mar 6, 2017

outstanding tasks

  • reorganise hive as having extended peer
  • Add/Remove as service + removeHandler
  • Drop() -> Drop(disconnectReason)
  • removeHandler sets error and that is registered
  • principled way to separate trigger events vs report or success/failure messages. However they are in almost perfect alignment
  • simplify event structures
  • remove cy-update.go in favour of direct json serialisation of the events
  • message passing backend
  • snapshot implementation
  • journal and snapshot controller and frontend UX: maybe a mutli-button sidebar saying: "start simulation driven from journal", "set up network from snapshot", "save snapshot", "start recoding". Journal replays should have a slider for speedup parameter
  • [ ]

@GitCop
Copy link

GitCop commented Mar 13, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: 7d2802d

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: eab6b51

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: 98f5fad

  • Commits must be prefixed with the package(s) they modify

  • Commit: 7a9110c

  • Commits must be prefixed with the package(s) they modify

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

@GitCop
Copy link

GitCop commented Mar 13, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: 7d2802d

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: eab6b51

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: 98f5fad

  • Commits must be prefixed with the package(s) they modify

  • Commit: 7a9110c

  • Commits must be prefixed with the package(s) they modify

  • Commit: d0ec03b

  • Commits must be prefixed with the package(s) they modify

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

@nolash nolash force-pushed the network-testing-framework branch from d0ec03b to a76ce75 Compare March 13, 2017 13:50
@GitCop
Copy link

GitCop commented Mar 13, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: 7d2802d

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: eab6b51

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: 98f5fad

  • Commits must be prefixed with the package(s) they modify

  • Commit: 7a9110c

  • Commits must be prefixed with the package(s) they modify

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

@GitCop
Copy link

GitCop commented Aug 8, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: 7a6ff56

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: 9822d74

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: 01fb8ed

  • Commits must be prefixed with the package(s) they modify

  • Commit: 8cd9adc

  • Commits must be prefixed with the package(s) they modify

  • Commit: a6a006c

  • Commits must be prefixed with the package(s) they modify

  • Commit: e26d672

  • Commits must be prefixed with the package(s) they modify

  • Commit: b7860c7

  • Commits must be prefixed with the package(s) they modify

  • Commit: b8bf32b

  • Your commit message body contains a line that is longer than 80 characters

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

nolash and others added 6 commits August 8, 2017 21:33
Add send asymmetric messages
Split up process-method
Extract symkey send in sep. method, now called by api
Renamed "env" var names to "envelope"
API method for get/set length of address to be revealed for routing
Add API and Pss documentation comments
Add test for "dark" message between two directly connected peers
@GitCop
Copy link

GitCop commented Aug 16, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: 7a6ff56

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: 9822d74

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: 01fb8ed

  • Commits must be prefixed with the package(s) they modify

  • Commit: 8cd9adc

  • Commits must be prefixed with the package(s) they modify

  • Commit: a6a006c

  • Commits must be prefixed with the package(s) they modify

  • Commit: e26d672

  • Commits must be prefixed with the package(s) they modify

  • Commit: b7860c7

  • Commits must be prefixed with the package(s) they modify

  • Commit: b8bf32b

  • Your commit message body contains a line that is longer than 80 characters

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

nolash and others added 3 commits August 18, 2017 09:54
Add per-message address specification
Add global max addresslength for autonomous replies
Add addresslength setting in PssMsgReadWriter
Add asymmetric option in PssMsgReadWriter
Remove redundant public accessor in whisper
Forward message if partial address and full match
Forward message if partial address and self recipient
swarm/pss: Added whisper encryption
@GitCop
Copy link

GitCop commented Aug 24, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: 7a6ff56

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: 9822d74

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: 01fb8ed

  • Commits must be prefixed with the package(s) they modify

  • Commit: 8cd9adc

  • Commits must be prefixed with the package(s) they modify

  • Commit: a6a006c

  • Commits must be prefixed with the package(s) they modify

  • Commit: e26d672

  • Commits must be prefixed with the package(s) they modify

  • Commit: b7860c7

  • Commits must be prefixed with the package(s) they modify

  • Commit: b8bf32b

  • Your commit message body contains a line that is longer than 80 characters

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

@GitCop
Copy link

GitCop commented Aug 28, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: 7a6ff56

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: 9822d74

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: 01fb8ed

  • Commits must be prefixed with the package(s) they modify

  • Commit: 8cd9adc

  • Commits must be prefixed with the package(s) they modify

  • Commit: a6a006c

  • Commits must be prefixed with the package(s) they modify

  • Commit: e26d672

  • Commits must be prefixed with the package(s) they modify

  • Commit: b7860c7

  • Commits must be prefixed with the package(s) they modify

  • Commit: b8bf32b

  • Your commit message body contains a line that is longer than 80 characters

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

@GitCop
Copy link

GitCop commented Aug 29, 2017

Thank you for your contribution! Your commits seem to not adhere to the repository coding standards

  • Commit: 7a6ff56

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: 9822d74

  • Your commit message body contains a line that is longer than 80 characters

  • Commit: 01fb8ed

  • Commits must be prefixed with the package(s) they modify

  • Commit: 8cd9adc

  • Commits must be prefixed with the package(s) they modify

  • Commit: a6a006c

  • Commits must be prefixed with the package(s) they modify

  • Commit: e26d672

  • Commits must be prefixed with the package(s) they modify

  • Commit: b7860c7

  • Commits must be prefixed with the package(s) they modify

  • Commit: b8bf32b

  • Your commit message body contains a line that is longer than 80 characters

Please check the contribution guidelines for more details.


This message was auto-generated by https://gitcop.com

@zelig
Copy link
Contributor Author

zelig commented Aug 29, 2017

superceded by #14982

@zelig zelig closed this Aug 29, 2017
@gbalint gbalint deleted the network-testing-framework branch May 25, 2018 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants