1 # Service Management and Orchestration (SMO)
3 With respect to OAM the SMO implements the O1-interface provider. According to the O-RAN OAM Architecture and the O-RAN OAM Interface Specification, the SMO has a NetConf Client for configuration and HTTP/REST/VES Server for receiving all kind of events in a VES format.
5 The setup contains an OpenDaylight based NetConf client and a VES Test Collector.
9 This docker-compose file starts a pre-configured, self-contained SDN-R solution for developer test or demo purposes
11 * **SDN-R** single node instance
13 ... representing the NetConf consumer on the Service Management and Orchstration framework (SMO) for the O1 interface.
14 based on ODL-Sodium/ONAP-Guilin
18 ... representing the VES (REST) provider at SMO for all kind of events.
21 ... representing SMO DMaaP component, includes message-router
25 docker-compose file version 2.2 is used and tested with
28 * Docker version 19.03.x
29 * docker-compose version 1.24.x
31 * docker-compose for the solution
32 * enable git private docker registry, if used
37 docker-compose --version
40 git clone https://gerrit.o-ran-sc.org:29418/oam.git
41 cd ~/oam/solution/integration/smo
48 * Check (adjust if required) environment variables
51 cd ~/oam/solution/integration/smo
58 cd ~/oam/solution/integration/smo
62 ### Log files and karaf console
66 docker exec -it sdnr tail -f /opt/opendaylight/data/log/karaf.log
69 * karaf console access (karaf:karaf)
72 ssh karaf@localhost -p 8101
78 docker logs -f vescollector
81 ### Customizing Solution
83 '.env' file contains customizing parameters
86 ### Verification Solution
88 #### Access to SDN-R UX
91 http://<host_ip>:8181/odlux/index.html
93 Password:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U
96 ### Terminate solution
98 To stop all container:
101 cd ~/oam/solution/integration/smo
105 re-start solution at any point in time with
107 cd ~/oam/solution/integration/smo
114 !!! be careful if other stopped containers are on the same system
116 docker system prune -a -f