| commit | f63b16e0666fe3182b0919005dd6073795ab1ccd | [log] [tgz] |
|---|---|---|
| author | wr148d <wr148d@att.com> | Mon Jan 31 12:47:12 2022 -0500 |
| committer | wr148d <wr148d@att.com> | Tue Feb 01 08:54:17 2022 -0500 |
| tree | a4f904becc74e01b9432e0fd348c8be04d0adb51 | |
| parent | 0eec968ce240c0f029de5c3d3f8b3e8037ee74ce [diff] |
[AAI] Docker image updates for package upgrades for security reasons Babel, schema-service, resources, traversal, and graphadmin docker images updated to get log4j version updates and other package updates based on security violations Issue-ID: AAI-3431 Signed-off-by: wr148d <wr148d@att.com> Change-Id: Iacd476bb2f70af1524878a887bfac669cc45f3fb
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.