| commit | e08eee030fd379fa7253e99626c314d021b1eacd | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Fri Apr 21 14:21:37 2023 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Thu Jun 01 15:44:40 2023 +0200 |
| tree | e5cf7bd85d6ea82d3de72e9f6fd802e3b7faa409 | |
| parent | 1a76edf1159156d832e62c268b54fd727f82057f [diff] |
[DOC] Update London OOM documentation Add information: - new Deployment options (Production, Development) - move Istio deployment to base installation - add Gateway-API and Keycloak Installation instructions - split and rename of a few files for updated structure - changed rst section formatting as suggested in sphinx rtd theme - add London Release Notes Issue-ID: OOM-3159 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I98b8541d51daba982fd6c8be0c85fae676d53c13
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.