Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Traffic Distribution workflow enhancements https://jira.onap.org/browse/APPC-1728
    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyREQ-187
     
    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyREQ-191

    1. 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) 
      Jira
      serverONAP JIRA
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyINT-1276
       
      Jira
      serverONAP JIRA
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyREQ-187
    2. APPC extensions for seamless Ansible LCM execution on vf-module, vnfc and v-server level 
      Jira
      serverONAP JIRA
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyAPPC-1728
       
      Jira
      serverONAP JIRA
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyREQ-191
    3. Scripts for Automation of APPC Ansible Workflows [Stretch]
      Jira
      serverONAP JIRA
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyAPPC-1728
      Jira
      serverONAP JIRA
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyREQ-191
  2. vFW K8S support in CDS (
    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyINT-1184
     and
    Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyREQ-182
    )
    1. Modifications in vFW K8S helm charts to make them compatible with CDS blueprints
    2. Modifications in vFW CDS blueprint to make it worksing with vFW K8S Helm charts
    3. Modifications in SO Multicloud for creations of K8S instance profile base on information from CDS
    4. Modifications in CDS required for creation of K8s profile by CDS itself
    5. More details: Integration with CDS
  3. Change management schedule optimization algorithm enhancements
    1. Support wide variety of constraints
    2. Policy-enabled
    3. Enable modular and dynamic composition of policies/constraints
  4. 5G PNF Software upgrade - the PNF support U/C Wiki: PNF SOFTWARE UPGRADE in R6 Frankfurt
  5.  Workflow Designer Enhancements (SDC)
    1. 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).
    2. Enhance Workflow Designer to support Service Level workflows.

...

ProjectPTLUser Story / EpicRequirement
AAI

APPCTakamune Cho

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyAPPC-1728

  1. Delivery of "vFW Software Upgrade and Traffic Distribution" Use Case transfromed from "vFW Traffic Distribution Use Case"
  2. APPC extensions for seamless Ansible LCM execution on vf-module, vnfc and v-server level
  3. Automation of APPC configuration for Ansible [Stretch]
CLAMP

 OOF

 Policy



 SDCWish List - No US/Epic
  1. Make Workflow Independent Artifact
  2. Enhance WFD to support Service Level Workflows
 SDNC
  1. Delivery of "vFW K8s Use Case" Integrated with CDS  - modification in CDS required for K8s workflow support
 SOWish List - No US/Epic
  1. Workflow as Independent Artifact
  2. Support Service Level Workflows
 VIDWish List - No US/Epic
  1. Support Service Level Workflows
 VNFRQTS

INT
  1. Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyINT-1184
  2. Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyINT-1276
  1. Delivery of "vFW K8s Use Case" Integrated with CDS: Helm charts and CDS blueprint
  2. Delivery of "vFW Software Upgrade and Traffic Distribution" Use Case transfromed from "vFW Traffic Distribution Use Case"
MULTICLOUDBenjamin Cheung
  1. Jira
    serverONAP JIRA
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyINT-1184
  1. Creation of K8S profile base on the input from CDS. The profile will be created by Multicloud component just before the instantiation of vFW "VNF"

*Each Requirement should be tracked by its own User Story in JIRA 

...