From: Anil Vishnoi [mailto:vishnoia...@gmail.com] Sent: Thursday, October 12, 2017 2:22 PM To: Faseela K <faseel...@ericsson.com> Cc: Muthukumaran K <muthukumara...@ericsson.com>; Tom Pantelis <tompante...@gmail.com>; infrautils-...@lists.opendaylight.org; controller-dev@lists.opendaylight.org; R Srinivasan E <r.e.sriniva...@ericsson.com>; Dayavanti Gopal Kamath <dayavanti.gopal.kam...@ericsson.com> Subject: Re: [controller-dev] Expose Datastore health to applications via infrautils.diagstatus
On Thu, Oct 12, 2017 at 1:38 AM, Faseela K <faseel...@ericsson.com<mailto:faseel...@ericsson.com>> wrote: I had the same discussion with Michael. Since infrautils is placed as some entity below controller/md-sal, he had the opinion that the service should be registered from above and the status should be exposed. Yeah, we had brief discussion about it in DDF, and i think that's the ideal way to do it. So here is how diagstatus module works – any application should register as a “service” with the framework, report an initial status(using the APIs provided by diagstatus). There is another OsgiService “ServiceStatusProvider” exposed, and if applications implement the same, that will be called everytime an external request is made to get the current service status. Isn't it that in both the approach, controller will have to depend on infrautils? Yes! Thanks, Faseela
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
