Deployment Checklist - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Administrator's Guide
To view the delivery trace log:
•
Web interface—Media Flow Controller trace log entries are available for viewing on the
Web interface Trace Logs page.
•
CLI—To upload a trace log, run upload tracelog scp://<URL>. Now you can access the
trace log at the specified system, move it (if needed) and view its contents. See
"Terminology" on page 30
installed in order to SCP or FTP, respectively, files to your machine.

Deployment Checklist

First, you must determine how many bitrate profiles you want for each video. See
Your Needs" on page 252
For "Creating Assets Using an SaaS" on page
1. Create an account with encoding.com
2. Post one single-bitrate video file to your Web server.
3. Create the setup.xml file describing the Website of your chosen encoding service and
your login credentials for the service, where you want the multi-bitrate profiles output to,
and credentials for that (for example, FTP site and credentials), and how often you want
status polling done. See
4. For each asset, create the asset.xml file describing the single-bitrate video file, how many
multi-bitrate profiles you want created for it and at what rates, including frames-per-
second, container format, and keyframe interval. See
an SaaS" on page
5. Use the SFAssetGenerator.py script to
create multi-bitrate (MBR) profiles for each single-bitrate video file.
6. "Verify that Encoding has Completed" on page 259
FTP output account given in the setup.xml file.
7. "Prepare Media Flow Controller for Assets Created Using an SaaS" on page 260
creating the segment_config.xml file describing the multi-bitrate assets for Media Flow
Controller including the IP address of the Media Flow Controller, where the assets are
located, access credentials for obtaining the assets, and a temporary directory in the
system for SmoothFlow processing.
8. Use the SFSegment.py script referencing the segment_config.xml file to initiate
SmoothFlow processing and publishing to Media Flow Controller, and render the assets
ready for delivery.
9. Check
For "Creating On-Demand Assets" on page
1. Encode multi-bitrate profiles for each video using the method of your choice; follow
"Bitrate Profiles Naming Conventions for On-Demand Assets" on page
2. For each asset,
creating an AssetDescription.dat (text) file describing the multi-bitrate profiles including
frame rate, keyframe interval, and assured flow rate and threshold.
for the scp URL format); you must have an SCP or FTP server
and "Encoding Requirements" on page
"Scripts for Creating Assets Using an SaaS" on page
255.
"Logs for Assets Created Using an SaaS" on page
"Create AssetDescription.dat File for On-Demand Assets" on page 264
252.
253:
"Scripts for Creating Assets Using
"Initiate Encoding Using an SaaS" on page 256
and the assets are transferred to your
261.
262:
SmoothFlow Deployment
"Evaluating
255.
by
263".
Deployment Checklist
to
by
269