R6 USE CASE OBJECTIVES
- Traffic Distribution workflow enhancements https://jira.onap.org/browse/APPC-1728
- Build Traffic Distribution Use Case Extensions to merge Traffic Distribution with In Place Software Upgrade (Workflow as Python Script and APPC as LCM/Ansible executor)
- APPC extensions for seamless Ansible LCM execution on vf-module, vnfc and v-server level - APPC-1728Getting issue details... STATUS
- Scripts for Automation of APPC Workflows - APPC-1728Getting issue details... STATUS
- vFW K8S support in CDS (
-
INT-1184Getting issue details...
STATUS
)
- Modifications in vFW K8S helm charts to make them compatible with CDS blueprints
- Modifications in vFW CDS blueprint to make it worksing with vFW K8S Helm charts
- Modifications in SO for creations of K8S instance profile base on information from CDS
- Change management schedule optimization algorithm enhancements
- Support wide variety of constraints
- Policy-enabled
- Enable modular and dynamic composition of policies/constraints
- 5G PNF Software upgrade - the PNF support U/C Wiki: PNF SOFTWARE UPGRADE in R6 Frankfurt
- Workflow Designer Enhancements (SDC)
- Remove workflow from Model/CSAR, make it an independent artifact & distribute workflow as an independent artifact (include allowing user to associate workflow to resource model via a reference).
- Enhance Workflow Designer to support Service Level workflows.
BUSINESS DRIVER
Executive Summary - Enable automated, flexible and safe design, scheduling and execution of change activities across the network for physical and virtual network functions.
Business Impact - This will enable significant improvement of operational efficiencies and minimizing the risk of service impact during change deployments across the network.
Business Markets - Applicable to physical and virtual network functions deployed in large operational networks - cellular service (4G/5G), cloud service and data center networks.
Funding/Financial Impacts - Potential of significantly reducing the OPEX.
Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
Development Status
Project | PTL | User Story / Epic | Requirement |
AAI |
| ||
APPC | Takamune Cho |
| |
CLAMP |
| ||
OOF | |||
Policy |
| ||
SDC |
| ||
SDNC | |||
SO | |||
VID | |||
VNFRQTS |
*Each Requirement should be tracked by its own User Story in JIRA
Test Cases and Status
1 | There should be a test case for each item in the sequence diagram | NOT YET TESTED |
2 | create additional requirements as needed for each discreet step | COMPLETE |
3 | Test cases should cover entire Use Case | PARTIALLY COMPLETE |
4 | Test Cases should include enough detail for testing team to implement the test | FAILED |