| commit | 0879dfcaad420fcc7a6adc77b2b9c72b9522e3cb | [log] [tgz] |
|---|---|---|
| author | aravind.est <aravindhan.a@est.tech> | Wed Feb 22 09:05:50 2023 +0000 |
| committer | aravind.est <aravindhan.a@est.tech> | Wed Mar 15 15:02:47 2023 +0000 |
| tree | 57ce3bb4f6fe15232ba961da987474038b1519c1 | |
| parent | 8a626708ed05ca337586695b2056441fc6405fec [diff] |
[POLICY] Add Kserve participant Add kserve participant helm charts. Issue-ID: POLICY-4525 Signed-off-by: aravind.est <aravindhan.a@est.tech> Change-Id: I51f1ddb91302fd54c6e926f9f5c80e648b9a4a07
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.