| commit | edc1daa1f4e159ddd79d4e269b26b5cfb889297b | [log] [tgz] |
|---|---|---|
| author | Sylvain Desbureaux <sylvain.desbureaux@orange.com> | Tue Feb 15 15:27:44 2022 +0100 |
| committer | Sylvain Desbureaux <sylvain.desbureaux@orange.com> | Thu Feb 17 17:31:54 2022 +0100 |
| tree | 17351484cf721c5cc5003d18bb98fe1bf3ab12b4 | |
| parent | 044b886ee6c43d7087953ffa2267668f2a830a95 [diff] |
[GLOBAL] Upgrade Jetty Image Use latest Jetty image, change configuration and explain in code what needs to be done for next time. Issue-ID: AAI-3450 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I85c2f772b985e0f03654916a800c96e1dd345093
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.