SmoothFlow Deployment : Creating Assets Using an SaaS : Prepare Media Flow Controller for Assets Created Using an SaaS

Prepare Media Flow Controller for Assets Created Using an SaaS
The SFSegment.py script works with one XML file, segment_config.xml. You use this script to tell Media Flow Controller where the encoded multi-bitrate file chunks are located. Preparing Media Flow Controller requires these steps:
1.
Create 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.
2.
Run the SFSegment.py script to initiate SmoothFlow processing and publishing to Media Flow Controller, and render the assets ready for delivery.
Usage Options for SFSegment.py Script
Use the SFSegment.py python script by running the python command at the command line and using the following tags.
-s—segment_config.xml
-i—jobid.xml
-of—output video format
-af—Assured Flow Rate (AFR) threshold (should be set at a value greater than one half the bitrate of the highest bitrate profile in the asset)
Example:
python SFSegment.py -s segment_config.xml
-i <jobid_xml_file_generated_by_SFAssetGen>
[-of <output_video_format>] [-af <AFR_threshold>]
segment_config.xml file
The configurable parameters for segment_config.xml are described in Table 36, below, followed by an example file. Note! The <mfd-ip> tag = Media Flow Controller IP address.
 
Table 36 segment_config.xml Parameters  
Path to which the segmented data needs to be copied. Needs to be the origin server’s doc root (www/var/html) directory. This script can be run either on the origin server, or on another system where the doc root of the origin server is mounted as an NFS mount
<ftp-location> – The location of the multi-bitrate files , if the location of these files is different from the system where it is being run. This node requires the following additional sub-nodes:
<username> – the authorized FTP user
<password> – the authorized FTP user password
<server_ip> – FTP server IP address, source and destination, respectively, (if different)
<path> – path in or out, respectively
<local-path> – The location of the multi-bitrate files if they are co-located in the same system where this script is run (default is current directory where script is run)
< ?xml version="1.0"?>
<segment_config_info>
<!—IP address of the Media Flow Controller; required for generating the HTML content-->
<mfd-ip> {IP_address_of_Media Flow Controller} </mfd-ip>
<!—Where the final chunks reside, can be local or nfs-->
<origin-path> {/var/www/html/smoothflow} </origin-path>
<!—Where the multi-bitrate files are present; can be local or FTP. If FTP, then the script downloads the files to the given scratch-path. If local, then the script copies the multi-bitrate files to the given scratch path-->
<source-type loc= ftp | local> <!–Choose either ftp or local-->
<ftp_location>
<username> {username} </username>
<password> {password} </password>
<server_ip> {ftp_server_IP} </server_ip>
<path> {/test_out} </path>
</ftp_location>
<!—If ftp service is running on the same system-- >
<local-path> {/root/test_out} </local-path>
</source-type>
<scratch_path> {temp_dir_removed_by_script_when_done} </scratch_path>
</segment_config_info>

Report an Error
Media Flow Controller Administrator's Guide and CLI Command Reference
Copyright © 2010 Juniper Networks, Inc.