search

qri-io / rfcs

Request For Comments (RFCs) documenting changes to Qri
MIT License
12 stars 6 forks source link

RFC: storage command #50

Closed b5 closed 4 years ago

b5 commented 4 years ago

RFC to support push/pull with storage manipulation commands. Early comments welcome!

b5 commented 4 years ago

@Arqu, apologies, this PR erroneously includes a copy of the push/pull RFC, if I understand correctly, I think your comments about retention strategies apply to that RFC more than the storage one:

I hate to say it but it might even warant a separate RFC for just the retention strategies and network health, split of from storage, accept policies/params and storage commands.

Totally agreed. Might not have made this clear enough, but I'm hoping these RFCs just set the stage for work on defining retention strategies, and the strategies themselves should be described in future RFCs. The one retention strategy we do need right now is the none strategy, which when the storage max value is exceeded. In this "no strategy" case we need these storage commands to manually request a remote drop versions until we're under the limit again

b5 commented 4 years ago

Ratified! Thanks all