ipfs-cluster/go.mod

105 lines
4.8 KiB
Modula-2
Raw Normal View History

2019-03-08 01:44:07 +00:00
module github.com/ipfs/ipfs-cluster
require (
2019-04-29 16:57:13 +00:00
contrib.go.opencensus.io/exporter/jaeger v0.1.0
contrib.go.opencensus.io/exporter/prometheus v0.1.0
Consensus: add new "crdt" consensus component This adds a new "crdt" consensus component using go-ds-crdt. This implies several refactors to fully make cluster consensus-component independent: * Delete mapstate and fully adopt dsstate (after people have migrated). * Return errors from state methods rather than ignoring them. * Add a new "datastore" modules so that we can configure datastores in the main configuration like other components. * Let the consensus components fully define the "state.State". Thus, they do not receive the state, they receive the storage where we put the state (a go-datastore). * Allow to customize how the monitor component obtains Peers() (the current peerset), including avoiding using the current peerset. At the moment the crdt consensus uses the monitoring component to define the current peerset. Therefore the monitor component cannot rely on the consensus component to produce a peerset. * Re-factor/re-implementation of "ipfs-cluster-service state" operations. Includes the dissapearance of the "migrate" one. The CRDT consensus component defines creates a crdt-datastore (with ipfs-lite) and uses it to intitialize a dssate. Thus the crdt-store is elegantly wrapped. Any modifications to the state get automatically replicated to other peers. We store all the CRDT DAG blocks in the local datastore. The consensus components only expose a ReadOnly state, as any modifications to the shared state should happen through them. DHT and PubSub facilities must now be created outside of Cluster and passed in so they can be re-used by different components.
2019-02-20 14:24:25 +00:00
github.com/AndreasBriese/bbloom v0.0.0-20190306092124-e2d15f34fcf9 // indirect
2019-05-16 10:37:00 +00:00
github.com/ajstarks/svgo v0.0.0-20181006003313-6ce6a3bcf6cd // indirect
2019-05-08 11:33:22 +00:00
github.com/armon/go-metrics v0.0.0-20190430140413-ec5e00d3c878 // indirect
2019-03-08 01:44:07 +00:00
github.com/blang/semver v3.5.1+incompatible
github.com/boltdb/bolt v1.3.1 // indirect
2019-04-29 15:26:22 +00:00
github.com/btcsuite/btcd v0.0.0-20190427004231-96897255fd17 // indirect
Consensus: add new "crdt" consensus component This adds a new "crdt" consensus component using go-ds-crdt. This implies several refactors to fully make cluster consensus-component independent: * Delete mapstate and fully adopt dsstate (after people have migrated). * Return errors from state methods rather than ignoring them. * Add a new "datastore" modules so that we can configure datastores in the main configuration like other components. * Let the consensus components fully define the "state.State". Thus, they do not receive the state, they receive the storage where we put the state (a go-datastore). * Allow to customize how the monitor component obtains Peers() (the current peerset), including avoiding using the current peerset. At the moment the crdt consensus uses the monitoring component to define the current peerset. Therefore the monitor component cannot rely on the consensus component to produce a peerset. * Re-factor/re-implementation of "ipfs-cluster-service state" operations. Includes the dissapearance of the "migrate" one. The CRDT consensus component defines creates a crdt-datastore (with ipfs-lite) and uses it to intitialize a dssate. Thus the crdt-store is elegantly wrapped. Any modifications to the state get automatically replicated to other peers. We store all the CRDT DAG blocks in the local datastore. The consensus components only expose a ReadOnly state, as any modifications to the shared state should happen through them. DHT and PubSub facilities must now be created outside of Cluster and passed in so they can be re-used by different components.
2019-02-20 14:24:25 +00:00
github.com/coreos/go-semver v0.3.0 // indirect
2019-04-29 15:26:22 +00:00
github.com/dgryski/go-farm v0.0.0-20190423205320-6a90982ecee2 // indirect
2019-03-08 01:44:07 +00:00
github.com/dustin/go-humanize v1.0.0
2019-05-16 10:37:00 +00:00
github.com/fogleman/gg v1.3.0 // indirect
2019-03-08 01:44:07 +00:00
github.com/gogo/protobuf v1.2.1
Consensus: add new "crdt" consensus component This adds a new "crdt" consensus component using go-ds-crdt. This implies several refactors to fully make cluster consensus-component independent: * Delete mapstate and fully adopt dsstate (after people have migrated). * Return errors from state methods rather than ignoring them. * Add a new "datastore" modules so that we can configure datastores in the main configuration like other components. * Let the consensus components fully define the "state.State". Thus, they do not receive the state, they receive the storage where we put the state (a go-datastore). * Allow to customize how the monitor component obtains Peers() (the current peerset), including avoiding using the current peerset. At the moment the crdt consensus uses the monitoring component to define the current peerset. Therefore the monitor component cannot rely on the consensus component to produce a peerset. * Re-factor/re-implementation of "ipfs-cluster-service state" operations. Includes the dissapearance of the "migrate" one. The CRDT consensus component defines creates a crdt-datastore (with ipfs-lite) and uses it to intitialize a dssate. Thus the crdt-store is elegantly wrapped. Any modifications to the state get automatically replicated to other peers. We store all the CRDT DAG blocks in the local datastore. The consensus components only expose a ReadOnly state, as any modifications to the shared state should happen through them. DHT and PubSub facilities must now be created outside of Cluster and passed in so they can be re-used by different components.
2019-02-20 14:24:25 +00:00
github.com/golang/protobuf v1.3.1
2019-05-08 11:33:22 +00:00
github.com/google/go-cmp v0.3.0 // indirect
github.com/google/uuid v1.1.1
2019-05-08 11:33:22 +00:00
github.com/gopherjs/gopherjs v0.0.0-20190430165422-3e4dfb77656c // indirect
2019-05-16 10:37:00 +00:00
github.com/gorilla/mux v1.7.2
2019-05-08 11:33:22 +00:00
github.com/hashicorp/go-msgpack v0.5.5 // indirect
2019-03-08 01:44:07 +00:00
github.com/hashicorp/go-uuid v1.0.1 // indirect
2019-04-29 15:26:22 +00:00
github.com/hashicorp/raft v1.0.1
2019-03-08 01:44:07 +00:00
github.com/hashicorp/raft-boltdb v0.0.0-20171010151810-6e5ba93211ea
Consensus: add new "crdt" consensus component This adds a new "crdt" consensus component using go-ds-crdt. This implies several refactors to fully make cluster consensus-component independent: * Delete mapstate and fully adopt dsstate (after people have migrated). * Return errors from state methods rather than ignoring them. * Add a new "datastore" modules so that we can configure datastores in the main configuration like other components. * Let the consensus components fully define the "state.State". Thus, they do not receive the state, they receive the storage where we put the state (a go-datastore). * Allow to customize how the monitor component obtains Peers() (the current peerset), including avoiding using the current peerset. At the moment the crdt consensus uses the monitoring component to define the current peerset. Therefore the monitor component cannot rely on the consensus component to produce a peerset. * Re-factor/re-implementation of "ipfs-cluster-service state" operations. Includes the dissapearance of the "migrate" one. The CRDT consensus component defines creates a crdt-datastore (with ipfs-lite) and uses it to intitialize a dssate. Thus the crdt-store is elegantly wrapped. Any modifications to the state get automatically replicated to other peers. We store all the CRDT DAG blocks in the local datastore. The consensus components only expose a ReadOnly state, as any modifications to the shared state should happen through them. DHT and PubSub facilities must now be created outside of Cluster and passed in so they can be re-used by different components.
2019-02-20 14:24:25 +00:00
github.com/hsanjuan/go-libp2p-gostream v0.0.31
github.com/hsanjuan/go-libp2p-http v0.0.2
2019-04-29 15:26:22 +00:00
github.com/hsanjuan/ipfs-lite v0.0.3
2019-05-08 11:33:22 +00:00
github.com/ipfs/go-bitswap v0.0.5 // indirect
2019-03-08 01:44:07 +00:00
github.com/ipfs/go-block-format v0.0.2
2019-05-16 10:37:00 +00:00
github.com/ipfs/go-cid v0.0.2
2019-04-29 15:26:22 +00:00
github.com/ipfs/go-datastore v0.0.5
Consensus: add new "crdt" consensus component This adds a new "crdt" consensus component using go-ds-crdt. This implies several refactors to fully make cluster consensus-component independent: * Delete mapstate and fully adopt dsstate (after people have migrated). * Return errors from state methods rather than ignoring them. * Add a new "datastore" modules so that we can configure datastores in the main configuration like other components. * Let the consensus components fully define the "state.State". Thus, they do not receive the state, they receive the storage where we put the state (a go-datastore). * Allow to customize how the monitor component obtains Peers() (the current peerset), including avoiding using the current peerset. At the moment the crdt consensus uses the monitoring component to define the current peerset. Therefore the monitor component cannot rely on the consensus component to produce a peerset. * Re-factor/re-implementation of "ipfs-cluster-service state" operations. Includes the dissapearance of the "migrate" one. The CRDT consensus component defines creates a crdt-datastore (with ipfs-lite) and uses it to intitialize a dssate. Thus the crdt-store is elegantly wrapped. Any modifications to the state get automatically replicated to other peers. We store all the CRDT DAG blocks in the local datastore. The consensus components only expose a ReadOnly state, as any modifications to the shared state should happen through them. DHT and PubSub facilities must now be created outside of Cluster and passed in so they can be re-used by different components.
2019-02-20 14:24:25 +00:00
github.com/ipfs/go-ds-badger v0.0.3
github.com/ipfs/go-ds-crdt v0.0.7
2019-03-08 01:44:07 +00:00
github.com/ipfs/go-fs-lock v0.0.1
github.com/ipfs/go-ipfs-api v0.0.1
Consensus: add new "crdt" consensus component This adds a new "crdt" consensus component using go-ds-crdt. This implies several refactors to fully make cluster consensus-component independent: * Delete mapstate and fully adopt dsstate (after people have migrated). * Return errors from state methods rather than ignoring them. * Add a new "datastore" modules so that we can configure datastores in the main configuration like other components. * Let the consensus components fully define the "state.State". Thus, they do not receive the state, they receive the storage where we put the state (a go-datastore). * Allow to customize how the monitor component obtains Peers() (the current peerset), including avoiding using the current peerset. At the moment the crdt consensus uses the monitoring component to define the current peerset. Therefore the monitor component cannot rely on the consensus component to produce a peerset. * Re-factor/re-implementation of "ipfs-cluster-service state" operations. Includes the dissapearance of the "migrate" one. The CRDT consensus component defines creates a crdt-datastore (with ipfs-lite) and uses it to intitialize a dssate. Thus the crdt-store is elegantly wrapped. Any modifications to the state get automatically replicated to other peers. We store all the CRDT DAG blocks in the local datastore. The consensus components only expose a ReadOnly state, as any modifications to the shared state should happen through them. DHT and PubSub facilities must now be created outside of Cluster and passed in so they can be re-used by different components.
2019-02-20 14:24:25 +00:00
github.com/ipfs/go-ipfs-blockstore v0.0.1
2019-03-08 01:44:07 +00:00
github.com/ipfs/go-ipfs-chunker v0.0.1
2019-05-08 11:33:22 +00:00
github.com/ipfs/go-ipfs-config v0.0.3 // indirect
2019-03-08 01:44:07 +00:00
github.com/ipfs/go-ipfs-ds-help v0.0.1
2019-04-29 15:26:22 +00:00
github.com/ipfs/go-ipfs-files v0.0.3
2019-03-08 01:44:07 +00:00
github.com/ipfs/go-ipfs-posinfo v0.0.1
github.com/ipfs/go-ipfs-util v0.0.1
2019-05-16 10:37:00 +00:00
github.com/ipfs/go-ipld-cbor v0.0.2
github.com/ipfs/go-ipld-format v0.0.2
2019-03-08 01:44:07 +00:00
github.com/ipfs/go-log v0.0.1
Consensus: add new "crdt" consensus component This adds a new "crdt" consensus component using go-ds-crdt. This implies several refactors to fully make cluster consensus-component independent: * Delete mapstate and fully adopt dsstate (after people have migrated). * Return errors from state methods rather than ignoring them. * Add a new "datastore" modules so that we can configure datastores in the main configuration like other components. * Let the consensus components fully define the "state.State". Thus, they do not receive the state, they receive the storage where we put the state (a go-datastore). * Allow to customize how the monitor component obtains Peers() (the current peerset), including avoiding using the current peerset. At the moment the crdt consensus uses the monitoring component to define the current peerset. Therefore the monitor component cannot rely on the consensus component to produce a peerset. * Re-factor/re-implementation of "ipfs-cluster-service state" operations. Includes the dissapearance of the "migrate" one. The CRDT consensus component defines creates a crdt-datastore (with ipfs-lite) and uses it to intitialize a dssate. Thus the crdt-store is elegantly wrapped. Any modifications to the state get automatically replicated to other peers. We store all the CRDT DAG blocks in the local datastore. The consensus components only expose a ReadOnly state, as any modifications to the shared state should happen through them. DHT and PubSub facilities must now be created outside of Cluster and passed in so they can be re-used by different components.
2019-02-20 14:24:25 +00:00
github.com/ipfs/go-merkledag v0.0.3
2019-05-16 10:37:00 +00:00
github.com/ipfs/go-mfs v0.0.7
Consensus: add new "crdt" consensus component This adds a new "crdt" consensus component using go-ds-crdt. This implies several refactors to fully make cluster consensus-component independent: * Delete mapstate and fully adopt dsstate (after people have migrated). * Return errors from state methods rather than ignoring them. * Add a new "datastore" modules so that we can configure datastores in the main configuration like other components. * Let the consensus components fully define the "state.State". Thus, they do not receive the state, they receive the storage where we put the state (a go-datastore). * Allow to customize how the monitor component obtains Peers() (the current peerset), including avoiding using the current peerset. At the moment the crdt consensus uses the monitoring component to define the current peerset. Therefore the monitor component cannot rely on the consensus component to produce a peerset. * Re-factor/re-implementation of "ipfs-cluster-service state" operations. Includes the dissapearance of the "migrate" one. The CRDT consensus component defines creates a crdt-datastore (with ipfs-lite) and uses it to intitialize a dssate. Thus the crdt-store is elegantly wrapped. Any modifications to the state get automatically replicated to other peers. We store all the CRDT DAG blocks in the local datastore. The consensus components only expose a ReadOnly state, as any modifications to the shared state should happen through them. DHT and PubSub facilities must now be created outside of Cluster and passed in so they can be re-used by different components.
2019-02-20 14:24:25 +00:00
github.com/ipfs/go-path v0.0.3
2019-04-29 15:26:22 +00:00
github.com/ipfs/go-unixfs v0.0.5
2019-05-16 10:37:00 +00:00
github.com/jbenet/goprocess v0.1.3 // indirect
github.com/jung-kurt/gofpdf v1.4.1 // indirect
2019-03-08 01:44:07 +00:00
github.com/kelseyhightower/envconfig v1.3.0
2019-05-08 11:33:22 +00:00
github.com/lanzafame/go-libp2p-ocgorpc v0.0.2
2019-05-16 10:37:00 +00:00
github.com/libp2p/go-libp2p v0.0.23
2019-03-08 01:44:07 +00:00
github.com/libp2p/go-libp2p-consensus v0.0.1
2019-05-08 11:33:22 +00:00
github.com/libp2p/go-libp2p-crypto v0.0.2
2019-03-08 01:44:07 +00:00
github.com/libp2p/go-libp2p-gorpc v0.0.2
2019-05-08 11:33:22 +00:00
github.com/libp2p/go-libp2p-host v0.0.3
2019-03-08 01:44:07 +00:00
github.com/libp2p/go-libp2p-interface-pnet v0.0.1
2019-04-29 15:26:22 +00:00
github.com/libp2p/go-libp2p-kad-dht v0.0.10
2019-05-16 10:37:00 +00:00
github.com/libp2p/go-libp2p-peer v0.1.1
2019-04-29 15:26:22 +00:00
github.com/libp2p/go-libp2p-peerstore v0.0.5
2019-03-08 01:44:07 +00:00
github.com/libp2p/go-libp2p-pnet v0.0.1
github.com/libp2p/go-libp2p-protocol v0.0.1
2019-05-16 10:37:00 +00:00
github.com/libp2p/go-libp2p-pubsub v0.0.3
2019-03-08 01:44:07 +00:00
github.com/libp2p/go-libp2p-raft v0.0.2
2019-05-16 10:37:00 +00:00
github.com/libp2p/go-maddr-filter v0.0.3 // indirect
github.com/libp2p/go-mplex v0.0.2 // indirect
Consensus: add new "crdt" consensus component This adds a new "crdt" consensus component using go-ds-crdt. This implies several refactors to fully make cluster consensus-component independent: * Delete mapstate and fully adopt dsstate (after people have migrated). * Return errors from state methods rather than ignoring them. * Add a new "datastore" modules so that we can configure datastores in the main configuration like other components. * Let the consensus components fully define the "state.State". Thus, they do not receive the state, they receive the storage where we put the state (a go-datastore). * Allow to customize how the monitor component obtains Peers() (the current peerset), including avoiding using the current peerset. At the moment the crdt consensus uses the monitoring component to define the current peerset. Therefore the monitor component cannot rely on the consensus component to produce a peerset. * Re-factor/re-implementation of "ipfs-cluster-service state" operations. Includes the dissapearance of the "migrate" one. The CRDT consensus component defines creates a crdt-datastore (with ipfs-lite) and uses it to intitialize a dssate. Thus the crdt-store is elegantly wrapped. Any modifications to the state get automatically replicated to other peers. We store all the CRDT DAG blocks in the local datastore. The consensus components only expose a ReadOnly state, as any modifications to the shared state should happen through them. DHT and PubSub facilities must now be created outside of Cluster and passed in so they can be re-used by different components.
2019-02-20 14:24:25 +00:00
github.com/libp2p/go-ws-transport v0.0.2
2019-03-08 01:44:07 +00:00
github.com/multiformats/go-multiaddr v0.0.2
github.com/multiformats/go-multiaddr-dns v0.0.2
github.com/multiformats/go-multiaddr-net v0.0.1
github.com/multiformats/go-multicodec v0.1.6
2019-04-29 15:26:22 +00:00
github.com/multiformats/go-multihash v0.0.5
Consensus: add new "crdt" consensus component This adds a new "crdt" consensus component using go-ds-crdt. This implies several refactors to fully make cluster consensus-component independent: * Delete mapstate and fully adopt dsstate (after people have migrated). * Return errors from state methods rather than ignoring them. * Add a new "datastore" modules so that we can configure datastores in the main configuration like other components. * Let the consensus components fully define the "state.State". Thus, they do not receive the state, they receive the storage where we put the state (a go-datastore). * Allow to customize how the monitor component obtains Peers() (the current peerset), including avoiding using the current peerset. At the moment the crdt consensus uses the monitoring component to define the current peerset. Therefore the monitor component cannot rely on the consensus component to produce a peerset. * Re-factor/re-implementation of "ipfs-cluster-service state" operations. Includes the dissapearance of the "migrate" one. The CRDT consensus component defines creates a crdt-datastore (with ipfs-lite) and uses it to intitialize a dssate. Thus the crdt-store is elegantly wrapped. Any modifications to the state get automatically replicated to other peers. We store all the CRDT DAG blocks in the local datastore. The consensus components only expose a ReadOnly state, as any modifications to the shared state should happen through them. DHT and PubSub facilities must now be created outside of Cluster and passed in so they can be re-used by different components.
2019-02-20 14:24:25 +00:00
github.com/onsi/ginkgo v1.8.0 // indirect
github.com/onsi/gomega v1.5.0 // indirect
github.com/pkg/errors v0.8.1
github.com/polydawn/refmt v0.0.0-20190408063855-01bf1e26dd14 // indirect
2019-05-16 10:37:00 +00:00
github.com/prometheus/client_golang v0.9.3
github.com/prometheus/procfs v0.0.0-20190516194456-169873baca24 // indirect
2019-03-08 01:44:07 +00:00
github.com/rs/cors v1.6.0
Consensus: add new "crdt" consensus component This adds a new "crdt" consensus component using go-ds-crdt. This implies several refactors to fully make cluster consensus-component independent: * Delete mapstate and fully adopt dsstate (after people have migrated). * Return errors from state methods rather than ignoring them. * Add a new "datastore" modules so that we can configure datastores in the main configuration like other components. * Let the consensus components fully define the "state.State". Thus, they do not receive the state, they receive the storage where we put the state (a go-datastore). * Allow to customize how the monitor component obtains Peers() (the current peerset), including avoiding using the current peerset. At the moment the crdt consensus uses the monitoring component to define the current peerset. Therefore the monitor component cannot rely on the consensus component to produce a peerset. * Re-factor/re-implementation of "ipfs-cluster-service state" operations. Includes the dissapearance of the "migrate" one. The CRDT consensus component defines creates a crdt-datastore (with ipfs-lite) and uses it to intitialize a dssate. Thus the crdt-store is elegantly wrapped. Any modifications to the state get automatically replicated to other peers. We store all the CRDT DAG blocks in the local datastore. The consensus components only expose a ReadOnly state, as any modifications to the shared state should happen through them. DHT and PubSub facilities must now be created outside of Cluster and passed in so they can be re-used by different components.
2019-02-20 14:24:25 +00:00
github.com/smartystreets/assertions v0.0.0-20190401211740-f487f9de1cd3 // indirect
github.com/smartystreets/goconvey v0.0.0-20190330032615-68dc04aab96a // indirect
2019-04-29 15:26:22 +00:00
github.com/ugorji/go v1.1.4
2019-03-08 01:44:07 +00:00
github.com/urfave/cli v1.20.0
Consensus: add new "crdt" consensus component This adds a new "crdt" consensus component using go-ds-crdt. This implies several refactors to fully make cluster consensus-component independent: * Delete mapstate and fully adopt dsstate (after people have migrated). * Return errors from state methods rather than ignoring them. * Add a new "datastore" modules so that we can configure datastores in the main configuration like other components. * Let the consensus components fully define the "state.State". Thus, they do not receive the state, they receive the storage where we put the state (a go-datastore). * Allow to customize how the monitor component obtains Peers() (the current peerset), including avoiding using the current peerset. At the moment the crdt consensus uses the monitoring component to define the current peerset. Therefore the monitor component cannot rely on the consensus component to produce a peerset. * Re-factor/re-implementation of "ipfs-cluster-service state" operations. Includes the dissapearance of the "migrate" one. The CRDT consensus component defines creates a crdt-datastore (with ipfs-lite) and uses it to intitialize a dssate. Thus the crdt-store is elegantly wrapped. Any modifications to the state get automatically replicated to other peers. We store all the CRDT DAG blocks in the local datastore. The consensus components only expose a ReadOnly state, as any modifications to the shared state should happen through them. DHT and PubSub facilities must now be created outside of Cluster and passed in so they can be re-used by different components.
2019-02-20 14:24:25 +00:00
github.com/warpfork/go-wish v0.0.0-20190328234359-8b3e70f8e830 // indirect
2019-03-08 01:44:07 +00:00
github.com/zenground0/go-dot v0.0.0-20180912213407-94a425d4984e
2019-04-29 15:26:22 +00:00
go.opencensus.io v0.21.0
go4.org v0.0.0-20190313082347-94abd6928b1d // indirect
2019-05-16 10:37:00 +00:00
golang.org/x/crypto v0.0.0-20190513172903-22d7a77e9e5f // indirect
golang.org/x/exp v0.0.0-20190510132918-efd6b22b2522 // indirect
golang.org/x/image v0.0.0-20190516052701-61b8692d9a5c // indirect
golang.org/x/net v0.0.0-20190514140710-3ec191127204 // indirect
2019-05-08 11:33:22 +00:00
golang.org/x/sync v0.0.0-20190423024810-112230192c58 // indirect
2019-05-16 10:37:00 +00:00
golang.org/x/sys v0.0.0-20190516110030-61b9204099cb // indirect
2019-04-29 15:26:22 +00:00
golang.org/x/text v0.3.2 // indirect
2019-05-16 10:37:00 +00:00
golang.org/x/xerrors v0.0.0-20190513163551-3ee3066db522 // indirect
gonum.org/v1/gonum v0.0.0-20190517105223-d76380b39392
gonum.org/v1/netlib v0.0.0-20190331212654-76723241ea4e // indirect
gonum.org/v1/plot v0.0.0-20190515093506-e2840ee46a6b
2019-05-16 10:37:00 +00:00
google.golang.org/api v0.5.0 // indirect
google.golang.org/genproto v0.0.0-20190516172635-bb713bdc0e52 // indirect
2019-03-08 01:44:07 +00:00
)