Versions Compared

Key

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

...

Project NameEnter the name of the project
Target Release NameFrankfurt
Project Lifecycle StateIncubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company AT&T, Nokia, Ericsson, Wipro, IBM, TechM, Orange, ChinaMobile, Huawei

Scope

What is this release trying to address?

...

  • VESCollector Enhancements
    • DCAEGEN2-1594 – VESCollector healthcheck support when authentication is enabled; Validation blocked by DCAEGEN2-1757 – spring version issue
    • DCAEGEN2-1483  – Event publish order issue
    • DCAEGEN2-1484  - Set dynamic partitionkey (Nokia dint commitstretch goal)
    • DCAEGEN2-1774 - Optimize VES schema load by retain in-memory than loading file each time (dint find corresponding jira, created new today)
    • DCAEGEN2-608   - Performance/benchmarking
    • DCAEGEN2-1776  - Remove certOnly and basicAuth from authentication methods
    • DCAEGEN2-1779  - Switch VES collector's K8s health checks to HTTPS
  • TCA-gen2 delivery and replace TCA/cdap
    • Mongodb support for tca-gen2
  • Deployment optimization (Plugin load, reduce bootstrap, Cloudify upgrade)
  • Python 3.x Plugin upgrade (5.0.5 - Cloudify mock available; 5.1 – full python 3.x)
  • Python 3.x support (Policy library)
  • DCAEGEN2-1548 - Python 3.x upgrade for Policy Lib
  • DCAE Dashboard Fixes and security updates
  • Automated test improvement (csit/robot)
  • DCAE Helm chart org (OOM-1574)
  • (transfer dependent on OOM team)

...

This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release. List identified release gaps (if any), and its impact.

Gaps identifiedImpact
To fill outTo fill out
  • Known Defects and Issues

OTI Function deliveryOTI functionality is planned to be introduced in phase. For Frankfurt, seed code for OTI-Handler and EventPRoc will be delivered. The complete e2e functionality will be available in next release. There is no impact to Frankfurt usecase by this functionality.
  • Known Defects and Issues

Provide a link toward the list of all known project bugs.

...

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

Risk identifiedMitigation PlanContingency Plan
To fill outTo fill out

Cloudify support for Python 3.x not available during Frankfurt timeframe. This impacts migration of Cloudify and associated plugins in Frankfurt (DCAEGEN2-1546)

Continue El-Alto version of Cloudify and Plugins under python 2.7None
  • Resources

Fill out the Resources Committed to the Release centralized page.

...