Overview

Scope

What is this release trying to address?

The core development is focused on building CMPv2 (Certificate Authority) abilities for both Direct Access from VNFs, but also from AAF's Certificate Manager.

AAF, as a project, wants to continue to integrate into overall ONAP goals with Logging Spec/Implementation and Swagger API documentation, as well as strive towards higher JUnit metrics.

Requirements

1) As an ONAP Environment:

I need a CMPv2 CA Server that is able to create Certificates.  The expectation is that there is one per Lab (Windriver, etc), but if available, one for All ONAP Envs would work, or One per Env (i.e. Daily), if the SAME core Certificate is used across the board.

2) As a VNF:

I need to obtain a Certificate directly from ONAP CMPv2 CA Server.

3) As AAF Certman (Component):

I need to be able to obtain Certificates from the CMPv2 Server as one of several Certificate Authority Adapters I already support.

4) As an ONAP Component:

I need the AAF Certificate Agent to support locally created private/public keys.

Minimum Viable Product

AAF continues to be viable if it provides current BasicAuth Authentication and Certificates to Apps with all its current components, and remains stable in Daily and Staging Environments.

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

ONAP Goals are to have multiple Client certificates from different CA Chains available for use as needed by Clients.

Release Deliverables

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

Sub-Components

Resources and Repositories for Application Authorization Framework

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

Platform Maturity

Frankfurt Release Platform Maturity

• 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 Outgoing Dependencies

API this project is delivering to other projects.

• 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, ...).

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

• TESTING AND INTEGRATION PLANS

Existing CSIT and JUnit plans are paramount.

If possible, we want to increase CSIT testing, depending on resource, per requests to PTLs.

Testing of CMPv2 Interfaces are not fleshed out as yet, because of outstanding questions:

CMPv2 Developers have been informed, and agreed, that their new code must have both JUnit Testing, and some sort of testing against a REAL CMPv2 Server.

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

• KNOWN DEFECTS AND ISSUES

Please refer to Frankfurt Defect Status

• RISKS

Frankfurt Risks

• RESOURCES

Resources Committed to AAF for Frankfurt

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

• DOCUMENTATION, TRAINING

Please update the following centralized wiki: Frankfurt Documentation

That includes

• Team contributions to the specific document related to he project (Config guide, installation guide...).

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