Versions Compared

Key

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

...

High level architecture diagram

See logging streaming filebeat sidecars all feeding into the Logging ELK stack - the containers we will be adding/re-adding are in red.

Image Added

Logging Architecture

Log Streaming Compliance and API

...

Area

Actual Level

log/pomba

Targeted Level for current ReleaseHow, EvidencesComments
Performance1/12/2
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability2/23/3via k8s
  • 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
Resiliency2/22/2via k8s
  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security0/11/1
  • 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/11/1
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability1/11/1
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability1/11/1
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

...

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
ELK stackKibana, Logstash, elasticsearch REST endpointsSince AmsterdamOut1.2.2 already out in CasablancaActive Logging Specifications

...

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

...

This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended recommended to provide these agreements and dates in this section.

...