- OS: Ubuntu 18.04 LTS (Bionic Beaver)
- CPU(s): 8
- RAM: 32 GB
- Storage: 160 GB
NOTE: sudo access is required for installation
Getting Started PDF
NOTE: cd to your directory where installation will be, i.e. /home/user
Run ...
$ sudo -i
$ git clone http://gerrit.o-ran-sc.org/r/it/dep -b bronze
$ cd dep
$ git submodule update --init --recursive --remote
This step will generate a script that will set up a one-node Kubernetes cluster for installing the SMO components. The resultant script can run as the cloud-init script when launching the VM, or run at a root shell after the VM is launched.
Note, because the O-RAN SC Bronze SMO consists components from ONAP Frankfurt release, the infrastructure software stack (Docker, Kubernetes, and Helm) versions are as required by the ONAP deployment. It is a different combination compared to what the Near RT RIC requires.
Run ...
$ cd tools/k8s/etc# edit the infra.rc file to specify the versions of docker, kubernetes, and helm.
# For SMO, the versions are as required by the ONAP Frankfurt release.
# Comment out the lines below the heading of "RIC tested"; and un-comment
# the lines following the heading of "ONAP Frankfurt"
$ cd ../bin
$ ./gen-cloud-init.sh # will generate the stack install script for what RIC needs
# The outputted script is will be used for preparing K8 cluster for RIC to deploy
# to file is "k8s-1node-cloud-init-k_1_15-h_2_16-d_18_09.sh"
Run ...
$ ./k8s-1node-cloud-init-k_1_15-h_2_16-d_18_09.sh
NOTE: Be patient as this takes some time to complete. Upon completion of this script, the VM will be rebooted. You will then need to login once again.
$ sudo -i
$ kubectl get pods --all-namespaces # There should be 9 pods running in kube-system namespace.
O-RAN Bronze SMO consists of components from three separate groups: ONAP, Non RT RIC, and RIC-AUX. It is deployed by running a script under smo/bin.
Run ...
$ cd smo/bin$ ./install
# If this is the first time SMO is installed on the SMO VM, it suggested to run "./install initlocalrepo" instead.
# The extra argument also initializes the local Helm repo.
# Also if this is the first time SMO is installed on the SMO VM, because it involves the preparation of the ONAP
# helm charts, the instillation may take hours to finish. It is suggested to run the install as a nohup command
# in background, just in case connection to the VM is interrupted.
# Upon successful deployment, the "kubectl get pods --all-namespaces" command should show 8 pods in nonrtric
# namespace, 27 pods/jobs in onap namespace, and 2 pods in ricaux name space, all in Running or Completed state.
Kubectl commads:
kubectl get pods -n nampespace - gets a list of Pods running
kubectl get logs -n namespace name_of_running_pod
Complete these tasks to get started
Recent space activity
Recently Updated | ||||||||
---|---|---|---|---|---|---|---|---|
|
Space contributors
Contributors | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|