DRAFT PROPOSAL FOR COMMENTS

Project Name	Enter the name of the project
Target Release Name	R1Amsterdam
Project Lifecycle State	Incubation
Participating Company	AT&T, Intel, Chinamobile, VMVare, JIO, VMVare

Scope

What is this release trying to address?

Describe the problem being solved by this release

Use Cases

Describe the use case this release is targeted for (better if reference to customer use case)Because of the large potential scope for DCAE, the work will be prioritized as follows:

Deliver DCAE Platform: Most of platform components are new and under active development and will need seedcode stabilization; this will our top priority as everything in DCAE depends on.
Deliver DCAE Services: We have identified the VES, Threshold Crossing app currently (based on vFW/vDNS)
Support integration effort for other usecase.

Use Cases

Use Case: vFW/vDNS (Approved)

Use Case: Residential Broadband vCPE (Approved) **

Use Case: VoLTE(approved) **

** The usecase support may be phased for R1 and dependent on completion of other commitment.

Minimum Viable Product

Describe the MVP for this release.

All core DCAE Platform components

- Cloudify Manager

- Consul

- DeploymentHander

- Policy-Handler

- ServiceChangeHandler

- Inventory-API

- Postgres

- Registrator

- ConfigBinding Service

- CDAP Broker

DCAE Service specific components

- VESCollector

- TCA (Analytics application)

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.

...

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	project=sanbox DCAE and issuetype in (epic) and fixversion='Amsterdam Release'
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	project=sanbox DCAE and issuetype in (story) and fixversion='Amsterdam Release'
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Indicate at a high level the longer term roadmap. This is to put things into the big perspective.

Once the platform components are stabilized, newer mS and application can be onboarded into DCAE platform to support additional usescases. DCAE controller integration with MultiVM project would allow support into multi-cloud environment.

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

Deliverable Name	Deliverable Description	To fill out	To fill out
blueprints	Executable/SourceCode
plugins	SourceCode
cdapbroker	SourceCode
cli	SourceCode/Tool/Documentation
deployment-handler	SourceCode
servicechange-handler	SourceCode
inventory-api	SourceCode/Docker image
policy-handler	SourceCode
configbinding	SourceCode
registrator	SourceCode
Pgaas (under ccsdk)	SourceCode
ves	SourceCode/Docker image
snmptrap	SourceCode/Docker image
tca	SourceCode

Sub-Components

List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.

Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.

DCAE Platform encompasses following sub-components.

Cloudify-manager (blueprints/plugins)
Consuls
cdapbroker
deployment-handler
servicechange-handler
inventory-api
policy-handler
configbinding
registrator
ves
Postgres

ONAP Dependencies

List the other ONAP projects your depends on.

VNF’s – The VNF supporting the R1 usecase should comply with VES specification or be able to send SNMP Traps to DCAE

Policy – For sending dynamic configuration and rules for analytics into DCAE. Policy-hander also uses policy-engine client-lib provided in PolicyEngine-0.9.win32.tar file.

CLAMP – For create/update DCAE collector, analytic and micro service configuration Policies.

DMAAP – We are dependent on Dmaap for pub/sub of events/Control Loop messages (to Policy and APP-C)

OOM – For instantiating the DCAE controller

CCSDK – For deploying database as a service for DCAE.

MSB – Integration with MSB (stretch)

Multi-VIM – Integration with Mutli-VIM project to leverage infrastructure api (stretch)

Architecture

High level architecture diagram

At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.

Block and sequence diagrams showing relation within the project as well as relation with external components are expected.

Anyone reading this section should have a good understanding of all the interacting modules.DCAE Platform consist of many sub-components. Given below is the interaction/flow between various DCAE components and external application.

Image Added

API Incoming Dependencies

List the API this release is expecting from other releases.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

API Name	API Description	API Definition Date	API Delivery date	API Definition link (i.e.swagger

)To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill outLink toward the detailed API description

)
DMAAP	All interface within DCAE service components leverage DMAAP.		Data Movement as a Platform Message Router
Policy	DCAE Policy-handler invokes only calls POST /getConfig (policyName value varies by scope, by policy_id) https://<PDPServer Location>:<port>/pdp/api/getConfig	Dependent on that respective team/project to provide this.
MultiVIM	OpenStack API for infrastructure API. This is invoked form Cloudify-plugin
SDC	SCH uses SDC external API to grab the entire service model and grab artifacts /asdc/v1/catalog/services/<service uuid>/metadata

API Outgoing Dependencies

API this release is delivering to other releases.

Link toward the detailed API description

API Name	API Description	API Definition Date	API Delivery date	API Definition link (i.e.swagger)

To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill out

CLAMP (& internal DCAE components)

Deployment handler provides the following API to allow client systems to request installations of components via blueprint, request uninstallation of previously-deployed components, and get status on installation and uninstallation operations. Because installation and uninstallation operations can be long-running, the API is asynchronous. Client systems can poll for results.

{Serverroot}/

à [GET] (provides server info)

{Serverroot}/dcae-deployments/{deployment_id}

à [PUT, DELETE]

{Serverroot}/dcae-deployments/{deployment_id}/operation/{op_id}

à [GET]

TBD

VNF

VESCollector provides following URI structure for events to be published

http(s)://{Domain}:{Port}/{optionalRoutingtPath}/eventListener/v{apiversion}/
          [POST] Singe event
http(s)://{Domain}:{Port}/{optionalRoutingtPath}/eventListener/v{apiversion}/eventBatch
          [POST] Batch event

CLAMP

Invokes inventory API for query
Inventroy APIInventory API for query

TBD

Third Party Products Dependencies

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).

To fill out

Name	Description	Version	To fill out	To fill out
Cloudify	TOSCA-based cloud orchestration software platform	3.4.0 (4.0.x)
Consul	Distributed service discovery and KV store	0.8.3
Ubuntu	OS	16.04

In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.

...

Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.

Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.

...

Jira Legacy

server	System Jira
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	project=sanbox DCAE and issuetype in (bug, task) and status not in (closed)
serverId	4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Risk identified	Mitigation Plan	Contingency Plan
To fill out	To fill out	To fill out

Resources

Fill out the Resources Committed to the Release centralized page.

Release Milestone

...

Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
Highlight the team contributions to the overall Release Documentation and training asset
High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
Documentation includes items such as:
- Installation instructions
- Configuration instructions
- Developer guide
- End User guide
- Admin guide
  ...
  
  New onboarding documentation would be provided for users to be able to onboard new mS into DCAE platform

Note

title	Note

The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.

...

Each project must edit its project table available at Project FOSS.

Charter Compliance

The project team comply with the ONAP Charter.

Release Key Facts

Fill out and provide a link toward the centralized Release Artifacts.

Versions Compared

Old Version 1

New Version Current

Key

Scope

What is this release trying to address?

Use Cases

Use Cases

Minimum Viable Product

Functionalities

Release Deliverables

Sub-Components

ONAP Dependencies

Architecture

High level architecture diagram

API Incoming Dependencies

API Outgoing Dependencies

Third Party Products Dependencies

Resources

Release Milestone

Charter Compliance

Release Key Facts

Page Comparison

Versions Compared

Old Version 1

New Version Current

Key

Scope

What is this release trying to address?

Use Cases

Use Cases

Minimum Viable Product

Functionalities

Release Deliverables

Sub-Components

ONAP Dependencies

Architecture

High level architecture diagram

API Incoming Dependencies

API Outgoing Dependencies

Third Party Products Dependencies

Resources

Release Milestone

Charter Compliance

Release Key Facts