Denis,

all you need for an OVSDB connection is the odl-ovsdb-southbound-impl. In that case you can point a ovsdb node to ODL via ovs-vsctl set manager and ODL will track it. If you wan the restconf component then you use the odl-ovsdb-southbound-impl-ui (which includes odl-ovsdb-southbound-impl) and you can also issue restconf calls to create the connections and query the model.

There have been issues where certain models start at different times and it causes issues for dependent models. You might be hitting that case. In my first test of the lithium release to just install the odl-ovsdb-southbound-impl feature there was an exception listed on the console converning models and the listening port was not opened. A second test it worked fine. So it's possible you might be hitting that.

The karaf logs should have the following if everything worked correctly:

2015-07-24 11:01:03,677 | INFO | config-pusher | SouthboundProvider | 184 - org.opendaylight.ovsdb.southbound-impl - 1.1.0.Lithium | SouthboundProvider Session Initiated
2015-07-24 11:01:03,683 | INFO | config-pusher | OvsdbDataChangeListener | 184 - org.opendaylight.ovsdb.southbound-impl - 1.1.0.Lithium | Registering OvsdbNodeDataChangeListener
2015-07-24 11:01:03,816 | INFO | entLoopGroup-5-1 | LoggingHandler | 119 - io.netty.common - 4.0.26.Final | [id: 0x8e720879] REGISTERED
2015-07-24 11:01:03,816 | INFO | entLoopGroup-5-1 | LoggingHandler | 119 - io.netty.common - 4.0.26.Final | [id: 0x8e720879] BIND(0.0.0.0/0.0.0.0:6640)