To scale SFA for increasing number of users we need to be able to add more cache servers.
Cache servers provide cache as NAS and for some configuration packaging and unpackaging files locally on cache servers.
This is how SFA currently operates in production.
The current approach is described in SFA HLD document (https://cdcvs.fnal.gov/redmine/attachments/download/6908/small_files_hld_v21.pdf). In current implementation a new cache server can also be added with its cache mounted on all disk and migrator nodes, but then packaging and unpackaging must be done over NAS (and not locally on cache server), which has proven to be an issue for NFS currently used as NAS provider.
The new approach is to group disk movers and migrators around dedicated disk library (cluster) to access a dedicated cache provided by certain cache server. In such an approach only members of the cluster can access data.
#3 Updated by Alexander Moibenko about 7 years ago
Policy applies only for writes.
If we want reads come through new cache we need to assign a new library to corresponding disk volumes just as we do for tape volumes when we move then from one library to another.
Question. If we install a new system around a new disk library manager cluster, and move an existing policy to this new cluster, will they be able to access files they wrote prior to the move?