Archive storage config API

[asutula]

Allows getting and setting the default ArchiveConfig per Bucket and allows you to pass an override ArchiveConfig with each call to Archive.

Updates everything from mongo, rpc, client, local buckets api, and cli.

closes #336
closes #339

[asutula]

Ok getting a legit error in the integration test TestArchiveBucketWorkflow. The error is:

executing cold-storage config: making deal configs: getting miners from minerselector: not enough miners that satisfy the constraints

@jsign just checking if there is something we need to change about the lotus devnet and/or powergate setup in here? Anything come to mind?

[asutula]

Updated the compose file to powergate 0.6.6 and lotus-devnet sha-35afaa3 and now the error is:

executing cold-storage config: all proposals were rejected

[jsign]

Ok getting a legit error in the integration test TestArchiveBucketWorkflow. The error is:

executing cold-storage config: making deal configs: getting miners from minerselector: not enough miners that satisfy the constraints

@jsign just checking if there is something we need to change about the lotus devnet and/or powergate setup in here? Anything come to mind?

Yes, most probably is related to forcing Peter's miners in the version of Powergate you've updated. Now that in v0.6.6 we switched to SR2 miner selector by default, might make sense again to have the original StorageConfig which doesn't have a replication factor of 5, which is my best guess about that error.
So the idea would be:

• Revert to the original StorageConfig with rep facto 1 and without trusted miners.
• Set explicitly for tests here to use --ffsminerselector=reputation, since now the default is sr2.

I can confirm this theory on Monday, but makes sense to me.
BTW, might require a new tag in Powergate and bubble up here.

[asutula]

Thanks @jsign. That gives me a path forward. Will dig in more later.

[jsign]

LGTM! I left some questions in the wild.

[sanderpick]

LGTM! I left a bunch of nits, but otherwise looks solid.