mirror of https://github.com/vacp2p/status-benchmarks.git synced 2026-01-06 21:24:09 -05:00

Files

Alberto Soutullo a92c7cde89 Second benchmark additions (#32 )

* Change controlbox pull to Always

* Update status-init to fix discovery issues.

* Improve logging in inject_messages_group_chat

* Save messages in a list with timestamps

* Add method for cleanup signals on logout (probably to avoid issues when loging in and searching for signals)

* Save last loging time

2025-09-29 19:29:38 +02:00

controlbox.yaml

Second benchmark additions (#32 )

2025-09-29 19:29:38 +02:00

Dockerfile

Add controlbox

2025-06-27 22:34:33 +02:00

README.md

Add controlbox

2025-06-27 22:34:33 +02:00

README.md

Controlbox

In order to easy access the status-desktop nodes with requests like:

base_url = f"http://{pod}:3333/statusgo/CallRPC"

response = requests.post(base_url, json={
        "jsonrpc": "2.0",
        "method": "wakuext_fetchCommunity",
        "params": [{
            "communityKey": community_id,
            "waitForResponse": True,
            "tryDatabase": True
        }],
        "id": 1
    })

We will create a pod inside the namespace. Scripts will be run from inside the cluster, having easier access to all nodes addresses. Also, this can be port-forwarded so you can still work from your IDE, setting up breakpoints and exploring variables.

This was the most comfortable/fastest approach to being able to concurrently interact with a big number of nodes.

Building

docker build -t controlbox .

Make sure you put your GitHub handle in the following line inside the Dockerfile:

RUN wget https://github.com/<your_github_handle>.keys -O /root/.ssh/authorized_keys \
    && chmod 600 /root/.ssh/authorized_keys

Running

Apply the controlbox.yaml file to your Kubernetes cluster.

Connecting to the Controlbox

Create a port forward to the controlbox pod on port 2222 -> 22, then:

ssh -p 2222 root@<controlbox-ip>

Alternatively (useful for scripts that need Kubernetes env vars) use k9s to shell into the pod.