17:00:11 <anipbu> #startmeeting release-sync
17:00:11 <odl_meetbot> Meeting started Wed Jun  1 17:00:11 2016 UTC.  The chair is anipbu. Information about MeetBot at http://ci.openstack.org/meetbot.html.
17:00:11 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:11 <odl_meetbot> The meeting name has been set to 'release_sync'
17:00:23 <anipbu> #topic M3 IRC Working Session
17:01:18 <anipbu> #info Open discussion for new projects to ask questions regarding Boron Milestone 3 (M3)
17:01:30 <Prem> #info Prem for VPNService
17:01:50 <hideyuki> #info Hideyuki for VTN
17:02:08 <gdavid> #info gdavid for uni-mngr
17:02:29 <Mknair> #info mknair@wipro.com for atrium
17:02:57 <anipbu> Mknair: how are things coming along for atrium M3?  Any questions with the miilestone items?
17:03:03 <vishnoianil> #info vishnoianil for ovsdb
17:03:51 <jamoluhrsen> #info jamoluhrsen for Integration/Test
17:04:15 <vrpolak> #info vrpolak for Integration/Distribution
17:04:24 <anipbu> Mknair: I noticed atrium does not have user guide outline for docs (a requirement for M3).  Do you need help setting that up?  https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=tree;f=manuals/user-guide/src/main/asciidoc;
17:05:08 <Mknair> There was one qn related to system test. We got a waiver from integration team.  Do we need to update the sections related to system test in m3 status
17:06:36 <jamoluhrsen> anipbu, Mknair: correct me if I'm wrong, but I think the M3 status for system test when you have a waiver is just to state that you have a waiver.
17:07:11 <Mknair> Yes.  For user guide appreciate if you can share the repository for uploading ascii docs
17:07:15 <jamoluhrsen> there would be a system test report to give at a later milestone where you can update with external results
17:09:29 <anipbu> Mknair: projects should add their user guide to the docs repository: https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=tree;f=manuals/user-guide/src/main/asciidoc;
17:10:09 <anipbu> Here are the steps-by-step guide to submitting user guide documentation to the docs repository: https://wiki.opendaylight.org/view/Documentation/Beryllium/Project_Documentation_Requirements#Submitting_Documentation_Outlines_.28M3.29
17:11:37 <anipbu> gdavid: how are things coming along for unimgr?  your projects looks to be in good shape for M3 =)
17:12:01 <gdavid> Things are good :)
17:12:17 <gdavid> Commiting last feature changes before th freeze
17:12:54 <Prem> anipbu:  I wanted to call out few things for VPNService
17:13:41 <Mknair> Also we have a dependency on didm project.  We are waiting for the didm to push relevant drivers to oil repo.  Hence we have not pushed the code for Atrium yet.
17:14:36 <anipbu> Prem: Hi.  Glad to see VPNService represented here.  Feel free to ask any questions!  We would be delighted to help.
17:14:42 <Prem> anipbu:  As you would be aware; VPNService is getting split into 3 parts -> GENIUS, NetVirt and VPNService
17:15:03 <anipbu> Mknair: have you contacted DIDM to inform them of the blocking issues?
17:15:35 <Prem> Migration is on its way and post the migration , VPNService would have a reduced scope.
17:16:32 <Prem> I am planning to call this out in M3 and wanted few more days before the scope is finalized
17:16:47 <anipbu> gdavid: glad to hear that.  Besides odl-unimgr, will there be any NEW additional user facing or top level features?
17:17:53 <gdavid> The yang model has been changed, so the api will be a little diffrent
17:18:02 <anipbu> Prem: generally, migration should be itemized and advertised in the release plan.  Have you updated the release plan and notified dependent projects?
17:18:24 <Mknair> anipbu:yes we have informed didm team and they are working on it.
17:18:43 <Prem> VPNService does'nt have any dependent projects and I am working on revised release plan
17:18:53 <anipbu> gdavid: what are the karaf feature names?
17:19:01 <davidmichaelkarr> Piping in about YangIDE, I don't know that I have any particular questions about the M3 status, but perhaps I don't know the right questions to ask.  I'm just going on the template and one example status report.
17:19:43 <anipbu> davidmichaelkarr: YANGIDE is missing user guide documentation: https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=tree;f=manuals/user-guide/src/main/asciidoc;
17:19:46 <gdavid> It will probably be the same name
17:20:29 <anipbu> gdavid: okay great!  Then we do not need to update the integration distribution with the new unimgr features.  =)
17:21:08 <davidmichaelkarr> anipbu: I noticed that, not sure what to do there yet.
17:21:11 <gdavid> We are adding more southbound implementations, so we might add more specific features for each one of the implementations, but if so, we will updat the integration team
17:21:50 <anipbu> Mknair: we are missing the system test plan template for your projects.  Do you need help creating one?https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#External_System_Test_Report
17:22:58 <anipbu> gdavid: we are missing the boron system test plan template for unimgr.  Do you need help creating one?  https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#External_System_Test_Report
17:23:38 <anipbu> davidmichaelkarr: Please follow the steps here to submit user guide documentation for YangIDE project: https://wiki.opendaylight.org/view/Documentation/Beryllium/Project_Documentation_Requirements#Submitting_Documentation_Outlines_.28M3.29
17:23:40 <gdavid> #anipbu we were planning to do it at the hackfest. When is it due?
17:24:16 <LuisGomez> #info LuisGomez for distribution
17:24:44 <LuisGomez> just joined, any question on distribution?
17:25:04 <anipbu> gdavid: EEEKS!  It is due tomorrow =(  Perhaps we can help you put together a simple skeleton?
17:25:34 <gdavid> @anipbu that will be great :)
17:25:39 <davidmichaelkarr> anipbu: What's the difference between "https://git.opendaylight.org/gerrit/docs" in that doc and "https://git.opendaylight.org/gerrit/p/docs.git" (added "p") from https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=summary ?
17:25:42 <anipbu> LuisGomez: Glad you could join us.  No questions yet regarding distribution.
17:28:12 <anipbu> davidmichaelkarr: I'm not sure the first one goes anywhere, the second link can be used to clone a project such as "git clone https://git.opendaylight.org/gerrit/p/docs.git" and the first is just a summery of patches to the docs project.
17:29:10 <Mknair> anipbu: here is the link for Atrium system test https://wiki.opendaylight.org/view/Atrium:Boron_Test_Plan
17:29:45 <davidmichaelkarr> anipbu: The doc you just gave me the link for says to clone "git clone https://git.opendaylight.org/gerrit/docs".  The summary page says it has the "p", your doc says it doesn't.
17:30:09 <anipbu> Mknair: could you please add a link to that boron test plan to to the section under Boron: https://wiki.opendaylight.org/view/CrossProject:Integration_Group/Project_System_Test_Report
17:30:43 <Mknair> Sure
17:32:38 <davidmichaelkarr> anipbu: I cloned both, and they seem very similar, but what's the difference?
17:32:52 <anipbu> davidmichaelkarr: good point, I just tried it out.  seems like you can git clone using either url.  Thanks for pointing that out.
17:33:01 <vrpolak> LuisGomez: Questions for distribution? I may have one. M3 report wants to have all features merged, but 37210 needs 39427 which needs controller-merge job fixed. Question is how to explain this in the M3 report.
17:33:02 <anipbu> davidmichaelkarr: they are both the same.
17:33:11 <davidmichaelkarr> anipbu: Ok.
17:33:53 <anipbu> Mknair: Your features are not in the distribution.  This is a requirement for M3.  https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features-index/src/main/resources/features.xml;
17:34:53 <anipbu> LuisGomez: Seems DIDM is still missing from the distribution.  Do they still have issues preventing them from being added to the distribution?
17:35:19 <Mknair> anipbu: our code is not yet in the repository.  We plan to do along with that
17:35:22 <jamoluhrsen> anipbu, LuisGomez: I think there is another project missing from distro too.
17:35:29 <jamoluhrsen> netide?
17:35:55 <Mknair> Along with Atrium code push
17:36:32 <LuisGomez> those projects missing in the distribution should be added by the projects themselves
17:36:45 <LuisGomez> they were removed for different reasons in the past
17:37:03 <jamoluhrsen> LuisGomez: agreed, but I bet they forget.
17:37:26 <LuisGomez> we can send a mail to remind those that are missing
17:38:21 <anipbu> Mknair: LuisGomez: Once the issues with DIDM is resolved and code can be pushed, please add Atrium features to the distribution as soon as possible.  M3 is the deadline for adding features into the distribution.  Any further delay prevents us from testing the distribution with all the Boron features.
17:40:37 <anipbu> gdavid: here is the unimgr test plan for Beryllium.  You can use the content there if things have not changed much.  https://wiki.opendaylight.org/view/UNIMgr:Test_Plan
17:40:50 <LuisGomez> anipbu, i think there is a clear M3 item for projects to check and add their features in the distribution. After M3 if we miss some project we will send mail to notify them.
17:41:34 <anipbu> gdavid: you can then cross check with the Boron System Test Template for any additional items.  https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template
17:41:52 <gdavid> anipbu thx
17:42:58 <Mknair> anipbu:sure we will follow up with didm team
17:43:23 <anipbu> vishnoianil: we seem to be missing the Boron system test plan template for ovsdb.  This is a requirement for M3.  https://wiki.opendaylight.org/view/CrossProject:Integration_Group/Project_System_Test_Report
17:43:46 <LuisGomez> vrpolak, i would recommend to send mail to controller project to say your features are blocked by their merge job?
17:44:50 <LuisGomez> at least the distribution fearures do not impact anybody so they can be merged after M3
17:46:02 <anipbu> davidmichaelkarr: since your project has a unique distribution mechanism, have you worked with the releng team to set up a proper distribution channel for your components?  I believe you will be using an eclipse update site (I may be wrong since I am not too familiar with eclipse plugins).
17:47:27 <vrpolak> LuisGomez: Alright, I will take one more look on why it is failing, and send an e-mail after that.
17:49:08 <anipbu> vrpolak: LuisGomez: jamoluhrsen: Please note that VPNService is getting split into 3 parts -> GENIUS, NetVirt and VPNService.  Do you think this will have impact to distribution, csit suites?
17:49:36 <jamoluhrsen> anipbu: it does have an impact to CSIT suites.  we are fighting through that currently in the netvirt part.
17:50:36 <LuisGomez> i guess there will be updates in int/test and int/dist after this split.
17:50:58 <anipbu> Prem: ^^^ (See Note Above)
17:51:36 <LuisGomez> and releng/builder too…
17:51:56 <Prem> anipu:  Yes
17:53:10 <Prem> anipbu: I believe GENIUS would have new set of CSIT test cases / Netvirt would inherit few from existing VPNService
17:53:50 <vrpolak> anipbu: For distribution, such a split usually means just that the same features should be taken from a different feature repositories. If projects update their repository references in features-index at the appropriate time, everything should go smoothly.
17:55:40 <anipbu> Prem: also as part of M3 requirement, documentation outlines would be needed for the new projects from the split as well.
17:56:45 <jamoluhrsen> Prem, anipbu: the netvirt from vpnservice will inherit the csit from vpnservice as well as more from the old netvirt.  it should get a lot of good coverage once we get things right.
17:57:08 <anipbu> vrpolak: and features-test as well.  But I notice that genius, netvirt already exists in https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features-test/src/main/resources/features.xml;
17:57:37 <anipbu> vrpolak: can we safely assume no further actions are needed on features-test side for the split?
17:58:49 <Prem> anipbu:  I will share the current VPNService asciidoc with new project PTLs
17:59:23 <anipbu> jamoluhrsen: great!  Lots of migration happening here.  But does vpnservice, genius, netvirt, ovsdb meet regularly to discuss the discuss the complex migration in Boron?
18:00:04 <Prem> anipbu: jamoluhrsen:  Not yet, we should start it
18:00:10 <jamoluhrsen> anipbu: I think some of this discussion happens on the OVSDB call on Tuesday's (8am PST), but there must be other stuff happening.
18:00:20 <vrpolak> anipbu: A features-test edit is only required if the feature being migrated also changes its name (or version), which is not usually the case.
18:01:54 <anipbu> Okay we are at the top of the hour.  Thank you everybody for coming in and asking questions regarding M3.  I hope folks found the Boron M3 IRC Working Session to be useful and productive.
18:02:35 <anipbu> Special thanks to all the folks from the SUPPORT projects for providing their expertise in answering questions as well.
18:03:09 <LuisGomez> vrpolak, fyi i think this patch will unblock controller merge: https://git.opendaylight.org/gerrit/#/c/39721/
18:03:27 <anipbu> Do folks have any additional questions regarding M3, otherwise I will end the meeting.  Feel free to continue the discussion on the mailing list, etc.
18:03:52 <Prem> anipbu:  Thanks for your support and hard work!
18:05:42 <anipbu> #topic cookies
18:05:45 <anipbu> #endmeeting