7e71986493
Today each storagenode should have a port which is opened for the internet, and handles DRPC protocol calls. When we do a HTTP call on the DRPC endpoint, it hangs until a timeout. This patch changes the behavior: the main DRPC port of the storagenodes can accept HTTP requests and can be used to monitor the status of the node: * if returns with HTTP 200 only if the storagnode is healthy (not suspended / disqualified + online score > 0.9) * it CAN include information about the current status (per satellite). It's opt-in, you should configure it so. In this way it becomes extremely easy to monitor storagenodes with external uptime services. Note: this patch exposes some information which was not easily available before (especially the node status, and used satellites). I think it should be acceptable: * Until having more community satellites, all storagenodes are connected to the main Storj satellites. * With community satellites, it's good thing to have more transparency (easy way to check who is connected to which satellites) The implementation is based on this line: ``` http.Serve(NewPrefixedListener([]byte("GET / HT"), publicMux.Route("GET / HT")), p.public.http) ``` This line answers to the TCP requests with `GET / HT...` (GET HTTP request to the route), but puts back the removed prefix. Change-Id: I3700c7e24524850825ecdf75a4bcc3b4afcb3a74 |
||
---|---|---|
.github | ||
certificate | ||
cmd | ||
crashcollect | ||
docs | ||
installer/windows | ||
multinode | ||
private | ||
resources | ||
satellite | ||
scripts | ||
storage | ||
storagenode | ||
testsuite | ||
versioncontrol | ||
web | ||
.dockerignore | ||
.gitattributes | ||
.gitignore | ||
.gitreview | ||
CODE_OF_CONDUCT.md | ||
CODEOWNERS | ||
CONTRIBUTING.md | ||
DEVELOPING.md | ||
docker-compose.tests.yaml | ||
go.mod | ||
go.sum | ||
Jenkinsfile | ||
Jenkinsfile.premerge | ||
Jenkinsfile.public | ||
Jenkinsfile.verify | ||
LICENSE | ||
MAINTAINERS.md | ||
Makefile | ||
monkit.lock | ||
proto.lock | ||
README.md |
Storj V3 Network
Storj is building a decentralized cloud storage network. Check out our white paper for more info!
Storj is an S3-compatible platform and suite of decentralized applications that allows you to store data in a secure and decentralized manner. Your files are encrypted, broken into little pieces and stored in a global decentralized network of computers. Luckily, we also support allowing you (and only you) to retrieve those files!
Table of Contents
Contributing to Storj
All of our code for Storj v3 is open source. If anything feels off, or if you feel that some functionality is missing, please check out the contributing page. There you will find instructions for sharing your feedback, building the tool locally, and submitting pull requests to the project.
A Note about Versioning
While we are practicing semantic versioning for our client libraries such as uplink, we are not practicing semantic versioning in this repo, as we do not intend for it to be used via Go modules. We may have backwards-incompatible changes between minor and patch releases in this repo.
Start using Storj
Our wiki has documentation and tutorials. Check out these three tutorials:
License
This repository is currently licensed with the AGPLv3 license.
For code released under the AGPLv3, we request that contributors sign our Contributor License Agreement (CLA) so that we can relicense the code under Apache v2, or other licenses in the future.
Support
If you have any questions or suggestions please reach out to us on our community forum or file a ticket at https://support.storj.io/.