#opendaylight-meeting: kernel projects

Meeting started by colindixon at 16:05:26 UTC (full logs).

Meeting summary

  1. agenda bashing (colindixon, 16:05:34)
    1. https://wiki.opendaylight.org/view/Kernel_Projects_Call#Upcoming_Agenda_Topics schedule (colindixon, 16:05:59)
    2. https://git.opendaylight.org/gerrit/#/c/46534/ it seems like adding put/merge variants was given up on because there's going to be a new way of working with the MD-SAL anyway (colindixon, 16:08:32)
    3. colindixon asks if there's a really much that will change that it makes sense to hold off (colindixon, 16:11:19)
    4. rovarga says that at the current time binding v1 and binding v2 are going to have totally different data brokers, so they won't be mixed (colindixon, 16:12:56)
    5. rovarga points out that by going through the binding independent data store in the back a binding v1 and binding v2 application can talk to each other just fine (colindixon, 16:13:35)
    6. vorburger asks if the plan is to just have each jar be either v1 or v2, but not both, but the overall system will be a mix (colindixon, 16:15:03)
    7. rovarga notes that for bundles that have a YANG file, they need to generate both v1 and v2 code generated (colindixon, 16:15:27)
    8. rovarga says that the two binding implementations don't overlap, so techincally, you could use both in an app, it would just suck (colindixon, 16:19:08)
    9. as we add more bindings, we need to figure out where they're generated, does each jar with a YANG model in it come with binding v1, v2 and maybe scala? that's overhead, but maybe tolerable. (colindixon, 16:20:10)
    10. rovarga says that it might be better to package individual bidings or generate the bindings as poms import it (colindixon, 16:20:35)
    11. rovarga notes that you need both the binding and the model to be imported at the end (colindixon, 16:21:13)
    12. rovarga draws a diagram showing how we will translate all bindings through the DOM (binding independent) layer to translate from one binding to another (colindixon, 16:26:55)
    13. vorburger says that at this point, he doesn't have the bandwidth to push this ball and fight for new put/merge variants right now (colindixon, 16:28:30)

  2. carbon milestones (colindixon, 16:31:39)
    1. all kernel projects got M0 milestones in (colindixon, 16:31:50)
    2. offest 0 (kernel) projects need to get M1 milestones are due Thursday (colindixon, 16:33:08)

  3. Eclipse integeration (colindixon, 16:33:19)
    1. vorburger says that as it stands when he uses Eclipse with our builds bad things happen, espeically if you do both at the same time (colindixon, 16:34:00)
    2. vorburger says that he's seen CLI builds fail because Eclipse happened to be open (colindixon, 16:34:41)
    3. vorburger says changing it so that we have two different target directories, one for Eclipse (or other IDEs) and another for the CLI builds would seem to fix this (colindixon, 16:35:12)
    4. rovarga says that in the past we had problems keeping this working, because (among other things) projects and/or plugins didn't obey the custom target directory (colindixon, 16:36:41)
    5. rovarga and vorburger say that we have a much, much cleaner build system now and so we might attack this again (colindixon, 16:37:08)
    6. colindixon adds that his experience was that we had enough issues with developers that don't use eclipse that you are constantly plugging holes to keep things working with Eclipse (colindixon, 16:41:46)
    7. there is a lot of conversation about how you do maven build plugin stuff in Eclipse using oomph to fix the issues that colindixon was talking about above (colindixon, 16:44:19)
    8. ACTION: vorburger and rovarga to talk about how to manage oomph plugins and Eclipse builds over e-mail (colindixon, 16:46:20)

  4. YANG 1.1 meeting (colindixon, 16:47:43)
    1. monday at 9a EST we have the YANG 1.1 meeting (colindixon, 16:48:14)
    2. a WebEx link will come up (colindixon, 16:48:30)

  5. we need projects to address Beryllium-SR4 test failures (colindixon, 16:49:09)
    1. AAA and bppcep failures are the ones of interest to people here (colindixon, 16:49:31)
    2. ACTION: rgoulding to look into AAA (colindixon, 16:49:44)

  6. security audit (colindixon, 16:50:18)
    1. rgoulding asks if we've had anyone do any security audits (colindixon, 16:50:41)
    2. currently we try to blacklist known-weak cyphers, but we found some projects using non-standard cyphers (colindixon, 16:51:03)
    3. rovarga says that we really need a crypto best practices page for OpenDaylight (colindixon, 16:51:45)
    4. rovarga also says that we should have some kind of periodic review (colindixon, 16:51:54)
    5. ACTION: rgoulding will start creating that best practices around crypto pages (colindixon, 16:52:52)
    6. rovarga looks around for crypto stuff that's non-standard; he finds openflowjava has a keystore that's a flat file, and a some kind of TLS configuration that's non-standard (colindixon, 16:55:03)

  7. apache mina and sshd-core upgrades (colindixon, 16:56:41)
    1. mina is bundled with karaf's classpath (rovarga, 16:57:45)
    2. (mina-ssh) (rovarga, 16:57:51)
    3. skitt and rovarga say that the patch upgrade these things broke things, it seems like karaf 4.0 will fix it (colindixon, 16:57:59)
    4. so we have to upgrade karaf to 4.0.x at the very least (rovarga, 16:58:08)
    5. otherwise things break (caused by the fact a version is on the JVM system classpath not as a bundle) (rovarga, 16:58:40)
    6. ACTION: skitt to add rgoulding as a reviewer for the Karaf-4 parent patch when he pushes it (colindixon, 16:58:52)
    7. we actually are ready to roll in netconf for mina-ssh 1.2.0 (rovarga, 16:59:05)


Meeting ended at 16:59:57 UTC (full logs).

Action items

  1. vorburger and rovarga to talk about how to manage oomph plugins and Eclipse builds over e-mail
  2. rgoulding to look into AAA
  3. rgoulding will start creating that best practices around crypto pages
  4. skitt to add rgoulding as a reviewer for the Karaf-4 parent patch when he pushes it


Action items, by person

  1. rgoulding
    1. rgoulding to look into AAA
    2. rgoulding will start creating that best practices around crypto pages
    3. skitt to add rgoulding as a reviewer for the Karaf-4 parent patch when he pushes it
  2. rovarga
    1. vorburger and rovarga to talk about how to manage oomph plugins and Eclipse builds over e-mail


People present (lines said)

  1. colindixon (44)
  2. rovarga (5)
  3. odl_meetbot (3)
  4. rgoulding (1)


Generated by MeetBot 0.1.4.