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.
V2PC also supports multi-OS enablement (including CentOS and CoreOS) and VM orchestration over mixed infrastructure (including VMWare, Kubernetes, and Bare Metal).
Figure 1-1 Cisco Virtualized Video Processing (V2P) Platform
V2PC Release 3.3.3 fixes a number of known defects found in Release 3.3.2. For a list of these defects, see Known Defects.
In addition, V2PC Release 3.3.3 adds support for the following:
GUI support for DASH CEA-608 and CEA-708 pass-through
Concurrent (parallel) upgrade of application (MCE and MPE) workers, optimized to reduce upgrade times. For details, see the Cisco Virtualized Video Processing Controller Deployment Guide.
Rotation of log files to help prevent the root disk partitions on Master nodes from filling up.
Improved handling of alarm and event bursts to avoid consuming excess system resources.
As part of the V2PC 3.3 release train, V2PC Release 3.3.3 also provides the following new features and enhancements over previous releases:
Dynamic MFC Configuration – V2PC Release 3.3.3 supports dynamic configuration of the media flow controller (MFC) that integrates applications such as Cisco Virtualized Media Packager (VMP) and Cisco Virtual Media Recorder (VMR) into the V2PC management framework.
Dynamic configuration allows operators to create and update MFCs without service interruption. For example, a channel lineup can be created, updated, or removed from a linear workflow MFC without having to interrupt service or restart the MFC.
This feature brings additional enhancements, including:
– Improved AIC-MFC communication for better error handling and error logging.
– Manual SLA support to enable dynamic resource allocation of the Cisco Capture Engine (CE) and Playback Engine (PE) components of VMP.
– Expansion and contraction of application clusters in the field through worker node enablement, disablement, and deletion.
Swagger UI API Service – V2PC Release 3.3.3 supports user access to its underlying API through the OpenAPI Specification, also known as Swagger. The open source Swagger UI web interface provides a common gateway both for new Swagger API calls and for legacy Service Manager (SM) APIs. Support for role based access control (RBAC) enhances API access security and robustness.
Thick Provisioning and Separate Log Volume – By default, V2PC Simplified Deployment supports thick provisioning of storage volumes, as well as the creation of a separate log volume to allow for more efficient use of disks and partitions.
Enhanced User Interface – The V2PC graphical user interface (GUI) benefits from enhancements to the Media Workflow Manager and Application Deployment Manager screens, as well as from integration of the Dynamic Configuration interface and the Swagger UI API gateway.
Unbundled Deployment – The V2PC installation ISO now ships unbundled from Cisco VMP so that either application can be deployed independently.
Logging Enhancements – V2PC Release 3.3.3 creates log entries as key-value pairs to make logs more searchable through Elasticsearch, and more useful for analysis and troubleshooting. This release also supports remote ELK log servers with the Fluentd open source data collector.
Increased Document Size and Robustness – V2PC Release 3.3.3 replaces Consul with socket.io for media flow communication. This removes the previous 512 kb document file size limit, enabling workflows to support a larger number of channels. Master node file robustness is also improved through master application (AICM) HA handling.
V2PC Deployment Guidelines and Image Location
The V2PC Master Controller repository node 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)
V2PC Unmanaged (Self Install) Kubernetes is recommended for new deployments beginning with V2PC Release 3.2.2.
To access and download the latest V2PC 3.3.3 images, navigate to V2PC Software Download page at:
Note For additional information about deploying and configuring V2PC, see the Cisco Virtualized Video Processing Controller Deployment Guide and Cisco Virtualized Video Processing Controller User Guide, respectively.
VMware, vCenter, vSphere
V2PC support for VMs requires the following virtualization software programs and releases:
VMware ESXi hypervisor version 6.0, Update 3, build 5050593 or later
VMware vCenter version 6.0 or later
VMware vSphere version 6.0 or later
V2P Product Family
The following V2P Product Family is validated as part of V2PC 3.3.3 solution testing with V2PC, VMP, VMR, and COS.
Table 1 V2P Product Compatibility
Virtualized Video Processing Controller (V2PC)
Virtual Media Packager (includes MCE and MPE)
Virtual Media Recorder (AIC, MFC, Docker Images)
Cloud Object Storage (COS)
* For COS, integration testing with V2PC is based on each product team’s test coverage.
This section provides a list of open defects for this release. This list is not intended to be comprehensive. If you have questions about a particular defect, contact your account representative.
Note Defects are identified by a case tracking number (Defect ID) and a headline that briefly identifies the case. The headlines in this section are presented exactly as they appear in the issue tracking system.
Table 2 lists the open defects in V2PC Release 3.3.3.
Table 2 Open Defects in V2PC Release 3.3.3
V2PC Platform: unable to log on V2PC GUI
Worker upgrade (td-agent) optimizations
V2PC Platform: v2p-ui request can not be received by SM
GUI backend support for Ads insertion
This section provides a list of resolved defects for this release. This list is not intended to be comprehensive. If you have questions about a particular defect, contact your account representative.
Table 3 lists the resolved defects in V2PC Release 3.3.3.
Table 3 Resolved Defects in V2PC Release 3.3.3
generic defects for use with git commit, on generic support like mainline sync etc
v2pc worker core dump enhancement
Package latest FluentD parser for MCE and MPE
some log file is not rotated
3.3.2-16057: CDVR MFC failed to disabled while one of the MPE still shows active after delete it
DRM support new type 'cpixf'
VLE playback times out after some time only when using IPVS
make_system_nodes.py crashes if no local ELK deployed / available (during platform upgrade)
[V2PC Bare Metal] v2pc installed on bare metal, disk space not fully utilized
Channels distribution in MCEs are not proper
Platform/Worker upgrade scripts need to allow for Prompt-On-Error option
Simplified AppWorker upgrade process needs to support concurrent worker upgrade.
[V2PC Bare Metal] v2pc should support bond management interface installation [Critical]
GUI backend support the segment renaming-revert from hotfix/3.3.3
vod-mfc doesn't work in all the vmp 2.11 bundle
3.3.3-16348: ipvs worker upgrade failed while upgrading VMP
2.11.0-3.3.3-16347: worker version need to change from 2.10 to 2.11 on aic worker status
unable to save VMR aic ; due to new field zone while creating new VMR aic.
[customer] channel lost on GUI
V2PC Platform: Multiple alarms are generated with same hash value
Addition of warn log level and time stamp fix in parser
change cisco-pe logrotate configuration and interval
[v2pc-GUI]: cannot save key profile for vgc dash configuration
3.3.3-16400: V2PC EAM request failed while entering the Delete alarm GUI page
Persist common fields (Input PID,Codec, Bitrate) for both Update & Disable in Publishing template
V2PC - Enhancement Keyprofile VGC with CENC-DASH DRM Type disable LA URL and WV Provider/ Added other DRM Types for CPIXF
Upgrade should skip elk if it is not reachable or ext elk is used
Salt / zookeeper logs are not getting rotated alarms are raised
MFC communicate with other AIC timeout after 8 minutes
some worker nodes didn't have /var/cores when do test upgrade core dump
Cisco VMP - Live: Publish Template issues on the V2PC
"ps -ef" hang causing aicm/mfcm leader switch frequently
V2PC - Publish Template variant named 'default' cannot be deleted unless renamed
add log for [customer] Duplicated channels on VMR MCEs
Use timeout to check v2pc service health instead of exit directly
Reduced minimum free disk space to 1 GB (masters only).
Upgrading from V2PC Release 3.2.x to 3.3.x
For full instructions on upgrading from V2PC Release 3.2.x to V2PC Release 3.3.x, see the V2PC Upgrade section of the Cisco Virtualized Video Processing Controller Deployment Guide.
Upgrade Enhancement for V2PC Release 3.3.3
V2PC Release 3.3.2 supports the option of specifying the worker nodes to be upgraded by their IP addresses. To add such a list, include the following line in the platform_upgrade.json file:
where <worker_ip1> and so on are the IP addresses of the specific worker nodes to be upgraded.
If this line is omitted, the upgrade process defaults to the behavior of earlier releases and updates all worker nodes.
Refer to the following documents for additional information about V2PC:
Cisco Virtualized Video Processing Controller User Guide
Cisco Virtualized Video Processing Controller Deployment Guide
Cisco Virtualized Video Processing Controller API Guide
Cisco Virtualized Video Processing Controller API Service Guide
Cisco Virtualized Video Processing Controller Open Source
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)
This product contains watermarking technology that is licensed from Verimatrix, Inc., and such functionality should not be used or distributed further by you without any additional license(s) required from Verimatrix, Inc.
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.