Hi all, I wrote a test-framework test with two child steps under a test case, call them A and B, where A can't stop unless B has stopped. (My specific example is that A is a VPC and B a host deployed on it.)
At present the test framework shuts down child entities in the order they were started, and so the test fails to stop cleanly. I'll work around this but it feels like it's worth a tweak to Brooklyn: what do you think? - 1. Shall we change the test case to shut down children in LIFO (last in first out) order? Should this be configurable or, in the spirit of Keeping It Simple, be just a change to the behaviour? 2. Would it be worth applying the same logic to the core Brooklyn code for stopping children [1]? Again, should this be configurable or just the new behaviour? What about default policies for shutdown of DynamicCluster? cheers Geoff [1] https://github.com/apache/brooklyn-server/blob/master/core/src/main/java/org/apache/brooklyn/core/entity/trait/StartableMethods.java#L112
