Tektronix QCloud User manual

x
QCloud Automated Video Content Verication System
ZZZ
Quick Start User Manual
*P077094200*
077-0942-00
xx
QCloud Automated Video Content Verication System
ZZZ
This document supports software version 7.6 and above.
www.tektronix.com
077-0942-00
Copyright © Tektronix. All rights reserved. Licensed software products are owned by Tektronix or its subsidiaries or suppliers, and are protected by na
tional copyright laws and international treaty provisions.
Tektronix pro previously published material. Specications and price change privileges reserved.
TEKTRONIX and TEK are registered trademarks of Tektronix, Inc.
QCloud is a trademark of Tektronix, Inc.
QCloud Technical Support
To obtain technical support for your QCloud system, send an email to the following address: cerify-support@tek.com
ducts are covered by U.S. and foreign patents, issued and pending. Information in this publication supersedes that in all
Contacting Tektronix
Tektronix, Inc. 14150 SW Karl Braun Drive P.O. Box 500 Beaverton, OR 97077 USA
For product information, sales, service, and technical support:
In North America, call 1-800-833-9200. Worldwide, visit www.tektronix.com to nd contacts in your area.
.
Warranty
Tektronix warrants that the media on which this software product is furnished and the encoding of the programs on the media will be free from defects in materials and workmanship for a period of three (3) months from the date of shipment. If any such medium or encoding proves defective during the warranty period, Tektronix will provide a replacement in exchange for the defective medium. Except as to the media on which this software product is furnished, this software product is provided “as is” without warranty of any kind, either express or implied. Tektronix does not warrant that the functions contained in this software product will meet Customer's requirements or that the operation of the programs will be uninterrupted or error-free.
In order to obtain service under this warranty, Customer must notify Tektronix of the defect before the expiration of the warranty period. If Tektronix is unable to provide a replacement that is free from defects in materials and workmanship within a reasonable time thereafter, Customer may terminate the license for this software product and return this software product and any associated materials for credit or refund.
THIS WARRANTY IS GIVEN BY TEKTRONIX WITH RESPECT TO THE PRODUCT IN LIEU OF ANY O TH ER WARRANTIES, EXPRESS OR IMPLIED. TEKTRONIX AND ITS VENDORS DISCLAIM ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. TEKTRONIX' RESPONSIBILITY TO REPLACE DEFECTIVE MEDIA OR REFUND CUSTOMER'S PAYMENT IS THE SOLE AND EXCLUSIVE REMEDY PROVIDED TO T HE CUSTOMER FOR BREACH OF THIS WARRANTY. TEKTRONIX AND ITS VENDORS WILL NOT BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES IRRESPECTIVE OF WHETHER TEKTRONIX OR THE VENDOR HAS ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.
[W9b – 15AUG04]
Table of Contents
Preface................................................................................................................................. ii
Product desc
System components . .. .. . .. . . . .. . .. . . . .. . .. . . . .. . .. . . . .. . .. .. . .. . .. .. . .. . . . .. . .. . . . .. . .. . . . .. . . . . . . .. . .. .. . .. . .. .. . .. . . . .. . .. . . . ii
Clustering requirements . . .. . . . .. . .. . . . .. . .. . .. .. . .. . . . . . . .. . .. .. . .. . .. . . . .. . .. . . . .. . .. . . . .. . .. . . . .. . .. . . . .. . .. . . . .. . .. . .. .. . .. . vii
Related doc
Installation.............................................................................................................................. 1
Before installation................................................................................................................ 1
Software i
Uninstalling software............................................................................................................. 8
Software reinstallation ........................................................................................................... 9
Software u
Network settings ................................................................................................................ 10
Conguring the QCloud installation ............................................................................................ 10
Operatio
n.............................................................................................................................. 11
Getting acquainted . . .. . . . .. . .. . . . .. . .. . .. .. . .. . . . . . . .. . .. .. . .. . .. . . . .. . .. . . . .. . .. .. . .. . .. . . . .. . .. . . . .. . .. . . . .. . .. . . . .. . .. . . . .. . . 11
Concepts ........................................................................................................................14
Procedu
ription............................................................................................................... ii
umentation ........................................................................................................ viii
nstallation.............................................................................................................. 3
pgrade ................................................................................................................ 9
res ...................................................................................................................... 16
Table of Content
s
QCloud Quick Start User Manual i
Preface
Preface
QCloud is an automated system for testing compressed digital media before transmission or use. Through a Web-based interface, you can create a Job, which will perform a sequence of checks on a set of media les, and view the results. This manual provides installation instructions and a high-level operational overview of this product.
Product description
This is a med connected on a network running Microsoft W indows. This automated video content verication system can be used to check for correct digital encoding and against baseband quality parameters. It provides both broadcast and production operations with a fast,
QCloud can systems and provide a completely automated workow. A Web based user interface allows test results to be viewed from any network connected workstation.
System co
QCloud accesses digital media from local storage, such as a local hard drive or DVD, as well as network storage, such as a Windows le server, FTP server, or S3 bucket.
A QCloud system can be set up in three basic ways:
The rst consists of a single self-contai ned unit which runs all the management and testing processes of the system.
The second consists of a networked cluster of two or more units, which enables simultaneous processing of a greater number of les. The networked cluster contains a single Supervisor and one or more Media Test Units.
The third consists of a cluster of three or more units with high availability (HA) support. QCloud Enterprise Cluster with high availability (also referred to as an HA cluster) is a QCloud cluster enabled with support in the case of a Supervisor system failure.
ia testing product which runs either on a single computer or on a cluster of two or more dedicated computers
cost effective Q C solution.
be integrated with your existing infrastructure using the CeriTalk API to interface with asset management
mponents
ii QCloud Quick Start User Manual
Preface
Networking
EC2s (Elastic Computing Clouds) are systems on AWS Cloud. In a clustered conguration, EC2s should be part of a VPC (Virtual Private Cloud). In a clustered conguration, network interface on all of the units, including the Supervisor, secondary Supervisor (HA cluster only) and Media Test Units, should be should be part of the VPC (Virtual Private Cloud). This connection is used to access media les, to service Web clients, and to carry cluster control trafc.
Figure i: Clustering topology
Software components
Software components include:
A Web-based user interface, which allows users to create and control Jobs, and to view or report the results of these
. This interface is accessed over the network by using a Web browser. All you need to know is the IP address
Jobs of your computer.
Media test service, which performs media le verication according to the rules you choose.
A database, which provides robust storage of the system entities, including users, Jobs, and Job results.
An XML-based control and reporting API known as CeriTalk. CeriTalk allows interaction with QCloud from within other applications, making it possible to integrate QC loud with other content management, broadcast automation, and
rkow systems.
wo
eb application server that provides access to the Web interface and runs the core services for the application.
AW
QCloud Quick Start User Manual iii
Preface
A license server, which controls the types of les that can be processed and tracks usage of the various features.
The system tray icon and menu, which provides access to the QCloud Web-based user interface and allows the application t service.
o be started and stopped. The system tray icon is not available when QCloud is installed as a Windows
QCloud as a standalone system
A standalone system is a single machine that combines the functions of a Supervisor unit and a Media Test Unit. The process that carries out the media le testing is known as the Media Test Client (MTC).
QCloud enterprise cluster
The Superv and view Jobs. It is responsible for locating the media les from the network, but delegates actual transfer and processing of these les to one or more Media Test Units. The Supervisor unit organizes and stores the resulting outputs.
Each Media Test Unit is responsible for processing the digital media les in a networked cluster. It applies the user-specied tests, an
On an AWS C
isor unit controls the cluster system. It hosts the database and the Web server, allowing multiple users to set up
d reports back the results. The Supervisor can also be congured to process the les.
loud, the following congurations are required for a QCloud enterprise cluster to function:
Security groups conguration within a VPC for QCloud
A security group is a rewall that regulates the ow of trafc across the EC2s within a VPC network on Cloud. Each EC2 can be associated with a particular available security group. The security group contains a set of rules that allow or disallow inbound and outbound trafc to those EC2s. Multiple security groups can be congured within a VPC. The security group should be congured in such a way that it allows both inbound and outbound trafc across a cluster of EC2s. At the same time, it secures the systems from external communication.
Example conguration of a security group
In the EC2 management console, open EC2 dashboard. Click on the “Security Groups” option under the “Network and
rity” section. This will list down all the available security groups. Note that this list displays the “Group Id” for each of the
Secu security groups. Select the security group to be updated with the rules. T he lower panel will display the security group details.
How to set inbound rules. The following procedure shows you how to set inbound rules.
1. Select the “Inbound” tab.
2. Select “Custom TCP rule” from the “Create a new rule” selection box.
3. In the “Port Range” text box, enter 0-65535. This will open up all available ports on TCP.
4. In the “Source” text box, enter the ID of the security gr oup. Each security group will come with an id assigned to
it in the form E.g.-<abcd1234>. This is same as the one displayed under “Group Id” column mentioned above for this security group.
5. Setting Outbound rules: 1: Select the Outbound tab. 2: Select “All TCP rule” from the “Create a new rule” selection box. 3: In the “Source” text box, enter 0.0.0.0/0 Basically this rule allows all TCP trafc between the EC2s that are associated with this security group. Also, this allows all trafc from the EC2 to the outside.
iv QCloud Quick Start User Manual
Preface
How to set outbound rules. The following procedure shows you how to set outbound rules.
1. Select the Outbound tab.
2. Select “All TCP rule” from the “Create a new rule” selection box.
3. In the “Source” text box, enter 0.0.0.0/0 Basically this rule allows all TCP trafc between the EC2s that are associated
with this secu
rity group. Also, this allows all trafc from the EC2 to the outside.
QCloud high availability enterprise cluster
The QCloud high availability enterprise cluster (also referred to as an HA cluster) is a QCloud cluster enabled with support in the case of a Supervisor system failure. In an HA cluster, one of the member units of the cluster is congured as a backup to the Primary Supervisor and is called the Secondary Supervisor.
If QCloud on the Primary Supervisor goes down for any reason (for example, due to a m achine crash), the Secondary Supervisor automatically takes over and manages the cluster. All other units (MTUs) now form a cluster with the Secondary Supervisor. Once the Primary Supervisor recovers, it will assume the role of the Secondary Supervisor and will be ready to take over when the current Supervisor goes down.
The Secondary Supervisor is a part of the HA cluster and can also process les like the Primary Supervisor and the MTUs in the cluster while performing the job of a Secondary Supervisor.
In an HA cluster, it is mandatory to attach an additional network interface for the EC2 that acts as Primary supervisor prior to installation. The private IP of this additional attached network interface should be used for communication (Ceritalk/Web UI). The private IP address of primary network interface (which is pre congured with an EC2) should be used for QCloud cluster communication.
When starting an HA cluster, the cluster units should be started in the following order:
1. Primary Supervisor
2. Secondary Supervisor
3. Media Test Units: these should be started one by one after both the Primary Supervisor and Secondary Supervisor are
started
QCloud Quick Start User Manual v
Preface
Cloud level and EC2 level congurations required before installation of the HA cluster units
The following are the congurations that need to be in place before QCloud is installed on EC2 systems.
1. Dene IAM role in the Amazon AWS Cloud console as follows:
a. In the console, get the IAM dashboard.
b. Create a new role using the “create new role” option in this page.
c. Select this newly created role and create a new policy for this role. For this, select the new role created above and
click on Attach Role Policy button at the bottom of the dashboard. In the UI that comes up, select “Custom Policy” option and click on Select next to it. In the Set Permissions window, enter a name for this policy and copy the below lines in the “Policy D ocument” text box.
These lines set the permission for QCloud to attach and detach network interface w hich is required for the functioning of HA and access of web UI using the single Ceritalk IP address even after fail over.
{ "Version": "2012-10-17", "S tatement": [ { "Action": [ "ec2:AttachNetworkInterface", "ec2:DetachNetworkInterface" ], "Effect": " Allow", "Resource": "*" } ] }
d. Click on “Apply Policy” button and this policy will now be displayed under the “Permissions tab”.
2. Create EC2 instances with the IAM role attached as follows:
a. After setting up the IAM role mentioned above, now the user should proceed to create EC2 instances required for the
HA cluster. During the creation of the instance, an option is provided for the user to select the IAM role. This will be a drop down control that will display all the congured IAM roles. The user should select the IAM role that has the above policy created in it and proceed creating the EC2 instance. Please note: The IAM role cannot be attached to an existing instance if it is not attached during the creation of the instance. Hence, the IAM role with the mentioned policy has to be created before creation of the EC2 instance and attached to the EC2 during the creation of instance.
3. Create an external network interface and select IP addresses during the installation of the Primary Supervisor as follows:
a. The HA cluster requires at least 2 Network Interface Cards to be present on the system where primary supervisor is
installed before the start of the installation of QCloud. This second network interface card should be an externally added network interface after the creation of the EC2 instance and before starting QCloud installation on Primary Supervisor. While creating the external network interface, it is possible to assign an IP address of your choice as private IP address for that network interface.
b. The interface that comes along with the EC2 instance during EC2 creation is called the primary network interface
card. The private IP address associated with this interface should be selected as the network interface for cluster formation during the installation of the QCloud Primary Supervisor in the Supervisor settings installation screen.
c. The private IP address associated with the externally attached network interface card should be selected for the
Ceritalk\web UI communication during the installation of QCloud primary supervisor in the Supervisor settings installation screen.
4. Update hosts le with IP Address and hostname combination as follows:
a. The IP address and hostname combination have to be updated into the hosts le for the IP address resolution during
cluster formation. This detail of all the units in the cluster needs to be updated into the hosts le of primary and secondary supervisor. The details of primary and secondary supervisors need to be updated into the hosts le of all the MTUs. The hosts le is found in c:\windows\system32\drivers\etc folder. Please note: This should be the cluster formation IP address and not the Ceritalk\web UI communication IP. This will be the IP address selected for cluster formation during the installation.
vi
QCloud Quick Start User Manual
Loading...
+ 27 hidden pages