Storage Solution Requirements
DRAFT
SmartSite's Storage Solution Requirements
See Jira: Sak-1978, sak-868Â
- High availability, 24/7 service no downtime if at all possible
- Disaster recovery, replication to secondary site
- Optimized for fast read/write access
- WebDAV
- Needs to handle large amounts of files that greatly vary in size
- handles distributed access
- Archiving solution (snapshot feature)
- Backup solution
- Flexible file structure
- Compatible with JSR 170
- DC goal is to get off of afs for r/w volumes
- migration strategy from AFS to SAN - possibly using symlinks on app servers
- need to be in a place to move off of AFS if we have a crisis
- continuous rsync needed
- some sort of sync match with the database
- short term solution for crisis prep may be different from (more ideal) long term solution
- Cost Issues:Â will OCFS2 really save us $200k and over what term?
- Any file sharing solution must be compatible with three basic types of file locking: flock, lockf, and fcntl.
Three uses of afs for smartsite
- Â Â Â software distribution
- Â Â Â communication to My and Registrar
- Â Â Â sakai content store with r/w locking mechanisms
Needed pieces
- Â Â Â san switch must have hba ports for each of app servers
- Â Â Â hba switches for each of app servers
- Â Â Â alternate is iscusi as link into SAN - scusi over IP
What testing is needed?
- Sakai and OCFS2 via HBA?
- Sakai access to OCFS2 via iscusi (is it possible?)
- Migration strategy?
- Continuous rsync of AFS to SAN?
Think in the long term about how this inter-relates with Virtualization Storage solutionsÂ