Versions Compared

Old Version 17

changes.mady.by.user Michael O'Brien

Saved on

compared with

New Version Current

changes.mady.by.user Michael O'Brien

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: add and fixVersion = "Beijing Release"

...

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

Use Cases

Use Case: Residential Broadband vCPE (Approved)

Use Case: vFW/vDNS (Approved)

Use Case: VoLTE(approved)

Minimum Viable Product

The MVP for Amsterdam will:

    • Logging RI as a demo/reference for teams not currently running filebeat containers in their pods 
      Currently the following are using filebeat already (aai, appc, so, policy, portal, sdc, sdnc, vid)
    • Logging AOP based library for use by all component teams as a spring shared jar.
    • Emit standardized, machine-readable logging output, correlated by transaction ID.
    • Allow dynamic reconfiguration of logging providers. 
    • Provide a reference configuration for Elastic Stack, automatically deployed by Kubernetes and the ONAP Operations Manager.
    • Provide reference configurations for shipping and indexing of ONAP logs to the ELK stack via filebeat.
    • Provide standard Kibana dashboards for transaction traceability and general lucene spec log searches

...

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=LOG and issuetype in (epic) and fixVersion = "Beijing Release"
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=LOG and issuetype in (story) and fixVersion = "Beijing Release"
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Deliverable Name

Deliverable Description

Revised logging guidelinesUpdates to What's New - ONAP Application Logging Guidelines reflecting new conventions and requirements.
Logging provider configuration defaultsRegularized configuration locations, simplifying deployment and customization.
Logging provider output defaultsRegularized output locations, simplifying deployment and customization, and the shipping and indexing of logs.
Logging provider migrationOptional standardization of logger providers, including upgrading from EOL Log4j 1.X.
Updated logging provider configuration(s)Updated, standardized configurations for all logging providers and ONAP components - specific to OOM in the OOM repo.
Filebeat configurationReference configuration for Elastic Stack Filebeat shipping.
Logstash configurationReference configuration for Elastic Stack Logstash indexing.
Elasticsearch configurationReference configuration for Elastic Stack Elasticsearch.
Kibana configurationReference configuration for Elastic Stack's Kibana Discover UI.
Elastic Stack deploymentAutomated OOM deployment of an Elastic Stack reference configuration, providing ONAP with an OOTB analytics platform.
DocumentationOther documentation supporting analytics configuration.

...

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.

...

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill outTo fill out

  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

...