| commit | 8d57918746be63112542f7d47602adc043398565 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Fri Sep 29 14:02:04 2023 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Mon Oct 02 14:49:47 2023 +0000 |
| tree | e1775587b315573bf704f822c91e29af49cefa7a | |
| parent | cfd8434fe9484b9219560159094b174421d6d6a2 [diff] |
[COMMON] Update Gateway-API resource definitions Update the definitions based on test results to avoid ArgoCD resyncs. Issue-ID: OOM-3184 Change-Id: I0e87d0bbea4a45a480fe078e4d9ae7a0f22ff764 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
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.