319c97585b
Start preparing syncs() and status() License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai> |
||
|---|---|---|
| ipfs-cluster | ||
| .travis.yml | ||
| api_test.go | ||
| api.go | ||
| cluster_test.go | ||
| cluster.go | ||
| component.go | ||
| config_test.go | ||
| config.go | ||
| consensus_test.go | ||
| consensus.go | ||
| illustrations.md | ||
| ipfs_cluster_test.go | ||
| ipfs_cluster.go | ||
| ipfs_connector_test.go | ||
| ipfs_connector.go | ||
| LICENSE | ||
| Makefile | ||
| package.json | ||
| raft.go | ||
| README.md | ||
| response.go | ||
| rpc_test.go | ||
| rpc.go | ||
| state.go | ||
| TODO.md | ||
| tracker.go | ||
ipfs-cluster
Clustering for IPFS nodes.
WORK IN PROGRESS
DO NOT USE IN PRODUCTION
ipfs-cluster is a tool which groups a number of IPFS nodes together, allowing to collectively perform operations such as pinning.
In order to do so ipfs-cluster nodes use a libp2p-based consensus algorithm (currently Raft) to agree on a log of operations and build a consistent state across the cluster. The state represents which objects should be pinned by which nodes.
Additionally, ipfs-cluster nodes act as a proxy/wrapper to the IPFS API, so an IPFS cluster can be used as a regular node.
ipfs-cluster provides a Go API, an equivalent HTTP API (in a RESTful fashion) and a command-line interface tool (ipfs-cluster-ctl) which plugs directly into it.
Table of Contents
Background
Since the start of IPFS it was clear that a tool to coordinate a number of different nodes (and the content they are supposed to store) would add a great value to the IPFS ecosystem. Naïve approaches are possible, but they present some weaknesses, specially at dealing with error handling and incorporating multiple pinning strategies.
ipfs-cluster aims to address this issues by providing a IPFS node wrapper which coordinates multiple cluster members via a consensus algorithm. This ensures that the desired state of the system is always agreed upon and can be easily maintained by the members of the cluster. Thus, every cluster member has an overview of where each hash is pinned, and the cluster can react to any contingencies, like IPFS nodes dying, by redistributing the storage load to others.
Install
TODO
Usage
The documentation and examples for ipfs-cluster (useful if you are integrating it in Go) can be found in godoc.org/github.com/ipfs/ipfs-cluster.
TODO
API
TODO
Contribute
PRs accepted.
Small note: If editing the README, please conform to the standard-readme specification.
License
MIT © Protocol Labs, Inc.