-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Share functionality of placement building between components #1803
Comments
With a proper interface, tree server can use this component too. |
caching is very meaningful for app performance and efficiency. Some attempts were made, but they are buggy, so lets also fix them suggest to w8 4 prelim work finish |
Do we have anything left here? |
for SN:
object ACL should definitely use shared policy component. Evacuator is rarely used, but better to use it too. Tree and estimations... i wouldnt bother them tbh finally, whole package should be purged IR and CLI also apply storage policies to network maps for various needs. Caching doesn't help them, so I would leave everything as is P.S. refs can be found by |
Object placement is build using
netmap.Source
andcontainer.Source
in most scenarios. Also there are some similar cases when we use same placement approach, e.g. shard evacuation introduced here and remote placement builder.I propose to concentrate all placement functionality in single shared code space in order to easily reuse it in new tasks.
The text was updated successfully, but these errors were encountered: