CVP Virtual Appliance

The CVP virtual appliance is a packaged ova file that consists of Base OS packages, Hadoop, HBase, Apache Tomcat, JAVA jdk and the CVP web application.

You can deploy the virtual appliance as either a single-node (standalone) cluster or a multi-node cluster (cluster of three nodes). A multi-node cluster provides more benefits over a single-node cluster as specified in the table below.

Table 1. Single-Node and Multi-Node Cluster Comparison
Single-Node Cluster Multi-Node Cluster

Low Scale

  • Supports 250 devices and 10k interfaces
  • Increasing resources may not mandatorily help due to bottlenecks of components

High Scale

  • Scalability is 6x times higher than single-node clusters
  • Supports multiple containers in components
  • Loads the share across nodes
  • Optimization, speed, and availability are higher than single-node clusters

No Redundancy - Does not support telemetry provisioning and streaming when the node goes down


  • Supports 2N+1 redundancy
    Note: If a node goes down, kubernetes schedules the lost node pods on the other two nodes.
  • Provides uninterrupted telemetry provisioning and streaming
  • Provides Return Merchandise Authorization (RMA) when a node fails
  • Each state has three replicas

Corruption Management

  • No recovery is available for lost data
  • Need manual intervention to fix hbase issues
  • Must remotely copy backups to a server everyday for restoring the node when the disk gets corrupted

Corruption Management

  • Automatically fixes issues 99% of the time
  • The feature to share load across nodes provides a faster and smoother experience

The different deployment options will be discussed later on in this section, but for production deployments it is recommended that the cluster option is chosen. The single VM instance is recommended for testing purposes as it provides a simpler setup and requires less resources.