OOM Infrastructure Guide

OOM deploys and manages ONAP on a pre-established Kubernetes cluster – the
creation of this cluster is outside of the scope of the OOM project as there
are many options including public clouds with pre-established environments.
If creation of a Kubernetes cluster is required, the life-cycle of this
cluster is independent of the life-cycle of the ONAP components themselves.

Minimum Hardware Configuration

Some recommended hardware requirements are provided below. Note that this is for a
full ONAP deployment (all components).

OOM Hardware Requirements



RAM

HD

vCores

Ports

224GB

160GB

112

0.0.0.0/0 (all open)

Customizing ONAP to deploy only components that are needed will drastically reduce these requirements.
See the OOM customized deployment section for more details.

Note

Kubernetes supports a maximum of 110 pods per node – this can be overcome by modifying your kubelet config.

See the kubelet confg guide for more information.

The use of many small nodes is preferred over a few larger nodes (for example 14 x 16GB – 8 vCores each).

OOM can be deployed on a private set of physical hosts or VMs (or even a combination of the two).

Software Requirements

The versions of software that are supported by OOM are as follows:

OOM Software Requirements (base)



Release

Kubernetes

Helm

kubectl

Docker

Cert-Manager

Strimzi

Jakarta

1.22.4

3.6.3

1.22.4

20.10.x

1.8.0

0.28.0

Kohn

1.23.8

3.8.2

1.23.8

20.10.x

1.8.0

0.32.0

OOM Software Requirements (optional)



Release

Prometheus Stack

Istio

Jakarta

35.x

—

Kohn

35.x

1.15.1