...
Project Name | Enter the name of the project |
---|---|
Target Release Name | R1 Beijing Release |
Project Lifecycle State | Incubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
Participating Company | AT&T, Intel, HuaweiChinaMobile, Orange, TechM, IBM, Huawei |
Scope
What is this release trying to address?
Scope: The scope of this release will be for the Portal Platform to support the below list.
...
- Support deployment, scalability issues of the platform
...
- Support role management for partnering apps - Policy, SDC, VID, AAI
...
- Angular upgrade to address the security issue - may impact partnering apps like Policy and VID.
...
:
- Internationalization language support (Platform Feature) - ChinaMobile support
- Design language/internationalization component in Portal and provide service apis to partnering apps like Policy, VID, SDC, AAI.
- This is collaborative work with larger community (Use Case UI ONAP Team), expecting implementation details soon from ChinaMobile
...
- resources.
...
- Testing (Technical Debt) - AT&T, IBM, TechM support
- CSIT tests for new Casablanca features.
- Support 50% code coverage without JavaScript. However, enable JavaScript Unit tests coverage to view the coverage results.
- Reporting feature enhancement in portal/sdk (Platform Feature) - AT&T support
- Defect fixes
Not-in-Scope: Please check Gaps.
...
Use Cases
Describe the use case this release is targeted for (better if the reference to customer use case).
...
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
List the other ONAP projects your depends on.
AAF (Application Authorization Framework) - for role/user creation, authentication, authorization.
OOM
MUSIC
UsecaseUI for internationalization feature contribution.
Architecture
High level architecture diagram
...
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.
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
- 0 -- none
- 1 – baseline performance criteria identified and measured
- 2 & 3 – performance improvement plans created & implemented
...
- 0 – none
- 1 – 72 hours component level soak w/random transactions
- 2 – 72 hours platform level soak w/random transactions
- 3 – 6 months track record of reduced defect rate
...
Integrating with MUSIC
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
...
- 0 – none
- 1 – manual failure and recovery (< 30 minutes)
- 2 – automated detection and recovery (single site)
- 3 – automated detection and recovery (geo redundancy)
...
>50% Test Coverage - https://sonar.onap.org/dashboard?id=org.onap.portal%253Aonap-portal-parent
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
...
- 0 – none
- 1 – CII Passing badge + 50% Test Coverage
- 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
- 3 – CII Gold
...
Integrating with MUSIC
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
...
- 0 – no ability to scale
- 1 – single site horizontal scaling
- 2 – geographic scaling
- 3 – scaling across multiple ONAP instances
Portal's maturity requirements status is maintained for Casablanca release here - Portal R3 Casablanca - Integration Test Plans
API
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
- 1 – single logging system across components; instantiation in < 1 hour
- 2 – ability to upgrade a single component; tracing across components; externalized configuration management
...
Jira | ||||||
---|---|---|---|---|---|---|
|
...
- 1 – user guide; deployment documentation; API documentation
- 2 – UI consistency; usability testing; tutorial documentation
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.
...
API this release is delivering to other releases.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
---|---|---|---|---|
InternationalizationAPIs | To support language and locale | June 25, 2018 | Aug 23, 2018 | UsecaseUI team to contribute the details as they collaborating with Portal team on this requirement. *Multi-Language Functionality API List:
|
Third Party Products Dependencies
...
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.
JUnit tests: 80% 50% code coverage is the goal for all repositories without javascript.
If resources become available, we will add more CSIT test cases.
...
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 |
---|---|---|
Originally planned priority items, but de-scoped due to lack of resources (below items are added to backlog and not being committed for Casablanca release).
|
|
Known Defects and Issues
Provide a link toward the list of all known project bugs.
...
Risk identified | Mitigation Plan | Contingency Plan |
---|---|---|
Resources | Actively seeking community support. | Current resources are only not enough to satisfy even the Highest Priority Epics (Platform Maturity, JUnit 80% test coverage). But that will be difficult to achieve. |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...