Go to file
Hector Sanjuan b388a45e92 Merge pull request #33 from ipfs/20-deps-mgmt
Dependency management: gx all deps + fetch gx from dist.ifps.io

Fixes #20.
2017-01-25 12:56:09 +01:00
ipfs-cluster-ctl Use urfave/cli for ipfs-cluster-service too. 2017-01-24 19:55:06 +01:00
ipfs-cluster-service Use urfave/cli for ipfs-cluster-service too. 2017-01-24 19:55:06 +01:00
.gitignore Issue #20: Download a local installation of gx 2017-01-25 12:48:16 +01:00
.travis.yml Fix #5: Rename apps to ipfs-cluster-service and ipfs-cluster-ctl 2017-01-23 13:34:22 +01:00
architecture.md Update go-libp2p-gorpc 2017-01-25 12:50:46 +01:00
captain.log.md Fix #27: Add captain's log and ROADMAP 2017-01-23 13:16:20 +01:00
cluster_test.go Update go-libp2p-gorpc 2017-01-25 12:50:46 +01:00
cluster.go Update go-libp2p-gorpc 2017-01-25 12:50:46 +01:00
config_test.go Fix tests with raftCfg config section and do not panic if its not there 2017-01-23 21:07:16 +01:00
config.go Fix tests with raftCfg config section and do not panic if its not there 2017-01-23 21:07:16 +01:00
consensus_test.go Merge pull request #29 from ipfs/25-leader-comm 2017-01-24 01:13:42 +01:00
consensus.go Update go-libp2p-gorpc 2017-01-25 12:50:46 +01:00
debug.go Unbuffered channel explains hanging issues. 2016-12-19 19:40:17 +01:00
ipfs_http_connector_test.go Use multiaddresses in the configuration and rename JSON entries for clarity 2017-01-23 18:38:59 +01:00
ipfs_http_connector.go Update go-libp2p-gorpc 2017-01-25 12:50:46 +01:00
ipfscluster_test.go global status and global sync should not error when a node is down 2017-01-24 00:54:26 +01:00
ipfscluster.go Update go-libp2p-gorpc 2017-01-25 12:50:46 +01:00
ipfsmock_test.go Get remote RPC requests working. First e2e tests. 2016-12-16 22:00:08 +01:00
LICENSE ipfscluster-server executable 2016-12-21 19:37:25 +01:00
Makefile Try to fix gx-go not rewriting correctly 2017-01-25 12:50:05 +01:00
map_pin_tracker.go Update go-libp2p-gorpc 2017-01-25 12:50:46 +01:00
map_state.go Make golint happy 2016-12-28 16:29:07 +01:00
nodebug.go Unbuffered channel explains hanging issues. 2016-12-19 19:40:17 +01:00
package.json Update go-libp2p-gorpc 2017-01-25 12:50:46 +01:00
raft.go A raft-boltdb import was permanently gx'ed 2017-01-25 12:50:46 +01:00
README.md Address formatting, mispellings, lint errors from goreportcard 2017-01-24 12:39:08 +01:00
rest_api_test.go Issue-21: Add cluster ID() method 2017-01-24 16:26:42 +01:00
rest_api.go Update go-libp2p-gorpc 2017-01-25 12:50:46 +01:00
ROADMAP.md Fix #27: Add captain's log and ROADMAP 2017-01-23 13:16:20 +01:00
rpc_api_test.go Update go-libp2p-gorpc 2017-01-25 12:50:46 +01:00
rpc_api.go Update go-libp2p-gorpc 2017-01-25 12:50:46 +01:00
silent.go Figured out globalSync and globalSync cid. Tests. More tests. 2016-12-20 19:51:13 +01:00
version.go Make sure the commit string gets set. Fix PublicKey. Output JSON in cluster-ctl 2017-01-24 16:56:14 +01:00

ipfs-cluster

standard-readme compliant GoDoc Go Report Card Build Status Coverage Status

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, cluster nodes act as a proxy/wrapper to the IPFS API, so they can be used as a regular node, with the difference that pin requests are handled by the Cluster.

IPFS Cluster provides a cluster-node application (ipfs-cluster-service), a Go API, a HTTP API and a command-line tool (ipfs-cluster-ctl).

Current functionality only allows pinning in all cluster members, but more strategies (like setting a replication factor for each pin) will be developed.

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, recovery and implementation of advanced 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 knows which content is tracked, can decide whether asking IPFS to pin it and can react to any contingencies like node reboots.

Captain

This project is captained by @hsanjuan. See the captain's log for information about current status and upcoming features. You can also check out the project's Roadmap.

Install

In order to install the ipfs-cluster-service the ipfs-cluster-ctl tool simply download this repository and run make as follows:

$ go get -u -d github.com/ipfs/ipfs-cluster
$ cd $GOPATH/src/github.com/ipfs/ipfs-cluster
$ make install

This will install ipfs-cluster-service and ipfs-cluster-ctl in your $GOPATH/bin folder.

Usage

ipfs-cluster-service

ipfs-cluster-service runs a member node for the cluster. Usage information can be obtained running:

$ ipfs-cluster-service -h

Before running ipfs-cluster-service for the first time, initialize a configuration file with:

$ ipfs-cluster-service -init

The configuration will be placed in ~/.ipfs-cluster/service.json by default.

You can add the multiaddresses for the other members of the cluster in the cluster_peers variable. For example, here is a valid configuration for a cluster of 4 members:

{
    "id": "QmSGCzHkz8gC9fNndMtaCZdf9RFtwtbTEEsGo4zkVfcykD",
    "private_key" : "<redacted>",
    "cluster_peers" : [
          "/ip4/192.168.1.2/tcp/9096/ipfs/QmcQ5XvrSQ4DouNkQyQtEoLczbMr6D9bSenGy6WQUCQUBt",
          "/ip4/192.168.1.3/tcp/9096/ipfs/QmdFBMf9HMDH3eCWrc1U11YCPenC3Uvy9mZQ2BedTyKTDf",
          "/ip4/192.168.1.4/tcp/9096/ipfs/QmYY1ggjoew5eFrvkenTR3F4uWqtkBkmgfJk8g9Qqcwy51",
          "/ip4/192.168.1.5/tcp/9096/ipfs/QmSGCzHkz8gC9fNndMtaCZdf9RFtwtbTEEsGo4zkVfcykD"
          ],
    "cluster_multiaddress": "/ip4/0.0.0.0/tcp/9096",
    "api_listen_multiaddress": "/ip4/127.0.0.1/tcp/9094",
    "ipfs_proxy_listen_multiaddress": "/ip4/127.0.0.1/tcp/9095",
    "ipfs_node_multiaddress": "/ip4/127.0.0.1/tcp/5001",
    "consensus_data_folder": "/home/user/.ipfs-cluster/data",
    "raft_config": {
        "snapshot_interval_seconds": 120,
        "enable_single_node": true
    }

The configuration file should probably be identical among all cluster members, except for the id and private_key fields. To facilitate configuration, cluster_peers may include its own address, but it does not have to. For additional information about the configuration format, see the JSONConfig documentation.

Once every cluster member has the configuration in place, you can run ipfs-cluster-service to start the cluster.

ipfs-cluster-ctl

ipfs-cluster-ctl is the client application to manage the cluster nodes and perform actions. ipfs-cluster-ctl uses the HTTP API provided by the nodes.

After installing, you can run ipfs-cluster-ctl --help to display general description and options, or alternatively ipfs-cluster-ctl help [cmd] to display information about supported commands.

In summary, it works as follows:

$ ipfs-cluster-ctl member ls                                                # list cluster members
$ ipfs-cluster-ctl pin add Qma4Lid2T1F68E3Xa3CpE6vVJDLwxXLD8RfiB9g1Tmqp58   # pins a Cid in the cluster
$ ipfs-cluster-ctl pin rm Qma4Lid2T1F68E3Xa3CpE6vVJDLwxXLD8RfiB9g1Tmqp58    # unpins a Cid from the cluster
$ ipfs-cluster-ctl status                                                   # display tracked Cids information
$ ipfs-cluster-ctl sync Qma4Lid2T1F68E3Xa3CpE6vVJDLwxXLD8RfiB9g1Tmqp58      # recover Cids in error status

Go

IPFS Cluster nodes can be launched directly from Go. The Cluster object provides methods to interact with the cluster and perform actions.

Documentation and examples on how to use IPFS Cluster from Go can be found in godoc.org/github.com/ipfs/ipfs-cluster.

API

TODO: Swagger

Contribute

PRs accepted.

Small note: If editing the README, please conform to the standard-readme specification.

License

MIT © Protocol Labs, Inc.