Page tree
Skip to end of metadata
Go to start of metadata

Purpose

This Wiki page is intended to capture and define the Auto Use Cases. 

Use Case Diagrams

Hybrid Cloud for R1 ONAP Deployment and Hybrid VNF Use Cases

Link to the source of the diagram below: hybrid_pod.vsdx

F Release Detailed Use Case Definitions

This section defines each use case in greater details.

Edge Cloud

SectionDescription
IDAuto-UC-01
Title

Service Provider's Management of Edge Cloud

DescriptionAs an NFV edge service provider, I need an edge platform that is both efficient (in terms of control/automation overhead) and largely autonomous for VNFs once launched. Thus ability to deploy the minimal subset of ONAP functions needed for autonomy under typical VNF lifecycle events, e.g. start, stop, scale, recover from faults, collect/process telemetry, ...
Primary Actor (s)
  1. Service Provider
  2. Cloud control plane and automation platform
Preconditions
  1. hardware environment in which Edge cloud may be deployed
  2. a Edge cloud has been deployed and is ready for operation
  3. ONAP has been deployed onto a cloud and is interfaced (ie provisioned for API access) to the Edge cloud
Main Success Scenario (s)
  • lifecycle management - stop, stop, scale (dependent upon telemetry)
  • recovering from faults (detect, determine appropriate response, act); ie exercise closed-loop policy engine in ONAP
    • verify mechanics of control plane interaction
  • collection of telemetry for machine learning
Alternate Scenarios<are there alternate sunny day scenarios which should be defined?>
Exception Scenarios<are there any rainy day or error scenarios to be defined?>
Post Conditions<what is the state of the system after the use case finishes?>
JIRA Traceability<trace to JIRA Epic or Story>

 

Resiliency Improvements through ONAP

SectionDescription
IDAuto-UC-02
Title

Resilience Improvements through ONAP

Description

As an NFV edge service provider, I need to assess what degree of added VIM+NFVI platform resilience I obtain by leveraging ONAP closed-loop control, vs VIM+NFVI self-managed resilience, so I can determine the ROI for integrating ONAP with my VIM+NFVI platforms, both locally on the VIM+NFVI platform, or remotely.

Primary Actor (s)
  1. Service Provider
  2. Cloud control plane
  3. Automation platform
Preconditions
  1. hardware environment in which Edge cloud may be deployed
  2. a Edge cloud has been deployed and is ready for operation
  3. ONAP has been deployed onto a cloud and is interfaced (ie provisioned for API access) to the Edge cloud
  4. Components of ONAP have been deployed on the Edge cloud as necessary for specific test objectives
Main Success Scenario (s)
  • assess VIM+NFVI resilience under specific stresses without ONAP support
  • assess VIM+NFVI resilience under specific stresses with ONAP support, i.e. VES+DCAE+CLAMP+specific policies to address the type of stress
  • stress the system via

    • traffic: different types as needed per the resiliency measurements

    • instability

      • physical infra failure (host, NIC, disk, ...)

      • virtual infra failure (cloud control plane components, SDNC components, NFVI components)

      • security threats

  • measure resiliency in terms of

    • link failure, e.g. loss ping failures

    • transaction failure, e.g. failed web/API requests

    • service failure duration

    • scope of disruption

Alternate Scenarios<are there alternate sunny day scenarios which should be defined?>
Exception Scenarios<are there any rainy day or error scenarios to be defined?>
Post Conditions<what is the state of the system after the use case finishes?>
JIRA Traceability<trace to JIRA Epic or Story>

Enterprise vCPE

SectionDescription
IDAuto-UC-03
Title

vCPE as a cloud service for enterprise users

DescriptionAs an NFV edge service provider, I need to provide the Enterprise2DC service to the tenants both efficiently and safely by deploying enterprise-based vCPE. Enterprise users could receive high-quality and cheap cloud service based on the operator’s BSS Portal and ONAP. And in here, ONAP is used to instantiate and operate the required vCPE in the access network as a cloud service.
Primary Actor (s)
  1. Enterprise Service Provider
  2. Cloud control plane and automation platform
Preconditions
  1. hardware environment in which Edge cloud may be deployed
  2. a Edge cloud has been deployed and is ready for operation
  3. the enterprise edge devices, such as ThinCPE, could get access to the Edge cloud with WAN interfaces
  4. ONAP has been deployed onto a cloud and is interfaced (ie provisioned for API access) to the Edge cloud
Main Success Scenario (s)
  • site2DC
    • service designing
    • customer ordering and vnfs onboarding
    • authorization and address assigning
    • vpn establishing, with VxLAN/IPSec/MPLS
    • auto-healing(vnf scaling, control loop with DCAE+Network AI+PCE)
  • site2site
    • refer to site2DC
  • site2Internet
    • refer to site2DC
Alternate Scenarios<are there alternate sunny day scenarios which should be defined?>
Exception Scenarios<are there any rainy day or error scenarios to be defined?>
Post Conditions<what is the state of the system after the use case finishes?>
JIRA Traceability<trace to JIRA Epic or Story>
  • No labels