ONAP Operations Manager Release Notes

Previous Release Notes


This document provides the release notes for the London release.


Release Data



Docker images


Release designation


Release date


New features

  • Introduction of “Production” ONAP setup, including:

    • Istio Service Mesh based deployment

    • Ingress (Istio-Gateway) deployment and usage as standard external access method

    • Internal Security provided by ServiceMesh and Component2Component AuthorizationPolicies

    • External Security by introducing AuthN/Z using Keycloak and OAuth2Proxy for Ingress Access

  • Removal of unsupported components (AAF, Portal, Contrib,…)

  • Update of Helmcharts to use common templates and practices

  • Optional support for Cassandra 4.x using k8ssandra-operator

  • REQ-1349 Removal of AAF. Internal communication encryption and authorization is offered by ServiceMesh

  • REQ-1350 All component must be able to run without MSB. Component helm charts modified to use MSB optionally and test the components during Daily and Gating with and without MSB

  • REQ-1351 External secure communication only via Ingress. Ingress resources created by templates and Ingress installation is described in the OOM documents

Bug fixes

A list of issues resolved in this release can be found here: https://jira.onap.org/projects/OOM/versions/11500

Known Issues

  • Components not working under ServiceMesh

    • CDS UI

    • SO Monitor UI

    • CLI


Software Deliverables

OOM provides Helm charts

Documentation Deliverables

Known Limitations, Issues and Workarounds

Known Vulnerabilities

  • Cassandra version needs to be updated to support new Python version see OOM-2900 In London supported as option (using k8ssandra-operator), see OOM Optional Addons


Security Notes

Fixed Security Issues


For more information on the ONAP Istanbul release, please see:

  1. ONAP Home Page

  2. ONAP Documentation

  3. ONAP Release Downloads

  4. ONAP Wiki Page