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

Waku: Deploy Waku nodes with Waku-Whisper bridge nodes for cluster #4

Open
oskarth opened this issue Nov 25, 2019 · 3 comments
Open

Waku: Deploy Waku nodes with Waku-Whisper bridge nodes for cluster #4

oskarth opened this issue Nov 25, 2019 · 3 comments
Assignees

Comments

@oskarth
Copy link
Member

@oskarth oskarth commented Nov 25, 2019

Problem

As a developer, I want to test end to end integration of Waku nodes with an environment as close to production as possible.

(Later for waku/1) As a user, I want to have the ability to use Waku mode to reduce my bandwidth usage. Additionally, I want to have compatibility with Whisper networks so I can receive and send messages to people not using the waku subprotocol.

Acceptance criteria

There are nodes running Waku-Whisper bridge in our cluster, such that if I connect to them (directly hardcoded like mailserver e.g., later discovered) using Waku node I can send and receive to clients using Whisper.

Details

As part of Waku, we want to deploy Waku nodes to our cluster for experimental end to end testing. These are running the subprotocol waku/0 and bridge traffic. See https://specs.vac.dev/waku.html#backwards-compatibility for more details.

Currently the only implementation that supports this is nim-eth. This means we want to deploy nim-eth with Waku capability and Waku Whisper bridge enabled. This will also be a great opportunity to ensure our app can actually interop successfully with the Nim based impl (should be fine but...you know).

Right now I'm not quite clear what changes we need to make to the nim-eth client, but I suppose we need to expose some CLI flags and then put it in a terraform/ansible playbook?

fyi @jakubgs (cluster) @kdeme (nim-eth) @cammellos (app) @adambabik (go/cluster)

@oskarth oskarth mentioned this issue Nov 25, 2019
15 of 15 tasks complete
@oskarth oskarth added this to Triage in Waku project Nov 25, 2019
@oskarth oskarth moved this from Triage to To do in Waku project Nov 25, 2019
@jakubgs

This comment has been minimized.

Copy link

@jakubgs jakubgs commented Nov 26, 2019

@kdeme maybe we could do a 1-on-1 and talk about how this waku node is supposed to run, and what the result is supposed to be.

@oskarth

This comment has been minimized.

Copy link
Member Author

@oskarth oskarth commented Dec 9, 2019

@jakubgs @kdeme I feel like there was some follow up to this but can't find it. Can you please link the relevant issue back here? IIRC re command line flags etc.

@oskarth oskarth mentioned this issue Dec 9, 2019
4 of 5 tasks complete
@kdeme

This comment has been minimized.

Copy link

@kdeme kdeme commented Dec 9, 2019

@oskarth oskarth moved this from To do to Backlog/Scratch in Waku project Dec 19, 2019
@oskarth oskarth moved this from Backlog/Scratch to To do in Waku project Jan 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Waku project
  
To do
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.