| commit | 5daf7a82c63e9684c6b500409d668a1d7f77d0f7 | [log] [tgz] |
|---|---|---|
| author | rope252 <gareth.roper@est.tech> | Tue Nov 01 15:19:48 2022 +0000 |
| committer | rope252 <gareth.roper@est.tech> | Tue Nov 01 15:23:08 2022 +0000 |
| tree | 6fbd9ad40974e275e5a987067857e9f669f050d4 | |
| parent | 26411370f979ba4e2d1fc1b9f4bd8e3f23f0fee1 [diff] |
[AAI] Add AAI http service for DCAE Service Mesh patch Adding functionality to deploy an additional service for AAI for port 80 If service mesh is enabled this service is required by the DCAE SM patch Change-Id: I234bfb335b77b7ebdd2bc4c2596924314c9f3fca Issue-ID: OOM-2820 Signed-off-by: rope252 <gareth.roper@est.tech>
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.