Make the volume API simple/standard

[ctengel]

Right now it is a hasty JSON. We should look to S3 or WebDAV where simple HTTP/REST is not clear

[ctengel]

As we do enhancements #2 #4 #8 around node status, disk free, metadata we want to have this

[ctengel]

emulating webdav LISTPROP is pointless

S3 ListObjects we are already not far off from (already using size for instance) Main things to add would be checksum and mime type

there should be a single status endpoint with

• status - readonly, readwrite, notready (i.e. coming online, or still processing old requests, send no new requests)
• volume size
• volume free

(these not covered by S3; per WebDAV we could use quota-used-bytes and quota-available-bytes

Other things on objects themselves will use standard HTTP headers:

• Range
• Content-Type
• Content-Digest
• Content-Length

I think that's really it. It's not complicated; there's less in common with S3 and WebDAV than originally thought think main thing still left to do in this issue is put together an OpenAPI spec for the handful of endpoints we support:

• GET /bucket
• GET /bucket/object
• PUT /bucket/object
• GET /health

The locator API is largely similar, mainly add info on number of replicas, and more 307s.... maybe add replicas: 1 to each volserve response.