| commit | c979732d500e2473f5299f33d969ec829bcbeac5 | [log] [tgz] |
|---|---|---|
| author | Jack Lucas <jflos@sonoris.net> | Fri Mar 18 12:32:59 2022 -0400 |
| committer | Jack Lucas <jflos@sonoris.net> | Wed Mar 23 10:12:19 2022 -0400 |
| tree | 88b9566aaa1ef0e4781586e3424acc09b41767ba | |
| parent | 0e55ea53b1886df5847f4838fb840b668b4acb1f [diff] |
[DCAEGEN2] Remove Consul loader init container DCAE microservices no longer rely on Consul to store their configuration information. This change modifies the common DCAE microservice deployment template to eliminate the initContainer that loads configuration information into Consul. Issue-ID: DCAEGEN2-3059 Signed-off-by: Jack Lucas <jflos@sonoris.net> Change-Id: I4d9d547de020fe1987afab1c99cd033799ed7b36
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.