Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Course AFS Space Allocation
    AFS space for courses is allocated via CRN, and CourseManagement in MyUCDavis writes data to this directory. The ACL is the MyUCDavis user.
    Ex.
    /afs/.ucdavis.edu/myucd/class/200603/ARE112001/
    Above uses TermCodeCRN, and class uniqueness

Problem Statement

In order to store content in AFS, to enable clustering in Sakai app servers, we must consider certain questions. Here are some of the questions we need to answer:these questions, and respective brief answers to them:
Further information and discussion on the answers to these questions may be found on child pages (e.g. AFS File Mappings, etc)

1. 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
2. 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. Project sites will have 2 types (user project sites, and institutional project sites), and course sites will be stored via /TermCode/CRN/Sakai instance structure. See AFS File Mapping documentation for more details.

...