This is the targed SLA for the JupyterHub service between The College of Letters & Science IT (CIT) and the UCSB community:
The College of Letters & Science IT (CIT)
SSMS | Life Sciences | Santa Barbara, CA 93106-4020
cit.ucsb.edu
- Service Name: Academic Computing via Jupyter
- Service Category: Instructional
- Service Type: Instruction
- Service Owner: Andreas Boschke
- Business Owner: Ted Cabeen
- Last Revised: July 31, 2026
To provide users with a robust instructional environment fully configured for their specific use cases, enabling them to focus on their work without spending time on manual environment setup.
All UCSB students, faculty members, and TAs requiring a consistent and reproducible computing environment for instructional use via Jupyter.
- Custom Dependencies: Easy specification of dependencies and requirements for requested course/workshop instances.
- Course Material Distribution: Seamless distribution of writable, non-shared files to students for coursework manipulation.
- Instructor Access: Faculty/TAs have limited access strictly to participant instances within their specific course/workshop for troubleshooting and grading.
- Multi-Instance Support: Users can participate in multiple unique instances simultaneously, each with custom configurations and available packages.
- Environment Updates & Testing: Administrative approval pipeline to push updates to running instances, alongside a designated test environment for instructors to verify changes before committing.
- Self-Service Reversion: Simple controls for users to revert system and package changes to restore service continuity.
- Authentication: Integrated login using standard UCSB NetID credentials.
- Session Preservation: Active instances are preserved for students during production hours.
Faculty and TAs may request JupyterHub environments pre-configured with:
- Python Notebooks
- R Notebooks / RStudio
- Apache Spark (R/Python/Scala/Java)
- Jupyternaut (Jupyter AI)
- Custom library or interface support additions necessary for instruction
| Metric |
Details |
| Hours of Availability |
24/7/365 general access for students |
| Supported Hours |
UCSB Business Hours (off-hours support provided on a best-effort basis) |
| Target Uptime |
99.9% |
| First Response Time |
Within 1 business day |
| Issue Resolution Time |
Within 2 business days for core service issues |
- Student data is retained for 1 year from the start of the course per initial volume provisioning, recoverable even after the term ends.
- Recovery Point Objective (RPO): 24 hours (maximum acceptable data loss window).
- Recovery Time Objective (RTO):
- Service Restoration: 48 hours (core platform reinstated locally or via public cloud fallback).
- Data Restoration: 7 days (full recovery of student files and coursework data backed by multi-site redundancy).
- Data Protection Level (IS-3): P3
- Data Availability Level (IS-3): A2
- Data Recovery Level (IS-12): RL2
- Cost: Covered by the Student Tech Fee and LSIT IUC Fund (free to instructors and students).
- How to Request: Submit a ticket via the Request Form.
- Additional Support: Submit a ticket via CIT Support.
- Consultation & Custom Curation: Dedicated support for SingleUser JupyterLab images.
- Automated CI/CD Pipeline: Automated builds, vulnerability scanning, patch updates, and image deployment.
- Hybrid Cloud Support: Flexible backend storage (public, private, and LFS) for varied data classification needs.
Data footprint (Jan 1 – Apr 9, 2024)
- Active Instances: 32
- Active Users: 2,527
- Storage Allocated: 7 TB of highly available NVMe-backed storage across 3,351 distinct volumes.