commit | 4ab4c050b49c78c54c5aa575051583ab3a727e9d | [log] [tgz] |
---|---|---|
author | FrancescoFioraEst <francesco.fiora@est.tech> | Thu Feb 24 10:46:15 2022 +0000 |
committer | Francesco Fiora <francesco.fiora@est.tech> | Tue Mar 29 07:56:16 2022 +0000 |
tree | 9fe7fcc0d67a9bcf9987c35fd7a1a7ebb12bedbe | |
parent | 90cd77349d5019c6cd2a41a078dca57923146bcb [diff] |
[POLICY] Update CLAMP OOM Configuration for Remove Clamp frontend Remove clamp-frontend code, as this is moved to policy-gui Issue-ID: POLICY-3358 Change-Id: Id6402815ead572e8cec9f1743709d6de6f28b79c Signed-off-by: FrancescoFioraEst <francesco.fiora@est.tech>
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.