SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Future-Proofing Academic Infrastructure: A Scalable Approach to Distance Education Services

becca avatar
becca
9 diapositives · 237 Views · Aug 22, 2014

This document outlines strategic planning considerations for enhancing academic computing infrastructure in distance education. It delves into the challenges and solutions surrounding multiple servers and services, focusing on the importance of scalability, user-friendliness, and centralizing authentication. Key initiatives discussed include implementing LDAP for single-sign-on across platforms and automating account management to streamline processes for CMS administrators. Additionally, it emphasizes the need for fault-tolerant systems to ensure service continuity and data protection as user demands grow.

#future-proofing academic infrastructure: a scalable approach to distance education services #future-proofing academic infrastructure: a scalable approach to distance education services ppt #powerpoint #presentation
Future-Proofing Academic Infrastructure: A Scalable Approach to Distance Education Services - slide 1
01 / 9Future-Proofing Academic Infrastructure: A Scalable Approach to Distance Education Services
1 / 17

Télécharger la présentation

Future-Proofing Academic Infrastructure: A Scalable Approach to Distance Education Services
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Academic Servers Infrastructure Distance Education: moodle.dyc.edu (2) ddl.dyc.edu project.dyc.edu (http://*.dl.dyc.edu) [backup systems] Institutional Reseach: survey.dyc.edu IT Dept: multiple servers

  2. Hodgepodge growth Added services and servers ad hoc. This worked until things grew too quickly: bb4 – stable/scalable (php/mysql) ~same tech as moodle bb6 – unstable/scalable (tomcat/o8) bb9 – unstable/unscalable (tomcat/so) Early decisions committed us to be backed into a corner

  3. Planning Consideration – Part 1 Create systems which will serve Academic computing needs far into the future. Agents ~ bus trip analogy Systems Admin ~ Auto mechanic (me) CMS Admins ~ Bus Driver (John et al., Mark et al.) End Users ~ Passengers (Stu./Profs.)

  4. Planning Considerations – Part 2 Scalable: As the number of users increases, does the amount of work to run the system increase? Sys Admin – running an email server for one person or 1000 is just as much work CMS Admin – currently doubling the number of users doubles the amount of work. This needs to be fixed. (Same problem with the labs.)

  5. Planning Considerations – Part 3 User Friendly: Is the system something people will want to use? Currently there are many services possible and available but the problem is that each has its own authentication and so people are lumping everything into one moodle site. (Service depts and courses). Eg. It would also be nice to have a space for disseminating research.

  6. Planning Considerations – Part 4 Money: done Somehow(?) I convinced people to buy $57,000 in equipment. Migration is almost complete to “fault tolerant” systems, ie systems where you have to have two simultaneous breakdowns before loosing service. Even more to loose data.

  7. The Plan and Goals 1) One central authentication for multiple services (LDAP), ie. Just one password for everything. 2) Plugable services – multiple moodles, multiple blogs, multiple drupal (online publication), multiple wikis, etc. Isolated or integrated to the extend needed. 3) Automation for CMS admins

  8. Plugable services A dept may need a customized or isolated site. Quick deployment! Egs. Moodle – http://it.dl.dyc.edu Wikis - http://aclabs.wiki.dl.dyc.edu Gallery - http://basile.gallery.dl.dyc.edu Drupal - http://basile.drupal.dl.dyc.edu (Fac. Research. whitehouse.gov)

  9. Automation for CMS Admins 1) Automatic addition of student accounts and courses with students enrolled to main moodle. Data pulled from NIAS. 2) Automatic addition of low privileged accounts to various CMSes. 3) Automatic addition of students to survey for online student satisfaction. Automatic generation of results.