cisco virtualized video processing controller user guide ......1 cisco virtualized video processing...

Cisco Virtualized Video Processing Controller User GuideRelease 3.3

March 1, 2018

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.

http://www.cisco.com

http://www.cisco.com/go/offices

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL 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 SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED 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, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, 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 DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, 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.

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 thisURL: 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 partnershiprelationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

Cisco Virtualized Video Processing Controller User Guide© 2017-2018 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/trademarks

C O N T E N T S

Overview 1-1

Product Overview 1-1

V2PC System Requirements 1-3

Getting Started 2-1

Logging In 2-1

Logging Out 2-1

Using the Dashboard 2-1

Configuring Platforms 3-1

Configuring the Platform Type 3-1

Configuring PICs 3-1

Creating the PIC 3-1

Enabling the PIC 3-2

Configuring an Unmanaged Kubernetes Instance 3-2

Configuring Application Resources 4-1

Configuring Providers 4-1

Add a Provider 4-1

Edit a Provider 4-2

Delete a Provider 4-3

Configuring Provider Networks 4-3

Configuring Default Providers 4-3

Configuring Zones 4-4

Add a Zone 4-4

Configure Multiple Zones 4-4

Edit a Zone 4-8

Delete a Zone 4-9

Configuring Nodes 4-9

Add a Node 4-9

Delete a Node 4-10

Configuring Custom Image Flavors 4-11

Deploying Applications 5-1

Creating Application Types 5-1

1Cisco Virtualized Video Processing Controller User Guide

Contents

Configuring Application Instances 5-2

Creating an Application Instance 5-2

Enabling an Application Instance 5-4

Disabling an Application Instance 5-6

Deleting an Application Instance 5-6

Dynamic Configuration 6-1

Configuring Deployed Applications 6-1

Reapplying a Resource SLA 6-2

Configuring Resource SLAs 6-3

Adding an MCE Node 6-3

Deleting an MCE Node 6-4

Adding an MPE Node 6-4

Deleting an MPE Node 6-5

Configuring Channels in Live Media Workflows 6-5

Adding Channels 6-6

Deleting Channels 6-6

Configuring Media Workflow Resources 7-1

Configuring Media Sources 7-1

Configuring an ATS Channel 7-1

Configuring an ATS Channel Lineup 7-2

Configuring Media Archives 7-3

Configuring NAS Media Sources 7-4

Configuring Policies 7-5

Configuring HTTP Header Policies 7-5

Configuring Asset Lifecycle Policies 7-6

Configuring Profiles 7-7

Configuring Auth Profiles 7-7

Configuring ESAM Profiles 7-8

Configuring Key Profiles 7-9

Configuring Storage 7-11

Configuring COS Stores 7-11

Configuring Network-Attached Storage 7-11

Configuring Templates 7-12

Configuring Publishing Templates 7-12

Configuring Media Workflows 8-1

Configuring Media Workflows 8-1

Configure Media Workflow Types 8-1


Contents

Configure a Media Workflow Instance 8-2

Toggle the Media Workflow State 8-2

Creating a VOD Media Workflow 8-3

Required Resources 8-3

Procedure 8-3

Creating a Live Media Workflow 8-5


Procedure 8-5

Creating a cDVR Media Workflow 8-7


Procedure 8-8

Configuring Remote ELK Logging 9-1

Configuration Procedure 9-1

High Availability 10-1

V2PC Master Node High Availability 10-1

Overview 10-1

Deploying a Master Node Cluster with HA 10-1

HA Support for MCE and MPE over V2PC 10-2

Creating Workers in Bulk 11-1

Prerequisites 11-1

Procedure 11-1

Limitations 11-3

Alarms, Events, and Statistics 12-1

Introduction 12-1

Viewing Current InfluxDB Data 12-2

Backing Up InfluxDB Data 12-3

Restoring InfluxDB Data 12-3

Sample Queries 12-4

Alarms at Master Nodes 12-4

OS Level 12-4

Third-Party Application Health Check 12-5

V2PC Component Health Check 12-5

Connection with Worker Nodes 12-6

Alarms at Worker Nodes 12-6

OS Level 12-6

Statistics at Master and Worker Nodes 12-7


Contents

OS Level 12-7


Preface

This guide provides user instructions for the Cisco Virtualized Video Processing Controller (V2PC). V2PC provides a unified control and management interface for all products in the Cisco V2P platform.

Document OrganizationThis document contains the following chapters and appendices:

Chapters or Appendices Descriptions

Overview Introduces V2PC and defines key terms and concepts.

Getting Started Explains how to log in to V2PC and use the Dashboard.

Configuring Platforms Provides instructions on deploying and manage platforms and platform instance controllers (PICs).

Configuring Application Resources Contains information on configuring nodes, providers, and custom image flavors in V2PC.

Deploying Applications Explains how to work with application types and application instances to deploy applications in V2PC.

Dynamic Configuration Describes the steps for modifying deployed applications and SLAs from the V2PC GUI with the application still in service, a new feature introduced with V2PC Release 3.3.

Configuring Media Workflow Resources Provides instructions for configuring the channels, policies, profiles, templates, archives, and other resources used in media workflows.

Configuring Media Workflows Explains how to create and configure media workflow instances based on media workflow templates.

Configuring Remote ELK Logging Describes procedures for configuring V2PC to add a remote ELK server and redirect V2PC logs to this server.

High Availability Provides information on High Availability (HA) support for the V2PC master node.

5Cisco Virtualized Video Processing User Guide

PrefaceDocument Conventions

Document ConventionsThis document uses the following 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.

Creating Workers in Bulk Explains how to use the V2PC GUI to perform bulk worker creation.

Alarms, Events, and Statistics Describes procedures for viewing, backing up, and restoring V2PC statistics and identifies the alarms and events that V2PC nodes can generate.

Chapters or Appendices Descriptions

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.

{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.


PrefaceRelated Publications

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.

Related PublicationsRefer to the following documents for additional information about V2PC:

• Cisco Virtualized Video Processing Controller Deployment 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.x


PrefaceRelated Publications


Cisco

C H A P T E R 1
Overview
This chapter provides general information on the Cisco Virtualized Video Processing Controller (V2PC), including product overview and system requirements.

Product OverviewV2PC is the control interface for the Cisco Virtualized Video Platform (V2P). V2PC provides an open platform that transforms the way video infrastructure is built, deployed, provisioned, and maintained. V2PC enables a video processing application to run over a cloud or on-premise infrastructure while flexibly orchestrating its media workflows and resources.

Figure 1-1 Cisco Virtualized Video Processing (V2P) Platform

1-1Virtualized Video Processing Controller User Guide

Chapter 1 Overview

Customers can rapidly create and orchestrate media workflows across video headends and data center environments, and can evolve seamlessly from a hardware based infrastructure to a hybrid or pure virtualized cloud infrastructure. The software centric workflows increase the reachability of content across a variety of content consumption platforms.

This transformation has resulted in flexible user experiences and simplified operations, allowing customers to better manage, modify, and scale media workflows to support services such as Live, VOD, Time Shift, and Cloud DVR (cDVR) to OTT consumers.

V2PC Components

V2PC works with a hierarchy of components that includes platforms, application containers, service containers, providers, zones, nodes, and the logical functions they support, which are configured into media workflows.

Application Containers

An application container is a logical container that binds together the nodes that contribute to a common function in the media pipeline. Each function is implemented as software application distributed among different nodes that can be VMs, physical appliances, a Linux container, or other functional unit. Application containers can scale independently and elastically based on demand.

Service Containers

A service container is a collection of application containers interconnected by one or more media workflows. Each media workflow defines the arrangement of the application containers within the media pipeline. The media workflow also guides the flow of content through the application containers and the associated processing of data. Media workflows can also be chained, so that the output from one media workflow serves as the input to another.

Media Workflows

A media workflow is a GUI configurable template used to create Live, VOD, or cDVR output.V2PC media workflows support Apple HTTP Live Streaming (HLS), Microsoft HTTP Smooth Streaming (HSS), or MPEG Dynamic Adaptive Streaming over HTTP (DASH) content by applying suitable input and output settings for each application. Media workflows are reusable templates that provide discrete processing functions such as transcoding, publishing, DRM, and DVR buffering.

Networks

V2PC can be deployed with 1, 2, 3, or 4 networks, depending on customer requirements. While a single flat network can be used for functional testing environments, V2PC customer environments will have at least two separate networks, one for management and another for data.

A V2PC network contains one or more regions, and each region is made up of one or more zones. A region can be associated with a geographical region, one or more data centers, or a service area. A zone is a set of cloud platform components (compute, network, storage, and security) that are fate-shared. A zone can be mapped to the underlying cloud platform provider such as a datacenter in vCenter, an availability zone, or any other combination of fate-shared cloud resource topologies.

1-2Cisco Virtualized Video Processing Controller User Guide

Chapter 1 Overview

Nodes

Each zone in a V2PC region is associated with one cloud controller, and has one or more nodes. V2PC works with several types of nodes, which differ by function:

• Repository node – Deployment and upgrade server

• Master node – GUI, configuration, orchestration server

• ELK node – Logging server

• VM Template – Idle VM for cloning applications or third-party nodes

• Application Engines (AE) – Redis, HA Proxy, IPVS

• Media Capture Engine (MCE) – an application within V2PC that performs linear content packaging and capturing, VOD content ingestion, and unified Ingest for Live, VOD, and cDVR. MCE also provides integration with COS and NAS storage.

• Media Playback Engine (MPE) – an application within V2PC that performs just-in-time packaging (JITP) of adaptive transport streams to various ABR formats.

Related Terminology

The following additional terms have specific meanings in the context of V2PC operations:

• Media Workflow Resources – configuration parameters for things like live sources, publish templates.

• Providers – Infrastructure environments such as Atlanta Lab, San Jose Lab, or AWS cloud.

• AIC – application instance controller; handles deployment and deletion of an application.

• Workflow MFC – template that describes creation of a custom workflow.

• Workers – individual virtual machines on which applications run.

• Image flavors – Groups of settings that define the VM, CPU, RAM, and storage for each worker.

V2PC System Requirements• The V2PC master controller should be deployed as 2x large (8 CPU, 32 GB RAM, 40 GB Disk

storage).

• The Repo server should be deployed as 2x large (8 CPU, 32 GB RAM, 40 GB Disk storage).

• The ELK node should be deployed as 2x large with 500 GB disks space (8 CPU, 32 GB RAM, 500 GB Disk storage).

Note VMware ESXi version and patch level requirements may vary by release. Be sure to check the release notes for your release for specific ESXi version and patch level requirements.


Chapter 1 Overview


Cisco

C H A P T E R 2
Getting Started
This chapter explains how to get started using the V2PC GUI.

Logging InOpen a web browser and, in the browser address bar, enter the URL for the V2PC GUI login page (for example, https://10.15.2.1:8443).

At the login prompt, enter a valid username and password in the fields provided, and click Login.

Note The default username is admin. The default password is default.

After logging in, you have full access to all features.

The V2PC GUI opens to Monitor > Dashboard > System Statistics tab by default.

Logging OutTo exit and log out of the V2PC GUI, click the Settings icon at top right of the page and select Logout.

Using the DashboardV2PC provides convenient system, statistics, and alarm and event monitoring using the Dashboard.

After deploying the applications and creating the media workflows, a logical next step is to monitor the statistics and events generated by the system. The Dashboard aggregates all monitoring information on the same page to give a snapshot of the system, available in the following tabs:

• System Statistics – Displays high-level system and application statistics.

• Media Workflows – Lists all configured media workflows. You can drill down to a node of the media workflow to see its CPU, memory, or disk usage. You can also see the performance, events, and nodes associated with the media workflow on this tab.

• Regions – Lists all configured regions. You can also drill down to Provider > Zones > Nodes to see the node CPU, memory, or disk usage.

• Nodes – Lists all nodes available in the system. This tab also shows the performance, events, and associated media workflows of the node.


Chapter 2 Getting Started

Figure 2-1 V2PC Dashboard


Cisco

C H A P T E R 3
Configuring Platforms
This chapter explains how to deploy and manage platforms and platform instance controllers (PICs).

Note PICs are needed for cDVR media workflows only. Live and VOD media workflows do not require them.

Configuring the Platform Type

Step 1 From the navigation menu, choose Platform Deployment Manager > Platform Types.

Step 2 Click Add (+) to add a new Platform Type. The Platform Types dialog opens.

Step 3 Choose the appropriate Package Name from the drop-down list. The currently available predefined platform type is cisco-k8s-upic (Unmanaged Kubernetes Platform).

Step 4 Specify a Description.

Step 5 Click Save.

Configuring PICs

Creating the PIC

Step 1 From the navigation menu, choose Platform Deployment Manager > Deployed Platforms.

Step 2 Choose the Platform Type from the Select Platform drop-down list.

Step 3 Click Add (+) to create a new platform deployment. The configuration wizard opens.

Step 4 Specify the Instance Info parameters and other relevant configuration details.

Step 5 Click Save.


https://100.2.31.54/

https://100.2.31.54/api/v1/proxy/namespaces/kube-system/services/heapster

https://100.2.31.54/api/v1/proxy/namespaces/kube-system/services/heapster

https://100.2.31.54/api/v1/proxy/namespaces/kube-system/services/kube-dns

Chapter 3 Configuring PlatformsConfiguring an Unmanaged Kubernetes Instance

Enabling the PICTo enable the PIC, navigate to Platform Deployment Manager > Deployed Platforms, change its Admin State to Enable, and click Update.

Note V2PC supports both PIC and UPIC options.

To disable the PIC, change Admin State to Disable and click Update.

Configuring an Unmanaged Kubernetes InstanceV2PC supports unmanaged Kubernetes (Docker) deployment. Complete the following steps to create a new unmanaged Kubernetes (cisco-k8s-upic) instance.

Step 1 From the V2PC GUI navigation menu, choose Platform Deployment Manager > Deployed Platforms.

Step 2 Choose the cisco-k8s-upic platform type from the Select Platform drop-down list.

Step 3 Click Add (+) to open the configuration wizard.

Step 4 Specify Instance Info details as follows:

• Name – Enter the instance name.

• Description – Enter a description.

• Region – Select the region for the PIC (Unmanaged).

Step 5 Specify endpoints details as follows:

• Endpoint – Enter the k8s API Server endpoint (for example, https://10.10.10.100:443).

• Docker Registry URL – Enter a Docker registry URL for k8s AIC apps.

Step 6 Specify SSL details as follows:

• If the endpoint is SSL enabled, paste the SSL certifications in the spaces provided for CA, Client Certificate, and Client Key.

Note If the endpoint protocol is http, these options be dimmed by default.

Step 7 Specify Basic Auth details as follows:

• If the endpoint is secured with BasicAuth, enter the Username and Password.

Note If the endpoint protocol is http, this option is dimmed.


Cisco

C H A P T E R 4
Configuring Application Resources
This chapter provides information on configuring providers, provider networks, default providers, zones, nodes, and custom image flavors in V2PC.

Configuring ProvidersV2PC provides support for the following providers.

• VMware

• Bare Metal Unmanaged

Add a ProviderTo configure a new provider:

Step 1 From the navigation menu, choose Application Deployment Manager > Resources > Providers.

Step 2 Select the desired provider Type and enter details for the provider.

Note • V2PC prepopulates the first provider you configure with default provider data.

• V2PC populates the DNS servers. Users cannot enter DNS server IP addresses.

Figure 4-1 Configuring a New Provider


Chapter 4 Configuring Application ResourcesConfiguring Providers

Step 3 When you have finished editing provider details, click Save.

Edit a Provider


Step 2 From the navigation menu, choose the region of interest (for example, region-0) from the Infrastructure Objects menu. The Regions page opens listing all providers for the region.

Step 3 Locate the provider to be edited and click its Edit Provider icon to modify its settings.

Figure 4-2 Editing a Provider

Step 4 Make the necessary changes and click Save.


Chapter 4 Configuring Application ResourcesConfiguring Providers

Delete a Provider



Step 3 Locate the provider to be deleted and click the Delete Provider icon to delete it.

Step 4 When prompted, click Yes to confirm the deletion.

Configuring Provider NetworksOn the Providers page, click Add (+) and configure one or more networks that will be referenced by this provider.

Figure 4-3 Configuring Provider Networks

Note The first network of a default provider is prepopulated with network data.

Configuring Default ProvidersThe V2PC GUI helps to create the first provider by prepopulating the required information, which it retrieves from an XML script file in JavaScript Object Notation (JSON) format named deployInfo.json.

Note The multiJSON file must specify possible images using the provisioning script.



Chapter 4 Configuring Application ResourcesConfiguring Zones

Step 2 Select Region-0 and confirm that Region-0 has no providers added.

Step 3 Click Add (+) to create a new default provider. The page loads with prepopulated data.

Step 4 Specify a name for the default provider and click Save.

Configuring Zones

Add a Zone



Step 3 Click the provider of interest (for example, infra-vdcm) to display the existing zones for the provider.

Step 4 Click Add (+) to open the configuration wizard for adding a new provider.

Step 5 Click Save, and then continue with zone configuration as described next.

Configure Multiple ZonesBeginning with Release 3.3.3, V2PC supports configuring applications (AICs) to use multiple zones, rather than being limited to a single zone and VMware ESXi cluster (and a single VM) as in earlier releases. Configuring AICs with multiple zones, each with its own ESXi cluster, enables the application to find all available nodes for each cluster when the application is deployed or has its SLA updated.

To configure an AIC to use multiple zones:

Step 1 Create (or confirm that you have already created) the ESXi clusters needed for the AIC.

The following example shows two ESXi clusters, each configured with one host:

Figure 4-4 Confirming Clusters for the AIC



Note • Use the same resource pool configuration for each cluster. In this example, both resource pool names are called v2pcresourcepool2, and this resource pool name would be for any other clusters added.

• Make a record of the datastore folders used by each cluster. You will need this information when configuring the provider in the V2PC GUI.

Step 2 Create a new provider as described in Add a Provider, page 4-1. You can use the default values or update the fields as needed to support the multiple-zone feature in your deployment.

Note If you had previously created a provider, you can edit the existing provider by inserting the folder and cluster names from the Provider page of the ESXi cluster.

The following example shows the Edit Provider dialog with two datastore folders and two cluster names:

Figure 4-5 Edit Provider Dialog with Two Clusters



Step 3 Create the required number of zones, associating each with a ESXi cluster through its configuration.

Note Be sure that the datastore and network names are correctly configured and associated with the ESXi cluster. Otherwise, node creation (performed in Step 4) will fail.

The following illustration shows an example of two-zone creation:

Figure 4-6 Creating Two Zones for a Provider



Step 4 Create nodes in each zone as described in Add a Node, page 4-9.

Step 5 Create the AIC as described in Configuring Application Instances, page 5-2.

Step 6 In the Zone field of the AIC, configure the number of zones needed to provide the required number of nodes that the AIC can use.



The following illustration shows an AIC configured with two zones:

Figure 4-7 AIC Configured with Two Zones

Note Zones are accretive, meaning that you can add a zone but not delete or change it after it has been saved and used by the application.

Edit a Zone




Step 4 Click Edit Zone beside the zone to be edited to open the configuration wizard for the zone.

Figure 4-8 Editing a Zone


Chapter 4 Configuring Application ResourcesConfiguring Nodes

Step 5 Make the necessary changes and click Save.

Delete a Zone

Note Before deleting a zone, be sure that the zone is not being referenced by any applications.




Step 4 Click Delete Zone beside the zone to be deleted.


Configuring NodesFrom the navigation menu, choose Application Deployment Manager > Resources > Nodes. This page displays the list of all deployed worker nodes.

Note V2PC supports bulk creation of worker nodes. For details, see Creating Workers in Bulk, page 11-1.

Add a Node




Chapter 4 Configuring Application ResourcesConfiguring Nodes


Step 4 From the navigation menu, choose the zone of interest (for example, zone-1) to display the existing nodes for the zone.

Step 5 Click Add (+) to open the configuration wizard for adding a new node.

Figure 4-9 Adding a New Node

Step 6 Click Save to save the new node.

Step 7 From the navigation menu, choose Application Deployment Manager > Resources > Nodes and confirm that all nodes are in Idle state.

Note It may take some time for this page to populate.

Delete a Node




Step 4 From the navigation menu, choose the zone of interest (for example, zone-1) to display the existing nodes for the zone.

Figure 4-10 Deleting a Node


Chapter 4 Configuring Application ResourcesConfiguring Custom Image Flavors

Step 5 Click Delete beside the node to be deleted.


Configuring Custom Image FlavorsIn addition to predefined image flavors, V2PC supports configuration of custom image flavors. To configure a custom image flavor:

Step 1 From the navigation menu, choose Application Deployment Manager > Resources > Image Flavors. The Image Flavors page opens listing the default image flavors.

Step 2 Click Add (+) to create a new image flavor. The Image Flavors dialog opens.

Step 3 Specify a Name and Description to identify the image flavor.

Step 4 Click Add (+) and specify additional details for the image flavor per system requirements.

Figure 4-11 Configuring a Custom Image Flavor

Step 5 Click Save to save the new image flavor.


Chapter 4 Configuring Application ResourcesConfiguring Custom Image Flavors


Cisco

C H A P T E R 5
Deploying Applications
V2PC uses wizard-based configuration to facilitate deployment of node applications. This chapter provides information on creating application types and configuring application instances – the two main steps needed to deploy applications in V2PC.

To create applications, the required application bundle must first be installed on the V2PC repository server. For example, to add an application manager (AM), capture engine (CE), or playback engine (PE), or SCE, the Virtual Media Packager (VMP) bundle must be installed on the repository server as described in Install the VMP Bundle in the Cisco Virtualized Video Processing Deployment Guide.

Note Similar requirements exist for other applications in the Cisco V2P product family, such as Virtual Digital Content Manager (vDCM), Virtual Media Recorder (VMR), and Cloud Object Storage (COS). Refer to the customer documentation for these applications for details as needed.

Creating Application TypesTo create a new application type in V2PC:

Step 1 From the navigation menu, choose Application Deployment Manager > Application Types. The Application Types page opens and displays a list of application types.

Figure 5-1 Application Types Page


Chapter 5 Deploying ApplicationsConfiguring Application Instances

Step 2 Click Add (+) and choose an application from the Package Name drop-down list.

Figure 5-2 Package Name Drop-Down List

Step 3 Click Save.

Configuring Application InstancesThe life cycle of an application in V2PC includes four phases:

• Creating the application instance

• Enabling the application instance

• Disabling the application instance

• Deleting the application instance

Creating an Application InstanceTo create a new application instance in V2PC:

Step 1 From the navigation menu, choose Application Deployment Manager > Deployed Applications. The Deployed Applications page opens.

Figure 5-3 Deployed Applications Page



Step 2 Choose an application type from the drop-down list.

Step 3 Click Add (+). The Create Application Instance dialog opens.

Figure 5-4 Create Application Instance Dialog

Step 4 Configure the Region, Provider, Zones, and Image template for the deployment.

Note Checks beside the icons at the top of the dialog indicate that the configuration now satisfies the attributes required for particular roles.

Step 5 Click the Configure (gear) icon for each role (for example, MCE) to navigate to the configuration dialog for that role. You can also use the Previous and Next buttons to navigate between dialogs.

Figure 5-5 Role Configuration Dialog



Step 6 Confirm that the configuration icon for each role has a check indicating that its attributes are fully configured.

Step 7 Click Finish to save the configuration.

Enabling an Application InstanceTo enable an application instance:

Step 1 From the navigation menu, choose Application Deployment Manager > Deployed Applications. The Deployed Applications page opens and displays a list of applications.

Step 2 Place a check beside the application to be enabled to select it.

Figure 5-6 Deployed Applications Page, Show Assets Icon

Step 3 Click Show Assets to view the assets for the application and confirm that it has the required number of idle nodes available in the zones configured in the application.



Figure 5-7 Available Nodes Listing

Step 4 Is the available node count at least equal to the Minimum Nodes required?

• If yes, click Enable to enable the application.

• If no, navigate to Application Deployment Manager > Resources > Provider, create the required number of additional nodes under that zone, then return to the Deployed Applications page and click Enable to enable the application.

Figure 5-8 Deployed Applications Page, Application In Service

Step 5 Confirm that the state of the application changes from Idle to In Service.



Disabling an Application InstanceTo disable an enabled application instance:


Step 2 Place a check beside the application to be disabled to select it, and then click Disable to disable it.

Figure 5-9 Deployed Applications Page, Disable Button

Deleting an Application InstanceTo delete an application instance:


Step 2 Place a check beside the application to be deleted to select it, and then click Delete (trash can).

Figure 5-10 Deployed Applications Page, Delete Icon



Note Deleted applications are removed from the Deployed Applications table.


Cisco

C H A P T E R 6
Dynamic Configuration
Beginning with Release 3.3, V2PC supports reconfiguring of deployed applications and resource service level agreements (SLAs) from the V2PC GUI even while the application is in In Service state. Users are allowed to modify the configuration of a deployed application based on the change policy defined by the application type for each attribute in the application.

A change policy is defined for each attribute to determine the operational states during which the attribute can be changed. If an attribute has no change policy defined, the attribute cannot be changed through the V2PC GUI while the application is in In Service state.

Configuring Deployed ApplicationsTo configure a deployed application while still in In Service state:


Step 2 Place a check beside the application to select it, then click Edit (pencil).

Figure 6-1 Deployed Applications Page, Edit Icon

Step 3 Change one of the following categories in a role:

• Desired nodes in Resource SLA section

• State of one or more nodes in Nodes Info section


Chapter 6 Dynamic ConfigurationReapplying a Resource SLA

• Value of one or more attributes in Configuration section

Note You can change only one of the categories in a role or across the roles in an application. When one of the categories is changed, the other categories in the same role and in other roles are disabled. To change the value of another category, you must first click Reset to reverse the current change.

Figure 6-2 Modified Application Configuration

Step 4 Click Finish to save the new configuration. A progress bar appears near the changed category to show that a related change is underway in the V2PC server.

For example, if the number of nodes is being changed from 1 to 2, V2PC dynamically reallocates an idle node from that zone to the application being modified.

Reapplying a Resource SLAWhen V2PC enables or deploys an application and the requested number of nodes is not available, V2PC determines the minimum number of nodes required for the role and allocates that number.

If that number does not satisfy the service level agreement (SLA) for the application, you can add nodes to the deployed application later, as follows:

Step 1 From the navigation menu, choose Application Deployment Manager > Resources > Providers and create the required number of nodes under the zone to which the application is assigned.


Step 3 Place a check beside the deployed application to select it, and then click Edit (pencil) to open the Edit Application Instance dialog.


Chapter 6 Dynamic ConfigurationConfiguring Resource SLAs

Figure 6-3 Edit Application Instance Dialog

Step 4 Select the role for which the additional nodes are to be acquired.

Step 5 Check Resource SLA Re-Apply.

Step 6 Click Finish.

Note You do not need to change the Desired Nodes value. V2PC uses previously configured values to acquire the remaining nodes. For example, if the resource SLA for a role was configured with 1 as the minimum number of nodes and 2 as the desired number, V2PC will enable the role if it has only one node available as this meets the minimum node requirement. V2PC stores the number of nodes originally desired (2 in this example) so that you can create and assign them later.

Configuring Resource SLAsV2PC supports adding and removing nodes in deployed Media Capture Engine (MCE) and Media Playback Engine (MPE) applications while the applications are still in the In Service state.

Adding an MCE NodeTo add a node to a deployed MCE application:


Step 2 Locate the cisco-ce application to be updated in the list of deployed applications and place a check beside it to select it.


Chapter 6 Dynamic ConfigurationConfiguring Resource SLAs

Step 3 Click Edit (pencil) to open the application for editing.

Step 4 In the edit dialog, navigate to MPE and change the Desired Nodes value to the number of nodes desired. For example, if the current value is 2 and one additional node is desired, change the value to 3.

Note To add MCE nodes, the system must have a sufficient number of idle nodes available.

Step 5 Click Finish to save the change.

Step 6 On the Deployed Applications page, locate and select the cisco-ce application, click Edit to open its edit dialog, and review the Nodes section to confirm that the desired number of nodes has been added.

Deleting an MCE Node

Note This procedure will briefly affect any Live or VOD service associated with the MCE node to be deleted.

To delete a node from a deployed MCE application:


Step 2 Locate the cisco-ce application to be updated in the list of deployed applications and place a check beside it to select it.

Step 3 In the edit dialog, open the drop-down list for the node to be deleted and choose Delete.

Caution You are not asked to confirm the deletion. The node is deleted as soon as you click Delete.

Step 4 Change the Desired Nodes value to decrease the number of nodes desired by one. For example, if the number of desired nodes is 3, change the value to 2.


Adding an MPE NodeTo add a node to a deployed MPE application:


Step 2 Locate the cisco-pe application to be updated in the list of deployed applications and place a check beside it to select it.

Step 3 Click Edit (pencil) to open the application for editing.

Step 4 In the edit dialog, navigate to MPE and change the Desired Nodes value to the number of nodes desired. For example, if the current value is 2 and one additional node is desired, change the value to 3.


Chapter 6 Dynamic ConfigurationConfiguring Channels in Live Media Workflows

Note To add MPE nodes, the system must have a sufficient number of idle nodes available.


Step 6 On the Deployed Applications page, locate and select the cisco-pe application, click Edit to open its edit dialog, and review the Nodes section to confirm that the desired number of nodes has been added.

Deleting an MPE Node

Note This procedure will briefly affect any Live or VOD service associated with the MPE node to be deleted.

To delete a node from a deployed MPE application:


Step 2 Locate the cisco-pe application to be updated in the list of deployed applications and place a check beside it to select it.

Step 3 In the edit dialog, open the drop-down list for the node to be deleted and choose Delete.

Caution You are not asked to confirm the deletion. The node is deleted as soon as you click Delete.

Step 4 Change the Desired Nodes value to decrease the number of nodes desired by one. For example, if the number of desired nodes is 3, change the value to 2.


Configuring Channels in Live Media WorkflowsV2PC supports adding and deleting channels in Live media workflows in accordance with the policies defined for the associated resources. The default policies for the Live (livecaptureplayback) media workflow allow users to change the configuration of a Channellineup resource associated with the workflow (for example, live-hls-mediaflow) while the media workflow is still in In Service State.

Note Unless modified from their defaults, policies for other media workflows do not allow users to configure the associated objects when the media workflow is in In Service state.


Chapter 6 Dynamic ConfigurationConfiguring Channels in Live Media Workflows

Adding ChannelsTo add channels to a deployed Live media workflow while still in In Service state:

Step 1 From the navigation menu, choose Media Workflow Manager > Media Workflows. The Media Workflows page opens showing a list of all channels currently defined.

Step 2 Navigate to Media Workflow Manager > Resources > Media Sources > ATS Channel Lineups.

Step 3 Add one or more channels to the associated channel lineups.

Step 4 Navigate to Media Workflow Manager > Media Workflows and confirm that the channels are added.

Deleting ChannelsTo delete channels from a deployed Live media workflow while still in In Service state:

Step 1 From the navigation menu, choose Media Workflow Manager > Media Workflows. The Media Workflows page opens showing a list of all channels currently defined.

Step 2 Navigate to Media Workflow Manager > Resources > Media Sources > ATS Channel Lineups.

Step 3 Delete one or more channels from the associated channel lineups.

Step 4 Navigate to Media Workflow Manager > Media Workflows and confirm that the channels are deleted.


Cisco

C H A P T E R 7
Configuring Media Workflow Resources
This chapter provides procedures for configuring media workflow resources – the channels, policies, profiles, templates, archives, and other resources that can be referenced from multiple media workflows. Media workflows bind policies, templates and other resources together to ingest and package assets for one or more media sources.

Configuring Media Sources

Configuring an ATS Channel

Step 1 From the navigation menu, choose Media Workflow Manager > Media Workflows > Media Sources > ATS Channels.

Step 2 Click Add (+) to add a new channel. The Create ATS Channel dialog opens.

Figure 7-1 Create ATS Channel Dialog


Chapter 7 Configuring Media Workflow ResourcesConfiguring Media Sources

Step 3 Complete the fields in this dialog by specifying the Name, Channel ID, Source Type (UDP or HTTP), and Primary – Target Multicast Address/Source IP.

To add an ABR Profile, click Add (+) in the ABR Profiles section.

Note ABR profiles are not sharable among ATS channels. If you use the V2PC GUI to create ABR profiles within an ATS channel and then delete the ATS channel, the ABR profiles associated with the channel are also deleted. However, if you create ABR profiles outside the V2PC GUI and then share them among multiple ATS channels, you cannot delete the shared ATS channels from within the V2PC GUI.

Step 4 Click OK.

Configuring an ATS Channel Lineup

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Media Sources > ATS Channel Lineups.

Step 2 Click Add (+) to add a new channel lineup. The ATS Channel Lineups page opens.

Figure 7-2 ATS Channel Lineups Page

Step 3 Add the desired channel(s) from the right pane to the new channel lineup in the left pane.

Step 4 Specify a Name, Description, and Media Archive for the channel lineup.

Step 5 Click Save.



Note The right pane only displays channels belonging to the media archive currently selected in the drop-down list. If multiple media archives exist, select the desired media archive from the list to make its corresponding channels available in the right pane.

Configuring Media ArchivesMedia archives are storage locations for stream segments that have reached a predefined archive time. Segments stored in media archives can be reconstituted for later use and then re-archived.

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Media Sources > Media Archives.

Step 2 Click Add to add a new archival configuration. The Media Archives page opens.

Figure 7-3 Media Archives Page

Step 3 Specify the following parameters as needed (all are optional):

• Archive Time – Elapsed time after which the stream is put into archive storage.

• Re-archive Time – Time after which the reconstituted stream can be archived again.

• Archive Start Time – Time to start running the archival process for any segment that has passed the Archive Time.

• Archival Duration – How long to run the archival process before taking a break.



• Archival Pause – Pause time between archival runs.

Step 4 Click Save.

Configuring NAS Media Sources

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Media Sources > NAS Media Sources.

Step 2 Click Add (+) to add a new NAS media source. The NAS Media Sources page opens.

Figure 7-4 NAS Media Sources Page

Step 3 Specify the following parameters:

• Name – Name of the NAS media source, or content library (required). The name is a string of up to 30 characters. Acceptable characters are uppercase and lowercase letters, numbers, periods (.), dashes (-), and underscores (_). The name must not begin with a period (.) and is not case-sensitive.

• Description – Description of the NAS media source. The description is a string of up to 30 characters, and can include uppercase or lowercase letters, numbers, and any special characters.

• Share Path – Share path used by the NAS media source on the network (required). The share must be mounted and active on the V2PC system before the files in this path are accessible.

• NFS Version – Version of the Network File System (NFS) used by the NAS media source. Valid versions are 3.0 and 4.0.

• Servers (IP Address Ranges) – Range of servers available to the NAS media source. For a single server, the Start and End IP addresses are the same.

Step 4 Click Save.


Chapter 7 Configuring Media Workflow ResourcesConfiguring Policies

Configuring Policies

Configuring HTTP Header PoliciesThe HTTP header policies control the HTTP headers for publishing content.

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Policies > HTTP Header Policies.

Step 2 Click Add (+) to add a new HTTP Header Policy. The HTTP Header Policies dialog opens.

Figure 7-5 HTTP Header Policies Dialog


• Name – Name of the HTTP header policy (required). The name is a string of any length. Acceptable characters are uppercase and lowercase letters and numbers. No special characters are allowed. The name is not case-sensitive.

• Description – Description of the HTTP header policy. The description is a string of up to 70 characters, and can include uppercase or lowercase letters, numbers, and any special characters.

• Request Type – Indicates whether the rule is for a Manifest or Chunk.

• HTTP Version – Version of HTTP request. The only valid value is HTTP 1.1.

• Header Name – HTTP header name. Predefined headers are provided, but can be edited or modified.

• Header Value – HTTP header value.


Chapter 7 Configuring Media Workflow ResourcesConfiguring Policies

Note For a Live service, if Request Type is set to Manifest and HTTP Version is set to HTTP 1.1, Header Name must be set to Cache-Control and Header Value must be set to max-age=0. Each HTTP header policy must contain at least one rule.

Step 4 Click OK.

HTTP Header Policy Examples

• Chunk http 1.1 Cache-control max-age=3600 (recommended for VOD; 0 for Live)

• Manifest http 1.1 Cache-control max-age=3600 (recommended for VOD; 0 for Live)

Configuring Asset Lifecycle PoliciesAsset lifecycle policies control the Time-Shift TV (TSTV) window for Live capture.

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Policies > Asset Lifecycle Policies.

Step 2 Click Add (+) to add a new Asset Lifecycle Policy. The Asset Lifecycle Policies dialog opens.

Figure 7-6 Asset Lifecycle Policies Dialog


• Asset Lifecycle Policy Name – Name of the asset lifecycle policy (required). The name is a string of up to 63 characters. Acceptable characters include uppercase and lowercase letters, numbers, periods (.), dashes (-), and underscores (_). The name must not begin with a period (.), and it is not case-sensitive.


Chapter 7 Configuring Media Workflow ResourcesConfiguring Profiles

• Type – Type of asset lifecycle policy. The only valid value is DVR Window.

• Description – Description of the asset lifecycle policy. The description is a string of any length, and can include uppercase or lowercase letters, numbers, and any special characters.

• Policy Rules – Specify the following:

– Match Tags – Indicates whether the rules apply to an entire asset or only to a segment. Segment is required for a Live service. MatchTags can be configured for both Segment and Manifest, and can be stored either locally (in virtual memory on CE workers) or remote (in NAS or COS storage).

– Time – Time in seconds after which the specified action is to be taken.

– Action – Action to apply to the asset or segment. Valid values are Move and Purge.

– Storage – NAS store associated with the rule.

– Enabled – Indicates whether the rule is enabled. Valid values are True (enabled) and False (disabled).

Step 4 Click OK.

Configuring Profiles

Configuring Auth ProfilesAuthorization (auth) profiles are profiles that point to an auth provider. To set up an auth profile:

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Profiles > Auth Profiles.

Step 2 Click Add (+) to add a new auth profile. The Auth Profile dialog opens.

Figure 7-7 Auth Profile Dialog




• Name – Name of the auth profile (required). The name is a string of any length. Acceptable characters include uppercase and lowercase letters, numbers, periods (.), dashes (-), and underscores (_). The name must not begin with a period (.), and it is not case-sensitive.

• Type – Type of auth profile. The only valid value is swauth.

• User ID – User ID for auth profile.

• Access Key – Auth profile access key.

• Auth Server URL – URL for the auth server.

• Token Refresh Interval – Time in seconds after which the auth token is refreshed.

• Description – Description of the auth profile. The description is a string of any length, and can include uppercase or lowercase letters, numbers, and any special characters.

Step 4 Click OK.

Configuring ESAM ProfilesThe Event Signaling and Management (ESAM) profiles define ESAM multi-screen ad insertion.

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Profiles > ESAM Profiles.

Step 2 Click Add (+) to add a new ESAM Profile. The ESAM Profile dialog opens.

Figure 7-8 ESAM Profile Dialog




• Name – Name of the ESAM profile (required). The name is a string of any length. Acceptable characters include uppercase and lowercase letters, numbers, and underscores (_). The user ID must not begin with a period (.), and it is not case-sensitive.

• POIS URL – Placement Opportunity Information System (POIS) URL of the ESAM server (required).

• Description – Description of the ESAM profile. The description is a string of up to 235 characters, and can include uppercase or lowercase letters, numbers, and any special characters.

• Version – Version of the ESAM profile. Choose a version from the drop-down list. Valid versions are OC-SP-ESAM-API-I01 and OC-SP-ESAM-API-I03.

Step 4 Click OK.

Configuring Key ProfilesThe key profiles define encryption profiles.

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Profiles > Key Profiles.

Step 2 Click Add (+) to add a new key profile. The Key Profile dialog opens.



Figure 7-9 Key Profile Dialog


• Key Profile Name – Required name for the key profile. The name is a string of up to 200 characters. Acceptable characters include uppercase and lowercase letters, numbers, and underscores (_). The user ID must not begin with a period (.), and it is not case-sensitive.

• Description – Optional description for the key profile. The description is a string of up to 235 characters, and can include uppercase or lowercase letters, numbers, and any special characters.

• KMS Type – KMS type used by the key profile. Valid KMS types are VGC (supports DRM types HLS-AES-128) and NAGRA.

• DRM Type – DRM type used by the key profile. Valid DRM types are VGC-HLS and CENC-DASH CENC. Choose CENC-DASH to enable Common Encryption Scheme (CENC) for DASH.

• Key Service URI – Optional key service URI used to acquire the key profile.

• CENC Priority – Required when CENC DASH is enabled (DRM Type = CENC-DASH). Choose Widevine or PlayReady as appropriate.

• Widevine – Choose Enable or Disable as appropriate.

• License Acquisition URL – Required if Widevine is enabled; optional if Widevine is disabled.

• Widevine Provider – Optional field used to identify the provider for Widevine, if used.

• Playready – Choose Enable or Disable as appropriate for PlayReady content protection.

Step 4 Click OK.


Chapter 7 Configuring Media Workflow ResourcesConfiguring Storage

Configuring StorageCisco Cloud Object Storage (COS) provides virtual object-based storage for V2P media workflows. COS storage nodes are organized into clusters to provide a distributed, scalable, and resilient storage solution.

Configuring COS Stores

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Storages > COS Stores.

Step 2 Click Add (+) to add a new COS Store. The COS Stores page opens.

Figure 7-10 COS Stores Page


• COS Store Name – Specify a name to identify the COS Store. The name must be unique.

• Container – Specify the container.

• Auth Profile – Choose the auth profile from the drop-down list.

• Description – Enter a name.

Step 4 Click Save.

Configuring Network-Attached Storage

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Storage > Network-Attached Storage (NAS).

Step 2 Click Add (+) to add a new NAS store. The Network-Attached Storage (NAS) page opens.


Chapter 7 Configuring Media Workflow ResourcesConfiguring Templates

Figure 7-11 Network-Attached Storage (NAS) Page


• Name – Name of the NAS store (required). The name is a string of up to 30 characters. Acceptable characters are uppercase and lowercase letters, numbers, periods (.), dashes (-), and underscores (_). The name must not begin with a period (.) and is not case-sensitive.

• Description – Description of the NAS store. The description is a string of up to 100 characters, and can include uppercase or lowercase letters, numbers, and any special characters.

• Share Path – Share path used by the NAS store on the network.

• NFS Version – Version of the Network File System (NFS) used by the NAS store. Valid versions are 3.0 and 4.0.

• Start and End IP Address – The first three bytes of the Start IP Address must match those of the End IP Address. For example, 1.1.1.1 to 1.1.1.2 is a valid start and end IP address range, but not 1.1.1.1 to 1.1.2.2. For a single server, the Start IP Address and the End IP Address are the same.

Step 4 Click Save.

Configuring Templates

Configuring Publishing Templates

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Templates > Publishing.

Step 2 Click Add (+) to add a new publishing template. The Publishing Templates dialog opens.

Figure 7-12 Publishing Templates Dialog




• Name – Name of the template (required). The name is a string of up to 63 characters. Acceptable characters include uppercase and lowercase letters, numbers, periods (.), dashes (-), and underscores (_). The name must not begin with a period (.), and it is not case-sensitive.

• Description – Description of the template. The description is a string of any length, and can include uppercase or lowercase letters, numbers, and any special characters.

• Package Format – Package format supported by the template. Valid values are HLS (the default setting), HSS, HDS, CIF, and CIF-DASH-TS, and DASH-MP4.

• Segment Duration – For segmented files, maximum time, in seconds, to write to a file before starting a new segment (required). The segment duration must match the encoder boundary Point (EBP) configured on the encoder, or it must be a multiple of the EBP value.

• Key Rotation – Number of seconds to wait before using a new encryption key.

• DVB Bitmap Pass Through – Only applicable to HLS package format. Enables passthrough of DVB bitmap subtitle PID to downstream applications. The DVB bitmap subtitle data in the source is retained in the TS segments.

• DVB Bitmap To ID3 – Only applicable to HLS package format. Transforms DVB bitmap subtitles to SMPTE Timed Text (SMPTE-TT) format. SMPTE-TT XML files containing subtitle images are tagged by the ID3 tag and embedded as timed metadata in TS segments.

• Subtitle Policy – Subtitle policy associated with the template.

Step 4 Specify the following Package options:

• Stream Configuration – Configure the stream as described in Stream Configuration, page 7-14. The stream can be HLS, HSS, CIF, or CIF-DASH-TS based on user requirements. Choose HLS for Apple clients, HSS for Microsoft players, or CIF as appropriate.

• Variants – Enables you to provide a subset of video and audio bit rates to specific devices. For example, you could create a variant called mac and assign three top bit rates to it, and then create another variant called ipad and assign three lower bit rates to it.



– Name – Name of the variant (required). The name is a string of any length, and can include uppercase or lowercase letters, numbers, and any special characters.

– Selective Publish – Supports selective publishing of DASH video profiles as detailed in –If you configure 1.05 MB and 2.9 MB, both 1 MB and 3 MB are displayed in the manifest because both are within 5% of an actual bit rate., page 7-15. When set to False, no video is filtered and the system appends these profiles to the manifest. When set to True but without specifying any video streams, no video is filtered.

Note Selective Publish is supported for HLS content through the VMP Service Manager GUI. For details, see the Cisco Virtual Media Packager User Guide for your VMP release.

– Default Audio Stream (PID) – Name of the default audio stream associated with the variant.

– Enable SMPTE-TT – Enables (if True) or disables (if False) SMPTE Timed Text format for the variant.

– Enable WEBVTT – Enables (if True) or disables (if False) Web Video Text Tracks format for the variant.

– Enable CC608 – Provides the option to disable or enable pass-through of CEA-608 closed captions.

– Enable CC708 – Provides the option to disable or enable pass-through of CEA-708 closed captions.

• Video Streams – Identifies the individual variants by bit rate in bits per second and resolution in pixels.

• Content Protection – Specifies the DRM method.

• Transport – Specifies the HTTP transport policy.

Step 5 Click OK.

Stream Configuration

The Stream Configuration table in the Publishing Templates dialog displays the following parameters for each stream associated with the selected variant:

• Type – Type selections are Audio, Subtitle, Video, ID3, UserConfig (required).

• Action – Update or Disable Stream Configuration (required).

• Language – Language used for the stream, such as en for English.

• PID/ID – ID of the PID.

• Codec – Format of the stream, such as AAC, DD/AC-3, DD+/EC-3.

• Bitrate (bps) – This column is available when the order of the variant is BITRATE. The bit rate that you enter must be within 5% of an actual bit rate. The output manifest will include these profiles with the order user specified.

• Name – Name of the output stream. The name is a string of any length, and can include uppercase or lowercase letters, numbers, and any special characters.

• Language – Language used for the output stream, such as en for English (required).

Click the appropriate icon to add, edit or delete, then click Save to save your settings or Cancel.

When configuring bit rates for video and audio streams, keep the following considerations in mind:



• The order in which you configure the bit rates is the order in which they are displayed in the manifest.

• The bit rates must be within 5% of an actual output stream generated by the source. Otherwise, the system excludes that bit rate from the manifest.

• If none of the bit rates in a list is within 5% of an actual bit rate, the VMP generates a 404 error code when you request a manifest.

• If you do not specify a list of bit rates, then the VMP includes all of the bit rates generated by the source in the manifest.

For example, if you have a Digital Content Manager (DCM) that generates video bit rates of 1MB, 2MB, 3MB, 4MB, and 5MB:

– You can configure video bit rates of 1 MB, 4 MB, and 5 MB to display them in the manifest in descending order, or of 5 MB, 4 MB, and 1 MB to display them in ascending order.

– If you configure 1.5 MB and 4 MB, only 4 MB is displayed in the manifest. 1.5 MB is not within 5% of an actual bit rate.

– If you configure 1.5 MB and 3.5 MB, the VMP generates a 404 error code because neither bit rate is within 5% of an actual bit rate.

– If you configure 1.05 MB and 2.9 MB, both 1 MB and 3 MB are displayed in the manifest because both are within 5% of an actual bit rate.

Configuring Selective Publishing

Selective publishing lets you configure DASH I-frame video stream assets in a selection of video profiles, or variants, to tailor the resolution and frame rate of the stream to specific TV and mobile display devices. Only assets matching the specified filter conditions are published.

Variants for mobile devices support HE-AAC audio profiles only. Variants configured for TV delivery support either HE-AAC or AC3 audio profiles.

Regarding filter conditions, either resolution or bit rate, or both, can be specified. If resolution is specified, only assets that exactly match are published. If resolution and bit rate are both specified, the settings should be compatible. In the event of a conflict, resolution takes priority over frame rate.

To enable selective publishing for a DASH video asset from the V2PC GUI:

Step 1 From the V2PC GUI navigation menu, choose Media Workflow Manager > Resources > Templates > Publishing.

Step 2 Choose DASH-MP4 as the Package Format.

Step 3 Choose Publish Template > Package > Variant.

Step 4 In the DASH publish template, choose True for Selective Publish.

Step 5 In Video Streams, add the required resolution (in pixels) and bit rate (in bits per second) filter conditions.

Note If there are filters specified in video streams but no video assets match them, no video is output. If there are multiple filters specified in video streams, video assets matching any filter are published.


Cisco

C H A P T E R 8
Configuring Media Workflows
This chapter provides procedures for configuring media workflows. V2PC simplifies this task by allowing users to create media workflow instances based on workflow templates.

V2PC supports three basic types of media workflows:

• Video on Demand (VOD) – enables playback of recorded video content from virtual storage.

• Live – enables delivery of video content directly from a capture, encoding, and distribution pipeline.

• Cloud DVR (cDVR) – enables recording, storage, and playback of video program material using virtual resources.

The Media Workflow Manager page lets you configure each of these media workflows.

Configuring Media WorkflowsV2PC media workflows are collections of resources, policies, and templates. You can use media workflows to configure a sequence of applications to implement media ingest, control, storage, and playback for multi-screen use cases such as VOD, Live, and cDVR. A media workflow can also orchestrate resources across regions.

A media workflow can be created by selecting a media workflow type and adding a media workflow instance.

Note Before adding the media flow controller (MFC) in V2PC, the corresponding AIC and resources (service domain objects) must be created, enabled, and placed in In Service state. See Deploying Applications, page 5-1 for details on adding an AIC.

Configure Media Workflow Types

Step 1 From the navigation menu, choose Media Workflow Manager > Media Workflow Types.

Step 2 Click Add (+) to add a new media workflow type. The Media Workflow Types page opens.

Figure 8-1 Media Workflow Types Page


http://cdvr1.pe1.v2pcopys.com/cdvrl-live/lax02/lax02.m3u8

Chapter 8 Configuring Media WorkflowsConfiguring Media Workflows

Step 3 Choose an available media workflow type from the Package Name drop-down list:

• Live: cisco-mfc

• VOD: cisco-vod-mfc

• cDVR: cdvr-mfc

Note These media workflow types are available on the V2PC repository and are ready for use directly from the GUI. Other custom media workflow types may be available depending on your V2PC system deployment.

Step 4 Click Save.

Configure a Media Workflow Instance

Step 1 From the navigation menu, choose Media Workflows to open the Media Workflows page.

Step 2 Choose the desired media workflow from the drop-down list and click the + button. The Configuration dialog opens.

Note You can configure VOD, Live, and cDVR media workflows using the wizard that appears at the bottom of the page.

Step 3 In the Name field, type a name for the media workflow instance.

Step 4 Select appropriate Resources and Configurations for each node.

Step 5 Click Save.

Toggle the Media Workflow StateTo enable or disable a media workflow after completing the configuration, go to the navigation menu, click Media Workflows, select the desired media workflow, and then click Play to enable, or Stop to disable.


Chapter 8 Configuring Media WorkflowsCreating a VOD Media Workflow

Creating a VOD Media WorkflowV2PC supports user deployment of VOD media workflow instances either from the V2PC GUI or using the V2PC REST API. These instructions describe V2PC GUI operations. For API information, see the Cisco Virtualized Video Processing Controller API Guide.

Required ResourcesThe following resources are required to create a VOD media workflow:

• NAS MediaSource

• NAS Storage or COS Store

• Publish templates

Note For media workflows that include several publish templates (for example, several HLS and DASH publish templates), all publish templates should have the same segment duration. Otherwise, the final segment duration for the media workflow is not predictable. For example, if a media workflow includes publish templates of 2-seconds, 6-seconds, and 8-seconds duration, its final segment duration may be 2, 6, or 8 seconds depending on which publish template occurs last in the workflow.

ProcedureFollow these steps to configure a VOD media workflow:

Step 1 From the navigation menu, choose Media Workflow Manager >Media Workflow Types and create a cisco-vod-mfc media workflow type.

Note The cisco-vod-mfc is already uploaded to the V2PC repository by default, and is ready to use.

Figure 8-2 Media Workflow Types Page


Chapter 8 Configuring Media WorkflowsCreating a VOD Media Workflow

Step 2 Confirm that AICs (cisco-ce, cisco-pe, cisco-am) are created and enabled in the Application Deployment Manager and that the NAS Mediasources is created.

Step 3 From the navigation menu, choose Media Workflow Manager > Media Workflows, select vodcaptureplayback, and then click Add (+) to add a new media workflow controller.

Figure 8-3 Media Workflows Page - Selecting vodcaptureplayback

Step 4 On the Media Workflows page, navigate to each application by clicking its icon or using the Previous and Next buttons. In each case, select application instance and other configurations specific to the application.

Figure 8-4 Media Workflow Configuration Wizard

Step 5 After configuring all applications, click Finish.


Chapter 8 Configuring Media WorkflowsCreating a Live Media Workflow

Creating a Live Media WorkflowV2PC allows the user to view the channels associated with a live media workflow and to drill down on each asset to view its details.

Required ResourcesThe following resources are required to create a Live media workflow:

• Channels

• Channel Lineup

• Publish Templates

• Asset Life Cycle Policies


ProcedureFollow these steps to configure a Live media workflow:

Step 1 On the Media Workflow Manager >Media Workflow Types page, create a cisco-mfc media workflow type.

Step 2 Confirm that the necessary AICs (cisco-ce, cisco-pe, and cisco-am) are created and enabled in Application Deployment Manager and that the ATS Channel Lineup is created.

Step 3 Navigate to the Media Workflow Manager > Media Workflows menu and choose the livecaptureplayback menu option.

Step 4 On the Media Workflows page, navigate to each application by clicking its icon or using the Previous and Next buttons. In each case, select the application instance and other configurations specific to each endpoint.

Figure 8-5 Media Workflow Configuration Wizard - Configuring livecaptureplayback


Chapter 8 Configuring Media WorkflowsCreating a Live Media Workflow

Step 5 After configuring all applications, click Finish.

Showing Media Workflow Assets

Place a check beside a media workflow to select it, and then click Show Assets to view the list of associated channels. The Assets tab in the lower half of the page list the channels.


Chapter 8 Configuring Media WorkflowsCreating a cDVR Media Workflow

Figure 8-6 Showing Live Media Workflow Assets

Click the name of a channel in the Assets tab to view the details of the channel.

Figure 8-7 Viewing Live Media Asset Details

Creating a cDVR Media Workflow

Note Before configuring a cDVR media workflow, confirm that the MEMSQL database, Docker registry, and COS have been configured by your system administrator.

Required ResourcesThe following resources are required to create a cDVR media workflow:

• Channels

• Channel Lineup



• Publish Templates


ProcedureFollow these steps to configure a cDVR media workflow:


Step 2 Verify that the VMR application has been added under Applications and is in In Service state.

Step 3 From the navigation menu, choose Media Workflow Manager > Media Workflow Types.

Step 4 Click Add (+) at upper right to add a new media workflow.

Step 5 Choose cdvr-mfc from the Package Name drop-down list, and then click Save.

Step 6 Verify the package and version, and then return to the Media Workflows page.

Step 7 Under Media Workflows, choose the media workflow type cdvrcaptureplayback.

Step 8 Click + to the right of the Workflow Type field and provide a name for the media workflow.

Step 9 Click the Media Source icon in the media workflow diagram and choose the appropriate Application Instance and Channel Lineup from their respective drop-down lists.

Step 10 Click the Capture icon in the media workflow diagram and choose the appropriate Capture app instance and configuration from their respective drop-down lists.

Step 11 Click the Recorder icon in the media workflow diagram and choose the appropriate Recorder app instance and configuration from their respective drop-down lists.

Step 12 Click the Playback icon in the media workflow diagram and choose the appropriate Playback app instance and configuration from their respective drop-down lists.

Step 13 Click Save to save your entries and return to the Media Workflow Manager page.

Step 14 Verify the newly created media workflow shows a status of idle.

Step 15 Place a check beside the media workflow to select it, and then click the Play button.

Step 16 Confirm that the status of the media workflow transitions from idle to inprogress and then to inservice.

Step 17 Click the Show Assets button to review and confirm the media workflow assets. Use the buttons at upper right to toggle between form view and flowchart view.

Media Workflows and Dynamic Configuration

When a media workflow is in the In Service state, the configuration of the workflow itself cannot be changed. However, the configurations of the resource objects referenced by the workflow can be changed if such changes are allowed by the resource policies defined for them.



For example, if an in-service instance of a livecaptureplayback (Live) media workflow references a live-hls-mediaflow (Channel Lineup) resource object, channels can be added to or deleted from the lineup object because such changes are allowed by the resource policy for the Live instance.

Figure 8-8 Changing Channel Lineup Configuration of In Service Media Workflow


Cisco

C H A P T E R 9
Configuring Remote ELK Logging
This chapter explains how to configure V2PC to add a remote ELK server and redirect V2PC logs to the remote server. The ELK server must be up and running, but need not have been bootstrapped during the initial V2PC deployment.

This procedure involves running a script from any V2PC master node to change the logging location to the remote ELK server, and can be performed at any time following initial V2PC deployment.

The script performs two basic tasks:

• Registers the new ELK server IP address as a Consul service. The next time you create a new node, the node automatically sends logs to the specified ELK server IP address.

• For each node listed, updates the td-agent.conf file to reflect the new ELK server IP address and then restarts td-agent/fluentd. After restarting, the daemon sends logs to that IP address.

Configuration ProcedureTo send V2PC logs to a remote ELK server that was not created during the initial bootstrap process:

Step 1 Confirm that the V2PC instance is bootstrapped with an updated ISO image, or has been upgraded using the v2plogging-master rpm on the master nodes and the v2p-logging-worker rpm on the worker nodes.

Step 2 Copy (scp) the v2pcssh.key file to the /opt/cisco/v2p/v2pc/v2p-logging-master/src/ directory on any master node.

Note This key was generated by the Docker container during the bootstrap process, and is used to access the nodes of your V2PC instance.

Step 3 Change to the V2PC logging master source directory as follows:

cd /opt/cisco/v2p/v2pc/v2p-logging-master/src/

Step 4 In this directory, create a new text file named IPlist.txt and enter a list of all of the nodes that should send logs to the remote ELK server. Use the format shown below, with each node entered on its own line:

[NODE TYPE(master/worker)] [IP]ex: master 20.0.112.33

master 20.0.112.35worker 20.0.112.38...


Chapter 9 Configuring Remote ELK LoggingConfiguration Procedure

Note A sample IPList.txt file is available for use as a template. Contact Cisco for details.

Step 5 Execute the following command to run the script:

./changeELKServer.sh </path/to/v2pcssh.key> </path/to/ip/list.txt> <elk-log-ip>

where:

• </path/to/v2pcssh.key> is the location of v2pcssh.key

• </path/to/ip/list.txt> is the location of IPlist.txt

• <elk-log-ip> is the IP address of the remote EKL server

Note An alternate script named ./changeELKWizard.sh is available with prompts to guide users through the steps of entering the arguments and changing the ELK server td-agent. Contact Cisco for details.


Cisco

C H A P T E R 10
High Availability
This chapter provides information on High Availability (HA) support for the V2PC master node.

V2PC Master Node High Availability

OverviewV2PC supports High Availability (HA) for the master node. Three master nodes are currently deployed for a minimum HA cluster. V2PC also supports single node deployment with HA disabled.

In an HA cluster of three nodes, all V2PC platform components will survive in any of the following failure scenarios:

• One master node fails due to a reboot, crash, network partition, and so on.

• One instance of any service component fails in one node; for example, one mongo instance failure, one service manager instance failure, and so on.

• V2PC allows for multiple services to degrade with one simultaneous instance failure per service; for example, one MongoDB instance failure with one Service Manager instance failure at the same time.

V2PC master nodes are built on top of multiple services. Each service has its own HA method, with either Active/Active or Active/Standby HA.

Deploying a Master Node Cluster with HA

Installation

For the V2PC bootstrap procedure, see the setup steps described in the Cisco Virtualized Video Processing Controller Deployment Guide. On choosing the HA topology, the system is automatically initialized with three master nodes having HA support.


Chapter 10 High AvailabilityV2PC Master Node High Availability

Access to V2PC GUI

The V2PC service leader provides services to users in HA mode. To access the V2PC GUI seamlessly during leadership switches, an external DNS server brings up the V2PC cluster. The external DNS information can be specified under the mosDNS section of the bootstrap JSON file. The GUI can be accessed using https://v2pc-ui.$External_Domain:8443.

The user device must have access to the external DNS server and be configured to use this server. We strongly recommend using an external DNS server to install the V2PC cluster.

If an external DNS server is not provided or is configured incorrectly (for example, with an incorrect hash key), the GUI logs a warning but continues to operate. If this occurs, you can access the GUI using the IP address of the master V2PC GUI. To find the IP address of the master node, log in to the one of the master nodes and run the command nslookup master.v2p-ui.service.$Primary_Region.$Domain.

Note In the event of a leadership switch, the IP address must be rediscovered and the new master IP address used.

HA Support for MCE and MPE over V2PCV2PC support for HA with MCE and MPE works as summarized below.

Single Master Failure

• For a single MCE worker and a zookeeper leader not on the master, there is no service disruption.

• For a single MCE worker and a zookeeper leader on that master, there is a service disruption, the asset fails, and it is necessary to disable and re-enable the media workflow.

• For two or more MCE workers and a zookeeper leader not on the master, there is no service disruption.

• There is no service disruption to MPE in any of these failure scenarios.

All Three Master Nodes Fail

If all three master nodes fail, there is no service disruption to existing playout. Existing playout will continue.


Cisco

C H A P T E R 11
Creating Workers in Bulk
This chapter provides instructions for creating workers in bulk through the V2PC GUI.

Prerequisites• The user has bootstrapped the V2PC cluster from the launcher node.

• The user has created the provider, network, and zone from the V2PC GUI.

Procedure

Step 1 From the navigation menu, choose Application Deployment Manager > Resources > Nodes. The Nodes page opens.

Figure 11-1 Nodes Page

Step 2 Click the Add (+) icon to add one or more worker nodes. The Bulk Nodes Creation dialog opens.


Chapter 11 Creating Workers in BulkProcedure

Figure 11-2 Bulk Nodes Creation Dialog

Step 3 Enter the number of nodes and other information as needed:

• Number of nodes – Enter number of nodes

• Region – Select Region Name

• Provider – Select Provider Name

• Zone – Select Zone

• Description – Enter Description

• Image Tag – Select Image

• Image Flavor – Select Image Flavor

• Flavor Name – Select Image Flavor Name

Step 4 Enter the IP addresses for the management and data interfaces:

• Management – Select Network and enter IP Address Start Range

• Data In – Select Network and enter IP Address Start Range

• Data Out – Select Network and enter IP Address Start Range

Step 5 Click Create. The GUI automatically configures each node and assigns a sequential IP address.

Note All nodes are created in the configured zone.

A popup window displays the status of the node creation process.

Figure 11-3 Node Creation Status Window



Limitations• From the V2PC GUI navigation menu, choose Application Deployment Manager > Resources >

Nodes to confirm that nodes are created as expected.

• There is a limit of up to 10 worker nodes maximum creation at a time.

• Bulk worker creation only supports contiguous IP address ranges.


Cisco

C H A P T E R 12
Alarms, Events, and Statistics
This chapter describes the procedures for viewing, backing up, and restoring V2PC statistics. It also lists the alarms and events that V2PC master and worker nodes can generate, and the statistics V2PC can collect.

Caution Statistics data is not highly available. If the hosting server crashes and cannot recover data, that data will be lost. This chapter provides guidance on preventing loss of statistics in the event of a fatal crash.

IntroductionInfluxDB, a database for time series data, aggregates control plane statistics for the V2PC platform and its applications. The InfluxDB database instance runs on the ELK node VM.

All statistics from various V2PC nodes are sent to InfluxDB through the Sensu monitoring platform. The Sensu server runs in a high-availability (HA) configuration on the V2PC master nodes. Through Sensu checks, the statistics handler collects statistics from each node or service and sends it to InfluxDB running on the ELK node.

Note For additional information on InfluxDB, see the documentation for InfluxDB version .12 at: https://docs.influxdata.com/influxdb/v0.12

Figure 12-1 V2PC Statistics Aggregation


https://docs.influxdata.com/influxdb/v0.12

https://docs.influxdata.com/influxdb/v0.12

Chapter 12 Alarms, Events, and StatisticsViewing Current InfluxDB Data

The InfluxDB metastore contains internal information about the status of the system, including user information, database and shard metadata, and enabled retention policies. Because there is only one ELK node instance in a V2PC deployment, there is no high availability on the statistics data aggregated in InfluxDB. As a result, the loss of the ELK node or InfluxDB instance can result in loss of this data.

We therefore recommend performing a regular backup schedule for statistics data. The following sections provide instructions for logging in to the InfluxDB shell, performing a backup of the database, and if ever necessary, restoring the database from a previous backup.

Viewing Current InfluxDB DataTo log in to InfluxDB on ELK node and use the database shell to view stored statistics data:

Step 1 On the master node, execute the command consul members to identify the active ELK node.

Step 2 Log in to the ELK node via SSH. The default login credentials are:

• User ID: root

• Password: cisco

Step 3 On the command line, type influx to access the InfluxDB command shell prompt.

Step 4 Type auth admin default.

Step 5 Type show databases.

Step 6 Type use stats_system to access the stats_system database, where V2PC stores statistics data.

Step 7 Type show measurements to show a list of measurements (similar to tables in an SQL database).


Chapter 12 Alarms, Events, and StatisticsBacking Up InfluxDB Data

For example, COS node statistics are stored in the aic_cosnodestats measurement.

Backing Up InfluxDB DataIf a node is running, you can create a backup of the metastore for an instance by executing the command influxd backup /influxdb_backups/metadata. This command backs up the InfluxDB metadata to the directory /influxdb_backups/metadata.

To back up the InfluxDB database:

Step 1 Log in to the ELK node as described in Viewing Current InfluxDB Data, page 12-2.

Step 2 Run the command influxd backup –database stats_system /influxdb_backups/database to back up the influxDB database stats_system to the directory /influxdb_backups/database.

To perform a backup of a remote node, specify the host and port of the remote instance using the -host configuration switch, as show in the following example:

influxd backup -database stats_system -host 10.0.0.1:8088 /tmp/mysnapshot

Restoring InfluxDB Data

Note Restoring from a backup is only supported while the InfluxDB daemon is stopped. To restore from a backup, you must provide the path to the backup.

To restore the InfluxDB database from an earlier backup:

Step 1 Log in to the ELK node as described in Viewing Current InfluxDB Data, page 12-2.

Step 2 Run the command influxd restore /tmp/backup to restore the contents of /tmp/backup.

The following optional flags are available for this command:

• -metadir <path to meta directory> – This is the path to the meta directory to which the metastore backup should be recovered. For packaged installations, specify /var/lib/influxdb/meta.

• -datadir <path to data directory> – This is the path to the data directory to which the database backup should be recovered. For packaged installations, specify /var/lib/influxdb/data.

• -database <database> – This is the database to which the data should be restored. This option is required if no -metadir option is provided.

• -retention <retention policy> – This is the target retention policy to which the stored data should be restored.

• -shard <shard id> – This is the shard data that should be restored. If specified, -database and -retention must also be set.


Chapter 12 Alarms, Events, and StatisticsSample Queries

Step 3 Restore the backup in two steps, as follows:

a. Restore the metastore so that InfluxDB knows which databases exist:

$ influxd restore -metadir /var/lib/influxdb/meta /tmp/backup/<metastore>

Where <metastore> is the metastore to be restored. For example, to restore meta.00:

$ influxd restore -metadir /var/lib/influxdb/meta/tmp/backup/backup/meta.00

b. Recover the backed up stats_system database as follows:

$ influxd restore -database stats_system -datadir /var/lib/influxdb/data /tmp/backup

Sample QueriesUse the following queries from the database shell to show database, measurement, tags, and field information:

• Show tags for all measurements: show tag keys

• Show fields for all measurements: show field keys

• Show fields for all series: show series

• Show tags for measurement aic_cosnodestats: show tag keys from aic_cosnodestats

• Show fields for measurement aic_cosnodestats: show field keys from aic_cosnodestats

• Show series for measurement aic_cosnodestats: show series from aic_cosnodestats

• SHOW TAG VALUES WITH KEY = cosNodeID

• Show retention policies on stats_system

Use the following queries from the database shell to show COS node statistics:

• select * from aic_cosnodestats where time > now() - 1m

• select count(storageUsed) from aic_cosnodestats

Use the following HTP queries from the database shell against InfluxdB:

• https://172.20.235.82:8443/db/query?&u=admin&p=default&db=stats_system&pretty=true&q=show%20measurements

• https://172.20.235.82:8443/db/query?&u=admin&p=default&db=stats_system&pretty=true&q=select+*+from+aic_cosnodestats+where+cosNodeID=%27335574603%27

• http://172.22.120.80:8086/query?&u=admin&p=default&db=stats_system&pretty=true&q=select * from aic_cosnodestats where cosNodeID='335574603' and time > now() - 6d

Alarms at Master Nodes

OS Level• CPU warning if usage > 80%

• CPU critical if usage >= 100%


Chapter 12 Alarms, Events, and StatisticsAlarms at Master Nodes

• Disk warning if usage >= 85%

• Disk critical if usage >= 95%

• Disk warning if inode usage >= 85%

• Disk critical if inode usage >= 95%

• Memory warning if usage >= 80%

• Memory critical if usage >= 95%

• NTP warning if abs(offset) >= 10 ms

• NTP critical if abs(offset) >= 100 ms

Third-Party Application Health Check• Consul critical if all consul-agents are not available

• Consul warning if some consul-agents are not available

• Mongo critical if all mongodbs are not available

• Mongo critical if mongodb master is not available

• Mongo warning if some mongodb slaves are not available

• RabbitMQ critical if all rabbitmqs are not available

• RabbitMQ warning if some rabbitmqs are not available

• Redis critical if all redis-servers are not available

• Redis critical if redis-server master is not available

• Redis warning if some redis-server slaves are not available

• RSyslog critical if rsyslog is not running

• 3rd party application healthy check

• Salt-master critical if all salt-masters are not available

• Salt-master warning if some salt-masters are not available

• Sensu-api critical if all sensu-apis are not available

• Sensu-api warning if some sensu-apis are not available

• Sensu-server critical if all sensu-servers are not available

• Sensu-server warning if some sensu-servers are not available

• Zookeeper critical if all zookeepers are not available

• Zookeeper warning if all zookeepers are not available

V2PC Component Health Check• Docserver critical if all docservers are not available

• Docserver critical if docserver master is not available

• Docserver warning if some docserver slaves are not available

• ResourceManager critical if all RMs are not available


Chapter 12 Alarms, Events, and StatisticsAlarms at Worker Nodes

• ResourceManager critical if RM master is not available

• ResourceManager warning if some RM slaves are not available

• ServiceManager critical if all SMs are not available

• ServiceManager critical if SM master is not available

• ServiceManager warning if some SM slaves are not available

• Unified_errorlogd critical if unified_errorlogd is not running

• Unified_translogd critical if unified_translogd is not running

• AICM critical if all AICMs are not available

• AICM critical if AICM master is not available

• AICM warning if some AICM slaves are not available

• MFCM critical if all MFCMs are not available

• MFCM critical if MFCM master is not available

• MFCM warning if some MFCM slaves are not available

• PICM critical if all PICMs are not available

• PICM critical if PICM master is not available

• PICM warning if some PICM slaves are not available

• EAM critical if all EAMs are not available

• EAM critical if EAM master is not available

• EAM warning if some EAM slaves are not available

• v2p-ui critical if all UIs are not available

• v2p-ui critical if UI master is not available

• v2p-ui warning if some UI slaves are not available

• v2pc-dns critical if all v2pc-dns are not available

• v2pc-dns critical if v2pc-dns master is not available

• v2pc-dns warning if some v2pc-dns slaves are not available

• AIC/MFC/PIC instance critical if it is not running

Connection with Worker Nodes• keep-alive warning if no response within 25 seconds

• keep-alive critical if no response within 300 seconds

Alarms at Worker Nodes

OS Level• CPU warning if usage > 80%


Chapter 12 Alarms, Events, and StatisticsStatistics at Master and Worker Nodes

• CPU critical if usage >= 100%

• Disk warning if usage >= 85%

• Disk critical if usage >= 95%

• Disk warning if inode usage >= 85%

• Disk critical if inode usage >= 95%

• Memory warning if usage >= 80%

• Memory critical if usage >= 95%

• NTP warning if abs(offset) >= 10 second

• NTP critical if abs(offset) >= 100 second

Statistics at Master and Worker Nodes

OS Level• CPU usage percentage

• Disk used, available, usage percentage

• Memory used, available, usage percentage

• Network received Kbytes per second

• Network sent Kbytes per second


Chapter 12 Alarms, Events, and StatisticsStatistics at Master and Worker Nodes


cisco virtualized video processing controller user guide ......1 cisco virtualized video processing...

Documents