#opendaylight-meeting: tws

Meeting summary

1. agenda bashing (colindixon, 17:03:11)
   1. we have two topics for today: (1) cluster testing robot macros and (2) the YANG/Java binding spec v2 (colindixon, 17:03:12)
   
   
2. binding spec v2 (colindixon, 17:06:09)
   1. starts with what already exist since Helium. (adetalhouet, 17:08:04)
   2. YANG modeled data to respective Java Object structures and DTOs (compiled time & runtime) (adetalhouet, 17:08:35)
   3. Binding Spec v1 was introduces in Hydrogen, Binding Spec v2 started to emerge early Boron (adetalhouet, 17:09:15)
   4. Decision was to start from scratch for the Binding Spec v2 (adetalhouet, 17:09:46)
   5. the binding v2 spec is done, but the implementation is still in process (colindixon, 17:10:31)
   6. https://gist.github.com/tonydamage/82b15f0cd1f39b729d4e binding v2 spec (colindixon, 17:11:16)
   7. some of the goals of the v2 spec are bugs from v1 spec (colindixon, 17:13:16)
   8. https://gist.github.com/tonydamage/82b15f0cd1f39b729d4e#known-problems-of-binding-specification-v1 this has links to teh bugs from the v1 spec (colindixon, 17:13:43)
   9. one example is that YANG has 5 namespaes for different types, but they're mapped onto one namepace in java, so you have to fix that, e.g., a grouping, vs. a container, vs. ... (colindixon, 17:17:52)
   10. colindixon asks why we are thinking of using pakcage names for that instead of using the class name, e.g., org.opendaylight.yang.grouping.Example vs. org.opendaylight.yang.ExampleGrouping (colindixon, 17:18:36)
   11. rovarga says at least one reason is that YANG names are freeform, so you could have example and example-grouping both being types (colindixon, 17:19:29)
   12. https://github.com/opendaylight/mdsal/blob/master/binding2/mdsal-binding2-spec/src/site/asciidoc/binding-2.adoc binding spec v2 docs (colindixon, 17:21:44)
   13. note the above doesn't have the images linked appropropately, but the recording does (colindixon, 17:23:30)
   14. there's an example with a a bunch fo foos, indentifiers, and unions showing how type names are mapped in a combination of package names and class names (colindixon, 17:25:50)
   15. colindixon asks what happens if you have two modules with the grouping simple, answer is that the package names here aren't complete and in the future you will have to have the module namespace as part of the package name as well (colindixon, 17:29:05)
   16. colindixon asks when classes get a suffix, e.g., data.top.Foo vs. grp.simple.FooData (colindixon, 17:31:13)
   17. the answer seems to be that if you are a "foreign" type, e.g., if you're data in the grp namespace (colindixon, 17:32:06)
   18. in part, this is because the intantiation of a grouping is different from the grouping itself in v2, this fixes the semantics of augmentation (colindixon, 17:34:13)
   19. vishnoianil asks if we have examples in code, martin says some of that exists (colindixon, 17:45:01)
   20. vishnoianil asks if there's an impact analayis, martin and rovarga say that v1 and v2 can coexist, so that there should be no impact, but projects will be generally expected to move from v1 to v2 over time (colindixon, 17:47:01)
   21. vishnoianil asks what if people depend on projects that use v2, will they have to move, the answer is no because you go through binding independent DTOs which are the unerlying common element between v1 and v2 (colindixon, 17:48:45)
   22. you could make an RPC call from v2 to a provider using v1 and it should just work (colindixon, 17:49:00)
   23. colindixon encourages other people to go look at this (colindixon, 17:49:34)
   
   
3. cluster testing robot macros (colindixon, 17:50:15)
   1. we started cluster testing in the past, but we didn't have a set of simple, clear, generic resources (colindixon, 17:53:06)
   2. http://docs.opendaylight.org/en/latest/_static/integration/robot/ClusterManagement.robot.html docs (colindixon, 17:53:43)
   3. luis goes over the keywords (colindixon, 17:54:14)
   4. keywords are 5 bins: (1) shard setup, (2) shard state, (3) entity owner, (4) cluster member operations, (5) rest operations (colindixon, 17:56:08)
   5. for those watching the webex recording, the cluster testing starts around 44 minutes in the recording (colindixon, 17:57:40)
   6. luis shows a bunch of exampel tests that already use the cluster management keywords (colindixon, 17:59:32)
   7. this includes bgpcep, controller, netconf, netvirt, openflowplugin, ovsdb, ... (colindixon, 17:59:55)
   8. luis thanks vrpolak and a few others for all their help (colindixon, 18:00:50)

Action items

1. (none)

People present (lines said)

1. colindixon (51)
2. rovarga (6)
3. adetalhouet (4)
4. odl_meetbot (3)