Status: 2020-05-25 - under development
The minimum SMO deployment for O-RAN-SC Bronze Health-Check use case requires the following ONAP components:
- DMaaP
- DCAE standard VES Collector
- CCSDK/SDNC with enabled wireless technology applications
The deployment bases ONAP OOM functions and Kubernetes.
In order to address ONAP integration findings from Frankfurt release, it is recommended to use the master ONAP master branch for OOM and SDNC components.
- https://gerrit.onap.org/r/admin/repos/oom
- https://gerrit.onap.org/r/admin/repos/ccsdk/features
- https://gerrit.onap.org/r/admin/repos/dcaegen2/collectors/ves
- https://gerrit.onap.org/r/admin/repos/dmaap/messagerouter/msgrtr
- https://gerrit.onap.org/r/admin/repos/aaf
- https://gerrit.onap.org/r/admin/repos/logging-analytics/pomba/pomba-sdnc-context-builder
SMO deployment based on ONAP-Frankfurt-Release
This procedure provides:
- ONAP-DCAE
- ONAP-DMaaP
- ONAP-SDNC (single node, SMO functionality)
Limitations (wip):
- AAF: not yet supported
- ONAP-SDNC OOM deployment not yet on master branch.
Prerequisites:
- kubernetes cluster (1.13.5)
- helm installation (2.16.x)
- More details: setup cloud environment(openstack/kubernetes) https://docs.onap.org/en/elalto/guides/onap-developer/settingup/index.html
Setup
- clone oom repo from gerrit.onap.org
- fetch patchset for ONAP-SDNC
git clone -b frankfurt http://gerrit.onap.org/r/oom --recurse-submodules oom_smo cd oom_smo git fetch "https://gerrit.onap.org/r/oom" refs/changes/31/106331/4 && git checkout FETCH_HEAD # HEAD is now at 275f7de9 [SDNC] oom for clustered disaggregated SDN-R
- verifiy if local helm repo is available, otherwise follow intructions in onap setup
helm repo list #NAME URL #stable https://kubernetes-charts.storage.googleapis.com #local http://127.0.0.1:8879
- build local onap helm repo
cd oom_smo/kubernetes make all; make onap # take a coffee helm search onap