ONAP Operations Manager Release Notes

Previous Release Notes

This document provides the release notes for the London release.

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

OOM provides Helm charts

Project Description - a guide for developers of OOM
OOM Developer Guide - a guide for developers of OOM
OOM Infrastructure Guide - a guide for those setting up the environments that OOM will use
OOM Deployment Guide - a guide for those deploying OOM on an existing cloud
OOM User Guide - a guide for operators of an OOM instance
OOM Access Info - a guide for operators who require access to OOM applications

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