Versions Compared

Old Version 9

changes.mady.by.user James Forsyth

Saved on

compared with

New Version Current

changes.mady.by.user James Forsyth

Saved on

Key

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

DRAFT PROPOSAL FOR COMMENTS

...

Project NameEnter the name of the project
Target Release NameDublin
Project Lifecycle StateIncubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company List the company participating in this release. At least 3-4 organizations, including an operator are recommended.AT&T, Amdocs, Orange, Huawei, ZTE, Nokia, IBM, TechMahindra

Scope

What is this release trying to address?

The scope of the Dublin Release of AAI will address CII Badging Security Program and Platform Maturity Requirements, as well the approved 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.

Key Scope Items:

ItemSummary

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-531

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-1331

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-1340

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-1406

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-1989

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-1998

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2026

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2096

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2097

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2099

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2100

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2102

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2103

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-2111


Use Cases

AAI R4 Use Case and Functional Requirements Impacts

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
  • 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
  • Champ - Abstraction from underlying graph storage systems that A&AI would interface with.
  • Gizmo - CRUD Rest API endpoint for resources and relationships, delivering atomic interactions with the graph for improved scalability.
  • Enricher - Enables complementing AT&T data with federated data from additional sources
  • 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

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance11
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability11
  • 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
Resiliency22
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security12 (Stretch goal)
  • 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
Scalability1

1


  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11
  • 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)
To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill outLink toward the detailed API description
DMaaPEventing bus


MSBService registry


SDCAAI Model loader consumes model objects


AAFAuthentication / Authorization



  • API Outgoing Dependencies

...

Link toward the detailed API description
API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill out
SOREST APIM3TBD
APPCREST APIM3TBD
POLICYREST APIM3TBD
VIDREST APIM3TBD
SDNCREST APIM3TBD
HOLMESREST APIM3TBD
VF-CREST APIM3TBD
CLIREST APIM3TBD
MultiVimREST APIM3TBD
SDCREST API(upload/query images)M3TBD
ExtAPIREST APIM3TBD
UUIREST APIM3TBD
OOFREST APIM3TBD

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

To fill out
NameDescriptionVersionTo fill outTo fill out
JanusGraphOpen-source, distributed graph database

0.2.2

UbuntuOpen-source software operating system16.0.4-LTS
Cassandra

Open-source distributed storage system

3.11
DockerVM container
SpringBootOpen-source Microservice application sever1.5.18 or 2.x
ElasticSearchSearch framework2.4.1
HAPROXYmicroservice front end1.8

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

...

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill out

  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

...