| commit | 314df904244f02122c011803e15012fc9dee2251 | [log] [tgz] |
|---|---|---|
| author | mpriyank <priyank.maheshwari@est.tech> | Thu Sep 22 10:41:54 2022 +0100 |
| committer | Fiachra Corcoran <fiachra.corcoran@est.tech> | Thu Nov 03 14:28:09 2022 +0000 |
| tree | 8f52f75f38b0c5f6712db533f1013ea9b417aaae | |
| parent | 8778cc162677eac7d2db8302f035efc37878fdec [diff] |
[CPS] Security logging fields - Removed the old logback.xml file. - Added logback-spring.xml with the new format for logging in json format - Updated the file mount path in deployment file. - Above change is just for CPS-Core Issue-ID: CPS-1291 Change-Id: If1b657a4959023fc18d0a4710891a55dfeb29b22 Signed-off-by: mpriyank <priyank.maheshwari@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.