1 / 37

Sakai/OSP Portfolio Implementation @ UvA

Sakai/OSP Portfolio Implementation @ UvA. Bas Toeter Universiteit van Amsterdam b.toeter@uva.nl. Agenda. Infrastructural Architecture File storage, Database, LDAP, e-mail, sizing. Customization Sites, Roles, Realms, Permissions. Software Development Aspects Development, deployment.

lycoris-rhea
Download Presentation

Sakai/OSP Portfolio Implementation @ UvA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Sakai/OSP Portfolio Implementation @ UvA Bas ToeterUniversiteit van Amsterdamb.toeter@uva.nl

  2. Agenda • Infrastructural Architecture • File storage, Database, • LDAP, e-mail, sizing. • Customization • Sites, Roles, • Realms, Permissions. • Software Development Aspects • Development, deployment.

  3. OSP @ Amsterdam • Piloted with OSP 2.0 in 2005 / 2006 • Worked on internationalization and testing • Set up a QA server with automated testing • Documented a couple of tools • Sakai 2-2-x production since January 07 • Worked on OSP bug fixing and testing • Set up a QA server • Sakai 2-4 • Worked on OSP requirements • Some testing • We have a Portfolio only implementation

  4. Infrastructural Architecture • Sizing • How may users do what at the same time? • cpu, memory, storage, database, bandwidth • Load balancing • Enterprise Integration • File Storage • Mail • Database • User management / Authentication

  5. Sizing • Guestimates: • Current numbers • 637 users • 62 MB database • 449 MB uploaded files Dual 3.4Ghz CPU 4GB memory Redundant storage

  6. Load balanced infrastructure

  7. Load balanced infrastructure • Two Cisco content switches • (Which are a pain to configure) • Running in failover mode • Sessions are sticky • Users need to keep going to the same instance • No true clustering, just load balancing • Offloading SSL

  8. sakai.properties # identify your application server with a short name, un… # choose a server id even if you are running a single a… serverId=bomans # the URL to the server, including transport, DNS name,… serverUrl=https://portfolio.uva.nl # force all URLs out of Sakai back to Sakai to be secure… # Otherwise, the URLs will reflect the attributes of the… force.url.secure=443 # For OSP, only set auto.ddl = true on one cluster server auto.ddl = true | false

  9. File Storage • Files stored on Storage Area Network • Network Storage mounted on a fileserver • Using NFS between members and fileserver • Reduced storage overhead through many ‘small’ (~800GB) volumes (lowers cluster size)

  10. sakai.properties # root of archive file system area - used to write… # when clustering app servers, this should be a sh… # storagePath@org.sakaiproject.archive.api.Archive… storagePath@org.sakaiproject.archive.api.ArchiveService = /home/portfolio-files/sakai/archive # when storing content hosting's body bits in file… # to act as volumes to distribute the files among … # see the readme file (2.2.7 File Based Content Ho… bodyVolumes@org.sakaiproject.content.api.ContentHostingService = volume1 # Site quota setting (KB) siteQuota@org.sakaiproject.content.api.ContentHostingService = 204800

  11. Mail Integration • Outgoing mail • Goes out through a local sendmail • ‘Smarthost’ configuration Local sendmailprocess Corporate SMTP servers Portfolio server

  12. Mail Integration • Incoming mail • Not doing this …. yet • May do something like this: Local sendmailprocess James Corporate SMTP servers Portfolio server @portfolio.uva.nl

  13. Mail Integration • Incoming mail • Or simpler: Local sendmailprocess James Corporate SMTP servers Portfolio server @portfolio.uva.nl

  14. sakai.properties # smtp server for outgoing emails smtp@org.sakaiproject.email.api.EmailService=localhost # email address to send errors caught by the portal… portal.error.email=portfolio-fb-ic@uva.nl #setup request; from address for emails to users about… setup.request=portfolio-fb-ic@uva.nl # flag to enable or disable James for incoming email… smtp.enabled = false

  15. Database • Size (oversized multipurpose db) • SUN V890 - 16 GB physical - 4 dual core UltraSparc IV @ 1200 MHz runningSolaris 8 2/04 s28s_hw4wos_05a SPARC. • Oracle 9.2.0.8 • JDBC Driver • ojdbc14.jar v. 10.2.0.1.0 (1.536.979 bytes) • AL32UTF8 Character set

  16. User Management • User creation via a tool • Controlled rollout • LDAP authentication • Implemented a UserDirectoryProvider • Supports fallback and multiple domains • Does not create accounts

  17. The big picture..

  18. Customization • Gateway site • Different My workspace’s • Managing site types • Delegated site creation • Realms, Roles, Permissions

  19. Customize your Gateway • Gateway is a site defined in !gateway • Use the Sites tool to modify

  20. Diversifying the My Workspace • Different users have different needs and get different tools…..defined in ‘site template’

  21. The effect of Type on My Workspace

  22. Sites • Choices in setting up portfolio sites • Portfolio in My Workspace ? • One Portfolio site per student ? • A site per study program? • Site per study program per year? • Presentation and Matrix tools in different sites? • Leave it up to faculty !

  23. Portfolio sites • Defined as a category in toolOrder.xml <category name="portfolio"> <tool id = "sakai.iframe.site" /> <tool id = "sakai.synoptic.chat" /> <tool id = "sakai.synoptic.discussion" /> <tool id = "sakai.synoptic.announcement" /> <tool id = "home" selected = "true" /> <tool id = "sakai.syllabus" /> <tool id = "sakai.announcements" /> <tool id = "sakai.resources" /> <tool id = "osp.glossary" /> <tool id = "osp.matrix" /> <tool id = "osp.presentation" /> <tool id = "osp.evaluations" /> <tool id = "sakai.siteinfo" required = "true" /> </category>

  24. Allowing local admins to create Portfolio sites (only) • Use Sites tool to open local_admins my workspace template

  25. Allowing local admins to create Portfolio sites (only) • Scroll down and open ‘Pages’ section

  26. Allowing local admins to create Portfolio sites (only) • Open the ‘Worksite Setup’ page • Click on the tool id of the sakai.setup tool • Scroll down to ‘Configuration’

  27. Allowing local admins to create Portfolio sites (only) • Remove siteTypes ‘project’ and ‘course’

  28. Realms define Roles… • Define roles in site template realms • OOTB: !site.template.portfolio • Reuse or modify

  29. …and Permissions • For Sakai tools • not (yet) for OSP tools

  30. OSP Tool Permissions • Can be defined in sakai.properties # Glossary tool permissions glossary.permissions.override=false glossary.permissions.map.count=1 glossary.permissions.map.1=Coordinator glossary.permissions.map.1.siteTypes=portfolio glossary.permissions.map.1.value.count=4 glossary.permissions.map.1.value.1=osp.help.glossary.delete glossary.permissions.map.1.value.2=osp.help.glossary.add glossary.permissions.map.1.value.3=osp.help.glossary.edit glossary.permissions.map.1.value.4=osp.help.glossary.export

  31. Software Development Aspects • Basic idea • Being able to test, and accept before moving into production • Script as much as possible • Create a simple deployment process

  32. Develop, Test, Accept, Run!

  33. DEV ACC PRD Script as much as possible

  34. tomcat1/ /usr/local/tomcat1/ toolorder.properties sakai.properties /etc/sakai/toolorder.properties /etc/sakai/sakai.properties Simple Deployment Process • Deployment file contains • Tomcat and • Config files portfolio_prd-r2227-2007-02-12_16.34.tar.gz

  35. Todo.. • Upgrade to Sakai 2.4 • Move to virtualized hardware • Externalize authentication • Connect to IDMS and CAS

  36. Questions..?

More Related