| commit | 5470cda865785bd638aab556dfdb127ce97913ef | [log] [tgz] |
|---|---|---|
| author | Bruno Sakoto <bruno.sakoto@bell.ca> | Mon Mar 14 22:50:52 2022 -0400 |
| committer | Sylvain Desbureaux <sylvain.desbureaux@orange.com> | Tue Mar 22 08:35:26 2022 +0000 |
| tree | 4aa4bb17a254047ec9b9650287e8b0a5036d67b9 | |
| parent | f91c26bb28e7ee59ccc941647190c18257f23a01 [diff] |
[CPS] Configure roles-wrapper dependency If needed, RBAC roles are created when deploying cps chart. This change is coming from the need to deploy cps chart standalone independently from onap main chart. A previous change has been made in https://gerrit.onap.org/r/c/oom/+/126713 and reverted with https://gerrit.onap.org/r/c/oom/+/126961 for onap main chart compatibility. Then this current change supports both integrated and standalone cps deployments depending on a configurable variable. Default deployment remains onap integrated one. Issue-ID: CPS-862 Change-Id: Ic787a8bcf9373f060a91966614a0145dec2a7c90 Signed-off-by: Bruno Sakoto <bruno.sakoto@bell.ca>
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.