Versions Compared

Old Version 19

changes.mady.by.user Mark Scott

Saved on

compared with

New Version 20

changes.mady.by.user Mark Scott

Saved on

Key

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

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

Lusheng Ji

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-566

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-567

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDCAEGEN2-564

  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

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyDMAAP-28

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

Steven Wright

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVNFRQTS-263

Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyVNFRQTS-264

  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

Gliffy Diagram
size500
nameSummary SeqDia Template
pagePin10
version8



























End to End flow to be Tested:  DCAE 3GPP PM Mapper

Gliffy Diagram
size500
nameSummary SeqDia Template
pagePin10

Test Cases and Status:  DCAE Data File Collector

#Test CaseStatus
1

xNF:  Ensure fileReady event is received from xNF at DCAE VES collector.

Expected output: fileReady event received

Status
titleNot yet tested

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

Status
titleNot yet tested

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

Status
titleNot yet tested

4 

DCAE File Collector:  Ensure event is processed and any invalid file entries (i.e. missing or corrupt data) are logged.

Expected output: fileReady event meets VES 6.x specification

Status
titleNot yet tested

5 DCAE File Collector:  After succesful event parsing, confirm secure connection to file location is initiated for file retrieval. E.g. connection to xNF file location contained in the event.

Status
titleNot yet tested

6DCAE File Collector: Confirm that if a successful connection can not be made to the location, an error log is raised. E.g. authentication failed, destination unreachable, etc.

Status
titleNot yet tested

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

Status
titleNot yet tested

8DCAE File Collector: Ensure any files which are not available are logged. E.g. file no longer on the xNF, logged as non-existant file.

Status
titleNot yet tested

9DCAE File Collector: Confirm that in the event a file fails to transfer successfully, retry is initiated.

Status
titleNot yet tested

10DCAE File Collector: Confirm that in the event the maximum number of retries is exceeded, an error is logged. E.g. file not able to be retrieved.

Status
titleNot yet tested

11DCAE File Collector: Ensure the connection to xNF is closed.

Status
titleNot yet tested

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

Status
titleNot yet tested








Test environment requirements for above test cases:

  • xNF (or emulator) with VES 6.x support for 'fileReady' event.
    • E.g. xNF able to produce data files and send VES fileReady events,
    • E.g. xNF emulator able to produce 'fileReady' notification events including updated events, or a series or predefined VES events at periodic intervals.
  • xNF (or separate) ftpes capable server.
  • sample data files for collection. E.g. 3gpp PM files
  • Test environment reqs:
    • DMaaP R3, at minimum need DR running and configured for Bulk PM support
    • DCAE R3, MR with support for VES 6.x spec
    • DCAE R3, Data File Collector installed and configured
    • xNF instantiated at ONAP, e.g. in A&AI



Test Cases and Status:  DCAE 3GPP PM Mapper

#Test CaseStatus
1DMaaP DR: Confirm that bulk data is available on expected DR feed.

Status
titleNot yet tested

2DCAE 3GPP PM Mapper: Confirm that DR client (mapper) is able to retrieve data.

Status
titleNot yet tested

3
DCAE 3GPP PM Mapper: Confirm that mapper can validate the data using schema (e.g. 3gpp xml format).

Status
titleNot yet tested

4 

DCAE 3GPP PM Mapper: Confirm any file validation errors are logged.

Status
titleNot yet tested
 

5 DCAE 3GPP PM Mapper: Confirm that mapper creates expected VES PM events for the mapped data.

Status
titleNot yet tested
 

6DCAE 3GPP PM Mapper: Confirm that any mapping errors are logged.

Status
titleNot yet tested

7DCAE 3GPP PM Mapper: Confirm that mapped events are forwarded on DCAE Message Router.

Status
titleNot yet tested
 



End-to-End feature integration:

  • Test cases (tbd) to test end-to-end feature interaction for PnP, Bulk PM (File collector + Mapper), closed loop (e.g. TCA triggered on specific PM counter in the bulk data) and action performed.