Overview
DRAFT PROPOSAL FOR COMMENTS
The content of this template is expected to be fill out for M1 Release Planning Milestone.
Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki. |
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Dublin Release |
| Project Lifecycle State | Incubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | AT&T, Tech Mahindra, Ericsson, Orange, IBM |
The Dublin Release will be focusing on the following areas:
Describe the use case this release is targeted for (better if reference to customer use case).
APPC will contribute partially to the following use cases as part of the functional requirements.
Same as was defined for Casablanca, but with the adding of increasing better performance for starting application, geo-redundancy etc. For details, please see above on S3P section
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.
The long term road map is to achieve all the goals outlined in the approved project proposal; to be fully model and standards driven, be agnostics and make no assumptions about the network. Support configuration and lifecyle management of VNF/VNFC in a generic fashion so that on-boarding any new VNF/VNFC is just a matter of configuration and data. Longer term items include:
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description | Deliverable Location |
|---|---|---|
| "App-c Image" Docker Container | Executable | Docker images available on nexus3 |
| Java Source Code | The Java code for the main App-c components. | appc Git repository |
| Deployment Scripts | Linux shell scripts and Maven pom files used to generate the Docker containers. | appc/deployment Git repository |
| Directed Graph Xml Files (DGs) | Xml files define the directed graphs which are installed to database during startup and are used to determine actions taken by app-c | appc/deployment Git repository |
| Yang Model Files | Yang files are used to define the LCM action | appc Git repository |
| Property Files | Property files are used to define values that may need to be changed depending on the environment app-c is run in. | appc Git repository |
| CDT tool | an APP-C Design Tool enabling VNF owners to create templates and other artifacts used by APP-C Configure actions (used to apply a post-instantiation configuration) as well as other life cycle commands | appc/cdt Git repository |
| Parent Repo | The repository for the parents pom files. | appc/parents Git repository |
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
List the other ONAP projects you depend on.
APPC depends on the the following components as part of the general ONAP architecture:
At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.
Indicate where your project fit within the Dublin+Architecture.
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.
For details on the APPC architecture, refer to the APPC User Guide.
Refering to CII Badging Program and S3P, 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 | 0 | 1 2 - Stretch goal | ||
| Stability | 1 - project team 2 - Integration team | 1 - project team but we may not reach 80% code coverage 2 - Integration team Assume Integration team will address Level 2 - 72 hour test in Dublin | *current (1/13/19) code coverage is 67.9%
| |
| Resiliency | 2 | 2 | ||
| Security | 1 | 1, 2 (partial, please see the comments) | there is http internal connection between CDT and APPC, we need to find the resource to migrate from http to https. | |
| Scalability | 1 | 1 | ||
| Manageability | 1 | 1, 2(partial, please see the comments, APPC will comply two items on level 2) |
| |
| Usability | 1 | 1 | Recommendation for Casablanca is Level 2; however, we cannot meeting Level 2 All new API’s must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines; - There was an issue with ODL & API version - need to investigate further |
List the API this project is expecting from other projects.
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) | |
|---|---|---|---|---|
| SDC | REST API | Currently Available | TBD | |
| AAI | REST API | Currently Available | TBD | |
| CCSDK | OpenDayLight, SLI, AAI Client, dblib | End of March | TBD | |
| DMaaP | API to publish/subscribe to events sent for VNF/VM action requests. | Currently Available | TBD | DMaaP API |
| AAF | Application Authorization Framework | Currently Available | Currently Available |
API this project is delivering to other projects.
API Name
| API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |
|---|---|---|---|---|
| NB Interface | REST API | Link toward the detailed API description |
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 | |
|---|---|---|
| ODL | OpenDaylight controller platform | Fluorine SR2 |
| Docker | Docker container host | 1.12 |
| MariaDB | data base container | 10.1.11 |
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.
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 |
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 |
|---|---|---|
| ODL upgrade to Fluorine - depends on CCSDK projects | Fall back to Nitrogen |
Fill out the Resources Committed to the Release centralized page.
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
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 |
APPC will follow requirement by documentation team based on the APPC release capacities. |
Documentation updates planned for Dublin release are tracked under Documentation Epic:
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.
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.