...
Info |
---|
These instructions work on linux/MacOS or on windows via WSL using a local or remote kubernetes cluster. It is recommended to run ranpm RANPM on a kubernetes cluster instead of local docker-desktop etc. as the deployment is somewhat resource intensive. |
Requirement on Kubernetes
...
(RANPM Installation)
The demo set can be run on local or remote kubernetes cluster. Kubectl must be configured to point to the applicable kubernetes instance. Nodeports exposed by the kubernetes instance must be accessible by the local machine - basically the kubernetes control plane IP needs to be accessible from the local machine. (The installation scripts take care of getting a token form Istio, using dep/ranpm/install/scripts/kube_get_controlplane_host.sh as the baseurl. The K8s controlplane should be accessible from localhost)
Introduction to Helm Charts
...
There are many other parameters in the file that may require adaptation to fit a certain environment. For example hostname
, namespace
and port
to kafka
message router etc. These integration details are not covered in this guide.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
# Here you can enable inclusion or exclusion of each component. Disabled components will not be installed, and their later configurations will be ignored. nonrtric: installPms: true installA1controller: true installA1simulator: true installControlpanel: true installInformationservice: true installRappcatalogueservice: true installRappcatalogueenhancedservice: true # Enable either installNonrtricgateway or installKong. Both cannot be enabled at the same time installNonrtricgateway: false installKong: true installDmaapadapterservice: true installDmaapmediatorservice: true installHelmmanager: true installOrufhrecovery: true installRansliceassurance: true installCapifcore: true installServicemanager: true # When enabling Ranpm, set value false above for installControlpanel, installInformationservice, installNonrtricgateway installRanpm: false # rApp Manager functionality relies on ONAP ACM for its operation installrAppmanager: true # DME Participant should only be activated when ONAP ACM installation is available for this participant to utilize installDmeParticipant: false volume1: # Set the size to 0 if you do not need the volume (if you are using Dynamic Volume Provisioning) size: 2Gi storageClassName: pms-storage hostPath: /var/nonrtric/pms-storage volume2: # Set the size to 0 if you do not need the volume (if you are using Dynamic Volume Provisioning) size: 2Gi storageClassName: ics-storage hostPath: /var/nonrtric/ics-storage volume3: size: 1Gi storageClassName: helmmanager-storage ... ... ... |
...