The content of this template is expected to be fill out for M1 Release Planning Milestone.
Overview
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Dublin |
| Project Lifecycle State | Incubation, Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company | AT&T Ericsson, Nokia, China Mobile, Amdocs |
Scope
What is this release trying to address?
The Dublin release of AAF project will address the following items:
- bug fixes, maintenance and feature alignment
- increased stability of running AAF in K8s environment
- Enhance AAF Locator to handle Internal and External access information
- helping ONAP Services engage with AAF generated Certificates and clients
- (Stretch Goal) Provide CMPv2 Cert APIs for VNFs
Note: AAF already has Silver CII Badging https://bestpractices.coreinfrastructure.org/en/projects/2303
Use Cases
ONAP Services will be able to engage AAF Configuration as a "Init Container", prior to starting, which will give them certificates, etc.
Both External and Internal services will be able to utilize AAF Locator to find AAF Resources in ONAP
(Stretch Goal) Present AAF Locator solution as part of Scalability/Resiliency initiatives
(Stretch Goal) Be able to generate Certificates for VNFs with CMPv2 Protocol
Minimum Viable Product
The ONAP AAF Project will deliver the following documentation as its minimum viable product:
AAF's 7 Microservices, running in OOM
AAF Documentation
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.
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description |
|---|---|
| Enhanced Locator | Be able to provide Location info for Internal ONAP services and External Access |
Sub-Components
List all sub-components part of this release.
aaf-service
aaf-locator
aaf-oauth
aaf-cm
aaf-gui
aaf-fs
aaf-hello
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.
Architecture
High level architecture diagram
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 Archiecture 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.
Platform Maturity
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 | 2 (Stretch Target may not reach) | AAF audit trails all transactions. With Dublin, we want to add additional Performance testing in ONAP, not just originating company. |
|
| Stability | 2 | 3 | AAF has clean record of Uptime in initial Company. Only need to finish work to have this happen in K8S |
|
| Resiliency | 2 | 3 | See AAF Locator |
|
| Security | 2 | 2 | CII Badge: https://bestpractices.coreinfrastructure.org/en/projects/2303 |
|
| Scalability | 2 | 3 | AAF Locator changes allows for High Scale. Will be bringing to Architecture. |
|
| Manageability | 1 | 1 | It is possible that in doing other OOM integration, we'll improve this as a matter of course. |
|
| Usability | 1 | 2 (Stretch, depends on def of Usability Testing) | https://docs.onap.org/en/casablanca/guides/onap-provider/index.html |
|
API Incoming Dependencies
List the API this project is expecting from other projects.
AAF is Infrastructure. As such, it does not expect input from other projects.
API Outgoing Dependencies
API this project is delivering to other projects.
API is included in GUI
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, ...).
Cassandra, Version 3.11 (Note: The expectation is that users of AAF may have their own Cassandra installations. Chances are, Datastax client is compatible if near this version)
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.
Junits
CSIT (automated functional tests)
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.
(Note: Many bugs may be related to Side Tools (like SSM or Side-Car), which are add-ons, and do not necessarily affect ONAP functionality as a whole)
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 |
|---|---|---|
CMP interface integration requested. No pre-built CMP Java libraries have been identified. | Further research. | See how long it takes to implement CMP v2 elements from scratch |
Resources
Fill out AAF Resources 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
- ...
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.