| commit | 8b94826c2c9ad0e1423b752cf896b10e41625933 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Fri Jan 19 15:52:06 2024 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Fri Jan 19 16:00:00 2024 +0100 |
| tree | 5633f330bb4cab2b6958f2f71fe94e485bb0c9fd | |
| parent | 21d48641d6344e9f00523ca15d49d44fcdb277b3 [diff] |
[SDNC] Support root secret for external DB In case of an external DB the secret containing the root password can be given in the global.mariadbGalera section and has to be used in the DB jobs Issue-ID: OOM-3266 Change-Id: I05d36169e7f8c6aa18712e0a75621d1cd001f1b3 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
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.