Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »


This use case started in Casablanca Release. We have carryover items and enhancements. Please see 5G - OOF (ONAP Optimization Framework) and PCI (Physical Cell ID) Optimization for the base wiki page for this use case.

Showcase VNFTest Environment

Integration Team Liaison







Development Status

ProjectPTLJIRA Epic / User Story*Requirements
AAI
James Forsyth

  1. May need to add attributes for 5G DU and 5G CU PNF / VNF objects. (TBD).
DCAEVijay Venkatesh Kumar
  1. DCAE should onboard PCI Handler Microservice
  2. Collector should accept FM/PM messages from RAN Simulator and publish to DMaaP
  3. PCI-Handler microservice should process PCI Collision and PCI Confusion messages and trigger OOF Optimization as needed.
  4. Microservice should support ANR function
 OOF
 Sarat Puthenpura

  1. OOF PCI Algorithm should support different optimization objectives (e.g. minimize changes, minimize confusion)
  2. OOF should support joint PCI and ANR function
 Policy
 Pamela Dragosh


  1. Policy module should support handling of partial success where only some of the PCI change actions from a set of changes are successful (e.g. allow partial changes, revert to previous state)
  2. Policy CLC should co-ordinate between PCI SON Control Loop (CL) and other control loops (CL) acting on the same PNF or VNF
 SDC
 Michael Lando

  1. PCI Handler Microservice should be added to SDC Catalog to support DCAE onboarding
 SDNC
 Dan Timoney

(Carryover items from Dublin)

-SDNC-430: Modify RAN informational model and yang model for RAN
-SDNC-431: Implement config DB and REST API (SDN-R / OOF interface)
-SDNC-432: Interfacing SDN-R with Policy
•Receive DMaaP message in CL format from Policy (Modify Config message using existing LCM API), send netconf message changing PCI value to cellID as specified, update config DB, and publish change on DMaaP (DMaaP client is available and can be called)
-SDNC-432: Receive netconf notification from RAN, update configDB, and publish change on DMaaP

  1. SDNC-430: Modify RAN informational model and yang model for RAN
  2. -SDNC-431: Implement config DB and REST API (SDN-R / OOF interface).
    NOTE: ConfigDB work should align with larger Controller and configuration projects/use cases.
  3. -SDNC-432: Interfacing SDN-R with Policy - Receive DMaaP message in CL format from Policy (Modify Config message using existing LCM API), send netconf message changing PCI value to cellID as specified, update config DB, and publish change on DMaaP (DMaaP client is available and can be called)
  4. SDNC-432: Receive netconf notification from RAN, update configDB, and publish change on DMaaP
  5. SDNC should maintain an operational database and configuration database. May be a modification of SDNC-431.

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

Testing

Current Status

  1. Testing Blockers

  2. High visibility bugs
  3. Other issues for testing that should be seen at a summary level
  4. Where possible, always include JIRA links


End to End flow to be Tested

**This should be a summary level Sequence diagram done in Gliffy** 

Test Cases and Status


#Test CaseStatus
1There should be a test case for each item in the sequence diagram

NOT YET TESTED

2create additional requirements as needed for each discreet step

COMPLETE

3Test cases should cover entire Use Case

PARTIALLY COMPLETE

4 Test Cases should include enough detail for testing team to implement the test

 FAILED

  • No labels