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. |
| Table of Contents | ||
|---|---|---|
|
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name |
| Casablanca | |
| Project Lifecycle State | Incubation |
| Participating Company | AT&T, Huawei, Cloudify, |
| Nokia, Tech Mahindra, |
| Ericsson |
Scope
What is this release trying to address?
The DCAE Beijing Casablanca release has two primary objectives: 1. improving platform maturity; 2. supporting use cases.
...
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 |
|---|---|---|---|---|
| Performance | 1 | 1 |
| |
| Stability | 1 | 2 |
| |
| Resiliency | 1 | 1+ |
| |
| Security | 0 | 1 |
| |
| Scalability | 0 | 1 |
| |
| Manageability | 0 | 1 |
| |
| Usability | 1 | 1 |
|
API Incoming Dependencies
...
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) |
|---|---|---|---|---|
| SDC model distribution API | API for retrieving TOSCA model of close loop | To fill out | Link toward the detailed API description | |
| Policy Engine | API for retrieving configuration policy updates | |||
| A&AI | API invoked for information enhancements | |||
| DMaaP Message Router | API for topic publish / subscribe | |||
| DMaaP Bus Controller | DMaaP Bus Controller is a part of DMaaP that provides topic provisioning; this is the API for topic provisioning. (TBD based on AAF availability) |
API Outgoing Dependencies
API this project is delivering to other projects.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| VES Ingestion | API for VNFs to send VES data | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
| DCAE Deployment Handler | NB API for invoking the deployment of DCAE subcomponents | |||
| DCAE Inventory | API for Add/Delete DCAE copy's TOSCA models |
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 |
|---|---|---|
| OpenStack | ||
| Cloudify Manager | ||
| Consul | ||
| CDAP | ||
| Hadoop | ||
| PNDA | ||
| Flink | ||
In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
...
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.
...
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 |
Resources
Fill out the Resources Committed to the Release centralized page.
...
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
- ...
...