National Techie Event 2008

Click here to load reader

download National Techie Event 2008

of 39

  • date post

    15-May-2015
  • Category

    Education

  • view

    492
  • download

    2

Embed Size (px)

description

Jason Ming Sun & I made this presentation at a National Techie Training Day in 2008 to promote the use of the Sakai OSS learning and collaboration platform among HE institutions in South Africa. The event was sponsored by DITCHE.

Transcript of National Techie Event 2008

  • 1. National Techie Event 2008 Jason Ming Sun Deon van der Merwe

2. Introduction to Sakai 3. The Sakai Community

  • Composition
    • Academic institutions & commercial enterprises working in partnership with standards bodies & other open-source initiatives.
  • Goals
    • Work collaboratively to develop innovative software applications designed to enhance teaching, learning, research & collaboration within higher education & beyond.
  • Values
    • Knowledge sharing, information transparency, meritocracy, do-ocracy.
  • Praxis
    • 150+ production installations
    • 100+ volunteers active in design, development & testing of Sakai releases.

4. The Sakai Foundation

  • Mission
    • Manage & protect IP
    • Serve as a liability shield for the community
    • Provide basic infrastructure & small staff
    • Help coordinate design, development, testing & distribution of software
    • Champion open source & open standards.
  • Governance
    • Ten board members elected by member reps to serve three-year terms
    • Executive Director manages day-to-day operations.
  • Partners
    • 112 member institutions & organizations contribute $10K per year ($5K for smaller institutions).
  • Budget
    • Underwritten by members ~ $1M per annum
    • Funds 4-6 staff members, admin services, computing infrastructure, project coordination, conferences, Sakai Fellows Program, advocacy & outreach activities.

5. The Sakai Value Proposition

  • Academic Institutions
    • Participate in a dynamic, peer-based community
    • Solve common problems through collaboration
    • Tap into global sources of innovation
    • Leverage inter-institutional economies of scale
    • Get project, team & code transparency
  • Commercial Enterprises
    • Enhance brand name recognition
    • Establish new client relationships
    • Generate revenue
  • Individuals
    • Work on cool projects
    • Work with cool people worldwide
    • Incredible opportunities for learning and development (e.g. Programmers Caf)
    • Hang out at International Sakai Conferences

6. Sakai Users 7. Sakai at Unisa ( my UNISA) 8. Themy Unisa Team(Jan 2008) 9. Decisions, decisions, decisions.

  • Keep(old system)
  • Build
  • Buy(Commercial Products and Partners e.g. BlackCT)
  • Borrow(Open Source e.g. Sakai & Moodle)
    • User
    • Contributor
    • Mature OSS product Best of three words

10. Why Sakai(Value Proposition)

  • Academic institutions
    • Participate in a dynamic, peer-based community
    • Solve common problems through collaboration
    • Tap into global sources of innovation
    • Leverage inter-institutional economies of scale
    • Get project, team & code transparency
  • Individuals
    • Work on cool projects
    • Work with cool people worldwide
    • Incredible opportunities for learning and development
    • Hang out at International Sakai Conferences

11. Why Sakai

  • In addition to previous.
    • In-house research and architecture development.
    • TheSakai Project was introduced to Unisa by a visiting Senior Gartner consultant.
    • Virtually 100% match between the architecture adopted by Sakai and the online architecture envisaged for Unisa.
    • Maturing product
    • Very active (and approachable) community
    • Coordinated community (Foundation)

12. Deployment History

  • January 2006 Sakai v2.1
      • Registered students, end 2006:1 20 765
  • May 2007 Sakai V2.3
    • Registered students, end 2007:159 538
  • April 2008 Sakai V2.5.x
    • Registeredstudents to date in 2008:185 923

13. Support

  • Students
    • Getting started pamphlets
    • Unisa Call Centre (Dedicated agents with ICT Team Leader)
    • Online Help within Sakai
  • Staff
    • ICT Help Desk
    • Deployment specialist (turn complaint into an opportunity)
    • my Unisa Help & TutorialWebsite ( adding video )
    • my UnisaTeam
    • Partnership with the Institute for Curriculum and Learning Development (ICLD)
    • Account Managers

14. Support

  • Technical(Internal)
    • Portal and Academic Solutions (PAS) ormy UnisaTeam
    • Other ICT Staff
    • Sakai Community
    • Sakai South Africa Partners
    • SA and International Commercial Partners

15. Enterprise Change Management & Training

    • Deployment Specialist
      • Formal Training
      • Coffee Sessions
      • One-on-One training
      • Road Shows and Exhibits
      • Posters, Pamphlets, Hand-outs
      • Features in Institutional Newsletters
      • Academic Excellence Awards
    • Departmental Partnerships (CCM, ICLD)
    • PAS Team
    • my Unisa Board
    • Many presentation at all levels

16. Usage 17. Over to Jason. 18. Environment Sakai release: 2.5.xOS: Ubuntu ServerOS version: Gutsy Web server: Apache HTTP Server and TomcatWeb server version: 2.2.4Database: Oracle 10gJVM: Java 1.5.xJVM version: 1.5.0_11JVM tuning: JAVA_OPTS="-server -Xms700m -Xmx700m -XX:MaxPermSize=500m" 19. Hardware 64-bit processing: NoApplication server(s): VMware ESX3 virtual server farm = Physical Dell PE1955 Blade, 2 x Dual Core Xeon 5160 3.2Ghz 16GB RAM Virtual 6GB, 2 x CPUTotal app servers: 12Db server(s): Oracle 10gTotal db servers: 1File storage: Fileserver/NFS: Virtual 2GB, 1 x CPUCluster/load balancing: Pound/Apache-mod_jk Software Load Balancing 20. myUnisa Cluster 21. Pound.cfg

  • ListenHTTPS
  • Address 196.20.20.20
  • Port 443
  • Cert "/SSL/certificate.pem
  • xHTTP 1
  • HeadRemove "(X-Forwarded-For|X-SSL-Connect)
  • Service
  • URL "^/axis-webservices(.*)$"
  • BackEnd
  • Address 196.20.20.21
  • Port 80
  • TimeOut 500
  • End
  • End
  • Service
  • BackEnd
  • Address 196.20.20.22
  • Port 80
  • TimeOut 500
  • Priority 1
  • End
  • BackEnd
  • Address 196.20.20.23.
  • End
      • End

22. Redundancy

  • Apache mod_jk load balances over 2 tomcat application servers (e.g. tomcat failure)
  • Pound (software load balancer) inherently monitors availability of Apache HTTP server and directs traffic away from the problematic node (e.g. web server reboot)
  • vm ware v-motion allows automatic migration of a virtual host from blade server to blade server in case of a blades hardware failure
  • Multiple levels of redundancy

23. Disaster Recovery

  • vm ware Virtual Infrastructure supported by SAN (Storage Area Network)
  • SAN mirroring to remote DR site
  • Complete set of blade servers at DR site