Mixer Deployment Overview
If you want to use mixer nodes in your autoscale cluster, that will involve a few additional steps beyond the standard autoscale setup. The CEF (Chrome Extension Framework) mixer requires the following additional components:
- A mixer server node.js back-end (mock server provided for testing)
- Special configuration of the Non-mixer node images
- A custom mixer node image with
mixerwebapp and CEF libraries
The Red5 Pro mixer testbed examples use the
live webapp on the non-mixer nodes, which is used for publishing all live streams (including composite ones), and a Node.js server which handles the creation and management of compositions. The
live webapp has been extended to call a configurable webhook endpoint every time a stream is published or unpublished. The webhook endpoint is provided by the Node.js server, which uses the information to manage an active streams list. This streams list is provided to a grid moderator through a WebSocket connection between the Node.js server and the mixer testbeds used by the moderator. In this way the moderator can see which streams are live and add any of those to a composition.
The basic flow of communication in an autoscale cluster which includes the mixer node type:
For more details about the Red5 Pro Mixer solution, see these documents.