Hello, here are the minutes of the weekly Kernel Projects meeting from today:
(06:52:50 CET) odl_meetbot: Minutes: http://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.html (06:52:50 CET) odl_meetbot: Minutes (text): http://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.txt (06:52:50 CET) odl_meetbot: Log: http://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html Tx, M. #opendaylight-meeting: kernel-weekly Meeting started by vorburger at 17:06:50 UTC (full logs <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html> ). Meeting summary 1. *NETCONF Test Tool removal* (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-5>, 17:07:45) 1. jmorvay asks if this tool can be removed (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-6>, 17:07:57) 2. jmorvay explains what this does.. testing tool is a NETCONF server which simulates like a switch or router (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-7>, 17:09:02) 3. it has an option when you start it to specific if you want to use the real MD-SAL data store or its local in-memory List (this is not the MD-SAL in-memory TestDataBroker) (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-10>, 17:10:29) 4. jmorvay propose to keep the md-sal backed one, but ditch that fake data store (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-11>, 17:11:32) 5. rovarga says that the fake data store is useful for performance testing netconf protocol (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-12>, 17:12:26) 6. vorburger suggests asking if using the MD-SAL in-memory TestDataBroker could be an option here; rovarga says no, because that's still too heavy (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-13>, 17:14:20) 7. jmorvay reason for wanting to remove it is maintenance burden, rovarga says not much maintenance is needed (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-14>, 17:15:09) 8. jmorvay reason was JAXB removal, rovarga says it's OK to keep it in the test tool (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-15>, 17:16:18) 9. https://github.com/opendaylight/netconf/tree/master/netconf/tools/netconf-testtool (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-16>, 17:18:49) 2. *YANG 1.1 action support in NETCONF* (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-17>, 17:20:43) 1. Martin Sandberg says Ericsson is looking for this, and has had some email exchange with jmorvay, there is a JIRA (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-18>, 17:21:30) 2. jmorvay <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/jmorvay> says there is some basic support but more work is needed, shouldn't be that hard for non-clustered, for clustering "also needs some proxy clustered services" (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-19>, 17:22:23) 3. https://git.opendaylight.org/gerrit/#/c/74745/ (jmorvay <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-20>, 17:24:09) 4. https://lists.opendaylight.org/pipermail/netconf-dev/ (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-22>, 17:26:52) 3. *Code Freeze in 2 days* (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-23>, 17:28:18) 1. skitt clarifies it's been moved from in 2 days to next week ( vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-24>, 17:28:36) 2. rovarga says distribution is currently broken, skitt merging netconf right now, and it should be OK after that (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-25>, 17:29:08) 3. TSC call on Thursday needs to discuss this (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-26>, 17:29:26) 4. rovarga says it should be OK tomorrow (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-27>, 17:30:06) 5. jmorvay says his netconf patches could wait for Sodium if he has to, rovarga says it would be great to still get it into Neon ( vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-28>, 17:31:22) 6. vorburger asks what the timeline and plan for branching and then opening master as Sodium will be (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-29>, 17:34:58) 7. rovarga says that there should be just 1 day of interruption, so we'll have stable/neon (for blockers only) and master open for Sodium the day after (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-30>, 17:36:12) 8. small request: if someone using multi-patch job in a regular basis can review this patch: (LuisGomez <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-31>, 17:36:50) 9. : https://git.opendaylight.org/gerrit/#/c/79586/ (LuisGomez <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-32>, 17:36:54) 10. the TSC call on Thursday needs to make the decision for the code freeze cut off, community majority will probably want to post pone in (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-33>, 17:36:54) 4. *Multi Patch Job* (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-37>, 17:38:19) 1. LuisGomez requesting skitt rovarga may be to review https://git.opendaylight.org/gerrit/#/c/79586/ (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-38>, 17:38:28) 5. *Attendees* (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-40>, 17:42:38) 1. vorburger skitt LuisGomez TomP rovarga Martin Sandberg jmorvay ( vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-41>, 17:43:06) 6. *Gerrit API* (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-42>, 17:43:19) 1. skitt asks for interest in a "bot" which could auto-merge jobs ( vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-51>, 17:46:57) 2. LuisGomez says this could be a project for an intern (but still needs someone to manage it) (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-52>, 17:47:13) 3. vorburger points to this opendaylight-bot, which never went this far (to actually "control" Gerrit via API), that was the dream ( vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-53>, 17:47:44) 4. vorburger says there are of course existing bot systems using in OpenStack and Kubernetes and elsewhere which perhaps could be re-used in OpenDaylight (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-54>, 17:48:12) 5. https://zuul-ci.org ? LuisGomez says LF already said No to this a while ago (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-55>, 17:50:07) 7. *Cookies* (vorburger <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html#l-56>, 17:52:44) Meeting ended at 17:52:50 UTC (full logs <https://meetings.opendaylight.org/opendaylight-meeting/2019/kernel_weekly/opendaylight-meeting-kernel_weekly.2019-01-22-17.06.log.html> ). Action items 1. (none) People present (lines said) 1. vorburger (39) 2. rovarga (9) 3. odl_meetbot (4) 4. jmorvay (2) 5. LuisGomez (2) 6. skitt (1) Generated by MeetBot <http://ci.openstack.org/meetbot.html> 0.1.4. -- Michael Vorburger, Red Hat vorbur...@redhat.com | IRC: vorburger @freenode | ~ = http://vorburger.ch
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
