Helm charts, configuration files, and automation scripts that deploy the auxiliary functions for RIC. The auxiliary functions are defined as the features and services that interact with the RIC but they do not collocated with the RIC cluster. These functions includes but not limited to non-realtime management components (e.g., dashboard, DMaaP, VEScollector) that interact with RIC using A1/O1 interfaces.
. ├── 80-Auxiliary-Functions Contains components that interact with RIC through A1/O1 │ ├── bin Contains deployment and uninstall scripts │ ├── etc Contains deployment configuration files │ └── helm Contains helm charts ├── 85-External Services Deployment scripts and chart for external service used by RIC to reach services outside of cluster └── README.md This file
$ # Modify the configuration files in ./80-Auxiliary-Functions/etc/ $ . ./80-Auxiliary-Functions/bin/install $ # If you have an override value.yaml file, please use $ #. ./80-Auxiliary-Functions/bin/install YOUR_OVERRIDE_FILE
$ . ./80-Auxiliary-Functions/bin/uninstall
You can configure the Helm release name, Kubernetes namespace using configuration files located in ./80-Auxiliary-Functions/etc/
In the one-click deployment solution, the above setting will be overrided by environment variables shown below. *RICAUX_RELEASE_NAME *RICAUX_NAMESPACE
The IP address described below should be the interface IP address of the VM hosting the platform cluster. If the platform cluster is multi-node, any of the nodes can be specified here.
$ # Set the value of ext/ip in values.yaml to be the external IP address. If you will use an override file and it has ext/ip set, $ # make sure it is set correctly. $ . ./85-Ext-Services/bin/install $ # If you have an override value.yaml file, please use $ #. ./85-Ext-Services/bin/install YOUR_OVERRIDE_FILE
$ . ./85-Ext-Services/bin/uninstall