sonm-io / insonmnia Goto Github PK

View Code? Open in Web Editor NEW

44.0 44.0 10.0 2.59 MB

The platform

License: Apache License 2.0

Makefile 3.11% Go 93.22% Protocol Buffer 3.68%

containers docker golang sonm

insonmnia's People

Contributors

Stargazers

Watchers

Forkers

maaktweluit adolfoeliazat whardier johndpope leanderdulac nunofernandes-plight sakartvelo teotikalki keenanhutchens ayoubjadouli

insonmnia's Issues

Miners must be identified by some secure unique ID

For now miners are marked by their remote addresses, when they connect to a hub.
It can lead to a collision, as such id is not preserved across reconnections.
At the same time, the id must be secure against forging (i.e. RSA). Probably integration with Whisper based discovery can help there.

Miner should detect if it has public IPv4/IPv6

We need this to pick a proxy technology.
Suggested way to do it:

use i.e. http://checkip.amazonaws.com/ to identify out public IP
check if any of ifaces has such IP

Whisper based discovery

Security improvements

gRPC should not use insecure

Just link some:
#4
#16

error running docker

Hello,

I've followed your readme, but sonm node can not be launched :

docker run --rm -p 10002:10002 -p 10001:10001  sonm/insonmnia sonmhub

docker: Error response from daemon: failed to create endpoint elegant_goodall on network bridge: failed to add the host (vethac43067) <=> sandbox (veth3a8eca5) pair interfaces: operation not supported.

And if I try to run the mining node :

docker run -d --env DOCKER_API_VERSION=1.24 --net=host -v /run:/var/run sonm/insonmnia:alpha3 sonmminer --hubaddress=35.177.238.170:10002

e14ad68223455c3040fd887f9b115e2e221a54c33d939f49ba5ff0dd3c6dd059
docker: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "process_linux.go:245: running exec setns process for init caused \"exit status 29\"".

I use a Debian 7.5 wheezy
ports 10001 and 10002 are opened. What could I try ?

Thanks

Miner-ERR: caller":"miner/overseer.go:181","msg":"failed to decode container Stats","error":"EOF"

Hi,
after setting up everything i got this error msg

{"level":"info","ts":1497644086.9966042,"caller":"miner/server.go:46","msg":"got ping request from Hub"}
{"level":"info","ts":1497644087.3768384,"caller":"miner/server.go:168","msg":"yamux.Ping OK","rtt":0.3307154}
{"level":"info","ts":1497644092.2185774,"caller":"miner/server.go:168","msg":"yamux.Ping OK","rtt":0.1724198}
{"level":"info","ts":1497644096.9977195,"caller":"miner/server.go:46","msg":"got ping request from Hub"}
{"level":"info","ts":1497644097.380747,"caller":"miner/server.go:168","msg":"yamux.Ping OK","rtt":0.3344896}
{"level":"info","ts":1497644102.2202399,"caller":"miner/server.go:168","msg":"yamux.Ping OK","rtt":0.1739581}
{"level":"info","ts":1497644106.9966178,"caller":"miner/server.go:46","msg":"got ping request from Hub"}
{"level":"info","ts":1497644107.376295,"caller":"miner/server.go:168","msg":"yamux.Ping OK","rtt":0.3301447}
{"level":"info","ts":1497644112.218085,"caller":"miner/server.go:168","msg":"yamux.Ping OK","rtt":0.1718555}
{"level":"warn","ts":1497644116.6997435,"caller":"miner/overseer.go:181","msg":"failed to decode container Stats","error":"EOF"}
{"level":"warn","ts":1497644116.7002566,"caller":"miner/overseer.go:181","msg":"failed to decode container Stats","error":"EOF"}
{"level":"warn","ts":1497644116.7008421,"caller":"miner/overseer.go:181","msg":"failed to decode container Stats","error":"EOF"}
{"level":"warn","ts":1497644116.7013047,"caller":"miner/overseer.go:181","msg":"failed to decode container Stats","error":"EOF"}
{"level":"warn","ts":1497644116.70174,"caller":"miner/overseer.go:181","msg":"failed to decode container Stats","error":"EOF"}
{"level":"warn","ts":1497644116.702189,"caller":"miner/overseer.go:181","msg":"failed to decode container Stats","error":"EOF"}
{"level":"warn","ts":1497644116.702618,"caller":"miner/overseer.go:181","msg":"failed to decode container Stats","error":"EOF"}
{"level":"warn","ts":1497644116.7031195,"caller":"miner/overseer.go:181","msg":"failed to decode container Stats","error":"EOF"}
{"level":"warn","ts":1497644116.7034366,"caller":"miner/overseer.go:181","msg":"failed to decode container Stats","error":"EOF"}
{"level":"warn","ts":1497644116.7038846,"caller":"miner/overseer.go:181","msg":"failed to decode container Stats","error":"EOF"}

and btw your server @ 13.58.62.176:27960 is down ^^

Hub stores information about miners in a persistent storage

Proxy TCP traffic to/from Miner via Hub

Now Miner has multiplexed TCP connection to a Hub. We can use extra channels to proxy TCP traffic to/from the miner via Hub

Steps for naive solution:

Miner should detect NAT (look at #15)
If the miner needs proxy, the hub should listen a port, patch returned values to a CLI
when accept returns a connection, open new stream in the conn to Miner
transfer traffic through it.
all open listeners must be bound to a miner's context and task inside Hub to be properly disposed.
miner must transport actual info about lauched tasks

Suggested optimizations for naive userspace proxy solution: