15:00:01 <phrobb> #startmeeting M1/M2 Cross Project Mtg
15:00:01 <odl_meetbot> Meeting started Wed Jan 21 15:00:01 2015 UTC.  The chair is phrobb. Information about MeetBot at http://ci.openstack.org/meetbot.html.
15:00:01 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:01 <odl_meetbot> The meeting name has been set to 'm1_m2_cross_project_mtg'
15:00:15 <tbachman> #info tbachman for groupbasedpolicy
15:00:18 <phrobb> #topic roll call - Project Leaders and TSC Members please #info in
15:00:29 <regXboi> #info regXboi (TSC member)
15:00:45 <phrobb> #chair tbachman gzhao regXboi
15:00:45 <odl_meetbot> Current chairs: gzhao phrobb regXboi tbachman
15:00:54 <tbachman> :)
15:01:00 <phrobb> Welcome and good morning everyone
15:01:05 <tbachman> phrobb: welcome!
15:01:31 <shague> #info shague ovsdb
15:01:33 <oflibMichal> #info oflibMichal for openflowjava and topoprocessing
15:01:35 <ebrjohn> #info ebrjohn Brady Johnson, SFC project lead
15:01:53 <lori> #info lori lispflowmapping
15:02:05 <sdean778> #info Steve Dean, DIDM and SNMP Plugin projects
15:02:11 <yuling> #info yuling for tsdr
15:02:15 <Fabiel> #info Fabiel for Persistence Data Store
15:02:38 <ttkacik1> #info ttkacik1 controller
15:03:06 <LuisGomez> #info LuisGomez integration
15:03:16 <tbachman> LuisGomez: thx for your help yesterday, btw!
15:03:21 <tbachman> (last night, that is)
15:04:15 <Prem> #info Prem vpnservice
15:04:30 <phrobb> last call for Roll Call….
15:04:52 <ttkacik1> #info ttkacik for Yangtools
15:04:56 <tbachman> #info tbachman for opflex
15:05:13 <tbachman> (proxy on gbp and opflex for alagalah for today)
15:05:22 <phrobb> #topic Questions From One Project To Another
15:05:28 <LuisGomez> tbachman, my pleasure
15:05:33 <phrobb> Are there any questions that any project has for another?
15:05:47 <ebrjohn> I have a question
15:06:03 <ebrjohn> I sent an email to the release list, and would like to discuss here if possible
15:06:12 <phrobb> .. and as a reminder, M2 for Offset 0 Projects is tomorrow - So their release plans should be final at this point
15:06:20 <phrobb> go for it ebrjohn
15:06:31 <mlemay_> #info mlemay for reservation
15:06:52 <ebrjohn> ok, so in the SFC project we are having problems installing ovsdb and openflow plugins automatically when karaf starts
15:07:17 <ebrjohn> The issue was tracked down by Thanh Ha, and he suspects SFC may not be the only project with this problem
15:07:43 <ebrjohn> are any other projects having problems loading ovsdb and/or openflow plugins at karaf boot???
15:07:58 <tbachman> ebrjohn: what are you seeing when you load them?
15:08:01 <tbachman> an exception?
15:08:02 <phrobb> ebrjohn:  can you point us to the email thread to catch up?
15:08:06 <tbachman> or they just don’t load?
15:08:06 <shague> ebrjohn: Thanh and Ed took another look at the commit that was failing and found a different issue I am testing now. So sfc might be fine. The previous issue thanh found might still exist
15:08:41 <ebrjohn> shague: what's the previous issue??
15:09:08 * tbachman is running out of fingers to count on for build issues
15:09:15 <shague> previous was the issue thanh brought up about how projects are overridding the mvn repo.
15:09:32 <zxiiro> #info zxiiro releng/builder
15:09:43 <tbachman> phrobb: as a minute-taker, are we just looking to archive here?  (i.e. are we info-ing anything)?
15:09:46 <ebrjohn> tbachman: this is an issue held-over from Helium, not sure about all the details
15:09:52 <shague> last night, though, thanh and ed found a different issue which is the real cause for the sfc build failing the tests. I am testing that now.
15:10:01 <ebrjohn> the main issue now was that it works fine in local, but fails in jenkins
15:10:16 <phrobb> Yes, it would be nice to Info the summary of the conversation tbachman if you don't mind
15:10:21 <tbachman> phrobb: k
15:10:27 <colindixon> #info colindixon for docs (and maybe TTP)
15:10:31 <ebrjohn> shague: ok, then maybe we can table this issue for now??
15:10:38 <mohnish> #info mohnish
15:10:45 <shague> ebrjohn: yeah
15:11:12 <phrobb> Any other questions?….
15:11:13 <sdean778> I have a question for the AAA team about working with the SNMP Plugin team on a Security Credential Service.  I filed enhancement request(bugzilla # 2576) and sent email, but no response.  Who should I talk with offline about this?
15:11:28 <ebrjohn> phrobb: here's the email I was referring to: https://lists.opendaylight.org/pipermail/release/2015-January/001234.html
15:11:29 <phrobb> Has everyone had the chance to review the Offset 0 projects on which they rely?
15:11:33 <dneary> phrobb, Here - missed roll call
15:11:46 <phrobb> thanks dneary
15:11:51 <tbachman> #info ebrjohn reports an issue with booting with SFC project
15:11:59 <tbachman> #link https://lists.opendaylight.org/pipermail/release/2015-January/001234.html email thread describing issue seen by ebrjohn
15:12:25 <tbachman> #link https://lists.opendaylight.org/pipermail/release/2015-January/001235.html subsequent email from zxiiro on the subject
15:12:33 <phrobb> Last call for questions….
15:13:08 <phrobb> #topic Project Announcements - Do Any Projects Have Changes They Would Like To Announce?
15:13:10 <tbachman> #info sdean778 asks the AAA project about working with the SNMP plugin team on a security credential service, filed as an enhancement request (bugzilla #2576), with email sent
15:13:41 <colindixon> tbachman: do we have anyone from AAA here?
15:14:02 <tbachman> colindixon: didn’t see anyone
15:14:25 <sdean778> I'll try emailing AAA team again
15:14:28 <colindixon> tbachman, sdean778: do we want to send an e-mail?
15:14:30 <colindixon> fair enough
15:14:36 <colindixon> if that doesn’t work, we’ll see what’s next
15:14:42 <tbachman> colindixon: sdean778 says he sent one
15:14:46 <colindixon> the good news is that AAA is offset 1
15:14:48 <colindixon> tbachman: got it
15:15:48 <phrobb> Any Other Announcements or requests by any project?
15:16:13 <colindixon> I have a question about where I should log a feature request for JSON to/from Binding DataObject conversion since the tooling seems to live half in YangTools (JSON to DataObject) and half in Controller (DataObject to JSON)
15:16:17 <tbachman> #link https://lists.opendaylight.org/pipermail/aaa-dev/2015-January/000244.html email from sdean778 requesting credential service
15:16:20 <colindixon> or should I just log them in both places
15:16:24 <colindixon> thanks tbachman
15:16:30 <tbachman> #info colindixon asks where I should log a feature request for JSON to/from Binding DataObject conversion since the tooling seems to live half in YangTools (JSON to DataObject) and half in Controller (DataObject to JSON)
15:16:33 <tbachman> colindixon: np!
15:16:56 <regXboi> colindixon: I'd file them in both places for now and then file a request to get that split cleaned up
15:17:01 * colindixon notest hat the functionality is likely there, it’s just really painful to figure out and I think others would likely find it useful if we made it easy
15:17:05 <regXboi> because that feels artificial
15:17:11 <colindixon> regXboi: that was my take
15:17:25 <tbachman> #info phrobb notes as a reminder, M2 for Offset 0 Projects is tomorrow - So their release plans should be final at this point
15:17:26 <tbachman> [10:06am]
15:17:46 <colindixon> tbachman: well they should be final tomorrow
15:17:58 <tbachman> #undo
15:17:58 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1a8b410>
15:18:28 <tbachman> #link https://bugs.opendaylight.org/show_bug.cgi?id=2576 bugzilla enhancement request for AAA credential service
15:18:37 <phrobb> ttkacik1, rovarga, any thoughts on colindixon's question?
15:18:42 <tbachman> #info phrobb notes as a reminder, M2 for Offset 0 Projects is tomorrow - So their release plans should be final tomorrow
15:20:09 <phrobb> Last Call for Announcements...
15:20:41 <phrobb> #topic Any questions on what should, or should not be in Release Plans?
15:21:45 <phrobb> #info Please note that M2 for Offset-1 Projects is Next Thursday (1/29)
15:22:34 <dneary> phrobb, Is "Create a user-focussed document explaining the primary use-case for your project" a requirement?
15:22:39 * dneary opens a can of worms
15:22:48 <phrobb> Would any Project Lead like to request their Release Plan to be reviewed by this group during next week's IRC meeting?
15:23:12 <rovarga> tbachman: ugh, sorry, was away
15:23:15 <regXboi> dneary: why wouldn't it be?
15:23:42 <rovarga> colindixon: ah
15:23:42 <colindixon> dneary: where is that requirement coming from?
15:23:51 <ttkacik1> colidixon please open enhancement bug
15:23:54 <rovarga> colindixon: so the tooling exists completely in yangtools ATM
15:24:10 <colindixon> rovarga: interesting, I’ll do that today
15:24:21 <rovarga> colindixon: binding-data-codec for Binding/NN
15:24:26 <tbachman> #info dneary asks if “Create a user-focussed document explaining the primary use-case for your project" a requirement?
15:24:29 <rovarga> colindixon: what sort of feature are you looking for?
15:24:49 <phrobb> dneary:  I would expect that such information is contained in the User Guide, but no, I do not believe it is explicitly called out as a requirement
15:25:08 <tbachman> #info phrobb says he would expect that such information is contained in the User Guide, but no, I do not believe it is explicitly called out as a requirement
15:25:30 <regXboi> phrobb: so I'll play devil's advocate on that one
15:25:33 <rovarga> colindixon: yang-data-codec-json for NN->JSON
15:25:43 <regXboi> if it isn't a requirement, then how does it appear in the User Guide?
15:25:49 <tbachman> #info rovarga says the tooling exists completely in yangtools ATM
15:26:00 <dneary> regXboi, ISTR a debate on "documentation" not being specific enough to be a release requirement
15:26:16 * regXboi is amazed that tbachman is trying to info two parallel conversations :)
15:26:19 <rovarga> for JSON->NN I am not so sure
15:26:20 <colindixon> rovarga: the ability to convert a “free-floating” (not stored at a path in the MD-SAL) DataObject to JSON/XML and the ability to specify a DataObject class and some XML/JSON and get a DataObject of that type back (or an error)
15:26:20 <tbachman> lol
15:26:23 <tbachman> regXboi: I’m a mess
15:26:25 <tbachman> also on the phoone
15:26:34 <tbachman> unsynchronized threads
15:26:38 <tbachman> which is what you get
15:26:48 <tbachman> lol
15:26:48 <dneary> colindixon, Just a question on my part at this point... I know there was a debate about having docs as a release requirement at the start of the cycle, and did not see the conclusion
15:27:05 <colindixon> so, dneary and regXboi, there *is* a requirement to produce documentation
15:27:11 <regXboi> dneary: ISTR is not an acronym I'm translating?  care to share the magic decoder ring output?
15:27:13 <colindixon> my guess is that would be part of user-facing documentation
15:27:18 <dneary> Thanks colindixon, phrobb
15:27:23 <dneary> regXboi, I seem to recall
15:27:28 <rovarga> colindixon: a dataobject is not 'free-floating' ever. it always is attached to a SchemaPath, which gives it the context
15:27:31 <regXboi> dneary: thanks
15:27:34 <phrobb> Fair enough regXboi.  We are getting better at guiding projects on the type of documentation they provide but have not yet gone to that level of granularity… to my knowledge… folks (including you) from the Documentation team can correct me or augment this answer
15:27:35 <dneary> np
15:27:39 <colindixon> but, our requirements for documentation are… somewhat nebulous
15:28:13 <colindixon> becuase coming up with concrete, understandable, enforceable requirements for docs is hard
15:28:15 <regXboi> phrobb: colindixon is correct: the requirements are still somewhat nebulous
15:28:39 <phrobb> regXboi:  isn't that what I said with a lot more words? :-/
15:28:41 <regXboi> I'm hoping that projects show a level of maturity in using common sense when it comes to documentation
15:28:41 <colindixon> phrobb: that’s right
15:28:50 <rovarga> colindixon: so to understand it, you want a service, which given a schemacontext (for models) and either JSON or a DTO, produces the other, correct?
15:29:08 <colindixon> rovarga: more or less, yes
15:29:13 <colindixon> rovarga: we can also take this offline if it’s easier
15:29:35 * regXboi says "no no, let's try for a third parallel conversation"
15:29:40 * tbachman is trying to catch up
15:29:45 * regXboi also wonders if we need to start having tags on #info
15:30:00 <rovarga> colindixon: sure, let's take it offline. will need uses cases, to be able to validate the solution domain, too :)
15:30:02 <colindixon> #Info phrobb, colindixon, and regXboi say that while the requirement dneary asks for around docuemnation logically makes sense, it’s not quite defined as a requirement due to haveing better, but not perfect documentation process
15:30:09 <colindixon> rovarga: yes :-)
15:30:23 <colindixon> rovarga: as I say, I’m srue it’s all there, it’d just be nice to put a user friendly API on the front
15:30:44 <colindixon> regXboi: I’d like to add that here: https://wiki.opendaylight.org/view/InternProjects:Main#Improved_ODL_Meetbot
15:30:54 <colindixon> but I’m not sure humans can use it
15:30:59 <colindixon> phrobb: what’s next?
15:31:25 <LuisGomez> #info besides the doc requirements it would be good to incentive good documentation this release, maybe some award or recognition to those projects producing good docs
15:31:29 <phrobb> Last call for Questions and Announments…
15:32:02 <rovarga> yeah ... we will need to update guava
15:32:30 <phrobb> #info Reminder that if you have a question, announment, or request of this group (like asking to have your release plan reviewed), Please post it on the wiki at the following link....
15:32:41 <rovarga> which needs cooperation from odlparent and controller as far as I understand
15:32:52 * tbachman finally hangs up phone
15:33:05 <phrobb> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Lithium_Release_Plan#Cross_Project_Meetings <<— Cross Project Meetings
15:33:13 <rovarga> odlparent needs to do the bump, controller will break on upgreade to guava >=16, but fix is trivial (but requires Guava 15)
15:33:24 <tbachman> phrobb: nice
15:34:10 <phrobb> Last Call folks… looks like we'll end this meeting early….
15:34:20 <tbachman> #info rovarga would like to update guava, which means odlparent needs to do the bump, controller will break on upgrade to guava >=16, but the fix is trivial (but requires guava 15)
15:34:27 <colindixon> tbachman: thanks!
15:34:30 <tbachman> colindixon: np!
15:34:35 <tbachman> sorry for the drop in coverage ;)
15:34:44 <regXboi> phrobb: hold on
15:34:49 <colindixon> EVERYONE, please go look at the offset 0 projects release plans and see if you need to add anything or are worrking
15:34:50 <phrobb> regXboi:  OK
15:34:50 <tbachman> as we all know, tbachman is single-threaded :P
15:34:55 <regXboi> rovarga is talking about a guava update
15:35:27 <regXboi> I'll ask - why do we need a guava update?
15:35:42 <tbachman> regXboi: I think it’s related to what colindixon was asking for
15:36:20 <regXboi> tbachman: could be, but let's make it clear why it's needed
15:36:25 <tbachman> regXboi: good point
15:36:41 <tbachman> #info rovarga asks colindixon if they want a service, which given a schemacontext (for models) and either JSON or a DTO, produces the other
15:36:45 <tbachman> #info colindixon says more or less
15:36:58 <colindixon> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Lithium_Release_Plan#Offset_0_Projects EVERYONE, please go look at the offset 0 projects release plans and see if you need to add anything or if things need to be changed at all
15:37:14 <tbachman> colindixon: thx
15:37:21 <colindixon> rovarga: why do we need to update guava?
15:37:33 <tbachman> #info colindixon asks rovarga why the guava update is needed
15:37:51 <rovarga> colindixon: escapers
15:38:13 <rovarga> colindixon: we use HTML (and other) open-coded escapers all over the place
15:38:20 <rovarga> colindixon: most of them are far from correct
15:39:09 <tbachman> #info rovarga says it’s because of escpers; HTML (and other) open-coded escapers are used all over the place, and most of them are far from correct
15:39:25 <rovarga> there may be other features (we're at guava 14, while 18 has been released. I have not checked for features thoroughly)
15:39:30 * regXboi goes ugh
15:39:31 <catohornet> Is there an effort to fill-in the Doc column contacts column?
15:40:15 <tbachman> catohornet: are you referring to gzhao
15:40:19 <tbachman> gzhao’s spreadsheet?
15:40:36 <colindixon> regXboi: did you have other comments?
15:40:51 <regXboi> colindixon: nope
15:40:57 <colindixon> ok
15:41:05 <regXboi> my ugh was to html escapers
15:41:14 <tbachman> #info catohornet asks if there’s an effort to fill-in the Doc contacts column
15:41:23 <phrobb> catohornet:  I believe that gzhao will be asking projects for that information, if it is available, in the M2 updates…  It will be required by the M3 update
15:41:37 <colindixon> catohornet: I don’t think yet, but I think we’re going to ask for it at M3 if not before
15:42:10 <colindixon> as phrobb says
15:42:16 <tbachman> #info colindixon says he doesn’t believe there’s an effort to fill in the doc contacts column yet, but thinks we’re going to ask for it at M3 if not before
15:42:29 <colindixon> the docs group would love to have them sooner if people know who they shoudl be
15:42:47 <colindixon> any more questions?
15:42:56 <phrobb> Last Call
15:43:15 <colindixon> going once
15:43:28 <phrobb> going twice....
15:43:29 <colindixon> going twice
15:43:32 <abhijitkumbhare> #info abhijitkumbhare (coming in early for the next meeting)
15:43:37 * tbachman watches colindixon raise speed-auction gavel
15:43:37 <regXboi> sold!
15:43:39 <phrobb> #endmeeting