Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: filters fixed

...

Project NameEnter the name of the project
Target Release NameR1 Amsterdam
Project Lifecycle StateIncubation
Participating Company AT&T, Intel, Chinamobile, VMVare, JIO, VMVare

Scope

What is this release trying to address?


The Because of the large potential scope for this release DCAE, the work will be deploy prioritized as follows:

  1. Deliver DCAE Platform

...

  1. : 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.  
  2. Deliver DCAE Services:  We have identified the VES, Threshold Crossing app currently (based on vFW/vDNS)
  3. Support integration effort for other usecase.

Use Cases

Use Cases

Describe the use case this release is targeted for (better if reference to customer use case).

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.

...

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=DCAE and issuetype in (epic) and fixversion='Amsterdam Release'
serverId425b2b0a-557c-3c0c-b515-579789cceedb

...

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=DCAE and issuetype in (story) and status in (open) fixversion='Amsterdam Release'
serverId425b2b0a-557c-3c0c-b515-579789cceedb

...

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’s     – The VNF supporting the R1 usecase should comply with VES specification or be able to send SNMP Traps to DCAE

Policy 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 – CLAMP  – For create/update DCAE collector, analytic and micro service configuration Policies.

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

OOM OOM      – For instantiating the DCAE controller

CCSDK CCSDK  – For deploying database as a service for DCAE.

MSB -   Integration MSB       –  Integration with MSB (stretch)

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

...

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.

DCAE Platform consist of many sub-components.  Given below is the interaction/flow between various DCAE components and external application.


Image AddedAnyone reading this section should have a good understanding of all the interacting modules.

API Incoming Dependencies

...

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

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI 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
DMAAPAll interface within DCAE service components leverage DMAAP.

Data Movement as a Platform Message Router 
PolicyDCAE 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




SDCSCH 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.


API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI 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

 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




CLAMPInvokes inventory API for query
Inventroy APIInventory API for query
TBD
Link toward the detailed API description


Third Party Products Dependencies

...

NameDescriptionVersion

Cloudify

TOSCA-based cloud orchestration software platform

3.4.0 (4.0.x)

Consul

Distributed service discovery and KV store

   

0.8.3

UbuntuOS 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.

...

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill out

Resources

Fill out the Resources Committed to the Release centralized page.

Release Milestone

...

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.