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

Deploy test network #648

Closed
ulope opened this Issue Jun 14, 2017 · 1 comment

Comments

Projects
None yet
3 participants
@ulope
Collaborator

ulope commented Jun 14, 2017

Problem Definition

Deploy a test network

Environment

  • blockchain: geth X ropsten (maybe later rinkeby)
  • deployment: AWS

Scenario

  • 100 raiden nodes
  • 3 ERC20 tokens
  • connect token networks over time
  • initiate transfers to other nodes
  • receive transfers from other nodes
  • leave token networks
  • test interwoven transfers (token/mediation/direct)
  • apart from some specific transfers it should have some transfer "background noise"

Existing Infrastructure

  • ansible AWS deployment scripts
  • (predictable) node address/account generation scripts
  • contract deployment scripts
  • token deployment & distribution scripts
  • simplified deployment by using raiden.AppImage (instead of installing python+dependencies)

Missing/incomplete infrastructure

  • public testnet connection with minimal sync overhead (trusted node(s))
  • public testnet ETH faucet/distribution for participant addresses/accounts
  • global scenario view
  • scenario playbook control via raiden restful API/RPC (this should replace scenario_runner.py which was a modded raiden app instance)
  • scenario assertions via raiden restful API/RPC ("node37 sent 5 and received 7 token Y, assert balance before settle")
  • scenario assertions via blockchain (assert token balance after settlement: "node37 balance of token Y has changed '-2'")
  • node error alarms (raiden processes should be monitored for livelyhood)
  • central log-file collection (logs are stored on AWS instances, but recovery may be tedious with current implementation)

Nice to have's

  • global scenario instrumentation (connection graph, transfer success/failure rate, path lengths)

@ulope ulope added this to the Developer Preview milestone Jun 14, 2017

@ulope ulope added the sprint_12 label Jun 14, 2017

@ulope ulope self-assigned this Jun 14, 2017

@LefterisJP LefterisJP added the 3 label Jun 14, 2017

@konradkonrad konradkonrad referenced this issue Jun 20, 2017

Closed

Create transfers on the test network #649

0 of 3 tasks complete
@ulope

This comment has been minimized.

Show comment
Hide comment
@ulope

ulope Sep 5, 2017

Collaborator

The testnet has been deployed (#712). Subtasks are being tracked in

Collaborator

ulope commented Sep 5, 2017

The testnet has been deployed (#712). Subtasks are being tracked in

@ulope ulope closed this Sep 5, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment