/
AAF R2 Beijing Release - M1 Release Planning

AAF R2 Beijing Release - M1 Release Planning

Mar 06, 2018


Overview

Project Name

Application Authorization Framework

Project Name

Application Authorization Framework

Target Release Name

Beijing  Release

Project Lifecycle State

Incubation

Participating Company 

AT&T, Intel, Tech Mahindra

Scope

What is this release trying to address?

AAF trying to address the secured communication threw certificate management & token based Authentication,Authorization

Use Cases

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

For 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.

Epics

Stories

Longer term roadmap

 AAF is to organize software authorizations so that applications, tools and services can match the access needed to perform job functions.  This is a critical function for Cloud environments, as Services need to be able to be installed and running in a very short time, and should not be encumbered with local configurations of Users, Permissions and Passwords.To be effective during a computer transaction, Security must not only be secure, but very fast. Given that each transaction must be checked and validated for Authorization and Authentication, it is critical that all elements on this path perform optimally.

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

Deliverable Name

Deliverable Description

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

As part of the Beijing release,Certificate Management will be added to the AAF

Architecture



Architecture

High level architecture diagram



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

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

  • 0 -- none

  • 1 – baseline performance criteria identified and measured

  • 2 & 3 – performance improvement plans created & implemented

Stability

0

1

Participate to Stability runs Level 1

  • 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

Resiliency

1

1



  • 0 – none

  • 1 – manual failure and recovery (< 30 minutes)

  • 2 – automated detection and recovery (single site)

  • 3 – automated detection and recovery (geo redundancy)

Security

0

1

Reach CII passing badge, increasing test coverage as remaining item

  • 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

Scalability

0

1

Reach Level 1 single site horizontal scaling

  • 0 – no ability to scale

  • 1 – single site horizontal scaling

  • 2 – geographic scaling

  • 3 – scaling across multiple ONAP instances

Manageability

1

1

Using LOG4J common framework for logging

  • 1 – single logging system across components; instantiation in < 1 hour

  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management

Usability

1

1

API documentation provided

  • 1 – user guide; deployment documentation; API documentation

  • 2 – UI consistency; usability testing; tutorial documentation