storage_management
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
storage_management [2022/02/11 19:23] yves |
storage_management [2022/09/15 19:48] (current) yves |
||
|---|---|---|---|
| Line 9: | Line 9: | ||
| For these reasons it's important to have tile server solution that is flexible. | For these reasons it's important to have tile server solution that is flexible. | ||
| - | PMA.core supports the following storage media: | + | PMA.core supports the following [[rootdir_config#adding_mounting_points|storage media]]: |
| * local hard disk (think of you conventional ''C:'' and ''D:'' drives and partitions) | * local hard disk (think of you conventional ''C:'' and ''D:'' drives and partitions) | ||
| * network storage like SMB shares (must be accessible via UNC ''%%\\server\path\to\data%%'' routes) | * network storage like SMB shares (must be accessible via UNC ''%%\\server\path\to\data%%'' routes) | ||
| - | * S3-compliant cloud storage (Amazon AWS, Western Digital HGST, NetApp, Arvados, IBM...) | + | * [[rootdir_s3|S3-compliant cloud storage]] (Amazon AWS, Western Digital HGST, NetApp, Arvados, IBM...) |
| - | * Microsoft Azure storage | + | * [[rootdir_azure|Microsoft Azure storage]] (including [[rootdir_azure#data_lake_gen2_storage|Data Lake Gen 2]]) |
| * 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!) | ||
| 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. | ||
| - | [[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 [[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.1644596595.txt.gz · Last modified: 2022/02/11 19:23 by yves
