#opendaylight-meeting: md_sal_interest_call

Meeting summary

1. Abstract Data Broker Testing (tbachman, 16:19:24)
   1. https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Testing page describing testing for MD-SAL (tbachman, 16:20:03)
   2. The AbstractDataBrokerTest instantiates the binding broker, dom broker and datastore (tbachman, 16:20:36)
   3. devinavery has used this for writing into the store with his own yang model, but there are some specific issues (tbachman, 16:20:57)
   4. sal-binding-it, sal-test-model, sal-binding-broker-impl dependencies were all needed, along with guava (tbachman, 16:25:06)
   5. There may be dependencies on yang-data-api, yang-binding, etc., depending on what you’re doing (tbachman, 16:25:29)
   6. This makes it very easy to test interaction using a mock datastore (tbachman, 16:25:43)
   7. ACTION: devinavery will push a gerrit showing his test soon (tbachman, 16:26:04)
   
   
2. karaf (tbachman, 16:27:39)
   1. https://wiki.opendaylight.org/view/Karaf:Step_by_Step_Guide guide to go from nothing to a karaf’d project (tbachman, 16:28:31)
   2. there’s a maven archetype for creating features (tbachman, 16:28:52)
   3. Is a karaf feature the equivalent of a plugin (tbachman, 16:31:08)
   4. edwarnicke says not necessarily (tbachman, 16:31:14)
   5. there’s a single command to run the archetype (tbachman, 16:33:12)
   6. the wiki covers some of the common failure cases that you may encounter (tbachman, 16:34:49)
   7. as well as exceptions that can be ignored (tbachman, 16:35:03)
   8. edwarnicke says that the way you want to test this is to delete your local .m2 and then run mvn clean install (tbachman, 16:37:07)
   9. in order to make sure that you’re not picking up something from your local .m2 (tbachman, 16:37:20)
   10. karaf allows users to select the features that they want, rather than having to worry about coming up with release artifacts/editions (tbachman, 16:44:44)
   11. installing features may result in other features being installed (tbachman, 16:50:21)
   12. question as to whether ODL will always require configuration to run (tbachman, 16:51:16)
   13. edwarnicke says this can be different for internal vs. external use (tbachman, 16:51:31)
   14. internally, you can add the things you want to the boot features (tbachman, 16:51:48)
   15. georgez asks if every project has to define their own features (tbachman, 16:52:24)
   16. edwarnicke says yes (tbachman, 16:52:27)
   17. georgez points out that dependent features need to be ready in order to use them. edwarnicke wants project to tell georgez if they are blocked by another project’s readiness (tbachman, 16:54:27)
   18. edwarnicke makes strong point - please don't use custom start levels as that can cause issues for everyone. (devinavery, 16:56:56)
   19. there is karaf happy hour this week @ 7:30 AM PST where you can come and get your karaf questions answered. (devinavery, 16:59:09)

Action items

1. devinavery will push a gerrit showing his test soon

Action items, by person

1. devinavery
   1. devinavery will push a gerrit showing his test soon

People present (lines said)

1. tbachman (35)
2. devinavery (8)
3. odl_meetbot (4)