15:31:37 <colindixon> #startmeeting weekly lithium IRC sync
15:31:37 <odl_meetbot> Meeting started Wed Feb 25 15:31:37 2015 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
15:31:37 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:31:37 <odl_meetbot> The meeting name has been set to 'weekly_lithium_irc_sync'
15:31:46 <colindixon> #topic roll call and agenda bashing
15:32:07 <colindixon> #info colindixon for docs, TTP, and TSC
15:32:16 <phrobb> We name this meeting something different each week :-/ …. we need to get better at that so the minutes are easy to find
15:32:26 <ttkacik> #info ttkacik for Controller
15:32:28 <tbachman> lol
15:32:30 <phrobb> chair me Colin and I'll help out
15:32:35 <colindixon> #chair phrobb gzhao tbachman
15:32:35 <odl_meetbot> Current chairs: colindixon gzhao phrobb tbachman
15:32:43 <dkutenic> #info dkutenic for bgpcep, tcpmd5
15:32:45 <jburns> #info jburns for iotdm
15:32:52 <colindixon> phrobb: the previous meetings were M1 M2 sync
15:32:54 <sdean778> #info sdean778 (Steve Dean) for DIDM and SNMP Plugin
15:32:55 <colindixon> which sounded wrong
15:32:56 * tbachman laughs when he hears “chair me”…. keeps envisioning somone smashing a chair over someone’s head
15:33:10 <colindixon> phrobb: I tried to pick this one so that we could reuse it
15:33:23 <phrobb> I called the last one I did "lithium cross project irc mtg"
15:33:32 <colindixon> phrobb: ah
15:33:34 <colindixon> my bad
15:33:38 <colindixon> I must have missed that
15:33:42 <fabiel> #info fabiel for Persistence Store Service
15:33:44 <ttkacik> #info ttkacik for Yangtools
15:33:44 <phrobb> no worries, we'll get there
15:34:07 <phrobb> tbachman:  lol
15:34:16 <colindixon> so, if anyone wants to add something to teh agenda, feel free to list it as a topic now so we can get through it in a few
15:34:28 <tbachman> all: alagalah will be here momentarily
15:35:17 <alagalah> #info alagalah for GBP, OpFlex
15:35:31 <alagalah> Sorry folks, meeting overflow
15:36:38 <phrobb> colindixon:  made a call for agenda topics.  If there are no additional ones, we'll start with any cross-project questions....
15:36:42 <alagalah> How are we on this fine Wednesday ?
15:36:45 <rovarga> #info rovarga also for yangtools
15:37:02 <phrobb> splendid alagalah, thanks for asking.  And you?
15:37:12 * tbachman has a question on some definitions
15:37:14 <colindixon> I’d like to say a few quick things about docs, but I’ll do it in time
15:37:58 <phrobb> tbachman:  ask away
15:38:21 <tbachman> I was wondering about what functionality freeze vs. API freeze means exactly
15:38:48 <colindixon> #info tbachman asks what the difference between functionality freeze and API freeze was supposed to be
15:39:19 <ttkacik> what happened in previous releases  - functionality (working code) was unsually delivered after API freeze
15:39:43 <colindixon> #info funcrtionality freeze means that at least enough functionality to get a PoC done or beta test the general idea of an API should be there
15:39:53 <ttkacik> and when someone tried to use that functionality - it usually leaded to API changes
15:40:21 <colindixon> #info API freeze is much harder, meaning that APIs should actually stay put and other projects shoudn’t have to make code changes as a consequence of anything you do
15:40:23 <colindixon> does that make sense?
15:40:24 <ttkacik> so reversing that gives you something to play to figure out if APIs are sufficient
15:40:34 <colindixon> what ttkacik says is the motivation for the freezes and the ordering
15:41:23 <alagalah> colindixon: phrobb FYI - as of last night GBP is dependent on SFC. We will update our artifacts. We have been working closely together, but technically we should go through the "request functionality" process.
15:41:59 <alagalah> Actually can phrobb colindixon gzhao clarify something for me ?
15:42:03 <phrobb> alagalah:  thanks for the heads up..
15:42:08 <colindixon> alagalah: sure
15:42:10 <phrobb> alagalah:  sure, what do you ned?
15:42:22 <phrobb> s/ned/need
15:42:23 * alagalah Actually I noodled it out for myself...
15:42:36 <phrobb> that was fast… quite the noodle
15:42:48 <colindixon> :-)
15:42:55 <alagalah> We are dependent on SFC... like just one of our renderers is dependent on OFPlugin therefore its a project dependency... I was curious about the degree of dependency... but its binary
15:42:56 <colindixon> if you think others are wondering the same thing, please ask
15:43:25 <colindixon> alagalah: yeah, going beyond binary dependencies seems beyond us (at least for this release)
15:44:04 <colindixon> phrobb: what’s the next topic?
15:44:27 <tbachman> sorry folks — back.
15:44:29 <tbachman> thx for the input
15:44:38 <phrobb> If no other questions, then the next topic is Project announcements
15:44:51 <phrobb> #topic Project Announcements
15:45:26 <phrobb> Anything any project wants to note for other projects - colindixon this may be a good place to state your documentation business
15:46:19 <colindixon> #Info the documentation project has been working to try to get the templates for projects to use for their outlines (due at M3 done) and I will be merging the templates this week
15:47:39 <colindixon> #link https://wiki.opendaylight.org/view/CrossProject:Documentation_Group:Lithium_Project_Documentation_Requirements#Timeline_for_Deliverables_from_Projects this has the overview, but the exact location of where you should put your docuemntation might change a bit in the next few days
15:48:36 <colindixon> #info the templates will be in the docs repo in the folder manuals/readme/src/main/asciidoc
15:48:51 <colindixon> #info expect more information about docs in a mail sent to release later this week
15:48:55 <colindixon> hopefully that helps
15:49:53 <alagalah> colindixon: It does, just added the link to our trello card for docs... many thanks
15:50:14 <alagalah> colindixon: Is there a maven flag that can magic up someone to do our documentation ?
15:50:28 <rovarga> #info yangtools has basic constraint enforcement ready to merge, we will probably be merging it on Monday or Tuesday
15:50:29 <phrobb> For Offset 1 projects, are there any changes in your planned functionality that will affect any of your dependent projects as M3 approaches (next week)?  If so have they been well communicated?
15:50:59 <gzhao> #info offset 1 projects please check  #link https://lists.opendaylight.org/pipermail/release/2015-February/001413.html , any question since M3 status is due next week
15:51:19 <phrobb> thanks for posting that gzhao
15:51:37 <colindixon> rovarga: is there a way for projects to turn that back off so that they can make progress while they debug it?
15:52:08 <rovarga> #info BUG-2362. Binding-Aware users should be unaffected (BUG-1953 did the same thing for them), Binding Independent users (like RESTCONF) may get bitten if they pass wrong values
15:52:31 <gzhao> #info LuisGomez will give a talk in TWS how to create integration system test template.
15:52:41 <phrobb> gzhao:  Can you update us on how projects are responding to the SingleFeature Test fix?
15:53:13 <rovarga> colindixon: fair question, but I am afraid the answer is no at this time
15:53:46 <colindixon> rovarga: maybe even just instructions about how to roll yangtools back to before it and then buidl with -nsu?
15:54:05 <gzhao> #link https://docs.google.com/spreadsheets/d/1PYxjiSYEks44uJByVO1P44rnI5xTJRulpKyrSsDQF9g/edit#gid=1598222722 <== spreadsheet to track single feature test
15:55:05 <gzhao> #info right now, only two projects, nic and lisp responded and lisp was verified.
15:55:35 <colindixon> gzhao: note that the list I produced coudl have both false positives (e.g., lisp) and false negatives
15:56:30 <gzhao> colindixon: I think if people read edwarnicke's example, and your ttp example, they should figure it out.
15:56:41 <colindixon> gzhao: yes
15:56:44 <alagalah> colindixon: rovarga Question: From yesterdays MD-SAL meeting, did anyone take an action, or is this the forum, for someone to give an update on cross-project gerrit process ?
15:56:57 <alagalah> I know we are running into the doco meeting
15:57:19 <colindixon> alagalah: sadly, the docs meeting for today has been canceled, so we’re OK for now
15:57:36 <colindixon> alagalah: no, I don’t think anyone did
15:57:36 <alagalah> colindixon: rovarga (ack) ... is it something we should put on this meeting's standing agenda ?
15:57:55 <alagalah> colindixon: rovarga ie is this the right forum ?
15:58:10 <colindixon> #info alagalah asks if anyone took an action time on how to better convey when patches in different projecrts depend on one another
15:58:39 <alagalah> colindixon: rovarga Perhaps if we have time a mention on the TSC call ?
15:58:39 <colindixon> #info yesterday, on the MD-SAL call, this came up and robert suggested using topics as a way to do that
15:59:05 <colindixon> alagalah: I can put it on the agenda for a few minutes
15:59:27 <colindixon> for now, I think the answer is topics but it won’t help you figure that out from the CLI where your builds are failing
15:59:54 <alagalah> colindixon: I think its appropriate, especially as projects integrate at a say the same offset level, where it appears the issue was born out of offset0/1 projects, but maybe relevant to others.
15:59:55 <colindixon> #info other suggestions here have been: (a) using reptool and (b) possibly cross project dependencies in gerrit
16:00:01 <colindixon> yeah
16:00:08 <colindixon> we can bring it up
16:00:14 <alagalah> colindixon: Done, thanks
16:00:23 <colindixon> the issue is that somebody needs to find time to go play with things
16:00:29 <colindixon> and see how they work
16:00:43 <gzhao> collecting M3 status for offset 1 will be challenging, integration automation test starts and karaf features defined.
16:00:43 <colindixon> rovarga: so, how hard would it be to make constraint checking a flag?
16:01:12 <colindixon> gzhao: yeah… we need to work on that and figure out how much can be automated or semi-automated
16:01:15 <ttkacik> colindixon: that flag is global or per-model basis?
16:01:39 <colindixon> ttkacik: global and enabled by default, but something that I could locally disable
16:01:55 <colindixon> so that I can keep making progress while I debug issues with it
16:02:37 <colindixon> does that make sense?
16:03:00 <colindixon> I’m just looking for a safety valve so that if somebody finds everythign there is broken
16:03:38 <ttkacik> #info yangtools and controller project plans to remove CompositeNode and CompositeNode related APIs and methods on 2015-03-09
16:03:38 <ttkacik> #info these APIs were deprecated early in Helium
16:03:38 <ttkacik> #info affected projects are ttp, aaa and sfc - courtesy patches which will migrate these projects from deprecated API will be provided  by 2015-03-04
16:03:38 <ttkacik> #info Binding-aware only users are not affected by change
16:03:45 <rovarga> colindixon: not quite sure, will have to get back on that
16:04:08 <colindixon> rovarga: sure, it’s just a thought if it’s easy
16:04:16 <colindixon> ttkacik: thanks! that sounds perfect
16:04:36 <ttkacik> colindixon: already looking at ttp test :)
16:04:54 <colindixon> any help there would be appreciated :-)
16:04:57 <colindixon> other topics?
16:05:17 <phrobb> #info Last call for Project Announcments....
16:05:32 <ttkacik> actually was suprised there are only four classes affected outside controller and yangtools
16:06:02 <phrobb> #topic Any Final Questions… On Process, M3, or any other?
16:06:34 <phrobb> Going once……
16:06:55 <phrobb> Going twice…..
16:07:09 <gzhao> #info encourage people to attend Monday TWS
16:07:24 <gzhao> especially offset 1
16:07:47 <phrobb> alagalah:  What's on the agenda for TWS on Monday?
16:07:58 <alagalah> phrobb: luis and integration
16:08:06 <alagalah> phrobb: hold 1 for link and I will #link #info
16:08:38 <phrobb> alagalah:  Well worth attendance at twice the price!
16:08:59 <gzhao> alagalah: not on wiki yet
16:09:16 <alagalah> #link https://wiki.opendaylight.org/view/Tech_Work_Stream:Main#Upcoming_Meeting_Agendas gzhao recommends offset1 folks attend TWS Mar2, Luis talking about Integration testing requirements
16:09:25 <alagalah> gzhao: was yesterday
16:09:37 <alagalah> gzhao: I was editting it as I looked it up, removing old meetings from the agenda
16:09:44 <alagalah> gzhao: perhaps you looked as I was saving ?
16:10:03 <phrobb> Great reminder gzhao and alagalah
16:10:24 <phrobb> #info last call for final questions
16:10:42 <phrobb> #topic Cookies
16:10:49 <tbachman> lol
16:11:00 <phrobb> #info Thanks everyone for joining this morning… We'll do it again next week
16:11:07 <phrobb> #endmeeting