/
DMaaP R2 Beijing Release Plan

DMaaP R2 Beijing Release Plan

Jan 18, 2018


Overview

Project Name

Data movement as a platform

Project Name

Data movement as a platform

Target Release Name

Beijing  Release

Project Lifecycle State

Incubation (Refer to ONAP Charter, section 3.3 Project Lifecycle for further information)

Participating Company 

AT&T, Tech Mahindra

Scope

What is this release trying to address?

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 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 Router, 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.

Epics

key summary type created updated due assignee reporter priority status resolution
Refresh

Stories

key summary type created updated due assignee reporter priority status resolution
Refresh



Longer term roadmap

DMaaP is a premier platform for high performing and cost effective data movement services that transports and processes data from any source to any target with the format, quality, security, and concurrency required to serve the business and customer needs.

Release Deliverables



Deliverable Name

Deliverable Description

Deliverable Name

Deliverable Description

AAF integration with Data Router

DMaap Git repository

Data Router source code

DMaap Git repository

Data Router library

ONAP Nexus repository

Data Router API description

ONAP wiki

Data Router Release Notes

ONAP wiki

Data Router Documentation

DMaap Git repository

Bus Controller API

DMaaP Git repo

Bus Controller Container

ONAP Nexus repo

Bus Controller source code

DMaaP Git repo

Sub-Components

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

  • Data Router - for file transport

  • Bus Controller Provisioning API - for provisioning of topics (MR), feeds (DR) and permissions (AAF)

  • Bus Controller GUI - human interface to Bus Controller Provisioning API

Architecture

High level architecture diagram

Platform Maturity

Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.

Area

Actual Level

Targeted Level for current Release

How, Evidences

Comments

Area

Actual Level

Targeted Level for current Release

How, Evidences

Comments

Performance

0

1

Baseline performance criteria will be defined

  • 0 -- none

  • 1 – baseline performance criteria identified and measured

  • 2 & 3 – performance improvement plans created & implemented

Stability

1

1

72 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

Resiliency

2

2

K8S 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)

Security

0

1



  • 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

Scalability

1

1

Level 1 single site horizontal scaling

  • 0 – no ability to scale

  • 1 – single site horizontal scaling

  • 2 – geographic scaling

  • 3 – scaling across multiple ONAP instances

Manageability

1

1

Using 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

Usability

1

2

API documentation and swagger API provided

  • 1 – user guide; deployment documentation; API documentation

  • 2 – UI consistency; usability testing; tutorial documentation