| commit | fcb7878f85baf46713e5f63db8b2a50a18d0da79 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Mon Nov 07 17:57:41 2022 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Wed Nov 09 09:12:38 2022 +0100 |
| tree | d2b14180e7f5ef9c48d11320dad0679470d5d856 | |
| parent | 49628f8ba3c0faf2090aae6b26aa7d8c62b3f72d [diff] |
[MULTICLOUD] Correction for AAI service port in MultiCloud API AAI service port changed to 80 and service aai-internal additionally the AAI_PROTOCOL is added, which requites a patch for MultiCloud (https://jira.onap.org/browse/MULTICLOUD-1495) Issue-ID: OOM-3015 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: Ibc0833dd13b7e1110c77711bae30f3af52eda0c4
The ONAP Operations Manager (OOM) is responsible for life-cycle management of the ONAP platform itself; components such as SO, SDNC, etc.
It is not responsible for the management of services, VNFs or infrastructure instantiated by ONAP or used by ONAP to host such services or VNFs.
OOM uses the open-source Kubernetes container management system as a means to manage the containers that compose ONAP where the containers are hosted either directly on bare-metal servers or on VMs hosted by a 3rd party management system.
OOM ensures that ONAP is easily deployable and maintainable throughout its life cycle while using hardware resources efficiently.
Full documentation is available in ONAP documentation in operations and administration guides.
Please see contributing file to learn on how to contribute
All issues should be filled in ONAP Jira.