aboutsummaryrefslogtreecommitdiff
path: root/TODO
blob: 5d74e6c08c3ed613ae0741b3ee428b42a94b8597 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
Testing
-------

How are we going to test that our replication method works correctly?
We will have to introduce lots of dummy data and then add/remove nodes many times.


Attaining S3 compatibility
--------------------------

- test & fix multipart uploads
- abort multipart upload
- fix sync not working in some cases ? (when starting from empty?)

- api_server following the S3 semantics for head/get/put/list/delete: verify more that it works as intended
- PUT requests: verify content-md5 if provided
- possibly other necessary endpoints ?


Lower priority
--------------

- less a priority: hinted handoff
- repair: re-propagate block ref table to rc
- FIXME in rpc_server when garage shuts down and futures can be interrupted
  (tokio::spawn should be replaced by a new function background::spawn_joinable)