3 Copyright (c) 2019 AT&T Intellectual Property.
5 Licensed under the Creative Commons License, Attribution 4.0 Intl.
6 (the"Documentation License"); you may not use this documentation
7 except incompliance with the Documentation License. You may obtain
8 a copy of the Documentation License at
10 https://creativecommons.org/licenses/by/4.0/
12 Unless required by applicable law or agreed to in writing,
13 documentation distributed under the Documentation License is
14 distributed on an "AS IS"BASIS, WITHOUT WARRANTIES OR CONDITIONS
15 OF ANY KIND, either express or implied. See the Documentation
16 License for the specific language governing permissions and
17 limitations under the Documentation License.
21 This is a comment, it will not be included)
22 [comment]: <> (in the output file unless you use it in)
23 [comment]: <> (a reference style link.)
28 This repo contains RAN Intelligent Controller (RIC) deployments related files.
33 The RIC deployment scripts are designed to deploy RIC components using helm charts. A deployment recipe yaml file that
34 contains parameter key:value pairs can be provided as a parameter for any deployment script in this repository. The
35 deployment recipe is acting as the helm override values.yaml file. If no deployment recipe is provided, default parameters
36 are used. The default parameters are set up to deploy a RIC instance using Linux Foundation repositories in a
37 self-contained environment.
40 ### Directory Structure
45 ├── LICENSES.txt License information
46 ├── README.md This file
47 ├── RECIPE_EXAMPLE Directory that contains deploy recipe examples
48 ├── ric-aux Deployment scripts, charts and configuration files for RIC auxilary functions
49 ├── ric-common Deployment scripts, charts and configuration files for RIC common template
50 ├── ric-infra Deployment scripts, charts and configuration files for infrastructure support
51 ├── ric-platform Deployment scripts, charts and configuration files for RIC platform components
52 └── ric-xapps xApp related scripts, charts and configuration files
54 ### Directory Naming Convention
56 The root directories are organized according to the deployment plans. Each directory contains subdirectories for
57 different deployable components. The prefixes of these subdirectories represent the deployment order. The smaller the
58 prefix number the eariler the corresponding component will be deployed. Consider the following example,
60 │ ├── 80-Auxiliary-Functions
76 │ ├── 80-Auxiliary-Functions
83 when deploying the ric-platform, the credential is deployed before RIC-Platform.
85 In each of the component directories, ./bin contains the binary and script files and ./helm contains the helm charts,
87 Some components contain an ./etc directory with configuration files and some contain a ./docker directory with docker related files for building the docker images.
89 Please refer to the README.md files in individual directory for more details.
91 Within ric-infra, ric-platform and ric-aux, each of the components above can be deployed and undeployed separately.
92 There are also scripts for deploying the ric-infra, ric-platform or ric-aux in its entirety.
94 The ./bin directory contains these scripts
96 The following sections discuss one-script deployment for each
98 ### To deploy RIC Infrastructure
100 Edit ./RECIPE_EXAMPLE/RIC_INFRA_RECIPE_EXAMPLE
101 You can choose whether to enable Kubernetes deployment, Helm Chart museum and ELFKP stack
102 You can specify the Helm release prefix and namespaces used
103 You must specify username and password for Docker repo
104 Then run the following to deploy:
106 $ . ./deploy-ric-infra -f ../RECIPE_EXAMPLE/RIC_INFRA_RECIPE_EXAMPLE
108 Run the following to undeploy:
110 $ . ./undeploy-ric-infra
113 ### To deploy RIC Platform
115 Edit ./RECIPE_EXAMPLE/RIC_PLATFORM_RECIPE_EXAMPLE
116 You can specify the Helm release prefix and namespaces used
117 Set the values of extsvcaux/ricip and extsvcaux/auxip to be the external IP addresses of VM hosting RIC cluster and VM hosting AUX cluster, respectively.
118 These values should be set in both the override file and the local values.yaml file
120 $ . ./deploy-ric-platform -f ../RECIPE_EXAMPLE/RIC_PLATFORM_RECIPE_EXAMPLE
122 Run the following to undeploy:
124 $ . ./undeploy-ric-platform
127 ### To deploy RIC Auxiliary functions
129 Edit ./RECIPE_EXAMPLE/RIC_PLATFORM_RECIPE_EXAMPLE
130 You can specify the Helm release prefix and namespaces used
131 Set the values of extsvcaux/ricip and extsvcaux/auxip to be the external IP addresses of VM hosting RIC cluster and VM hosting AUX cluster, respectively.
132 These values should be set in both the override file and the local values.yaml file
134 $ . ./deploy-ric-aux -f ../RECIPE_EXAMPLE/RIC_AUX_RECIPE_EXAMPLE
136 Run the following to undeploy:
138 $ . ./undeploy-ric-aux