Skip to content
This repository has been archived by the owner on Oct 1, 2020. It is now read-only.
/ edx-video-pipeline Public archive

[ARCHIVED] Video encode automation for edx-platform

License

Notifications You must be signed in to change notification settings

edx/edx-video-pipeline

Folders and files

NameName
Last commit message
Last commit date
Mar 29, 2018
Mar 29, 2018
Mar 29, 2018
Mar 29, 2018
Jul 5, 2017
Mar 29, 2018
Oct 30, 2017
Jul 28, 2017
Mar 29, 2018
Feb 14, 2018
Mar 29, 2018
Oct 30, 2017
Dec 7, 2017
Oct 30, 2017
Oct 16, 2017
Feb 9, 2018
Jul 3, 2017
Nov 8, 2017
Jul 5, 2017
Jul 28, 2017
Mar 29, 2018
Oct 25, 2017
Oct 27, 2017
Nov 1, 2017
Oct 30, 2017
Mar 14, 2018
Mar 29, 2018
Mar 14, 2018
Mar 29, 2018
Jul 5, 2017

Repository files navigation

edx-video-pipeline (A.K.A "Veda")

Video encode automation django app/control node for edx-platform

The video pipeline performs the following tasks - Ingest (Discovery, Cataloging, Sending tasks to worker cluster) - Delivery - Storage - Maintenance

The video pipeline seeks modularity between parts, and for each part to operate as cleanly and independently as possible. Each course's workflow operates independently, and workflows can be configured to serve a variety of endpoints.

INGEST: Currently we ingest remote video from edx-platform via the Studio video upload tool. The videos are discovered by the video pipeline and ingested upon succcessful upload, renamed to an internal ID schema, and routed to the appropriate transcode task cluster.

TRANSCODE: code for this is housed at https://github.com/edx/edx-video-worker

DELIVERY: Uploads product videos to specific third-party destinations (YT, AWS, 3Play, cielo24), retrieves URLs/Statuses/products.

STORAGE: A specified AWS S3 bucket=

MAINTENANCE: Logging, Data dumping, Celery node status and queue information

https://travis-ci.org/edx/edx-video-pipeline.svg?branch=master