Colin and anyone interested in the carbon-ddf-startup-shutdown.txt, +Jamie G,
on re-reading the the carbon-ddf-startup-shutdown.txt you sent from the summit (was attached to the email below), by way of https://wiki.opendaylight.org/view/Interns/Projects#Cleaner_shutdown_and_startup, it suddenly occurred to me that, without initially realizing, I think I may have actually solved possibly at least some of the requirements re. "how do we know when the controller is up?" as part of the work I did re. "Extended SingleFeatureTest incl. TestBundleDiag" ... The bundles-test thing recently introduced in odlparent, for the SingleFeatureTest incl. TestBundleDiag, probably has something that any future work in this topic ("OpenDaylight startup/shutdown") should look at build upon; see e.g. sources at https://github.com/opendaylight/odlparent/tree/master/bundles-test/src/main/java/org/opendaylight/odlparent/bundlestest I'm not planning to actually do any further work on this front myself (the new SFT seems to work great and add a lot value as-is), but ... if you are getting a student / ODL intern to do anything, or if anyone else reading this is interested doing further work on this topic, then you probably want to look at the bundles-test thing recently I introduced in odlparent and possibly leverage / wrap it for a sort of runtime "ready service", beyond its current use in the (new) SingleFeatureTest incl. TestBundleDiag. Tx, M. -- Michael Vorburger <vorbur...@redhat.com> | IRC: vorburger @freenode | ~ = http://vorburger.ch On Thu, Sep 29, 2016 at 2:29 AM, Colin Dixon <co...@colindixon.com> wrote: > See attached files for raw notes. > > --Colin > > > _______________________________________________ > controller-dev mailing list > controller-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/controller-dev > >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
