Versions Compared

Key

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

...

20180627_ still filling out - Michael O'Brien

Info
titleInfo

Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
Use the Wiki to document the release plan. Don't provide PowerPoint.
Use as much diagrams and flow charts as you need, directly in the wiki, to convey your message.

Table of Contents
outlinetrue

Overview

...

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

Release Components Name

Components Name

Components Repository name

Maven Group ID

Components Description

Components Name

Components Repository name

Maven Group ID

Components Description

logging-analyticslogging-analyticsorg.onap.logging-analyticsA reference analytics pipeline configuration
pomba-context-aggregatorlogging-analytics/

TODO: we need to discuss whether we are

org.onap.pomba (we would be the first mixed)

or org.onap.logging-analytics.pomba

org.onap.logging-analytics.pomba.context-aggregator


pomba-aai-context-builder logging-analytics/org.onap.logging-analytics.pomba.aai-context-builder 
pomba-sdc-context-builderlogging-analytics/org.onap.logging-analytics.pomba.sdc-context-builder
pomba-sdnc-context-builderlogging-analytics/org.onap.logging-analytics.pomba.sdnc-context-builder
pomba-network-discovery-context-builderlogging-analytics/org.onap.logging-analytics.pomba.network-discovery-context-builder
pomba-audit-commonlogging-analytics/org.onap.logging-analytics.pomba.audit-common
pomba-service-decomposition logging-analytics/org.onap.logging-analytics.pomba.service-decomposition 
pomba-network-discoverylogging-analytics/org.onap.logging-analytics.pomba.network-discovery
pomba-network-discovery-apilogging-analytics/org.onap.logging-analytics.pomba.network-discovery-api

Architecture

High level architecture diagram

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance12

address logstash and elasticsearch scaling

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-380

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-376

  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability23

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-380

  • 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

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-380

  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security12

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-409

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

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-380

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

...