DRAFT PROPOSAL FOR COMMENTS
...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | R1 Amsterdam |
| Project Lifecycle State | Incubation |
| 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:
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
- 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: Residential Broadband vCPE (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 Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=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=DCAE and issuetype in (story) and status in (open) fixversion='Amsterdam Release' serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
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.
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.
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) |
|---|---|---|---|---|
| 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.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|
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}/ | |||
| CLAMP | Invokes inventory API for query Inventroy APIInventory API for query | TBD |
Third Party Products Dependencies
...
| Name | Description | Version |
|---|---|---|
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.
...
| 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 | ||
|---|---|---|
| ||
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.