Versions Compared

Old Version 22

changes.mady.by.user Sai Gandham

Saved on

compared with

New Version Current

changes.mady.by.user Jonathan Gathman

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Project NameEnter the name of the project
Target Release NameDublin
Project Lifecycle StateIncubation,  Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company AT&T Ericsson, Nokia, China Mobile, Amdocs

...

  • 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  (This Stretch Goal is not doable in Dublin)


Note: AAF already has Silver CII Badging https://bestpractices.coreinfrastructure.org/en/projects/2303

...

(Stretch Goal) Present AAF Locator solution as part of Scalability/Resiliency initiatives

(Stretch Goal) Be able to generate Certificates for VNFs with CMPv2 Protocol. This stretch Goal cannot be done in Dublin

Minimum Viable Product

The ONAP AAF Project will deliver the following documentation as its minimum viable product:

...

Note: The Enhanced Locator shows great promise to enable ONAP Components to achieve Geo Scalability and Resiliency.  However, as is usual for Infrastructure, it must be essentially there and functional for Architecture to view and make recommendations.  We are pursuing both essential Capabilities and Architectural Approval during this release.

Note: VNFs are asking for CMPv2 API.  We cannot promise this because of Risks (see details below), which include not having a CMP compatible CA available to develop with, and lack of known Java CMP Libraries.  We will be looking at this, however during the Dublin Release, and demonstrate however far along we can get.. This Stretch goal cannot be done in Dublin.

Sub-Components

List all sub-components part of this 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.

...

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.

...

Risk identifiedMitigation PlanContingency Plan

This Stretch Goal has been Descoped

CMP interface integration requested, but to date, no pre-built CMP Java libraries have been identified.

If no existing CMP Java client exists that can be used, then we will have to build the API from scratch, which will take time and resources which are in short supply.

We have put the CMP as something we will work on, but cannot commit to.

This means it will not likely to be ready in Dublin, but may be ready in El Alto.


There is no contingency plan for the combination of lack of Java Library and lack of time to write the API from scratch . As a Stretch Goal, we can work on this during Dublin after commitments, in hopes of committing for El Alto.


This Stretch Goal has been Descoped

Explanation: Since AAF Certman would be functioning as intermediate to the Certificate Authority, that CA must exist and be deployed in ONAP before serious work can begin.

We cannot commit to anything that is not testable

There is no way to compensate for lack of CMP based CA. Until this is ready, CMP Access cannot be tested, and therefore, cannot be done. If ONAP works on obtaining and running a CMP based CA in Dublin, then there might be a good chance of committing for El Alto.

  • Resources

Fill out AAF Resources centralized page.

  • Release Milestone

...