## Introduction
With respect to Operation and Maintenance (OAM) the SMO implements the O1-interface and OpenFronthaul Management-Plane consumers.
-According to the O-RAN OAM Architecture and the O-RAN OAM Interface Specification, the SMO implements a NETCONF Client for configuration
-and a HTTP/REST/VES server for receiving all kind of events in
-VES format.
+According to the O-RAN OAM Architecture and the O-RAN OAM Interface Specification, the SMO implements a NETCONF Client for configuration
+and a HTTP/REST/VES server for receiving all kind of events in VES format.
The O-RAN-SC OAM deployment contains an OpenDaylight based NETCONF client and an ONAP VES Collector. Kafka is used as massage router for communication between the components. The Keycloak implementation offers and Identity service, while traefik acts as reverse proxy to terminate all incoming https traffic. For storing data in a persistence way the implementation of the mariaDB project is used.
+Before you start please think about a nice full qualified domain name of your environment. Your DNS or /etc/hosts settings needs to be updated.
+Here an inspiration: smo.dev.o-ran-sc.<your-organization>.com
+
## SMO OAM Components
This docker-compose file starts a pre-configured, self-contained SDN-R solution
Docker Compose version v2.32.4
```
+In case your environment acts behind a proxy, please see related docker documentations:
+
+https://docs.docker.com/engine/daemon/proxy/
+
+
### GIT
```