From 6a507a46b528da6cc25a052e72e8e2d9b45c89bf Mon Sep 17 00:00:00 2001 From: "stark, steven" Date: Wed, 24 Apr 2019 12:04:41 -0700 Subject: [VVP] adding vvp report for demo VNFs Change-Id: I1a6e910e54d6a2b68b99a7c2e3a5b9dc60a0f1e6 Issue-ID: VVP-186 Signed-off-by: stark, steven --- docs/docs_scaleout.rst | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'docs/docs_scaleout.rst') diff --git a/docs/docs_scaleout.rst b/docs/docs_scaleout.rst index bdb590895..57ccf67fa 100644 --- a/docs/docs_scaleout.rst +++ b/docs/docs_scaleout.rst @@ -12,6 +12,11 @@ Source files - VF module scaling template file: https://git.onap.org/demo/plain/heat/vLBMS/dnsscaling.yaml - VF module scaling environment file: https://git.onap.org/demo/plain/heat/vLBMS/dnsscaling.env +VVP Report +~~~~~~~~~~ + +:download:`vLBMS report ` + Description ~~~~~~~~~~~ The Scale Out use case shows how users/network operators can add Virtual Network Function Components (VNFCs) as part of a VF Module that has been instantiated in the Service model to an existing VNF, in order to increase capacity of the network. ONAP Casablanca release supports scale out with manual trigger from VID and closed-loop enabled automation from Policy. This is demonstrated against the vLB/vDNS VNFs developed for ONAP. For Casablanca, both APPC and SDNC controllers are used to demonstrate accepting request from SO to execute the Scale Out operation. APPC is the main controller used for this use case and it can be used to scale different VNF types. SDNC is experimental for now and it can scale only the vDNS VNF developed for ONAP. -- cgit 1.2.3-korg