...
- How do we integrate Sakai's resources and our current AFS file system?
Answer: via replacing ContentHostingService with our own implementation for AFS storage. The current ContentHostingService, backed by DbContentService provides minimal file storage capability - When user's create worksites, how does this get mapped?
Answer:
For user worksites, those would resolve to their current afs home mapping scheme (e.g. home/sn/samerson)
For other worksites, the /afs/ root will be used as a starting point to store content. This is assuming project,misc,and course sites have their own volume? This is still a pending question, because how are we to determine if AFS can handle that many directories under one root?
- What location does it get mapped?
Answer: /afs/ as root path for now, to be determined at a later point when to split this pathing up..
- Do course type of worksites get stored in existing AFS CourseManagement space?
Answer: To Be Determined.. If we use existing space, then we need some way to distinguish Sakai Space from My Space, etc.
- Where do project/research/ or any other non-user and non-course Sakai sites get stored?
Answer: under the /afs/ root path, but we need to determine a volume and/or whether or not the site name resolves to anything meaningful over time.How Sakai stores content
Current Sakai architecture supports storing course and user content both inside/outside of a database. The content path can be mapped to any given path one gives it in the sakai.properties configuration file:
ref: http://bugs.sakaiproject.org/confluence/display/FAQ/2.2.7.1+Configuration
...