It would be cleaner to include the datastore check apart from just ready state.
When the application-features get installed, corresponding yang models are absorbed to build schema context incrementally. There is no absolute telling when this completes depending upon how quick application features get installed (Which in turn depend upon their dependency graph(s)). The schemacontext present at the time of restoration will be used as it is for validating and restoring data during scenarios like reboot. Though most of the apps get installed as part of boot features, it would be better to include this exclusive check in addition to standard ready check Hope we are all in sync Regards Muthu From: Faseela K Sent: Tuesday, November 21, 2017 10:46 PM To: [email protected] Cc: [email protected]; Sam Hague; Dayavanti Gopal Kamath; Vivek Srivastava V; Muthukumaran K Subject: Proposing infrautils.ready integration for openflowplugin Hi Shuva/Arun As a follow up to diagstatus integration to openflowplugin, I would like to propose the integration of infrautils.ready for openflowplugin. This way openflowplugin can open the southbound ports after all bundles have come up properly. Also diagstatus can fetch the dynamic service status based on the current southbound connection status as well as other criteria. This will help in many cases, including initial system bring up as well as cluster reboot, as there is enough time for all applications to come up gracefully before they start receiving southbound events. Please let us know your thoughts on the same. Thanks, Faseela
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
