| commit | f51bbef3978f1176551d6891c7e583d128a0875a | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Fri Mar 31 12:07:23 2023 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Fri Apr 07 11:04:23 2023 +0000 |
| tree | 3d0748e1b5f7090dc92108d85b2f4f587d7bb642 | |
| parent | bb32bf993ac2b74c12fc435e756d9ce98bb73611 [diff] |
[COMMON][OTHERS] Fix dependency conditions In case of local DB the "init" dependency is activated as the "not" condition is not working Issue-ID: OOM-3152 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I27dba69a644bbcc2b61245c22784976ba7c66173
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.