| commit | bf35e55286a0ac2f4fe05f595cda7109f22a5e6a | [log] [tgz] |
|---|---|---|
| author | adheli.tavares <adheli.tavares@est.tech> | Thu Jul 25 10:03:13 2024 +0100 |
| committer | adheli.tavares <adheli.tavares@est.tech> | Fri Jul 26 11:01:38 2024 +0100 |
| tree | 5f9c9e24f665c52cf03647bb815771d6f14e25b2 | |
| parent | 878a4d86056f8cae15f95f7bbe172effc556d533 [diff] |
[POLICY] Deprecation of policy-gui - policy-gui is going into unmaintained state. Issue-ID: POLICY-5049 Change-Id: Ic83ab19a37d1c3e7007975b27ca150c4794a86e9 Signed-off-by: adheli.tavares <adheli.tavares@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.