What is the difference between odl-baseapp ( part of my application ) which is started up on karaf startup and features-baseapp ( which is NOT started up on karaf startup) ?
I notice that odl-baseapp and all its dependencies is running when I do karaf clean and list my features whereas features-baseapp is not installed. Then when I go to install features-baseapp, the problem with the port (described above happens). It seems to start fine but it freezes the openflow plugin because it has already been started. I *used* to feature:install features-baseapp when I was using Nitrogen but now it appears I must not install features-baseapp or there will be an issue with opeflow. Indeed, under nitrogen, I was seeing all the openflow bundles uninstalled and they would be installed and started when I start my feature but this has changed. So what is the difference between these two and am I doing something wrong? Is this a bug or expected behavior? If it is a bug then I'd like to bring it to the attention of somebody or file a report so please direct me there (If this is not openflow-dev relevant then please excuse the number of mails on this and let me know where I can post this). I am still learning about the system ( page faulting the gaps in my knowledge in -- a very painful process ) so please excuse the ignorance. Thank you for your help. On Sun, Aug 5, 2018 at 8:08 AM, M. Ranganathan <mra...@gmail.com> wrote: > 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 <ece...@gmail.com> 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 <mra...@gmail.com> 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 <ece...@gmail.com> 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 <mra...@gmail.com> wrote: >>> > >>> > <pom.xml> >>> >>> >> >> >> -- >> M. Ranganathan >> >> >> > > > -- > M. Ranganathan > > -- M. Ranganathan
_______________________________________________ openflowplugin-dev mailing list openflowplugin-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
