14:31:31 <colindixon> #startmeeting release reviews
14:31:31 <odl_meetbot> Meeting started Mon Jun 22 14:31:31 2015 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
14:31:31 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:31:31 <odl_meetbot> The meeting name has been set to 'release_reviews'
14:31:36 <phrobb> good morning colindixon
14:31:47 <colindixon> #chair phrobb dfarrell07
14:31:47 <odl_meetbot> Current chairs: colindixon dfarrell07 phrobb
14:31:54 <colindixon> #topic roll call
14:31:56 <colindixon> #info colindixon
14:32:00 <gzhao> #info gzhao
14:32:02 <colindixon> we’ll move to bgpcpe in a bit
14:32:22 <dkutenic> #info Dana for bgpcep
14:32:24 <colindixon> #link https://docs.google.com/spreadsheets/d/1PYxjiSYEks44uJByVO1P44rnI5xTJRulpKyrSsDQF9g/edit#gid=743945554 the scheduled for today (and future release reviews)
14:32:26 <vjanandr> #info vijay for snbi
14:32:30 <phrobb> #info PTLs and TSC members please #info in
14:32:35 <dkutenic> #info Dana again for tcpmd5
14:32:59 <colindixon> ok
14:33:04 <colindixon> let’s get started
14:33:16 <colindixon> #chair gzhao
14:33:16 <odl_meetbot> Current chairs: colindixon dfarrell07 gzhao phrobb
14:33:20 <gzhao> #info the name in green means PTL accepted in calendar invitation
14:33:29 <colindixon> #topic BGPCEP
14:33:33 <colindixon> gzhao: we have fijay
14:33:37 <colindixon> gzhao: so, I think we’re good
14:33:43 <gzhao> colindixon: yes
14:33:49 <colindixon> #link https://wiki.opendaylight.org/view/BGP_LS_PCEP:Lithium_Release_Review release review
14:33:55 <colindixon> #link https://wiki.opendaylight.org/view/BGP_LS_PCEP:Lithium_Release_Notes release notes
14:34:02 <colindixon> dkutenic: anything you want to add while we read
14:34:03 <colindixon> ?
14:34:14 <dkutenic> nope, will wait for your comments :-)
14:35:04 <gzhao> #info I don't have anything, there are well written.
14:36:16 <colindixon> dkutenic: are there any known issues/bugs?
14:36:40 <colindixon> dkutenic: and are there any notes around backward compatilbity and/or migration?
14:36:53 <dkutenic> no. but just a few minutes ago, there was one added into bugzilla, but it looks like incorrect use of restconf
14:36:59 <colindixon> sure
14:37:00 <phrobb> dkutenic: Your release relvew document is very well written.  Nice job!
14:37:22 <colindixon> dkutenic: there’s also somebody (I think a user) asking on #opendaylight about how to configure BGPCEP right now :p
14:37:37 <dkutenic> no notes about backwards compatibility...
14:37:49 <colindixon> #info this looks really good overall, dkutenic notes that there are no open bugs save one that seems to be user error
14:38:07 <colindixon> dkutenic: is that because it’s not supported or becuase the model should be the same and migration should be trivial?
14:38:26 <colindixon> #info colindixon asks about migration and/or backward compatibility
14:38:31 <phrobb> dkutenic Not tied to the release, but given the steep learning curve you mention there, would it be helpful if we recorded one or more short webinar-type sessions where you can explain the configuration and setup?
14:38:56 <dkutenic> colindixon: record...how?
14:39:18 <colindixon> dkutenic: phrobb would help you set that up
14:39:35 <LuisGomez> #info LuisGomez integration
14:39:40 <dkutenic> and I've just created more comprehensible wiki page: https://wiki.opendaylight.org/view/BGP_LS_PCEP:BGP_Use_Cases I don't think I can be any more explicit than this :-)
14:39:46 <gzhao> #info phrobb  suggests to record some short webinar-type sessions to explain the configuration and setup
14:40:17 <colindixon> dkutenic: see the above question about whether there’s nothing there for backward compatibility and/or migration because it’s not supported or because it’s trivial
14:40:20 <gzhao> #info dkutenic says there is a wiki page https://wiki.opendaylight.org/view/BGP_LS_PCEP:BGP_Use_Cases
14:40:47 <gzhao> any more questions on bgpecp?
14:40:55 <dkutenic> colindixon: I'd say both depends on what are you doing
14:40:56 <phrobb> OK, cool dkutenic.  Was just looking to help get more/better docs out there if needed.
14:41:35 <colindixon> #info dkutenic says that migration from Helium isn’t documented for now, but may be trivial in some cases
14:41:36 <colindixon> ok
14:41:37 <colindixon> that’s all
14:41:40 <colindixon> anything else?
14:42:02 <gzhao> #topic TCPMD5
14:42:15 <colindixon> dkutenic: it probably makes sense to note exactly what shouldn’t work with upgrades in the future (although I know we didn’t require it here)
14:42:29 <colindixon> #link https://wiki.opendaylight.org/view/TCPMD5:Lithium_Release_Review release review
14:42:34 <colindixon> #link https://wiki.opendaylight.org/view/TCPMD5:Lithium_Release_Notes release notes
14:42:40 <colindixon> more from dkutenic :-)
14:42:45 <dkutenic> colindixon: I'll check it and note things that are really incompatible
14:44:04 <dkutenic> note for tcpmd5, there were only commits that included version bump and pom cleaning
14:44:16 <dkutenic> in this release
14:44:26 <colindixon> cool, looks good
14:44:52 <colindixon> #info dkutenic notes that “for tcpmd5, there were only commits that included version bump and pom cleaning”
14:45:03 <phrobb> Agreed.  Looks good dkutenic.  No questions from me.
14:45:57 <gzhao> looks good to me.
14:46:26 <dkutenic> thanks
14:46:28 <colindixon> #topic SNBI
14:46:37 <colindixon> #link https://wiki.opendaylight.org/view/SecureNetworkBootstrapping:LithiumReleaseReview release review
14:46:49 <colindixon> #link https://wiki.opendaylight.org/view/SNBI_Lithium_Release_Notes. release notes
14:46:53 <gzhao> #info vjanandr  represents SNBI
14:46:59 <colindixon> #undo
14:46:59 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1ce4d90>
14:47:01 <colindixon> #Undo
14:47:01 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x1c485d0>
14:47:08 <colindixon> #link https://wiki.opendaylight.org/view/SNBI_Lithium_Release_Notes release notes
14:47:14 <colindixon> #info vjanandr representing SNBI
14:47:17 <colindixon> sorry
14:47:21 <colindixon> link in the spreadsheet was wrong
14:47:26 <gzhao> np
14:47:52 <gzhao> vjanandr: anything you want to add
14:47:56 <colindixon> or not…
14:48:02 <colindixon> #undo
14:48:02 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1abe490>
14:48:04 <colindixon> #undo
14:48:04 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x1ce4e50>
14:48:08 <colindixon> #info vjanandr representing SNBI
14:48:14 <colindixon> #link https://wiki.opendaylight.org/view/SNBI_Lithium_Release_Notes. release notes
14:48:16 <vjanandr> just that major development has been on the forwarding element side..
14:48:25 <colindixon> you need the period on the end
14:48:44 <colindixon> I moved it to the one without the period
14:48:48 <colindixon> so both should work with a redirect
14:49:01 <vjanandr> ok
14:49:32 <gzhao> vjanandr: ascii doc not get updated after -1
14:49:41 <gzhao> from colindixon
14:49:58 <colindixon> thank you gzhao
14:50:12 <vjanandr> ok I dint notice that..
14:50:15 <vjanandr> let me close on that
14:50:41 <colindixon> #link https://git.opendaylight.org/gerrit/#/c/20059/ the patch for asciidoc docs still needs to be revised and merged
14:50:50 <gzhao> #info vjanandr will close on the ascii document
14:51:10 <gzhao> #undo
14:51:10 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x19b8f90>
14:51:34 <gzhao> #action vjanandr will close on the ascii document to merge https://git.opendaylight.org/gerrit/#/c/20059/
14:51:38 <colindixon> vjanandr: any notes about backward compatibility and/or migration
14:51:41 <colindixon> ?
14:51:54 <vjanandr> no.. should be backward compatibile
14:51:59 <colindixon> ok
14:52:11 <colindixon> #info vjanandr notes that SNBI should be backward compatible with Helium
14:52:17 <colindixon> ok, other than the docs, I’m happy
14:52:41 <gzhao> colindixon: you type fast
14:52:47 <gzhao> nothing from me
14:53:12 <colindixon> #topic controller
14:53:21 <colindixon> #link https://wiki.opendaylight.org/view/OpenDaylight_Controller:Lithium:Release_Review release review
14:53:25 <colindixon> #link https://wiki.opendaylight.org/view/OpenDaylight_Controller:Lithium:Release_Notes release notes
14:53:30 <colindixon> gzhao: lots of scribing
14:53:36 <gzhao> can tony info in?
14:53:46 <colindixon> ttkacik: you around?
14:53:52 <ttkacik> #info ttkacik for Opendaylight Controller
14:54:04 <colindixon> ask and ye shall receive
14:54:14 <ttkacik> :)
14:54:37 <ttkacik> are we waiting?
14:55:09 <ttkacik> #link https://wiki.opendaylight.org/view/OpenDaylight_Controller:Lithium:Release_Review relese review
14:55:30 <colindixon> #undo
14:55:30 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x1aa8750>
14:55:37 <colindixon> ttkacik: I already posted the links
14:55:41 <colindixon> was just reading
14:55:43 <colindixon> it looks good
14:55:43 <ttkacik> colindixon I see
14:55:49 * colindixon points up
14:56:01 <colindixon> the link to the Helium release review in the release notes is broken
14:56:09 <colindixon> otherwise, this looks good
14:56:22 <ttkacik> link updated
14:56:32 <colindixon> ttkacik: done
14:56:48 <phrobb> ttkacik do we know if anyone in Li is using the deprecated AD-SAL api and if so what testing was done?
14:57:31 <ttkacik> phrobb: AD-SAL testing is still in CSIT for Openflowplugin
14:58:02 <colindixon> #info phrobb asks if we know if anyone in Lithium is still using the deprecated AD-SAL and what testing was done
14:58:19 <colindixon> #info ttkacik responds that some AD-SAL testing is still done using CSIT for OF plugin
14:58:21 <ttkacik> phrobb: as for Li users grep shows some artefacts using AD-SAL, but not sure if they are left-overs or are to be functional
14:58:37 <colindixon> I think VTN is still using some parts
14:58:43 <phrobb> OK, cool ttkacik.  I think this is a first majore API EOL, so wanted to ensure we documented it's closure
14:58:49 <phrobb> colindixon that was my understanding also
14:59:10 <gzhao> ttkacik: I noticed that your doc is pointing to github instead of wiki as most projects
14:59:28 <colindixon> phrobb, ttkacik: correct me if I’m wrong, but AD-SAL testing is largely left to projects instead of the controller at this point
14:59:33 <colindixon> gzhao: that’s beter
14:59:45 <ttkacik> gzhao: yes... but this are links to github mirror of docs projects
14:59:48 <colindixon> gzhao: it’s pointing to the rendered AsciiDoc from our github mirror of the docs repo
14:59:54 <gzhao> colindixon: should we encourage all projects to do so?
15:00:02 <colindixon> gzhao: yes
15:00:03 <ttkacik> gzhao: over the time yes
15:00:05 <colindixon> although it’s a bit late
15:00:06 <colindixon> :p
15:00:11 <gzhao> ttkacik: colindixon since it seems more dynamic to me
15:00:24 <gzhao> ttkacik: thanks
15:00:24 <colindixon> it’s pointing to the stable/lithium branch of the docs repo (I think
15:00:25 <ttkacik> gzhao: ideally with readme.adoc and release notes hosted in their own repo instead of docs :)
15:00:33 <colindixon> ttkacik: +1
15:00:45 <phrobb> colindixon Yes, that is my expectation that the projects test.  Just wanted to cross-reference with controller project on what dependent projects they were coordinating with re the deprecated APIs
15:00:54 <gzhao> ttkacik: ok, we should try this for Beryllium.
15:01:25 <gzhao> #info ttkacik says ideally with readme.adoc and release notes hosted in their own repo instead of docs
15:01:39 <colindixon> #info colindixon says that it’s his understanding that most projects depending on the AD-SAL are likely on their own for testing and finding bugs in the AD-SAL, we should likely build a list of those and make sure they understand the issue
15:02:11 <colindixon> phrobb and/or ttkacik is that something I could ask you two to do? or should I do it
15:02:49 <ttkacik> colindixon: will try to put a list of affected projects
15:02:54 <colindixon> my guess is that it’s pretty easy to do with this: https://github.com/nilok/odlutils
15:03:00 <colindixon> I should move that to the internal repos
15:03:03 <phrobb> colindixon I'm happy to work with ttkacik and the dependent projects to ensure we cover the AD-SAL topic as part of their release review
15:03:28 <colindixon> #action ttkacik and phrobb make a list of projects using the AD-SAL and reach out to them about testing in Lithium and migration in Beryllium
15:03:29 <colindixon> cool
15:03:31 <colindixon> anything else?
15:03:50 <ttkacik> nothing from my side
15:03:59 <gzhao> colindixon: will be your ttp
15:04:09 <colindixon> it’s yangtools now, right?
15:04:15 <gzhao> colindixon: yes
15:04:19 <gzhao> ttkacik: thanks
15:04:24 <colindixon> #topic yangtools
15:04:30 <colindixon> #link https://wiki.opendaylight.org/view/YANG_Tools:Lithium:Release_Review release review
15:04:36 <colindixon> #link https://wiki.opendaylight.org/view/YANG_Tools:Lithium:Release_Notes release notes
15:04:48 <colindixon> rovarga: anything you want to add while we read?
15:04:53 <colindixon> #info rovarga is representing yangtools
15:05:37 <phrobb> colindixon do we know rovarga is here?.. we're running a few minutes early
15:05:41 <rovarga> colindixon: not really, I think it's all there
15:05:44 <colindixon> ttkacik and/o rovarga did we ever create AsciiDoc for yangtools?
15:05:53 <phrobb> ah Hi rovarga
15:06:41 * rovarga needs to check, as ttkacik was taking care of the paperwork this release :-(
15:06:47 <colindixon> phrobb: TTP is next (which is me), so the only question now is whether adierken is here for SNMP in 10 minutes
15:07:10 <adierken> #info adierken SNMP
15:07:12 <colindixon> rovarga: I *think* we never did any AsciiDoc for YANG tools in this release
15:07:42 <gzhao> rovarga: does yangtools support java 8 as well?
15:08:04 <rovarga> colindixon: that aligns with my understanding, as most of the developer documentation sits either in controller or coretutorials
15:08:09 <ttkacik> colindixon: will push asciidocs for YT tomorow
15:08:19 <rovarga> gzhao: yup, it was the first project to do that
15:08:42 <colindixon> #info colindixon believes that there are no AsciiDoc for yantools at this point, but rovarga notes that most of it should be in controller or coretutorials (which is right)
15:09:01 <colindixon> #action ttkacik to post/update yangtools developer docs (even if just to point to the relevant sections in controller docs) tomorrow
15:09:03 <colindixon> thanks ttkacik!
15:09:18 <gzhao> rovarga: I am reading "require only a Java-7 compliant JVM to run" should that be java 7 and +
15:09:45 <rovarga> gzhao: sorry, will fix that right away
15:10:18 <colindixon> rovarga: this is all just minor stuff
15:10:29 <colindixon> do we have an overall sense of where we are with Java 7 vs. Java 8?
15:10:34 <colindixon> are there any projects that require Java 7?
15:11:09 <colindixon> #action colindixon to work with phrobb, zxiiro, gzhao, rovarga, ttkacik, and others to figure out what the overall release notes should say about Java 7 vs. Java 8
15:11:52 <gzhao> colindixon: rovarga do we know any project that can only run on java 7?
15:12:04 <rovarga> #info rovarga is not aware of any projects which would be runtime-incompatible with Java 8
15:12:32 <colindixon> we can follow up about that offline, it’s not relevant for the yangtools release review, but good to know overall
15:12:37 <gzhao> in that case, in release note should be Java7 and later version.
15:12:58 <colindixon> well, presumably we don’t want to say Java 7+ since we haven’t tested with Java 9
15:13:03 <rovarga> I fixed it to say 'require only JVM compliant with Java 7 SE or Java 8 SE to run'
15:13:16 <colindixon> perfect
15:13:17 <colindixon> ok
15:13:53 <zxiiro> fwiw autorelase builds with Java 7
15:14:06 <colindixon> anything else?
15:14:09 <colindixon> #topic TTP
15:14:38 <colindixon> ok…
15:14:42 <colindixon> I may have lost tubes
15:14:54 <colindixon> zxiiro: we could test if it built with Java 8
15:14:57 <colindixon> just for some sanity
15:15:12 <colindixon> #link https://wiki.opendaylight.org/view/Table_Type_Patterns/Lithium/Release_Review release review
15:15:22 <colindixon> #link https://wiki.opendaylight.org/view/Table_Type_Patterns/Lithium/Release_Notes release notes
15:15:27 <colindixon> #info colindixon representing TTP
15:15:37 * colindixon goes to check the logs to see if anything was lost
15:16:30 <zxiiro> colindixon: we could, i'll have to modify the daily job for that or create another job
15:16:59 * zxiiro adds it to his list of things to do today
15:17:23 <rovarga> zxiiro: colindixon: I think it will blow up on use of enunciate plugin, as some projects use it for docs (that's why merge jobs run with Java 7)
15:17:27 <gzhao> colindixon: we should add backward compatible in the sample release review
15:18:12 <rovarga> zxiiro: colindixon: so either it will succeed (and not produce docs) or fail :)
15:18:12 <colindixon> gzhao: yes
15:18:33 <zxiiro> rovarga: good to know. I'll create the Java8 job as a separate Jenkins job just so that it doesn't inturrupt the existing jobs
15:18:37 <colindixon> gzhao: technically it’s in the sample release notes, but not quite right
15:19:07 <colindixon> #action colindixon to add backward compatibly and migration to the sample release review and make it more clear in the sample release notes
15:19:17 <colindixon> any other questions on TTPs?
15:19:38 <colindixon> #info curtbeckmann is also here representing TTPs
15:19:49 <phrobb> Not from me colindixon .  The release review looks good
15:20:18 <gzhao> nothing from me on TTP
15:21:20 <colindixon> #topic SNMP
15:21:25 <colindixon> adierken: you’re up, links incoming
15:21:34 <colindixon> #link https://wiki.opendaylight.org/view/SNMP_Plugin:Lithium_Release_Review release review
15:21:39 <colindixon> #link https://wiki.opendaylight.org/view/SNMP_Plugin:Lithium_Release_Notes release notes
15:23:11 <colindixon> #link https://github.com/opendaylight/docs/blob/stable/lithium/manuals/user-guide/src/main/asciidoc/snmp/snmp-user-guide.adoc SNMP user guide (asciidoc in the docs repo)
15:23:51 <colindixon> adierken: are you there?
15:24:00 <adierken> I can change the review notes to point to the asciidoc
15:24:28 <colindixon> if you want, you can link there since you did the work, but I’d do it as an “also” instead of change
15:24:34 <colindixon> do you support snmp traps
15:24:46 <adierken> not currently
15:24:47 * colindixon has to run deal with a broken class
15:24:56 <colindixon> glass
15:25:02 <colindixon> gzhao: and phrobb can run things from here
15:25:10 <phrobb> colindixon yep we got it
15:25:15 <gzhao> colindixon: sure
15:25:31 <gzhao> adierken: could add a link of release note in the release review
15:25:50 <gzhao> this way people has one link can have access to both
15:26:02 <adierken> yup, will do
15:26:07 <gzhao> adierken: thanks
15:26:31 <phrobb> adierken can we call out no support for traps as part of the limitations section of the Rel. notes?
15:27:01 <gzhao> #info phrobb asks if we can call out no support for Traps in SNMP release notes
15:27:12 <adierken> I will add that now
15:27:38 <phrobb> thanks adierken.  I think that was where colindixon  was headed.
15:27:59 <gzhao> #action adierken will add no trap support in known issue and limitations
15:28:21 <gzhao> anything else for SNMP?
15:28:28 <phrobb> Everything else look good to me.  Any other questions/comments for the SNMP team?
15:28:46 <phrobb> going once.....
15:28:54 <phrobb> going twice.....
15:29:11 <gzhao> thanks everyone
15:29:15 <phrobb> I believe we are closed for the day.
15:29:29 <phrobb> Thanks Everyone for being here, and early
15:29:38 <phrobb> #topic COOKIES
15:29:55 <phrobb> #endmeeting