Peer allocation strategies: Disk-space Informer and Allocator and other strategies about ipfs-cluster

[hsanjuan]

@20zinnm you were looking for ways to contribute? Would you like to take at stab at this? It is a good starting point to get familiar with Cluster.

[meyerzinn]

I can take a look at it @hsanjuan.

[meyerzinn]

@hsanjuan To be clear, does creating a new Informer/Allocator include implementing it, or can clusters deal with incompatibilities?

[meyerzinn]

Also, I think we need to clean up the project layout.

[hsanjuan]

@20zinnm What do you mean incompatibilities?

And yes, creating means implementing it.

[meyerzinn]

So what, exactly, do I need to implement?
I followed the chain and figured I needed to update (a) the rpc, (b) the HTTP server. Am I missing something? @hsanjuan

[hsanjuan]

@20zinnm no, you just need create two modules, one Allocator and one Informer which implement the respective interfaces as the numpinalloc and numpin do. You don't need to worry about anything else in Cluster. Everything is linked above. These modules should cluster to work with a disk-space allocation strategy which would pin to the peers with more free space.

[meyerzinn]

@hsanjuan So say I'd like to make a capacity informer to allow peers to broadcast a quantifiable capacity. Would I then need to add to the protocol?

[hsanjuan]

@20zinnm you just need to implement the informer and the allocator. The informer has a GetMetric() method which gets regularly called.