Versions Compared

Key

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

...

Project NameEnter the name of the project
Target Release NameHonolulu
Project Lifecycle StateMature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company AT&T, Amdocs, OrangeBell Canada, China Mobile, Huawei, ZTEOrange, Nokia, IBM, TechMahindra, FujitsuWipro, YoppWorks

Scope

What is this release trying to address?

...

Highest priority will be assigned to support global 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.

AAI R8 Honolulu Release: TSC must have requirementsGlobal Requirements

Requirements

Use Cases: AAI R8 Honolulu Release: Functional Use Cases 

TSC MUST HAVES : AAI R8 Honolulu Release: TSC must have requirementsGlobal Requirements

Minimum Viable Product

  • A&AI Core: Resources - CRUD REST API endpoints for A&AI inventory resources
  • A&AI Core: Traversal - REST APIs for graph traversals.  Some APIs use the Gremlin Server
  • A&AI Core: Babel - Parses models received from SDC
  • A&AI Core: Event-Client - publishes an event stream of changes to the database
  • A&AI Core: Model-loader - Loading models parsed from SDC
  • A&AI Core: Logging-service - Service to standardize logging for compliance and readability
  • A&AI Core: GraphAdmin - suite of functionality to manage the graph database
  • UI - An ONAP portal application used by operations for visualizing and searching
  • Data Router: Makes decisions about workloads to be dispatched to search and tabular microservces.  Includes logic to recognize and direct requests based on request archetypes.
  • Search - Enable complex searches for sub graphs and functions that need to perform well across deeply nested structures using Elasticsearch.  Used by the UI
  • Cacher - The Response Caching Microservice (Cacher) is built to deliver multiple mechanisms of making API calls and populating the responses into a JSON datastore. The datastore is an embedded mongodb datastore, that stores cached API responses, which are updated via DMAAP events or can be synced by timed tasks or calls to the force sync endpoint.
  • ESR - External System Registry component (provided community can deliver support, update vulnerable dependencies, and maintain the project)Rest-Client - A library for an user to interface with the A&AI core APIs of resources and traversal

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
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = AAI and AND issuetype = Epic AND status in (epic) and status != "Closed" Open, "In Progress", Reopened, Submitted, Delivered) AND fixVersion = "Honolulu Release" ORDER BY updated DESC
serverId425b2b0a-557c-3c0c-b515-579789cceedb

...

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = AAI and AND issuetype = Story AND status in (story) and status != "Closed" Open, "In Progress", Reopened, Submitted, Delivered) AND fixVersion = "Honolulu Release" ORDER BY updated DESC
serverId425b2b0a-557c-3c0c-b515-579789cceedb

...

Search-data-serviceExecutable - caching interface

Deliverable Name

Deliverable Description

A&AI resourcesExecutable.  REST CRUD interface to graph database
A&AI traversal

Executable.  REST Interface for complex queries

Data routerExecutable

Executable
Router-coreLibrary
Sparky-feLibrary
Sparky-beExecutable (AAI UI)
Schema-serviceExecutable (delivers schema to other AAI mS)
GraphadminExecutable (graph administration functions)
ESRExectuable
OOM ConfigSource code - configuration using AAI dockers in the k8 OOM environments
Cacher


Sub-Components

See Resources and Repositories (Deprecated)#ActiveandAvailableInventoryPlease see the INFO.yaml files associated with each repo as the authoritative sources of information. https://gerrit.onap.org/r/admin/repos/q/filter:aai

Architecture

High level architecture diagram

...

Please fill out the centralized wiki page: Guilin Honolulu Release Platform Maturity

AAI data is filled out


  • API Incoming Dependencies

...

NameDescriptionVersion
JanusGraphOpen-source, distributed graph database

0.2.3

Cassandra

Open-source distributed storage system

3.11
DockerVM container
SpringBootOpen-source Microservice application sever1.5.22 or 2.xElasticSearchSearch framework6.8
HAPROXYmicroservice front end1.8
Centos/AlpineOSSee docker config files

...

Please update any risk on the centralized wiki page - Guilin Honolulu Risks

  • Resources

TBDAT&T, Amdocs, Bell Canada, China Mobile, Huawei, Orange, Wipro, YoppWorks

  • Release Milestone

The milestones are defined at the Guilin Release Planning: Honolulu and all the supporting project agreed to comply with these dates.

...

Please update the following centralized wiki:Guilin  Honolulu 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
    • ...

...