| commit | b10781bad2cdf34a3754937714a77b2fbeaa8e21 | [log] [tgz] |
|---|---|---|
| author | Seshu-Kumar-M <seshu.kumar.m@huawei.com> | Thu Mar 24 08:12:36 2022 +0530 |
| committer | Dan Timoney <dtimoney@att.com> | Thu Apr 07 13:54:28 2022 +0000 |
| tree | f15b70556cd852a21701456d09175df51bc95e6c | |
| parent | df4fc03d8540b4c1ee10b440b4f7d5b20d8e2685 [diff] |
[SO] First release images for the J release First images of SO for Jakarta release. Issue-ID: SO-3912 Signed-off-by: Seshu-Kumar-M <seshu.kumar.m@huawei.com> Change-Id: I666a5a7e3be27cf24c2c557c9ce2f696213d1aff
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.