| commit | 3f0b0a7044cb6d43d174340d551608cd16505b40 | [log] [tgz] |
|---|---|---|
| author | Lukasz Rajewski <lukasz.rajewski@t-mobile.pl> | Mon Apr 17 16:15:48 2023 +0000 |
| committer | Lukasz Rajewski <lukasz.rajewski@t-mobile.pl> | Tue May 02 11:09:29 2023 +0000 |
| tree | b41ff9975ab131da8a7fded798f99b16f525aff4 | |
| parent | 4cb23fffcbfe3e88475a6bd3c3e0e91835c38e28 [diff] |
[SO] London release image updates London release image updates - for test purpose only so far. Issue-ID: SO-4091 Signed-off-by: Lukasz Rajewski <lukasz.rajewski@t-mobile.pl> Change-Id: Iec7fe7c04dc645f2f65910e7df4e1b60e980c19c
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.