The content of this template is expected to be fill out for M1 Release Planning Milestone.


Project NameEnter the name of the project
Target Release NameBeijing
Project Lifecycle StateIncubation.  Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company AT&T, Amdocs, ZTE, Orange, Tech Mahindra


What is this release trying to address?

The scope of the Beijing Release of AAI will address CII Badging Security Program and Platform Maturity Requirements, as well the approved Release 2 Use Cases

Highest priority will be assigned to support security and platform maturity requirements.  As next highest priority, AAI will support the approved use cases.  Best-effort additional development will continue to support additional features not included in the approved use cases.

Use Cases

AAI will support to the best of its ability the Release 2 Use Cases

Minimum Viable Product


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.



Longer term roadmap

This presentation was given by AT&T's Phil Blackwood on AAI's weekly meeting: 2018-01-05 AAI Weekly Meeting notes

AAI Roadmap 2018-01-05.pdf

Release Deliverables

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

Deliverable NameDeliverable Description
Move to Active OpenSource Graph databaseA&AI is currently using titan which is not actively being developed . We want to explore and implement a replacement FOSS solution which is being actively developed.
GizmoExecutable. Atomic REST CRUD interface to graph database
A&AI resourcesExecutable.  REST CRUD interface to graph database
A&AI traversal

Executable.  REST Interface for complex queries

Data routerExecutable
OOM ConfigSource code - configuration recommendations for using AAI dockers in the OOM environments
IMExectuable - stretch goal


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


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.

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.

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance01The target is to capture baseline performance, but it is unclear what we'll be capturing.
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability01Unclear what kinds of random transactions will be sent to AAI.  Assuming it will be random runs of existing use cases w/ Robot or jmeter
  • 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
Resiliency12AAI will leverage OOMs single site failure detection and recovery
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security01AAI will get to 50+ test coverage, most repos already above 50% ONAP SONAR
  • 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

AAI will leverge OOM; currently working on a clustered solution for cassandra on docker

  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11AAI uses EELF and will continue to do so in Beijing
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

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 NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
DMaaPEventing bus

MSBService registry

SDCA&AI Model loader consumes model objects

Multi-VIMImage storage, cloud-infrastracture update


API this project is delivering to other projects.

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
SDCREST API(upload/query images)TBDTBD

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

JanusGraphOpen-source, distributed graph database


UbuntuOpen-source software operating system16.0.4-LTS

Open-source distributed storage system

DockerVM container
AJSCOpen-source Microservice application sever6
ElasticSearchSearch framework2.4.1
HAPROXYmicroservice front end1.7

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.

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 identifiedImpact
To fill outTo fill out

Provide a link toward the list of all known project bugs.

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 identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill out

Fill out the Resources Committed to the Release centralized page.

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

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.

To fill outTo fill outTo fill out

The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset.

Other Information

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.

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.