CSU-Report

Project Status Update

Project Lead: Max Tsai (janq@csufresno.edu)

Last Updated: 04/29/2019

Next - Phase 4 (Q3 - Q4 2019): Integration of AWS Transcribe (UI and Workflow) and new Accessible Video - Interactive Transcription
Current - Phase 3 (Q1 - Q2, 2019): Campus-wide Pilot with implemented SSO (CAS) and Canvas Pilot (LMS) integration. Expected to complete by the end of May 2019.
Phase 2 (end of Q4 2018):
- Development of Accessible Video Player (w/ interactive transcription)
- Evaluating AWS Transcribe
- Completed Cloud Migration from Lift-and-Shifting to version 4 (see below) and initiated a small group of Preview Pilot.
Phase 1 (end of Q2 2018): technology research (kicked off Cloud Community of Practice), application system design, and the base AWS cloud infrastructure. We have built out the initial AWS infrastructure implementation consisting of the test, development, and production ROOT accounts with fully integrated campus Single Sign On with Shibboleth to provide delegated accesses to AWS services through different IAM roles for infrastructure architects, the faculty researcher, student developers and test users. We are ahead of schedule in migrating full media content and implemented API-based synchronization to S3 buckets and exploring EFS shared storage. Bonus: establishing a Standard Development (Tool) environment with AppStreaming2.

Application System Design and AWS Infrastructure

Full Technical Document will be made available to California State campuses by the end of grant development and Limited Creative Common edition to Public.

AWS Migration

Lead Architect: Jay Fowler

https://docs.google.com/document/d/1-IuCusHLfXxRW0-ghG2uswXKV1sQ5meJPncVkFMTtH0/edit?usp=sharing

Streaming Server (Current Version)

Incremental improvements adds monitoring with CloudWatch, notifications with SNS and implements an SMTP gateway using SES.

Streaming Server V4

This version builds on the previous V3 model and decouples the application server and the web server components and using the application load balancer to send requests to the appropriate server ( publish vs stream ).

Streaming Server V3

This architecture utilized the Storage Gateway (SGW), which front-ends an S3 bucket. The SGW has local EBS caching and can be presented to many hosts, accessed remotely and was more cost effective.

Streaming Server V2

This architecture took advantage of the EFS, allowing for centralized access to the media files. It was costly $$ to incorporate EFS and restricted access to the VPC.

Phase I - Lift and Shifting

The streaming media service was to be migrated into this infrastructure. All 3.5TB of media files would have resided on the EBS volume attached to the EC2 instance. While this architecture aligned closest to our current environment, it did not take advantage of auto-scaling and load balancing and would require replication to secondary instances.

Budgets (AWS Credits)

By the end of Phase 1: about $3,000 AWS credits
For the upcoming Phase#2, we are expected to have Full Cycle of development including A.I. services, Content Sync, QA/User Testing of the streaming system. Estimated use of credits: $10-15k.
Current credit use: $11,499.88 (03/2019)

Report abuse