Fix blueprint event handling 44/67444/2
authorTom Pantelis <tompantelis@gmail.com>
Mon, 22 Jan 2018 22:15:22 +0000 (17:15 -0500)
committerStephen Kitt <skitt@redhat.com>
Tue, 23 Jan 2018 08:56:07 +0000 (08:56 +0000)
commit0e0e2378d379e2fbc12d8f93ef41b3267e10f83a
tree014ebc0ad3198be787830c1aadc41b4047ddda2b
parentd77fdd6a0474a32c896903eae4453d800a7189cf
Fix blueprint event handling

The BlueprintBundleTracker registers for blueprint events so it can
log when a bundle finished creating its container, successful or not,
and also has logic to restart the container on dependency failure.
However this was  broken due to changes in Aries. You now have to
register a specific BlueprintListener onstead of a general OGSI
EventHandler.

Also this affected the BlueprintContainerRestartServiceImpl as it
relies on blueprint events to now when all bundles have completed
restart.

Change-Id: Ibb121b3995147a56be7f606ed88e9c1f59e3cd4c
Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
opendaylight/blueprint/src/main/java/org/opendaylight/controller/blueprint/BlueprintBundleTracker.java
opendaylight/blueprint/src/main/java/org/opendaylight/controller/blueprint/BlueprintContainerRestartServiceImpl.java

©2013 OpenDaylight, A Linux Foundation Collaborative Project. All Rights Reserved.
OpenDaylight is a registered trademark of The OpenDaylight Project, Inc.
Linux Foundation and OpenDaylight are registered trademarks of the Linux Foundation.
Linux is a registered trademark of Linus Torvalds.