You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have 1 flumotion per stream. This currently uses 1 machine per stream as managing the configuration of multiple streams on one machine is to hard.
We should package flumotion up in a docker thingy - https://www.docker.io/
"Docker is an open-source project to easily create lightweight, portable, self-sufficient containers from any application. The same container that a developer builds and tests on a laptop can run at scale, in production, on VMs, bare metal, OpenStack clusters, public clouds and more. "
Flumotion in the TimVideos streaming system
There are 3 types of flumotion configurations; they should share a base docker image but also be provides a separate docker image correctly configured.
Collector - runs on site at a conference and does light encode to compress data so you can send it over the internet to an encoder.
Requires dvswitch support.
Encoder - runs in the cloud and converts video from the light encode format to something suitable for people to view in their browser.
Repeater/Amplifier - runs in the cloud and streams a copy of the encoder output. Allows the system to scale past the limits of a single machine.
There are a couple of support applications we use with flumotion; these should be installed inside the docker image and started as part of the container.
watchdog - Restarts failed components and does a full system restart when things go totally wrong.
register - Registers with the tracker website (so the stream can be found) and sends statistics and logs for reporting and load balancing support.
The text was updated successfully, but these errors were encountered:
Currently we have 1 flumotion per stream. This currently uses 1 machine per stream as managing the configuration of multiple streams on one machine is to hard.
We should package flumotion up in a docker thingy - https://www.docker.io/
"Docker is an open-source project to easily create lightweight, portable, self-sufficient containers from any application. The same container that a developer builds and tests on a laptop can run at scale, in production, on VMs, bare metal, OpenStack clusters, public clouds and more. "
Flumotion in the TimVideos streaming system
There are 3 types of flumotion configurations; they should share a base docker image but also be provides a separate docker image correctly configured.
There are a couple of support applications we use with flumotion; these should be installed inside the docker image and started as part of the container.
The text was updated successfully, but these errors were encountered: