DRAFT PROPOSAL FOR COMMENTS
The content of this template is expected to be fill out for M1 Release Planning Milestone.
Info
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
Use the Wiki to document the release plan. Don't provide PowerPoint.
Use as much diagrams and flow charts as you need, directly in the wiki, to convey your message.
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Amsterdam |
| Project Lifecycle State | Incubation |
| Participating Company | AT&T, Intel, Chinamobile, VMVare, JIO |
Scope
What is this release trying to address?
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: 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.
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.
Epics
Stories
Longer term roadmap
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 |
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
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}/ | |||
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, ...).
| 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.
Testing and Integration Plans
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.
Gaps
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
| Gaps identified | Impact |
|---|---|
| To fill out | To fill out |
Known Defects and Issues
Provide a link toward the list of all known project bugs.
Risks
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).
| 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
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
Team Internal Milestone
This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.
It is not expected to have a detailed project plan.
| Date | Project | Deliverable |
|---|---|---|
| To fill out | To fill out | To fill out |
Documentation, Training
- 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.
Other Information
Vendor Neutral
If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.
Free and Open Source Software
FOSS activities are critical to the delivery of the whole ONAP initiative. The information may not be fully available at Release Planning, however to avoid late refactoring, it is critical to accomplish this task as early as possible.
List all third party Free and Open Source Software used within the release and provide License type (BSD, MIT, Apache, GNU GPL,... ).
In the case non Apache License are found inform immediately the TSC and the Release Manager and document your reasoning on why you believe we can use a non Apache version 2 license.
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.