blob: cfd0b1f144f7a42f0578d32ba649bd3c83c6b204 [file] [log] [blame]
wriderbf0073e2019-11-03 14:35:07 -05001.. This work is licensed under a Creative Commons Attribution 4.0 International License.
2.. SPDX-License-Identifier: CC-BY-4.0
3.. ===============LICENSE_START=======================================================
4.. Copyright (C) 2019 AT&T Intellectual Property
5.. ===================================================================================
6.. This documentation file is distributed under the Creative Commons Attribution
7.. 4.0 International License (the "License"); you may not use this file except in
8.. compliance with the License. You may obtain a copy of the License at
9..
10.. http://creativecommons.org/licenses/by/4.0
11..
12.. This file is distributed on an "AS IS" BASIS,
13.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
14.. See the License for the specific language governing permissions and
15.. limitations under the License.
16.. ===============LICENSE_END=========================================================
17
18.. contents::
19 :depth: 3
20 :local:
21
wriderc1be4252019-11-26 10:13:54 -050022===================
23Installation Guides
24===================
wriderbf0073e2019-11-03 14:35:07 -050025
wriderc1be4252019-11-26 10:13:54 -050026This document describes how to install the components deployed by scripts and Helm charts
27under the it/dep repository, it's dependencies and required system resources.
wriderbf0073e2019-11-03 14:35:07 -050028
29.. contents::
30 :depth: 3
31 :local:
32
33Version history
wriderc1be4252019-11-26 10:13:54 -050034===============
wriderbf0073e2019-11-03 14:35:07 -050035
36+--------------------+--------------------+--------------------+--------------------+
37| **Date** | **Ver.** | **Author** | **Comment** |
38| | | | |
39+--------------------+--------------------+--------------------+--------------------+
wriderc1be4252019-11-26 10:13:54 -050040| 2019-11-25 | 0.1.0 |Lusheng Ji | First draft |
wriderbf0073e2019-11-03 14:35:07 -050041| | | | |
42+--------------------+--------------------+--------------------+--------------------+
43
44
wriderc1be4252019-11-26 10:13:54 -050045Overview
46========
wriderbf0073e2019-11-03 14:35:07 -050047
wriderc1be4252019-11-26 10:13:54 -050048The installation of Amber Near Realtime RAN Intelligent Controller is spread onto two separate
49Kubernetes clusters. The first cluster is used for deploying the Near Realtime RIC (platform and
50applications), and the other is for deploying other auxiliary functions. They are referred to as
51RIC cluster and AUX cluster respectively.
wriderbf0073e2019-11-03 14:35:07 -050052
wriderc1be4252019-11-26 10:13:54 -050053The following diagram depicts the installation architecture.
wriderbf0073e2019-11-03 14:35:07 -050054
wriderc1be4252019-11-26 10:13:54 -050055.. image:: images/nrtric-amber.png
56 :width: 600
57
58Within the RIC cluster, Kubernetes resources are deployed using three name spaces: ricinfra, ricplt, and ricxapp. Similarly, within the AUX cluster, Kubernetes resources are deployed using two name spaces: ricinfra, and ricaux.
59
60For each cluster, there is a Kong ingress controller that proxies incoming API calls into the cluster.
61With Kong, service APIs provided by Kubernetes resources can be accessed at the cluster node IP and
62port via a URL path. For cross-cluster communication, in addition to Kong, each Kubernetes namespace
63has a special Kubernetes service defined with endpoint pointing to the other cluster's Kong. This
64way any pod can access services exposed at the other cluster via the internal service hostname and port of
65this special service. The figure below illustrates the details of how Kong and external services work
66together to realize cross-cluster communication.
67
68.. image:: images/kong-extservice.png
69 :width: 600
wriderbf0073e2019-11-03 14:35:07 -050070
71
wriderc1be4252019-11-26 10:13:54 -050072VirtualBox VMs as Installation Hosts
73=======================================
wriderbf0073e2019-11-03 14:35:07 -050074
wriderc1be4252019-11-26 10:13:54 -050075The deployment of Amber Near Realtime RIC can be done on a wide range of hosts, including
76bare metal servers, OpenStack VMs, and VirtualBox VMs. This section provides detailed instructions
77for setting up Oracle VirtualBox VMs to be used as installation hosts.
wriderbf0073e2019-11-03 14:35:07 -050078
wriderc1be4252019-11-26 10:13:54 -050079.. include:: ./installation-virtualbox.rst
wriderbf0073e2019-11-03 14:35:07 -050080
81
82
wriderc1be4252019-11-26 10:13:54 -050083One-Node Kubernetes Cluster
84============================
85
86This sectioin descriibes how to set up a one-node Kubernetes cluster onto a VM installation host.
87
88.. include:: ./installation-k8s1node.rst
wriderbf0073e2019-11-03 14:35:07 -050089
90
wriderc1be4252019-11-26 10:13:54 -050091Installing Near Realtime RIC in RIC Cluster
92===========================================
wriderbf0073e2019-11-03 14:35:07 -050093
wriderc1be4252019-11-26 10:13:54 -050094After the Kubernetes cluster is installed, teh next step is to install the (Near Realtime) RIC Platform.
wriderbf0073e2019-11-03 14:35:07 -050095
wriderc1be4252019-11-26 10:13:54 -050096.. include:: ./installation-ric.rst
wriderbf0073e2019-11-03 14:35:07 -050097
98
wriderc1be4252019-11-26 10:13:54 -050099Installing Auxiliary Functions in AUX Cluster
100=============================================
wriderbf0073e2019-11-03 14:35:07 -0500101
wriderc1be4252019-11-26 10:13:54 -0500102.. include:: ./installation-aux.rst
wriderbf0073e2019-11-03 14:35:07 -0500103
wriderbf0073e2019-11-03 14:35:07 -0500104
wriderc1be4252019-11-26 10:13:54 -0500105Installing RIC Applications
106===========================================
107
108.. include:: ./installation-xapps.rst
109
110
wriderbf0073e2019-11-03 14:35:07 -0500111
112