mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

todo

Browse source
This commit is contained in:
Joey Hess 2024-08-09 16:57:10 -04:00
parent 412f6057e4
commit bde58e6c71
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 16 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

20
doc/todo/git-annex_proxies.mdwn
View file

@ -30,11 +30,17 @@ Planned schedule of work:
## work notes ## work notes
* balanced= and fullybalanced= need to limit the set of repositories to * `fullybalanced=foo:2` can get stuck in suboptimal situations. Eg,
ones with enough free space to contain a key. when 2 out of 3 repositories are full, and the 3rd is mostly empty,
it is no longer possible to add new files to 2 repositories.
Moving some files from one of the full repositories to the empty one
would improve things, but is there any way for fullybalanced to know
when it makes sense to do that?
* document balancing algo well enough that someone else could implement it If this is not resolved, it may be better to lose the ":number" part
from the design doc of balanced and fullybalanced. With 1 copy balanced, this situation does
not occur. Users wanting 2 copies can have 2 groups which are each
balanced, although that would mean more repositories on more drives.
* picking a low UUID and picking keys that mod N == 0 would let an attacker * picking a low UUID and picking keys that mod N == 0 would let an attacker
generate keys that balancing always puts on that UUID. To avoid this generate keys that balancing always puts on that UUID. To avoid this
@ -42,8 +48,14 @@ Planned schedule of work:
prevented by adding another UUID to the set, it could even be a dummy prevented by adding another UUID to the set, it could even be a dummy
UUID that is marked as having 0 size, so it will never be used. UUID that is marked as having 0 size, so it will never be used.
* document balancing algo well enough that someone else could implement it
from the design doc
* Add `git-annex maxsize` command. * Add `git-annex maxsize` command.
* balanced= and fullybalanced= need to limit the set of repositories to
ones with enough free space to contain a key.
* Implement [[track_free_space_in_repos_via_git-annex_branch]] * Implement [[track_free_space_in_repos_via_git-annex_branch]]
## completed items for August's work on balanced preferred content ## completed items for August's work on balanced preferred content