Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

DRAFT

Test Environment

Hard Ware

Accounts

  • Instructor accounts:
    • sakaiinst1, sakaiinst2
  • TA accounts:
    • sakaita1, sakaita2
  • Student accounts:
    • sakaistu1, sakaistu2, sakaistu3, sakaistu4

Sites

  • Project: Project Simple AFS
    • maintain (sakaiinst1, sakaiinst2, sakaita1, sakaita2)
    • access (sakaistu1, sakaistu2, sakaistu3, sakaistu4)
  • Course: Course Simple AFS
    • Instructor (sakaiinst1, sakaiinst2)
    • TA (sakaita1, sakaita2)
    • Student (sakaistu1, sakaistu2, sakaistu3, sakaistu4)

Testing Tools that rely on the resources service/tool and or implemented their own resource solution

Samigo : Uses its own resource implementation

  • Functionality:
    • The question type "File Upload" stores the uploaded file in "/var/samigo/jsf" --> "/afs/.ucdavis.edu/ap p/sakai/misc/samigo/smrtsite/jsf"
  • How To Test:
    • Create a quiz that contains at least one question of type "File Upload". Publish the quiz and take it as a student. Once the student has submitted the quiz, an instructor access the submitted quiz and retrieves the uploaded file.
    • (Extended Test) Take the quiz as another student.
    • (Extended Test) Take the quiz as another student but upload the same file (same file name) that the first student uploaded.
  • Expected Outcome:
    • After the student has uploaded the file, the file should be retrievable when the instructor looks at the submitted quiz. Also, the file needs to be present in the above mentioned location in AFS space.

Melete : Uses its own resource implementation

  • Functionality:
    • During the Content Section creation step, you can choose to "upload a file for this section's content"
    • The uploaded file is temporarily stored at: "/var/uploads" --> "/afs/.ucdavis.edu/app/sakai/misc/melete/smartsite/uploads"
    • After temporarily storing it in "/var/uploads" the file is moved to: /var/meleteDocs" --> "/afs/.ucdavis.edu/app/sakai/misc/melete/smartsite/meleteDocs"
      • Under meleteDocs, melete creates sub-folders, one per instructor (author) e.g. meleteDocs/inst_<some user name> (e.g. inst_tpa) and finally stores all the content in there.
  • How To Test:
    • Add a module (test module 1)
    • Add a content section (test section 1)
    • In the "You can create content for this section in one of three ways:" part, select "upload a file for this section's content"
    • Browse to file and click add
    • Click on Finish
  • Expected Outcome:
    • After clicking on "View" and selecting "test module 1" --> "test section 1", you should see the content of the uploaded file displayed in that page. Also, the file need to be present in the above mentioned location in AFS space.

Resources Tool: This is Sakai's main resource/content tool/service

  • Functionality:
    • Use a site's (My Workspace, Course, Project) Resources tool to add and retrieve content. The content is stored in "/var/sakai/content" --> "/afs/.ucdavis.edu/app/sakai/misc/content/smartsite".
  • How To Test:
    • Add content by using the Resources graphical user interface. This needs to be tested for all three types of sites (My Workspace, Course, Project)
    • Add content using WebDAV. This needs to be tested for all three types of sites (My Workspace, Course, Project)Instructions for using WebDAV:
      • In the Resources tool, click on "Upload-Download Multiple Resources"
      • Upload/retrieve single files
      • Upload/retrieve folders containing files as well as sub-folders
  • Expected Outcome:
    • All uploaded files/folders are visible in the Resources tool
    • Also, the files/folders need to be present in the above mentioned location in AFS space.
    • All retrieved/downloaded files/folders need to be present in the downloaded to location.

Any tool that uses Sakai's resources tool/service

  • Functionality:
    • There are a number of tools/services in Sakai that use the Sakai resources tool/service API. These tools are:
      • Administration Workspace: Site Archive Tool
      • Drop Box
      • Syllabus Attachments (Resources Picker)
      • Message Center Attachments (Resources Picker)
      • Schedule Attachments (Resources Picker)
      • Announcement Attachments (Resources Picker)
      • rWiki resource link (Resources Picker)
      • Assignments Attachments (Resources Picker)

Initial Notes:

Tools/Services:

  • Resource Tool
    • Add content
    • Remove content
    • Edit content
    • Perform the above operations to exploit potential concurrency issues. Some of this is applicable in an single application server environment as well as clustered environment.
  • Archiving features that use resource tool such as site archive etc. Are there other tools that allow archiving and use the resource tool's archive feature.
  • Samigo, file upload question type
  • Melete content
  • White List Batch Job: white-list.txt file will live in AFS space (/var/sakai/ucd-data/)
  • Black List Service: black-list.txt file will live in AFS space (/var/sakai/ucd-data/)
  • Set Provider Id Job: provider-id.txt file will live in AFS space (/var/sakai/ucd-date/)
    Input from Tom Arons:
  • AFS may perform slow for highly dynamic content
  • AFS may perform slow for lost of file creation at a time e.g. webdav 3000 files
  • There may be some issues when run in a clustered environment w.r.t. file dirty updates in cache

Error and Failure Scenarios:

  • Manipulate file/directory/volume permissions to cause error/failure
  • Mimic AFS outage via unmount volumes or other means (iptables)
  • No labels