Versions Compared

Key

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

...

The content of this template is expected to be fill out for M1 Release Planning Milestone - due 27 June via Release Planning

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

LoggingLogging
Target Release NameCasablanca
Project Lifecycle StateMature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company Amdocs, AT&T, Bell

...

Indicate at a high level the longer term roadmap. This is to put things into the big perspective.

Spec level integration with Acumos to allow cross platform transaction triage.

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

https://jira.acumos.org/browse/ACUMOS-710

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) 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.

Release Components Name

Components Name

Components Repository name

Maven Group ID

Maven Artifact ID

Java package name

Components Description

Components Name

Components Repository name

Maven Group ID

Maven Artifact ID

Java package name

Components Description

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

org.onap.pomba


pomba-context-aggregatororg.onap.pomba.context.aggregatorOrchestrates calls to various context builders and aggregates data from various data sources into one single payload
pomba-aai-context-builder logging-analytics/pomba/pomba-aai-context-builder org.onap.pomba pomba-aai-context-builderorg.onap.pomba.contextbuilder.aaiAAI Context builder. Interacts with A&AI and transforms A&AI data into common model structure
pomba-sdc-context-builderlogging-analytics/pomba/pomba-sdc-context-builderorg.onap.pombapomba-sdc-context-builderorg.onap.pomba.contextbuilder.sdcSDC Context builder. Interacts with SDC and transforms SDC TOSCA CSAR into common model structure
pomba-sdnc-context-builderlogging-analytics/pomba/pomba-sdnc-context-builderorg.onap.pombapomba-sdnc-context-builderorg.onap.pomba.contextbuilder.sdncSDN-C Context Builder. Interacts with SDN-C and transforms SDN-C data into common model structure
pomba-network-discovery-context-builderlogging-analytics/pomba/pomba-network-discovery-context-builderorg.onap.pombapomba-network-discovery-context-builderorg.onap.pomba.contextbuilder.networkdiscoveryNetwork Discovery Context Builder. Interacts with Network discovery component and transforms its data into common model structure
pomba-audit-commonlogging-analytics/pomba/pomba-audit-commonorg.onap.pombapomba-audit-commonorg.onap.pomba.common.auditPOJO project. Holds POMBA common  model POJO representation

Resources committed to the Releaseb

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

...

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 APIPOMBA Audit InititiationAPI to inititiate POMBA AuditDate for which the API is reviewed and agreedTo fill outLink toward the detailed API description

POMBA Audit Initiation Swagger

POMBA Context BuildersAPI that must be supported by all Context Builders

POMBA Context Builder Swagger
  • 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, ...).

NameDescriptionVersion
To fill outTo fill outTo fill out

...

ElasticSearch

ES is part of the ELK stack

5.5.0 - will upgrade to 5.6.0
LogstashLS is part of the ELK stack5.5.0 - will upgrade to 5.6.0
KibanaKB is part of the ELK stack5.5.0 - will upgrade to 5.6.0

  • Testing and Integration Plans

...

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill out
  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

...