Re: feature required for ovsdb connection

Baudinot Denis Gerold (badi) <badi@...>

Thank you Sam

I think there is a fundamental difference in our setups. I generated an archetype based on this:

And then I subsequently added dependencies and features as I required them.

Also I actually never get info from the "config-pusher" in my karaf.log. Instead I get an exception some time after I started karaf.

Exception in thread "config-pusher" java.lang.SecurityException: Insufficient roles/credentials for operation
at com.sun.proxy.$Proxy0.invoke(Unknown Source)
at com.sun.jmx.mbeanserver.MXBeanProxy$InvokeHandler.invoke(
at com.sun.jmx.mbeanserver.MXBeanProxy.invoke(
at com.sun.proxy.$Proxy15.beginConfig(Unknown Source)
at org.opendaylight.controller.config.util.ConfigRegistryJMXClient.beginConfig(
at org.opendaylight.controller.netconf.confignetconfconnector.transactions.TransactionProvider.getTestTransaction(
at org.opendaylight.controller.netconf.confignetconfconnector.operations.editconfig.EditConfig.test(
at org.opendaylight.controller.netconf.confignetconfconnector.operations.editconfig.EditConfig.executeTests(
at org.opendaylight.controller.netconf.confignetconfconnector.operations.editconfig.EditConfig.getResponseInternal(
at org.opendaylight.controller.netconf.confignetconfconnector.operations.editconfig.EditConfig.handleWithNoSubsequentOperations(
at org.opendaylight.controller.netconf.util.mapping.AbstractLastNetconfOperation.handle(
at org.opendaylight.controller.netconf.util.mapping.AbstractNetconfOperation.handle(
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.sendRequestGetResponseCheckIsOK(
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.pushConfig(
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.pushConfigWithConflictingVersionRetries(
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.internalPushConfigs(
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.process(
at org.opendaylight.controller.netconf.persist.impl.osgi.ConfigPersisterActivator$InnerCustomizer$

I didn't find an explanation for this yet

Von: Sam Hague [shague@...]
Gesendet: Freitag, 24. Juli 2015 17:09
An: Baudinot Denis Gerold (badi)
Cc: ovsdb-dev@...
Betreff: Re: [ovsdb-dev] feature required for ovsdb connection


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(

----- Original Message -----
From: "Baudinot Denis Gerold (badi)" <badi@...>
To: ovsdb-dev@...
Sent: Friday, July 24, 2015 10:24:41 AM
Subject: [ovsdb-dev] feature required for ovsdb connection


What I'am trying to figure out is which feature of ovsdb do I *need* to
install for establishing a n ovsdb connection.

Taking odl-ovsdb-openstack as an example: It requires only
odl-ovsdb-southbound-impl-ui as a feature from ovsdb (except netvirt bundles
which I assume are not responsible for this).

After installing the odl-ovsdb-southbound-impl-ui feature I checked if
something is listening to :6640 because OVS was not able to connect (via
set-manager) there. And apparently nothing is indeed listeing to that port.

What am I missing here?

Regards & Thanks

ovsdb-dev mailing list

Join to automatically receive all group messages.