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

Compare with Current View Page History

« Previous Version 10 Next »

The bulk PM feature consists of two main parts:

  • Event-driven bulk transfer of monitoring data from an xNF to ONAP/DCAE. A micro-service will listen for 'FileReady' VES events sent from an xNF via the VES collector. Once files become available the collector micro-service will fetch them using protocol such as FTPES (committed) or HTTPS. The collected data files are published internally on a DMaaP Data Router (DR) feed.
  • For 3GPP formatted measurement data and for consumers that prefer such data in VES format, an optional 3GPP PM Mapper micro-service is planned that can extract selected measurements from a 3GPP XML file and publish them as VES events on a DMaaP Message Router topic. The mapper receives the files by subscribing to a Data Router feed.

Presentations:

Development Status

ProjectPTLJIRADescription
DCAE

DCAEGEN2-566 - Getting issue details... STATUS

DCAEGEN2-567 - Getting issue details... STATUS

DCAEGEN2-564 - Getting issue details... STATUS

  1. Develop new file collector micro-service
  2. Develop new 3GPP PM mapper micro-service (stretch goal)
  3. Upgrade VES collector to support VES version 6.0 and new notification domain (dependency)
DMaaPRamprasad Koya

DMAAP-28 - Getting issue details... STATUS

  1. Integrate Data Router service (under investigation, not committed)
VNFRQTS

VNFRQTS-263 - Getting issue details... STATUS

VNFRQTS-264 - Getting issue details... STATUS

  1. Add general xNF requirements for bulk file transfer mechanism
  2. Add xNF requirements for transfer of bulk PM data in 3GPP format

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:  DCAE Data File Collector



End to End flow to be Tested:  DCAE 3GPP PM Mapper Summary SeqDia Template


Summary SeqDia Template

Test Cases and Status:  DCAE Data File Collector

#Test CaseStatus
1xNF:  Ensure fileReady event is received from xNF at DCAE VES collector.

NOT YET TESTED

2DCAE VES Collector:  Ensure fileReady event is processed and forwarded to correct topic on DCAE Message Router.

NOT YET TESTED

3
DCAE File Collector:  Ensure fileReady event is received from DCAE Message Router.

NOT YET TESTED

DCAE File Collector:  Ensure event is processed and connection to file location is initiated for file retrieval.

NOT YET TESTED

DCAE File Collector:  Ensure that for each new entry in the fileReady event the file is retrieved.

NOT YET TESTED

6DCAE File Collector:  Ensure the connection is closed.

NOT YET TESTED

7DCAE File Collector:  Ensure the data file(s) retrieved for that processed fileReady event are published to correct feed on DMaaP Data Router.

NOT YET TESTED 


Q:  Should we need separate test cases for validation and error handling scenario?  Or just include in above as exceptions per test case?


Test Cases and Status:  DCAE 3GPP PM Mapper

#Test CaseStatus
1

NOT YET TESTED

2

NOT YET TESTED

3

NOT YET TESTED


NOT YET TESTED 


NOT YET TESTED 

6

NOT YET TESTED

7

NOT YET TESTED 

  • No labels