| commit | 0d5c917c02b40b335251a39952bb46f70bcb73ce | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Tue Apr 19 18:10:52 2022 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Fri Jul 29 12:58:54 2022 +0200 |
| tree | ddf48aebc1c90ffd1e2c7654c61799e5d7d1317a | |
| parent | c8964e507dfc9b32a0f29f2a67ce74b1f8a260b9 [diff] |
[DMAAP] DMaaP ServiceMesh compatibility Remove the dependency to AAF during the deployment of the DMaaP Bus Controller, as it is not used in ServishMesh usecase Added a change to the job to use http interface and delete Istio sidecar Issue-ID: OOM-2820 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I81f41bc06fe8db260636a17e66ffbabd58f01d74
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.