======================================= #opendaylight-meeting: Karaf Meeting #1 ======================================= Meeting started by phrobb at 16:00:06 UTC. The full logs are available at http://meetings.opendaylight.org/opendaylight-meeting/2014/karaf_meeting__1/opendaylight-meeting-karaf_meeting__1.2014-07-23-16.00.log.html . Meeting summary --------------- * Each Project Contact please #info in with the project you are representing (phrobb, 16:00:35) * tbachman for Group Based Policy (tbachman, 16:01:07) * oflibMichal for openflowjava (oflibMichal, 16:01:24) * Thomas Kee for packetcable (xsited, 16:01:47) * Hideyuki for VTN (hideyuki, 16:01:53) * Lori Jakab for lispflowmapping (lori, 16:02:07) * Madhu for OVSDB (Madhu, 16:02:14) * Liem Nguyen for AAA (liemmn, 16:02:23) * Paul Zimmerman for ODL Docs (paulz, 16:02:26) * Andrew Grimberg for infrastructure (just in case...) (tykeal, 16:03:30) * ttkacik for YANGTools (ttkacik, 16:04:51) * abhijitkumbhare for OpenFlow plugin (abhijitkumbhare, 16:07:00) * Introduction to what is needed to support Karaf - Docs, tests, pkging, etc (phrobb, 16:08:29) * LINK: https://lists.opendaylight.org/pipermail/release/2014-July/000078.html it all starts here (Madhu, 16:08:46) * edwarnicke suggests us to move the wording of requirement -> recommendation in https://wiki.opendaylight.org/view/Simultaneous_Release:Helium_Release_Plan (Madhu, 16:10:26) * LINK: https://wiki.opendaylight.org/view/Runtime:Karaf_Features_Guidelines (edwarnicke, 16:11:39) * LINK: https://wiki.opendaylight.org/view/CrossProject:Helium_Release_Vehicle_Brainstorming:Pure_Karaf (Madhu, 16:12:21) * mlemay asks projects to either indicate whether or not they’d like his help in “karaf-ing” their project (tbachman, 16:12:55) * LINK: https://wiki.opendaylight.org/view/Simultaneous_Release:Helium_Release_Plan#Proposed_Release_Vehicles to indicate if the project will support Karaf for Helium (Madhu, 16:13:52) * edwarnicke suggests to provide both the feature dependency and the repo reference and it will help a great deal when the dependency tree grows . (Madhu, 16:18:14) * ACTION: edwarnicke will update the guidelines to describe how to properly setup features.xml in a way that transitive feature depenencies are handled easily :) (edwarnicke, 16:18:18) * LINK: https://wiki.opendaylight.org/view/Simultaneous_Release:Project_Expectations Project Expectations (Madhu, 16:21:07) * in order to understand what a project provides for the release (such as Features, documentation, etc...) project should provide a metafile as defined under https://wiki.opendaylight.org/view/Simultaneous_Release:Project_Expectations (Madhu, 16:25:26) * edwarnicke asks why we don’t specify conflicts and dependencies at the project level (tbachman, 16:28:55) * Madhu asks if this is a project level dependency or component level dependency (tbachman, 16:30:48) * mlemay says it’s really a maven dependency (tbachman, 16:30:57) * Madhu asks if this is purely for documentation, or also for packaging (tbachman, 16:31:32) * mlemay says it’s mainly for testing and documentation purpose (tbachman, 16:31:45) * mlemay confirms it is not a maven dependency :) this just negates tbachman assertion above (Madhu, 16:32:14) * in summary is a level of abstraction to uniformly obtain (programatically) what a project has to offer at a component level which can be used for uniform Documentation, Integration testing and for GUI (Madhu, 16:43:02) * LINK: https://wiki.opendaylight.org/view/Runtime:Karaf_Features_Guidelines Guidelines for creating and maintaining Apache Karaf feature files in each project (Madhu, 16:45:04) * mlemay asks that each project create a karaf feature.xml file. He can provide a skeleton that each project can start from, or mlemay offers to help build each project's feature file if need be. (phrobb, 16:49:47) * questions on standards for feature names… foo-features vs features-foo … we need a guideline so that everyone is consistent in their naming (phrobb, 16:51:51) * mlemay controller/features can be used as an example for others to follow (Madhu, 16:54:58) * LINK: https://wiki.opendaylight.org/view/Runtime:Karaf_Features_Guidelines#Feature_Best_Practices - updated with some additional guidelines (edwarnicke, 16:57:36) * ACTION: mlemay to provide a good example of a POM file for this Karaf work (phrobb, 17:01:42) * LINK: https://wiki.opendaylight.org/view/Runtime:Karaf_Features_Guidelines#Atomicity - updated to include advice on atomicity (edwarnicke, 17:08:07) * mlemay it is preferred to place it in projects root (Madhu, 17:08:12) Meeting ended at 17:09:20 UTC. Action items, by person ----------------------- * edwarnicke * edwarnicke will update the guidelines to describe how to properly setup features.xml in a way that transitive feature depenencies are handled easily :) People present (lines said) --------------------------- * Madhu (24) * tbachman (21) * edwarnicke (16) * phrobb (9) * odl_meetbot (5) * tykeal (2) * ChrisPriceAB (2) * hideyuki (2) * paulz (1) * oflibMichal (1) * xsited (1) * liemmn (1) * lori (1) * abhijitkumbhare (1) * ttkacik (1) Generated by `MeetBot`_ 0.1.4