Introduction

This document describes the new features, open caveats, and resolved caveats in the Deployer Release Fuji component of the Cisco Cloud DVR (cDVR) Solution.

Installation Requirements

The following is a list of installation requirements for Release Fuji.

  • IOPS limit requirement is 120K, for a full cDVR control plane, Alert bundle, and Log Analytics stack.

  • After the orchestration of Deployer Fuji, and before traffic steering to the new instance, you must execute the following file: cDVR Deployer Fuji Post Orchestration.zip. For details, contact Cisco Services.

New Features

The following is a list of new features for Release Fuji.

UPM Proxy

  • UPM Proxy introduces a microservice called Planner that internalizes the values that are currently stored in the UPM. Reduces transactions times.

Go SRM

  • MF7716: RR Record Request retry

  • RR delay deleting recorded content to reduce 1808 errors

Deployer Product Compatibility

The table below lists the components that are included in the Deployer and the recommended versions. The components are included in the Deployer release package.

Product

Version

Control Plane Components

PPS (Scheduler)

20.0.0-14

UPM

Obsolete

UPM Proxy

18.2.7-0

Recorder Router

1.2.0-342

Alerting Bundle

18.4.2-01

Log Analytics Stack

1.0.0.63

fluentd Parsers

cdvr_bolton_cp_fluentd_parsers-3-26

Kibana Visualizations Package

cdvr_bolton_cp_visualizations-1-13

Sensu KPI Package

sensu_service_kpi-1-10

Sensu Node Level Checks Package

sensu_nodelevel_checks-1-6

Visualizations

vmp_visualizations-1-9

vmr-dashboard-installation-1.0.1x86

cos-telemetry-es--docs-3.14.2-cos0.10

Orchestration

AMIs (Amazon Machine Images)

IVP-CentOS-6.8.0-3d

CSCOlxplat-CentOS-7.3.20170601-7a (7)

IVP-CentOS-7.4.20180129-4 (7.4)

Caveats

This section includes open and resolved caveats for this release.

Open Caveats

The following is a list of open caveats in Release Fuji.

Orchestration

  • During control plane upgrade, control plane cleanup and Route 53 steering questions should be ignored ('n' should be used).

  • After a control plane upgrade, the exiting monitoring stack could lose node names if the node names are changed due to Active Directory integration requirements. This causes all health checks to report with the changed node names, instead of the defined nomenclature in cDVR deployments.

  • In Deployer Fuji, post orchestration procedure is required after upgrading the analytics stack and before steering to the new instance. For details, contact Cisco Services.

Resolved Caveats

The following is a list of resolved caveats in Release Fuji. This list is not intended to be comprehensive. It lists the resolved caveats that are relevant to the current Deployer release. The caveat ID can be searched in the Synamedia Customer Service Desk (https://vss.service-now.com), where you can find details about the caveat.

Analytics

  • MDO8504 - haproxy log rotation creating bad files

  • MDO8239 - missing GOSRMlogs for Status=Failed

Go SRM

  • DE31734 - Fix issue with Master Election during Delayed Delete causing the same node to be elected all the time.

Related Links and Documentation

The following lists useful links:

The following lists the release notes and guides for other related components: