No - we don't have a plan to push stats directly to TSDR. On Tue, May 24, 2016 at 12:20 PM, YuLing Chen <[email protected]> wrote:
> Hi Abhijit, > > I believe TSDR should be fine with the latest changes/code of > OpenFlowPlugin. We'll double check by some more manual regression testing. > > B.T.W., just to confirm that the stats manager is still pushing data into > the data broker(MD-SAL in-memory data store), right? I heard about some > plan for the stats manager to push directly to TSDR, which might be good > for performance and scalability of the data broker. > > Thanks, > > YuLing > > On Mon, May 23, 2016 at 3:53 PM, Abhijit Kumbhare <[email protected]> > wrote: > >> Sharon, >> >> I assume you guys have worked around this - since you have not raised a >> bug or let us know the exact functionality you need. >> >> Thanks, >> Abhijit >> >> On Tue, Apr 5, 2016 at 6:30 PM, Abhijit Kumbhare <[email protected]> >> wrote: >> >>> Added OpenFlow Plugin. >>> >>> Sharon, >>> >>> First of all can you open a bug on OpenFlow Plugin with the title >>> starting with the string "Li migration: "? Please add the details including >>> what exact functionality you need and why it cannot be achieved or worked >>> around with the new design? >>> >>> Thanks, >>> Abhijit >>> >>> >>> On Tue, Apr 5, 2016 at 4:57 PM, An Ho <[email protected]> wrote: >>> >>>> Hi Sharon, >>>> >>>> Thank you for the clarification. I have remove my comment about TSDR >>>> and OpenFlowPlugin dependency on the tracking spreadsheet. >>>> >>>> In order to facilitate the migration for dependent projects to the >>>> OpenFlowPlugin Lithium design as the default for the Boron release, we >>>> would like dependant projects to identify issues, feedback, objections, and >>>> bugs by 4/7 with a target migration at Boron Offset 1 M2/M3 [2]. >>>> >>>> Would it be possible for you to kindly vote "GO" or "NOGO" and identify >>>> any bugs/issues pending at this spreadsheet [3], including the issues you >>>> mentioned in your email below with regards to the openflow statistics >>>> collector. >>>> >>>> Your feedback is greatly appreciated. Please do not hesitate to reach >>>> out to Abhijit Kumbhare and the OpenFlowPlugin team if you have any further >>>> questions regarding the timeline for the migration. >>>> >>>> >>>> Hi Abhijit Kumbhare, >>>> >>>> Is there anyone on the OpenFlowPlugin Team working with TSDR to address >>>> their concerns, specifically the ones Sharon mentioned in the email below? >>>> Has a bug been opened to track their concerns? >>>> >>>> >>>> Best Regards, >>>> An Ho >>>> >>>> [1] >>>> https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-project-report-boron/lastSuccessfulBuild/artifact/dependencies.log >>>> [2] >>>> https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-April/004883.html >>>> [3] >>>> https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=251530127 >>>> >>>> -----Original Message----- >>>> From: Sharon Aicler (saichler) [mailto:[email protected]] >>>> Sent: Tuesday, April 05, 2016 4:36 PM >>>> To: An Ho; [email protected]; Colin Dixon; Abhijit >>>> Kumbhare; [email protected] >>>> Subject: Re: TSDR and OpenFlowPlugin Li Migration >>>> >>>> Hi An, >>>> I explicitly mentioned in the questionnaire that we do have dependency >>>> on OpenFlowPlugin and that we are depended on the yang model. I also >>>> mentioned that the openflow statistics collector is not part of the plugin >>>> and that creates a challenge if it will need to interact directly with TSDR >>>> without passing through the DataBroker. >>>> >>>> >>>> Thanks, >>>> Sharon. >>>> ________________________________________ >>>> From: [email protected] < >>>> [email protected]> on behalf of An Ho < >>>> [email protected]> >>>> Sent: Tuesday, April 5, 2016 4:28 PM >>>> To: [email protected]; Colin Dixon; Abhijit Kumbhare; >>>> [email protected] >>>> Subject: [tsdr-dev] TSDR and OpenFlowPlugin Li Migration >>>> >>>> Hi Yuling C and TSDR Team, >>>> >>>> According to the Boron dependency log, your project has a dependency on >>>> OpenFlowPlugin [1]. However, your team verified in January that no actual >>>> use of the OpenFlowPlugin is made by the TSDR project [2]. >>>> >>>> If you may kindly confirm that this is still true, then I will update >>>> our tracking spreadsheet to indicate that TSDR has no real dependency on >>>> OpenFlowPlugin [3]. >>>> >>>> Best Regards, >>>> An Ho >>>> >>>> [1] >>>> https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-project-report-boron/lastSuccessfulBuild/artifact/dependencies.log >>>> [2] >>>> https://lists.opendaylight.org/pipermail/tsdr-dev/2016-January/000569.html >>>> [3] >>>> https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=251530127 >>>> >>>> >>>> _______________________________________________ >>>> tsdr-dev mailing list >>>> [email protected] >>>> https://lists.opendaylight.org/mailman/listinfo/tsdr-dev >>>> >>> >>> >> >
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
