| Table of Contents | ||
|---|---|---|
|
Overview
| Project NameEnter | the name of the projectApplication Authorization Framework |
|---|---|
| Target Release Name | Enter the name of the release you are targeting to deliverBeijing Release |
| Project Lifecycle State | Either Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
| Participating Company List | the company participating in this release. At least 3-4 organizations, including an operator are recommended.AT&T, Intel, Tech Mahindra |
Scope
What is this release trying to address?
Describe the problem being solved by this releaseAAF trying to address the secured communication threw certificate management & token based Authentication,Authorization
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).The existing Amsterdam use cases are still going to be supported and additional use cases related to the will be supported for the Beijing Release
Minimum Viable Product
Describe the MVP for this releaseFor Beijing release, the minimum viable product we are targeting is integrating AAF with multiple ONAP applications and perform secured transactions.
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.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Deliverable Name | Deliverable Description |
|---|---|
AAF integration with Appc | AAF Git repository |
| AAF source code | AAF Git repository |
| AAF library | ONAP Nexus repository |
| AAF API description | ONAP wiki |
| AAF Release Notes | ONAP wiki |
| AAF Documentation | AAF Git repository |
Sub-Components
List all sub-components As 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.the Beijing release,Certificate Management will be added to the AAF
Architecture
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
...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | 0 | 1 | Run performance basic test, depends on performance criteria availability for level 1 |
|
| Stability | 0 | 1 | Participate to Stability runs Level 1 |
|
| Resiliency | 1 | 21 |
| |
| Security | 0 | 1 | Reach CII passing badge, increasing test coverage as remaining item |
|
| Scalability | 0 | 1 | Reach Level 1 single site horizontal scaling |
|
| Manageability | 1 | 1 | Using LOG4J common framework for logging |
|
| Usability | 1 | 1 | API documentation provided |
|
...
API Incoming Dependencies
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)
...
None None None None None 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)
...
Provisining API for creating,deleting and listing the administrative objects Aug 02 2017 March 08 2018 AAF API Admin API API for the admin access Aug 02 2017 March 08 2018 AAF API CADI CADI ( CODE ACCESS DATA IDENTITY) Aug 02 2017 March 08 2018 AAF API 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
...
Docker Container engine 1.12 Cassandra database container 2.1.16 In case there are specific dependencies (Centos 7 vs Ubuntu 16. Etc.) list them as well.
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.
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.AAF will invest in CSIT tests to allow further integration testing, AAF already provided some tests as part of R1.
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
...
Testing/Integration limited testing of final product Known Defects and Issues
Provide a link toward the list of all known project bugs.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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).
...
- No known risks so far.
Resources
Fill out the Resources Committed to the Release 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
...
may be used to document internal milestones
...
that the team agreed on.
Also, 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,
...
provide these agreements and dates in this section.
It is not expected to have a detailed project plan.
Date
Project
Deliverable
To fill out
...
AAF AAF - CertMan,oAuth 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 ...
http://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/index.html
| Note | ||
|---|---|---|
| ||
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. |
...