| commit | 2d51104671ae198c8e711b64463a37a0e7f9bba3 | [log] [tgz] |
|---|---|---|
| author | Guangrong Fu <fu.guangrong@zte.com.cn> | Wed Mar 15 11:09:49 2023 +0800 |
| committer | Guangrong Fu <fu.guangrong@zte.com.cn> | Mon Mar 27 08:46:51 2023 +0800 |
| tree | 22936b1128da2e2eb3d4fd0df137a7026bd67c1a | |
| parent | 8a626708ed05ca337586695b2056441fc6405fec [diff] |
[HOLMES] Changed the way for MSB registration Register Holmes MSB through an annotation in the Helm chart. Enable/Disable TLS via an env variable. Added Ingress Configurations Issue-ID: HOLMES-612 Signed-off-by: Guangrong Fu <fu.guangrong@zte.com.cn> Change-Id: If1bd8a62ea3840943ccd04cbcc16442f65fd434b
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.