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.
...
SMO deployment based on ONAP-Frankfurt-Release
Jira Legacy |
---|
server | System Jira |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 3122c0e4-6090-3a7d-9725-8b5a32a8eaeb |
---|
key | OAM-47 |
---|
|
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
Code Block |
---|
|
mkdir ~/workspace
cd ~/workspace
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/6 && git checkout FETCH_HEAD
# HEAD is now at 275f7de9 [SDNC] oom for clustered disaggregated SDN-R
sudo cp -R ~/workspace/oom_smo/kubernetes/helm/plugins/ ~/.helm |
- verifiy if local helm repo is available, otherwise follow intructions in onap setup
Code Block |
---|
|
helm repo list
#NAME URL
#stable https://kubernetes-charts.storage.googleapis.com
#local http://127.0.0.1:8879
|
- build local onap helm repo
Code Block |
---|
|
cd ~/workspace/oom_smo/kubernetes
make all; make onap
# take a coffee
helm search onap
|
- create an overwrite yaml file, e.g. deploy_smo_bronce.yaml
Code Block |
---|
|
cat ~/workspace/smo/deploy_smo_bronce.yaml
# Copyright © 2020 Amdocs, Bell Canada, highstreet technologies GmbH
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
###################################################################
# This override file enables helm charts for all ONAP applications.
###################################################################
global:
aafEnabled: false
masterPassword: Berlin1234!
cassandra:
enabled: false
mariadb-galera:
enabled: true
aaf:
enabled: false
aai:
enabled: false
appc:
enabled: false
clamp:
enabled: false
cli:
enabled: false
consul:
enabled: true
contrib:
enabled: false
dcaegen2:
enabled: true
dmaap:
enabled: true
esr:
enabled: false
log:
enabled: false
sniro-emulator:
enabled: false
oof:
enabled: false
msb:
enabled: true
multicloud:
enabled: false
nbi:
enabled: false
policy:
enabled: false
pomba:
enabled: false
portal:
enabled: false
robot:
enabled: false
sdc:
enabled: false
sdnc:
enabled: true
replicaCount: 1
config:
sdnr:
sdnrwt: true
sdnronly: true
sdnrmode: dm
mountpointRegistrarEnabled: true
mountpointStateProviderEnabled: true
cds:
enabled: false
dmaap-listener:
enabled: false
ueb-listener:
enabled: false
sdnc-portal:
enabled: false
sdnc-ansible-server:
enabled: false
dgbuilder:
enabled: false
sdnc-web:
enabled: false
so:
enabled: false
uui:
enabled: false
vfc:
enabled: false
vid:
enabled: false
vnfsdk:
enabled: false
modeling:
enabled: false
|
Code Block |
---|
|
helm -n dev-smo local/onap -f ~/workspace/smo/deploy_smo_bronce.yaml --namespace onap --timeout 900 |
- verifiy pnf-registration, fault notification use case, please find examples for sending VES message in gerrit.