No evidence found in that file for openflow being started. I generate the archetype version 1.5.2 and my karaf version is 4.1.5.
I stripped the problem down to the essentials and I am able to reproduce the problem as follows: 1. Generate the archetype : mvn archetype:generate -DarchetypeGroupId=org.opendaylight.controller -DarchetypeArtifactId=opendaylight-startup-archetype -DarchetypeRepository= https://nexus.opendaylight.org/content/repositories/opendaylight.release/ -DarchetypeCatalog=remote -DarchetypeVersion=1.5.2 2. Edit the features/odl-baseapp/pom.xml and add just the following dependency: <dependencies> ...... <dependency> <groupId>org.opendaylight.openflowplugin</groupId> <artifactId>odl-openflowplugin-southbound</artifactId> <type>xml</type> <classifier>features</classifier> <version>0.6.2</version> </dependency> </dependencies> After I build and start karaf ( *Note that I have not started my feature yet* ) I see the following: feature:list | grep openflow odl-openflowplugin-libraries │ 0.6.2 │ │ Started │ odl-openflowplugin-libraries │ OpenDaylight :: Openflow Plugin :: Libraries odl-openflowplugin-nsf-model │ 0.6.2 │ │ Started │ odl-openflowplugin-nsf-model │ OpenDaylight :: OpenflowPlugin :: NSF :: Model odl-openflowjava-protocol │ 0.6.2 │ │ Started │ odl-openflowjava-0.6.2 │ ODL :: openflowjava :: odl-openflowjava-protocol odl-openflowplugin-southbound │ 0.6.2 │ │ Started │ openflowplugin-0.6.2 │ OpenDaylight :: Openflow Plugin :: Li southbound I can netstat and see that 6653 is being used. Now I go to start my feature: feature:install features-baseapp And I can no more see 6653 in my netstat. Note that I have added no code. This is just a skeleton. I wonder if I am editing the right file. Should I be adding the openflow dependency to features/odl-baseapp/pom.xml or elsewhere? Is this a bug report that I should file ( under which component ? ) Thanks a lot for your help. Regards, Ranga On Sat, Aug 4, 2018 at 11:30 PM, Luis Gomez <[email protected]> wrote: > Not sure which distribution you are using but you can check > etc/org.apache.karaf.features.cfg to see what is being installed when you > start it. > > On Aug 4, 2018, at 7:06 PM, M. Ranganathan <[email protected]> wrote: > > Still no luck. Here is my list of openflow features (after the change you > suggested ): > > odl-openflowplugin-app-forwardingrules-manager │ 0.6.2 > │ │ Started │ odl-openflowplugin-app-forwardingrules-manager > │ OpenDaylight :: Openflow Plugin :: Application - > odl-openflowplugin-libraries │ 0.6.2 > │ │ Started │ odl-openflowplugin-libraries > │ OpenDaylight :: Openflow Plugin :: Libraries > odl-openflowplugin-app-config-pusher │ 0.6.2 > │ │ Started │ odl-openflowplugin-app-config-pusher > │ OpenDaylight :: Openflow Plugin :: Application - > odl-openflowplugin-nsf-model │ 0.6.2 > │ │ Started │ odl-openflowplugin-nsf-model > │ OpenDaylight :: OpenflowPlugin :: NSF :: Model > odl-openflowjava-protocol │ 0.6.2 > │ │ Started │ odl-openflowjava-0.6.2 > │ ODL :: openflowjava :: odl-openflowjava-protocol > odl-openflowplugin-app-topology │ 0.6.2 > │ │ Started │ odl-openflowplugin-app-topology > │ OpenDaylight :: Openflow Plugin :: Application - > odl-openflowplugin-flow-services │ 0.6.2 > │ │ Started │ odl-openflowplugin-flow-services > │ OpenDaylight :: Openflow Plugin :: Flow Services > odl-openflowplugin-southbound │ 0.6.2 > │ │ Started │ openflowplugin-0.6.2 > │ OpenDaylight :: Openflow Plugin :: Li southbound > odl-openflowplugin-app-reconciliation-framework │ 0.6.2 > │ │ Started │ odl-openflowplugin-app-reconciliation-framework > │ OpenDaylight :: Openflow Plugin :: Application - > > > I still don't understand one thing -- why is the port being used BEFORE I > start my application? > > It appears that the openflow features are already running when the > container is started. Indeed when I do a feature list BEFORE starting my > own feature I get the SAME list as above. (i.e. the features are in the > started state already). > > This is different from my previous version (i.e. Nitrogen ) where these > features where listed in an Uninstalled state. > > Thanks, > > Ranga > > On Sat, Aug 4, 2018 at 7:42 PM, Luis Gomez <[email protected]> wrote: > >> This dependency breaks your feature: >> >> <dependency> >> <groupId>org.opendaylight.openflowplugin</groupId> >> <artifactId>features-openflowplugin</artifactId> >> <type>xml</type> >> <classifier>features</classifier> >> </dependency> >> >> >> With the above you are installing all features available in >> openflowplugin and some of them are not compatible with each other, so >> instead of bringing the full repo just bring one by one the features >> (odl-openflowplugin-*) that you need, for example: >> >> <dependency> >> <groupId>org.opendaylight.openflowplugin</groupId> >> <artifactId>odl-openflowplugin-southbound</artifactId> >> <type>xml</type> >> <classifier>features</classifier> >> </dependency> >> >> BR/Luis >> >> > On Aug 4, 2018, at 3:41 PM, M. Ranganathan <[email protected]> wrote: >> > >> > <pom.xml> >> >> > > > -- > M. Ranganathan > > > -- M. Ranganathan
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
