| commit | 71c8b84a44c57daba13ec4e8a19989658e8abcbc | [log] [tgz] |
|---|---|---|
| author | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Mon Dec 04 13:51:17 2023 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Thu Dec 07 08:43:24 2023 +0100 |
| tree | 4a876379fb342a9f1650f5ffe531ff5370da1807 | |
| parent | 2ad6c16c56c038178c8001a242e8c3243e21e9ba [diff] |
[PORTAL-NG] Publish ui and bff charts in OOM - upload ui and bff - preferences and history services will be added later - added portal-ng to ONAP chart and overrides Issue-ID: PORTALNG-66 Change-Id: I9182234be3afbdcdc95b23f0799a11d41384184e Signed-off-by: Fiete Ostkamp <Fiete.Ostkamp@telekom.de>
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.
