| commit | 8f95be29e36be0137463c056660dd11e0d20c171 | [log] [tgz] |
|---|---|---|
| author | jhh <jorge.hernandez-herrero@att.com> | Wed Apr 13 11:56:40 2022 -0500 |
| committer | Fiachra Corcoran <fiachra.corcoran@est.tech> | Fri Apr 22 14:53:30 2022 +0000 |
| tree | a54de4d725abf05f12cf6bf8bca86cff16f610a7 | |
| parent | ec452b50a4a1ea0aa0e18836bfe80ca1dab20f1b [diff] |
[POLICY] Update components to latest release The exceptions are policy-drools-pdp, policy-xacml-pdp, and policy-gui that are handled in different reviews. Issue-ID: POLICY-4089 Signed-off-by: jhh <jorge.hernandez-herrero@att.com> Change-Id: I5d03ce22d9c69380c6f76b24383555cf71803ea4 Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
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.