Versions Compared

Key

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

...

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-136

Project Impact

Note: Architecture discussions as well as prototyping is still ongoing, which could result in some changes to described project impact.

PROJECTPTLUser Story / EpicRequirement
A&AIEpic #1 PM control
  • Generic support for event generation is available by AAI.
  • Ensure PNF model in AAI contains proper attributes indicating its status.

    Assumptions

    • PNF and VNF models contain status attribute that can indicate when a new instance has been fully instantiated (may still require update to SO workflow)
    • AAI will send topology event on AAI-EVENT topic when status attributes are updated
    AAF

    Epic #2 Secure 5G Bulk PM

    Functionality will be developed in separate release requirement

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyREQ-140

    • CMPv2 Client implementation so that ONAP platform components can get operator certificates.
    • Ensure AAF provides interface allowing DCAE to deploy extra client certificate for external communication
    APPC


    CLAMPEpic #1 PM control
    • Ensure CLAMP can supportPNFs in Control Loops (TBD)Add PNF support (Jira ticket to be defined)

    Assumptions

    • Current analysis assumes that it is possible to reuse current CLAMP indicates that CLAMP has support for model-driven UI to parametrize the configuration policy for the new PMSH mS. This basic functionality could be enhanced in later step.
    CC-SDK

    DCAE

    Epic #1 PM control











    Epic #2 Secure 5G Bulk PM

    • Addition of new PMSH micro-service (open a DCAE JIRA TICKET)Any needed updates to PM Mapper mS to enable dynamic mapping of measurements that are part of active subscriptions (stretch goal, open a Jira ticket with low prioritysupporting
      • Configuration policy to provide PM subscription parameters
      • Sending closed loop event to trigger operational policy for xNF PM configuration
      • Interaction with AAI to discover xNF instances and fetch needed information
      • (Stretch goal) DMaaP or similar interface to request activation/de-activation of subscription
    • (Stretch goal) Optional capability to forward subscription data like measurement list to PM Mapper using appropriate mechanism (to be further discussed)

    -------

    Another enhancement

    • CMPv2 for operator certificate enrollment for secure 5G Bulk PM. 

    DMaaP



    External API

    MODELING

    Multi-VIM /

    Cloud



    OOFShankaranarayanan Puzhavakath Narayanan

    POLICY

    Epic #1 PM control

    • Policy to support
      • CDS Actor in operational policy. (dependency on
        Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keyREQ-33
        )
      • The intent is to use CDS with APEX policy (TBD)
    • Support APEX operation policy in combination with CDS actor (dependency)
    PORTAL

    SDN-C

    SDC

    SOEpic #1 PM control
    • Update Workflow shall update status attribute in AAI when the VNF/PNF instance has been fully instantiated
    VID

    VNFRQTS

    VNF-SDK

    CDS

    Integration

    Epic #1 PM control

    Jira Legacy
    serverSystem Jira
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyINT-1312

    • PM control e2e test case
    • New/updated xNF simulator with demo YANG model for PM control
    • Test artifacts:
      • CBA implementing new controller actions with transformation from xNF-agnostic subscription to xNF-specific YANG model
      • Operational policy to forward subscription configuration from PMSH to controller using the CDS Actor

    ...