The content of this template is expected to be fill out for M1 Release Planning Milestone.
Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Guilin |
| Project Lifecycle State | Incubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | AT&T, ZTE |
The scope of the Guilin Release of ESR will address Vulnerability Security Fix and Platform Maturity Requirements, as well the approved use cases.
Highest priority will be assigned to support security and platform maturity requirements. As next highest priority, ESR will support the approved use cases. Best-effort additional development will continue to support additional features not included in the approved use cases.
ESR R7 Guilin Release: Other requirements
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.
| Key | Summary | T | Created | Updated | Due | Assignee | Reporter | P | Status | Resolution |
|---|---|---|---|---|---|---|---|---|---|---|
| AAI-2888 | Upversion to DropWizard V2.0.2 | | Apr 29, 2020 | Apr 29, 2020 | Peng He | Peng He | | 开放 | 未解决 | |
| AAI-2889 | Java 11 support | | Apr 29, 2020 | Apr 29, 2020 | Peng He | Peng He | | 开放 | 未解决 | |
| AAI-2890 | ESR Guilin Document | | Apr 29, 2020 | Apr 29, 2020 | Peng He | Peng He |
| 开放 | 未解决 | |
| AAI-2891 | Kubernetes based Cloud regions Support | | Apr 29, 2020 | Apr 29, 2020 | Peng He | Peng He | | 开放 | 未解决 |
| Key | Summary | T | Created | Updated | Due | Assignee | Reporter | P | Status | Resolution |
|---|---|---|---|---|---|---|---|---|---|---|
| AAI-2847 | Added NFVO GUI internationalization file |  | Mar 30, 2020 | Apr 29, 2020 | Peng He | Peng He |
| 已关闭 | 完成 | |
| AAI-2856 | Remove JQuery 1.11.0 from ESR Version | | Apr 07, 2020 | Apr 29, 2020 | Peng He | Peng He | | 已关闭 | 完成 | |
| AAI-2857 | Upgrade to Apache Tomcat 9.0.31 | | Apr 08, 2020 | Apr 29, 2020 | Peng He | Peng He |
| 已关闭 | 完成 | |
| AAI-2858 | Remove BootStrap 3.1.1 from ESR GUI | | Apr 08, 2020 | Apr 29, 2020 | Peng He | Peng He | | 已关闭 | 完成 | |
| AAI-2859 | Upgrade to bootbox 5.4.0 | | Apr 08, 2020 | Apr 29, 2020 | Peng He | Peng He | | 已关闭 | 完成 | |
| AAI-2876 | Upversion to MSB-JAVA-JDK 1.2.5 | | Apr 22, 2020 | Apr 29, 2020 | Peng He | Peng He | | 已关闭 | 完成 | |
| AAI-2863 | Integrating aai-parent as the parent pom | | Apr 13, 2020 | Apr 29, 2020 | Peng He | Peng He | | 开放 | 未解决 | |
| AAI-2892 | Change MSB Server Port in Test Case Code and Test it |
| Apr 29, 2020 | Apr 29, 2020 | Peng He | Peng He | | 开放 | 未解决 | |
| AAI-2895 | Resolve Esr-gui Root Running |
| Apr 30, 2020 | Apr 30, 2020 | Peng He | Peng He |
| 开放 | 未解决 | |
| AAI-2896 | Resolve Esr-server Root Running |
| Apr 30, 2020 | Apr 30, 2020 | Peng He | Peng He |
| 开放 | 未解决 |
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.
Deliverable Name | Deliverable Description |
|---|---|
| ESR-GUI | Exectuable |
| ESR-SERVER | Exectuable |
None
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 ONAP Architecture diagram.
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.
Please refer to AAI Data.
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) |
|---|---|---|---|---|
| MSB | Service registry |
API this project is delivering to other projects.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
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 .
Name | Description | Version |
|---|---|---|
| BootStrap | Popular framework for building responsive and a template starter page | 4.3.1 |
| JQuery | Open-source JavaScript Library | 3.4.1 |
| Docker | VM container | |
| DropWizard | Open-source Microservice application Java Framework | 1.3.0 or 2.0.2 |
| Apache Tomcat | Open-source implementation of the Java Servlet | 9.0.33 |
| Jersey | Open-source RESTful Web Services framework | 2.16 |
| Jetty | Servlet Engine and Http Server | 9.4.22 |
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.
ESR will participate in the Integration testing
ESR will do unit test within the WR AAI tenant space
ESR will contribute additional robot test tooling which does better regression testing
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 |
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).
Please update any risk on the centralized wiki page
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 |
Please update the following centralized wiki:
That includes
Note
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.
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.