...
Code Block | ||
---|---|---|
| ||
KONG_DOMAIN=<string> KONG_PROTOCOL=<http or https protocol scheme> KONG_IPV4=<host string> KONG_DATA_PLANE_PORT=<port number> KONG_CONTROL_PLANE_PORT=<port number> CAPIF_PROTOCOL=<http or https protocol scheme> CAPIF_IPV4=<host> CAPIF_PORT=<port number> LOG_LEVEL=<Trace, Debug, Info, Warning, Error, Fatal or Panic> SERVICE_MANAGER_PORT=<port number> TEST_SERVICE_IPV4=<host string> TEST_SERVICE_PORT=<port number> |
Deployment using IT Dep
Clone the Git repo git clone "https://gerrit.o-ran-sc.org/r/it/dep".
The example recipe dep/RECIPE_EXAMPLE/NONRTRIC/example_recipe.yaml will do a full deployment including Kong, Capifcore, and Service Manager.
nonrtric:
installPms: true
installA1controller: true
installA1simulator: true
installControlpanel: true
installInformationservice: true
installRappcatalogueservice: true
installRappcatalogueenhancedservice: true
installNonrtricgateway: true
installKong: true
installDmaapadapterservice: true
installDmaapmediatorservice: true
installHelmmanager: true
installOrufhrecovery: true
installRansliceassurance: true
installCapifcore: true
installServicemanager: true
installRanpm: false
# rApp Manager functionality relies on ACM for its operation
installrAppmanager: true
# DME Participant should only be activated when ACM installation is available for this participant to utilize
installDmeParticipant: false
Stand-alone Deployment with it/dep
You can modify a local copy of this file to only include Kong, Capifcore and Service Manager, as in the following example.
nonrtric:
installPms: false
installA1controller: false
installA1simulator: false
installControlpanel: false
installInformationservice: false
installRappcatalogueservice: false
installRappcatalogueenhancedservice: false
installNonrtricgateway: false
installKong: true
installDmaapadapterservice: false
installDmaapmediatorservice: false
installHelmmanager: false
installOrufhrecovery: false
installRansliceassurance: false
installCapifcore: true
installServicemanager: true
installRanpm: false
# rApp Manager functionality relies on ACM for its operation
installrAppmanager: false
# DME Participant should only be activated when ACM installation is available for this participant to utilize
installDmeParticipant: false
Kong Clean Up
Please note that when doing an undeployment, we remove any Kong services and routes that are flagged with each of the following tags.
- apfId
- aefId
- apiId
- apiVersion
- resourceName
This is to ensure that we do a proper clean up. When we re-deploy, we know that our Kong database is starting from a fresh install. This was a known issue with one Kubernetes cluster.
The Control Panel also creates Kong services and routes. As these Kng resources don't have the above tags, they are not affected by this clean up.