Object server

[ctengel]

Possibly rewrite or replace altogether - our semantics are similar to S3 or WebDAV

Requirements

• Support Range request for get (useful for Web browser video playback)
• Don't load the whole file on GET or PUT (i.e. don't max out server memory)
• List out contents
• Disk free (so "locator" can query to see if there is enough space before redirecting a PUT here)
• Status/Health (can be future, allows read only mode, etc)

[ctengel]

#8 included as well; especially checksum

[ctengel]

time to beat 8-16 MB/s download

[ctengel]

Loading whole file into memory looks like it may be a deal breaker for the pi hardware

[ctengel]

Basically there are 3 choices:

• Improve the super basic code we have
• Switch to FastAPI or some other framework
• Use a basic S3ish storage instead like gofakes3 or rclone or versitygw

Spend a pom or two on each in order

[ctengel]

Issue averted via f66b88e and fc4a37c

[ctengel]

Currently about 16 MB/s or 128 Mbps replication - read+write - pretty good!!!

[ctengel]

We may actually be essentially maxing out 100 Mbps Ethernet on Pi 3! So software performance is really good :-) need to build out Pi 4 object servers to get much better