Overview

The vFirewall is the easiest amongst all the use cases and is used heavily for automated regression by the Integration team and by ONAP users who test and try out the platform. Currently, the use case does not fully support integration of newer ONAP features and components. The goal is to bring it up to standard with other use cases within the scope of closeloop domain.

Problem Statement

This is a parent page to track all the items where we would use the vFW usecase to demonstrate new features and interactions in the closeloop domain.

Current controlloop workflow for vFW usecase

Demonstrating CDS actor support in Policy using vFW

Upgrading vFWCL Integration Test Case to Include DCAE-DS and CLAMP in El Alto/Frankfurt

Stretch and future items

Business Requirement

Use the vFW usecase to demonstrate new ONAP features and component interoperability within the scope of controlloop.

Participating Companies

AT&T, Bell, Samsung

Artifacts

vFW Clamp and CDS integration use case.pptx

CBA: vFW_CDS_CBA.zip

Data dictionary: dd UPDATES IN cds ui with processor-db.json

Payload to CDS from Policy (rest), gRPC will entail same parameters.

{
  "commonHeader": {
    "originatorId": "Policy",
    "requestId": "1234",
    "subRequestId": "1234-12234"
  },
  "actionIdentifiers": {
    "blueprintName": "test",
    "blueprintVersion": "1.0.0",
    "actionName": "config-deploy",
    "mode": "sync"
  },
  "payload": {
    "config-deploy-request": {
      "service-instance-id": "serviceInstanceId",
      "vnf-id": "genericVnfId",
      "config-deploy-properties": {
        "active-streams": "$activeStreams"
      }
    }
  }
}

Goals

1. Demonstrating CDS actor support in Policy using vFW: To bring in integration of CDS into policy as another actor and demonstrate this integration using the vFirewall end-to-end closeloop usecase (design-time + runtime: instantiation and closeloop)
2. ....