These are the docker image versions used by the SMO project for F-Release.

Component Name	Image	Functional description
smo-collector	nexus3.o-ran-sc.org:10004/smo-collector:5.0.1	The SMO collector acts as the collector of events that are sent to the SMO. It receives the events and validates them against well known schemas before writing the event to the SMO Kafka bus. No specific implementation for F-Release.
smo-influxdb	influxdb:1.8.5	The SMO uses a standard distribution of Influx dB to store all events. No specific implementation for F-Release.
smo-grafana	grafana/grafana:7.5.11	The SMO uses a standard distribution of Grafana dashboard to display events received and sinked to the Kafka bus. No specific implementation for F-Release.
smo-zookeeper	confluentinc/cp-zookeeper:5.5.6	The SMO uses a standard distribution of zookeeper to manage the Kafka bus. No specific implementation for F-Release.
smo-kafka	confluentinc/cp-kafka:5.5.6	The SMO uses a standard distribution of the Kafka bus to act as the message bus on the SMO. No specific implementation for F-Release.
smo-kafdrop	obsidiandynamics/kafdrop:3.27.0	The SMO uses a standard distribution of Kafdrop to manage the Kafka bus. No specific implementation for F-Release.
smo-dmaap-adapter	nexus3.o-ran-sc.org:10004/smo-collector:5.0.1	The SMO DMaaP adapter converts events that are written to Kafka bus to DMaaP events when requested. No specific implementation for F-release
smo-influxdb-connector	nexus3.o-ran-sc.org:10004/smo-influxdb-connector:5.0.1	The SMO Influx dB connector is what the name states it to be. It is a connector between Kafka bus and Influx dB, such that events written to Kafka bus are saved into Influx dB. No specific implementation for F-release
smo-post-config	nexus3.o-ran-sc.org:10004/smo-post-config:5.0.1	The SMO post config container takes care of operations after all the containers are installed, and connecting them together. No specific implementation for F-release