Versions Compared

Old Version 14

changes.mady.by.user Dominic Lunanuova

Saved on

compared with

New Version Current

changes.mady.by.user Dominic Lunanuova

Saved on

Key

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

...

AAF integration with Message Router, Data Router, and Bus Controller will be added to the DMaap and some enhancements to the DMaap client.

Use Cases

The existing Amsterdam use cases are still going to be supported and additional use cases related to the DR and Bus Controller  will be supported for the Beijing Release.

Minimum Viable Product

For Beijing release, the minimum viable product we are targeting is  integrating AAF  with the Message routerRouter, sending and receiving messages using Data router, and provisioning topics and feeds via Bus Controller.

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

...

Deliverable NameDeliverable Description

AAF integration with Data Router

DMaap Git repository
Data Router source codeDMaap Git repository
Data Router libraryONAP Nexus repository
Data Router API descriptionONAP wiki
Data Router Release NotesONAP wiki
Data Routee Router DocumentationDMaap Git repository
Bus Controller APIDMaaP Git repo
Bus Controller ContainerONAP Nexus repo
Bus Controller source codeDMaaP Git repo

Sub-Components

As part of the Beijing release, the following components will be added to DMaaP:

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance01Baseline performance criteria will be defined
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability1172 hours soak test with random transactions
  • 0 – none
  • 1 – 72 hours component level soak w/random transactions
  • 2 – 72 hours platform level soak w/random transactions
  • 3 – 6 months track record of reduced defect rate
Resiliency22K8S auto detection and recovery
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security01
  • 0 – none
  • 1 – CII Passing badge + 50% Test Coverage
  • 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
  • 3 – CII Gold
Scalability11Level 1 single site horizontal scaling
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11Using EELF common framework for logging
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability12API documentation and swagger API provided
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

...

No known risks so far.

  • Resources

Updated  the Resources Committed to the Release .

  • Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

...