Cisco Virtualized Video Processing Controller User guide

Cisco Systems, Inc.

www.cisco.com

Cisco has more than 200 offices worldwide.

Addresses, phone numbers, and fax numbers

are listed on the Cisco website at

www.cisco.com/go/offices.

Cisco Virtualized Video Processing Controller

Deployment Guide

Release 3.3

February 20, 2018

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO

CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANU-

AL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS

OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE INCORPO-

RATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMIT-

ED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California,

Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE

SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DIS-

CLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MER-

CHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A

COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL,

OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO

DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS

HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and

phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the docu-

ment are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unin-

tentional and coincidental.

All printed copies and duplicate soft copies are considered un-Controlled copies and the original on-line version should be re-

ferred to for latest version.

Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at

www.cisco.com/go/offices.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view

a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their

respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company.

(1110R)

Cisco Virtualized Video Processing Controller Deployment Guide

1

Cisco Virtualized Video Processing Controller Deployment Guide

CONTENTS

Introduction 1-1

Product Description 1-1

V2PC Deployment Benefits 1-2

Deploying V2PC 2-1

V2PC Deployment Requirements 2-1

V2PC Deployment Sizing 2-1

Open Port Assignments 2-2

Virtual Disk Provisioning 2-2

Separate Logging Volume 2-4

Deployment Testing Requirements 2-4

Deploying the V2PC System 2-4

Configure VMware 2-4

Install the Launcher VM from the OVAs 2-6

Run the Launcher Bootstrap Script 2-12

Verify the Deployment 2-20

Install the VMP Bundle 2-21

Next Steps 2-22

Sample JSON File 2-22

Securing the Deployment 3-1

Protecting the V2PC Network 3-1

Securing the V2PC Data Flow 3-1

Root User Console Access 3-2

Troubleshooting the Deployment 4-1

Power Failure Recovery 4-1

Backup-Restore 4-1

Using the Backup Script 4-2

Using the Restore Script 4-2

Using the Worker Restore Script 4-3

Viewing Logs on the ELK Server 4-3

Using Show Status for Log Export 4-4

Creating Log Export 4-5

Contents

2

Cisco Virtualized Video Processing Controller Deployment Guide

Extracting the Log File 4-6

Monitoring DocServer 4-6

V2PC Upgrade 5-1

Considerations for Upgrade 5-1

Upgrade Procedure 5-2

V2PC Platform and Application Upgrade (or Rollback) 5-2

Upgrade the AIC and MFC 5-4

Upgrade the Application Worker 5-6

Downgrade the Application Worker 5-8

Application Rollback Following Major Platform Upgrade 5-9

Application Rollback Following Minor Platform Upgrade 5-10

Avoiding Known Upgrade and Downgrade Issues 5-10

Using the V2P Package Manager Utility 6-1

Package Requirements 6-1

Importing an Application Package 6-3

Importing and Publishing an NPM Module 6-4

Importing RPM Modules 6-4

Deleting an Application Package 6-4

Worker Node Installation and Upgrade Scripts 6-4

Importing System RPMs 6-6

Importing an Application Upgrade Bundle 6-7

Ports Opened in V2PC Release 3.3 A-1

Master Node A-1

MCE Node A-3

MPE Node A-4

IPVS Node A-5

Redis Node A-5

Haproxy Node A-6

ELK Node

A-7

Repository Node A-7

Changing Default Open Ports A-8

3

Cisco Virtualized Video Processing Controller Deployment Guide

Preface

This guide provides instructions for deploying the Cisco Virtualized Video Processing Controller

(V2PC). V2PC provides a unified control and management interface for all products in the Cisco V2P

platform.

Document Organization

This document contains the following chapters and appendices:

Document Conventions

This document uses the following conventions:

Chapters or Appendices Descriptions

Introduction Introduces V2PC and defines key terms and concepts.

Deploying V2PC Provides instructions for deploying V2PC.

Securing the Deployment Provides suggestions for securing the V2PC management

network and ports.

Troubleshooting the Deployment Suggests ways to resolve V2PC deployment issues.

V2PC Upgrade Describes procedures to upgrade V2PC and components.

Using the V2P Package Manager Utility Gives instructions for using the V2P Package Manager

Utility (v2pPkgMgr) to import an application upgrade

bundle.

Ports Opened in V2PC Release 3.3 Lists the programs, ports, and protocols associated with

each V2PC node.

Convention Indication

bold font Commands and keywords and user-entered text appear in bold font.

italic font Document titles, new or emphasized terms, and arguments for which you supply

values are in italic font.

[ ] Elements in square brackets are optional.

4

Cisco Virtualized Video Processing Controller Deployment Guide

Preface

Document Conventions

Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the

manual.

Tip Means the following information will help you solve a problem. The tips information might not be

troubleshooting or even an action, but could be useful information, similar to a Timesaver.

Caution Means reader be careful. In this situation, you might perform an action that could result in equipment

damage or loss of data.

Timesaver Means the described action saves time. You can save time by performing the action described in

the paragraph.

Warning

IMPORTANT SAFETY INSTRUCTIONS

This warning symbol means danger. You are in a situation that could cause bodily injury. Before

you work on any equipment, be aware of the hazards involved with electrical circuitry and be

familiar with standard practices for preventing accidents. Use the statement number provided at

the end of each warning to locate its translation in the translated safety warnings that

accompanied this device.

SAVE THESE INSTRUCTIONS

Warning

Statements using this symbol are provided for additional information and to comply with

regulatory and customer requirements.

{x | y | z } Required alternative keywords are grouped in braces and separated by

vertical bars.

[ x | y | z ] Optional alternative keywords are grouped in brackets and separated by

vertical bars.

string A nonquoted set of characters. Do not use quotation marks around the string or

the string will include the quotation marks.

courier font Terminal sessions and information the system displays appear in courier font.

< > Nonprinting characters such as passwords are in angle brackets.

[ ] Default responses to system prompts are in square brackets.

!, # An exclamation point (!) or a pound sign (#) at the beginning of a line of code

indicates a comment line.

5

Cisco Virtualized Video Processing Controller Deployment Guide

Preface

Related Publications

Refer to the following documents for additional information about V2PC:

•Cisco Virtualized Video Processing Controller User Guide

•Cisco Virtualized Video Processing Controller API Guide

•Cisco Virtualized Video Processing Controller API Service Guide

•Release Notes for Cisco V2PC 3.3.x

•Open Source Used in Cisco V2PC 3.3

6

Cisco Virtualized Video Processing Controller Deployment Guide

Preface

Related Publications

CHAPTER

1-1

Cisco Virtualized Video Processing Controller Deployment Guide

1

Introduction

This chapter provides the following information:

•Product Description, page 1-1

•V2PC Deployment Benefits, page 1-2

Product Description

The Cisco Virtualized Video Processing Controller (V2PC) is an open and extensible platform that

facilitates deployment and management of Cisco V2P video data plane applications (such as encoders,

packagers, and recorders) in the data center cloud environment. These applications are abstracted from

the underlying infrastructure such as VMware or Docker. This enables the rapid deployment of new

services such as Live, VOD, or CDVR to OTT consumers while enabling efficiency and reducing costs.

Figure 1-1 Cisco V2PC Distributed Deployment

1-2

Cisco Virtualized Video Processing Controller Deployment Guide

Chapter 1 Introduction

V2PC Deployment Benefits

The V2PC deployment offers the following key benefits.

•Common data center infrastructure

•All virtualized

•Can deploy all V2P applications

•Single pane to deploy media workflows

•Stores one format (CIF)

•Uses common Cisco Media Capture Engine (MCE) and Media Playback Engine (MPE)

•Supports just-in-time packaging (JITP)

•Provides common management and open REST API (media workflow resources)

•Logging Server/Sensu

•Flexible media platform-as-a-service (PaaS)

•Ubiquitous media cloud – federated data centers with distributed microservices

•Interconnect, control, and operate media functions as micro services across multiple data centers

•Flexible Infrastructure – Media functions can run as containers (or) VMs

CHAPTER

2-1

Cisco Virtualized Video Processing Controller Deployment Guide

2

Deploying V2PC

This chapter provides information on deploying V2PC. It includes the following topics:

•V2PC Deployment Requirements, page 2-1

•V2PC Deployment Sizing, page 2-1

•Deployment Testing Requirements, page 2-4

•Deploying the V2PC System, page 2-4

•Sample JSON File, page 2-22

V2PC Deployment Requirements

•Hardware: UCS B200-M3/M4

•Provider: VMware

Note • All ESXi Host UCS blade servers should have the same hardware specifications.

•VMware EXSi version and patch level requirements may vary by release. Be sure to check the

release notes for your release for specific EXSi version and patch level requirements.

•V2PC master repository node should be deployed as 2X-Large (8 CPU, 32 GB RAM, 40 GB Disk

storage)

•ELK node should be deployed as 2X-Large with 500 GB disks space (8 CPU, 32 GB RAM, 500 GB

Disk storage)

Note Cisco Media Origination System (MOS) provides important guidelines for configuring UCS server

network and interface policies to optimize the traffic flow through the MCE workers for Live, VoD, and

cDVR applications. For details, see UCS Configuration in the Cisco Media Origination System User

Guide – Software Version 2.5.1.

V2PC Deployment Sizing

The following tables provide V2PC sizing requirements for each of the components in the deployment.

2-2

Cisco Virtualized Video Processing Controller Deployment Guide

Chapter 2 Deploying V2PC

V2PC Deployment Sizing

* Two required per service: one pair for MCE and another pair for MPE.

** Two required per device type: one set for SCE-StateCacheEndpoint and one set for VOD service.

Note Legacy deployments using Cisco Media Origination System (MOS) do not require V2PC Masters or an

ELK node, but instead, require VMs for the Platform and Application Manager (PAM) and Centralized

Logging Server (CLS). See the User Guide for your MOS release for complete deployment information

for these nodes.

Open Port Assignments

By default, each component of the V2PC deployment has an associated set of assigned ports. Before

deploying V2PC, review the port assignments listed in Ports Opened in V2PC Release 3.3, page A-1 to

confirm that there are no conflicts with any existing ports in your network. As noted in the appendix,

some port assignments can be modified.

Virtual Disk Provisioning

When creating a VM at startup, VMware first checks the storage and memory reserved for the VM. If

VMware cannot verify that storage and memory are sufficient, VM creation fails, and the user must clear

the VM from the V2PC GUI and the vCenter infrastructure manually.

To help avoid VM creation failure, VMware provides the option of deploying V2PC and its worker nodes

with virtual disks with one of two provisioning modes:

•Thick provisioning reserves VM storage (vmdk) and memory. This avoids over-committing host

resources.

•Thin provisioning allocates only the amount of VMware storage and memory space needed to store

the data on a virtual disk, allowing for over-committing of host resources.

During V2PC installation, one of these provisioning modes is defined by a setting in the V2PC base

image (described below). All of the nodes in a given VM must use either thick or thin provisioning.

Table 2-1 V2PC Sizing Requirements

Component Flavor Name

vCPU

s RAM

Hard Drive

Partition 1

Hard Drive

Partition 2

Network

Interfaces

V2PC Masters (3) 2X-Large 8 32 GB 40 GB — 1 X 10 GE

MCE 2X-Large 8 32 GB 40 GB — 3 X 10 GE

MPE 2X-Large 8 32 GB 40 GB — 3 X 10 GE

Repository 2X-Large 8 32 GB 40 GB — 1 X 10 GE

IPVS Nodes (2) * X-Large 8 16 GB 40 GB — 2 X 10 GE

REDIS Nodes (2) ** X-Large 8 16 GB 40 GB — 2 X 10 GE

HAProxy Nodes (2) ** X-Large 8 16 GB 40 GB — 2 X 10 GE

AM (2) X-Large 8 16 GB 40 GB — 1 X 10 GE

ELK Node 2X-Large 8 32 GB 40 GB 512 GB 1 X 10 GE

2-3

Cisco Virtualized Video Processing Controller Deployment Guide

Chapter 2 Deploying V2PC

V2PC Deployment Sizing

Note V2PC Release 3.3 does not support CPU reservation.

V2PC itself does not support converting VMs from one type of provisioning to another after installation.

VMware does, however, provide instructions for manually converting VM hard disks from thin to thick

provisioning. For details, see the following VMware knowledgebase article:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2014832

Setting the Provisioning Mode

In the V2PC image template, the V2PC cluster JSON file includes a vdiskProvisionMode parameter

that controls the selection of thick or thin provisioning. During installation, the base image is imported

according to the specified provisioning mode.

In the base image template, vdiskProvisionMode is set to thick. All nodes created from this base image

have thick-provisioned disk and RAM sizes that are reserved from the ESX host memory pool.

If desired, resources can be over-committed by modifying the V2PC image template and uploading the

image with vdiskProvisionMode set to thin, as shown in the following example:

{

"imageDFormat": "vmdk",

"vmSourcePath": "/sw/v2p/images",

"vm_type": "template",

"hostname": "na",

"imageCFormat": "bare",

"imgTag": "cisco-centos-7.0",

"deployment": "pod1",

"datastore": "datastore2",

"vmName": "v2p-btest",

"vmSourceName": "centos7.ovf",

"vdiskProvisionMode": "thin"

}

,

This parameter is settable during installation through the V2PC cluster JSON wizard that generates the

v2p-cluster.json file. For details, see Install the Launcher VM from the OVAs, page 2-6.

Adding Thick Provisioning During Upgrade

During an upgrade to V2PC Release 3.3, thick provisioning can be added when importing the image and

package from the repository VM. Thick provisioning is selected by default, and the software includes

documentation and a manifest template to simplify the process of importing a V2PC base image in thick

mode.

Note See V2PC Upgrade, page 5-1 for upgrade instructions.

The image tag for the imported base image is separate from the image tag associated with the master,

ELK, and repository nodes. The upgrade utility is enhanced to upgrade system packages on the worker

nodes with a particular image tag. When using this utility to upgrade V2PC system nodes (master, ELK,

and repository), you must manually upgrade the worker nodes created with imported base image.

2-4

Cisco Virtualized Video Processing Controller Deployment Guide

Chapter 2 Deploying V2PC

Deployment Testing Requirements

Note Only new nodes created from the newly imported base image will be thick provisioned during upgrade.

Existing deployed V2PC nodes with hard disks configured for thin provisioning are not converted to

thick provisioning.

Separate Logging Volume

Beginning with V2PC Release 3.3, the V2PC base image has two logical volumes:

•The first logical volume is mounted at “/” and holds the root file system.

•The second logical volume is mounted at “var/log/” and hold the log files.

The use of a separate logical volume for log files limits the size of the logging directory. This prevents

exhaustion of the logging directory space, if it should occur due to excess logging by some applications,

from causing instability of the virtual machine due to lack of free storage space on the root file system.

Deployment Testing Requirements

The minimal functionality testing lab deployments require the following:

•Launcher (can be turned off after deployment)

•Repository x 1

•Master x 1 (supported production environments require 3 master nodes)

•ELK 1

•Template x 1

•MCE x Scale required for Capture

•MPE x Scale required for playback or delivery to CDN or client

•AM x 1 minimum, AM x 2 recommended for redundancy

•IPVS, HAProxy, Redis (2 nodes each required for each Live, VOD, or cDVR workflow)

Deploying the V2PC System

To fully deploy the V2PC, perform the following tasks in order:

•Configure VMware, page 2-4

•Install the Launcher VM from the OVAs, page 2-6

•Run the Launcher Bootstrap Script, page 2-12

•Verify the Deployment, page 2-20

Configure VMware

Configuring the VMware is required before deploying the V2PC. Follow the instructions below to

configure VMware.

2-5

Cisco Virtualized Video Processing Controller Deployment Guide

Chapter 2 Deploying V2PC

Deploying the V2PC System

Before You Begin

Confirm that you have the following:

•Recommended Hardware: UCS Chassis with B200-M3 or B200-M4 Blades Servers

•VMware ESXi hypervisor and vCenter

Note VMware EXSi version and patch level requirements may vary by release. Be sure to check the release

notes for your release for specific EXSi version and patch level requirements.

Configure VMware

Step 1 Install VMware vCenter as follows:

Note The installation procedure shown here is for a Windows host. A compatible VMware vCenter Server ISO

image is required for the installation. See the Release Notes for details.

a. Download the ISO image for the appropriate VMware vCenter Server version and patch level.

b. Mount the VMware vCenter ISO image by copying the .iso image file to the physical server (Linux

box) and mounting the image. For example:

mkdir /tmp/mnt

mount -o loop /downloads/VMware-VCSA-all-6.0.0-2656757.iso /tmp/mnt cd /tmp/mnt

c. Copy the extracted files to the Windows host. Alternatively, you can mount the ISO image directly

on the Windows host, using a tool like WinISO.

d. Open the vcsa folder and double-click the VMware-ClientIntegrationPlugin-<version> file.

e. Install the vcsa-setup.

Step 2 Configure vCenter as follows:

a. Make a note in advance of the data center, folder, resource pool, cluster, and host name(s) to be used

when configuring vCenter.

b. Log in to vCenter using a web browser or vSphere client.

c. Create a data center on vCenter by navigating to Home > Inventory > Datastores and Datastore

Clusters, right-clicking vCenter, selecting New Datacenter, and entering a unique name for the

data center (for example, v2pc-c3b12-datacenter).

d. Create a new VM folder by navigating to Home > Inventory > VMs and Templates, right-clicking

Datacenter, selecting New Folder, and entering a unique name for the folder (for example,

v2pc-folder).

e. Add a new cluster to the new data center by navigating to Home > Inventory > Hosts and Clusters,

right-clicking Datacenter, and selecting New Cluster.

f. Edit the new cluster to enable DRS by navigating to Cluster Settings > Cluster Features and

checking Turn On vSphere DRS. Click Next repeatedly until finished.

g. Add a host to the new cluster by navigating to Home > Inventory > Hosts and Clusters,

right-clicking the cluster, and selecting Add Host. Repeat as needed to add additional hosts.

h. Add a resource pool to the cluster by navigating to Home > Inventory > Hosts and Clusters,

right-clicking the cluster, and selecting New Resource Pool.

2-6

Cisco Virtualized Video Processing Controller Deployment Guide

Chapter 2 Deploying V2PC

Deploying the V2PC System

Step 3 Configure NTP client in ESXi host as follows:

a. Log in to the vCenter client and select the ESXi host.

b. Navigate to Configuration > Time Configuration > Properties > Options and configure NTP

settings.

c. Start the NTP service using the host option under Startup policy for the NTP Daemon.

Note NTP must be in sync with all ESXi hosts.

Install the Launcher VM from the OVAs

The Launcher has the OVF properties required to configure the networking for the VM. To install the

Launcher VM, first copy the repo.iso, coreOS.ova, and centos.zip files to the Launcher, and then run

the V2P Wizard as described below to generate the JSON file.

Note See the Release Notes for V2PC Release 3.3 for information on image downloads and retrieving the

latest files.

To download and deploy the Launcher OVA, follow the instructions below.

Step 1 Download the Launcher OVA file launcher-3.2.0-8971.ova to the VM to be configured.

When available, the Launcher OVA is available from the Cisco V2PC Software Downloads page at:

http://www.cisco.com/c/en/us/support/video/virtualized-video-processing-controller/tsd-products-support-series-home.html

Note The Launcher VM has only one network interface. This VM should have access to the network where

V2P components are deployed. You can add another network interface to this VM, but doing so requires

manual configuration.

Step 2 Choose the vCenter IP address from the navigation menu at left, and then from the main menu, choose

File > Deploy OVF Template to open the V2P Wizard.

2-7

Cisco Virtualized Video Processing Controller Deployment Guide

Chapter 2 Deploying V2PC

Deploying the V2PC System

Figure 2-1 Deploying the OVA Template

Step 3 Browse to the launcher OVA file location, then click Next.

Figure 2-2 Deploy OVA Template - Source

Step 4 Confirm default OVF settings, then click Next.

2-8

Cisco Virtualized Video Processing Controller Deployment Guide

Chapter 2 Deploying V2PC

Deploying the V2PC System

Figure 2-3 Deploy OVA Template - OVF Template Details

Step 5 Accept the End User License Agreement (EULA), then click Next.

Figure 2-4 Deploy OVA Template - EULA

Step 6 Provide the VM name, then click Next.

2-9

Cisco Virtualized Video Processing Controller Deployment Guide

Chapter 2 Deploying V2PC

Deploying the V2PC System

Figure 2-5 Deploy OVA Template - Name and Location

Step 7 Select the Host or Cluster on which to run the template, then click Next.

Figure 2-6 Deploy OVA Template - Host/Cluster

Step 8 Select a Resource Pool for the template, then click Next.

2-10

Cisco Virtualized Video Processing Controller Deployment Guide

Chapter 2 Deploying V2PC

Deploying the V2PC System

Figure 2-7 Deploy OVA Template - Resource Pool

Step 9 Select the Datastore, then click Next.

Figure 2-8 Deploy OVA Template - Storage

Step 10 Accept Thick Provision as the disk format, then click Next.

Note Additional steps are needed when upgrading from V2PC 3.2.3. See V2PC Upgrade, page 5-1 for details.

Page is loading ...

Cisco Virtualized Video Processing Controller User guide

Cisco Virtualized Video Processing Controller User guide

Related papers

Other documents