storage_management
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
storage_management [2022/02/11 19:22] yves |
storage_management [2022/07/18 14:59] antreas |
||
|---|---|---|---|
| Line 17: | Line 17: | ||
| * FTP server (yup, that [[https://www.filezilla.org|free FileZilla File Transfer Protocol server]] is still around and can be now put to new uses for digital pathology applications!) | * FTP server (yup, that [[https://www.filezilla.org|free FileZilla File Transfer Protocol server]] is still around and can be now put to new uses for digital pathology applications!) | ||
| - | Our tile server introduces [[root_directories|root directories]]: virtual mounting points that can point to any of these types of storage, where you have your slides available. | + | Our tile server introduces [[rootdir|root directories]]: virtual mounting points that can point to any of these types of storage, where you have your slides available. |
| Most importantly, you can configure your root-directories in a hybrid fashion, with some storage pointing to traditional hard disks, and other (perhaps long term) storage pointing to cloud resources. | Most importantly, you can configure your root-directories in a hybrid fashion, with some storage pointing to traditional hard disks, and other (perhaps long term) storage pointing to cloud resources. | ||
| Line 23: | Line 23: | ||
| This hybrid configuration model also means you can scale easily over time: you can start with a setup whereby your slides are mostly placed on a (big) local hard disk. After a while, you switch over to your organization's network storage. Even at a later stage, you can transparently migrate to S3-compliant cloud storage. When you have an external collaborator that temporarily wants to share their slide collection with you, you can ask them to setup an FTP server and patch a root-directory through to that one. | This hybrid configuration model also means you can scale easily over time: you can start with a setup whereby your slides are mostly placed on a (big) local hard disk. After a while, you switch over to your organization's network storage. Even at a later stage, you can transparently migrate to S3-compliant cloud storage. When you have an external collaborator that temporarily wants to share their slide collection with you, you can ask them to setup an FTP server and patch a root-directory through to that one. | ||
| - | [[working_with_root_directories|Root-directory resources]] can have authentication and impersonation information attached to them. In addition, PMA.core has its own [[acl|access control lists]] to determine what [[groups]] and [[user_management|individual users]] can see and do (according to [[crud|the CRUD principle]]). | + | [[rootdir|Root-directory resources]] can have authentication and impersonation information attached to them. In addition, PMA.core has its own [[acl|access control lists]] to determine what [[user_groups]] and [[user_management|individual users]] can see and do (according to [[crud|the CRUD principle]]). |
| A comprehensive blog article on the subject of storage and image management is provided at [[https://realdata.pathomation.com|our blog]]. | A comprehensive blog article on the subject of storage and image management is provided at [[https://realdata.pathomation.com|our blog]]. | ||
storage_management.txt · Last modified: 2022/09/15 19:48 by yves
