Handle parent/child relationship in the orchestration engine/console

[ypujante]

Currently the agent handle parent/child relationship, but it is not supported in the orchestration engine (and console). The role of this task will bring support.

Parent/child relationship can be used for:

Example1: webapp
parent = servlet container
children = webapps / wars

Example2: OSGi
parent = OSGi container
children = bundles

The idea is that the lifecycle of the children is obviously related to the lifecycle of the parent but once the parent is up, they can be undeployed/redeployed independently

[mdubey-personal]

We should write unit test to make sure plan generation is working correctly with parent child relationships.
Document using examples on how GLUScripts of parent and child would need to interact with each other.

A more comprehensive test plan for this feature could be:

Create a model with empty container as parent and webapps as children. The testing will include:

• do a deploy of a child without explicitly deploying parent first => container should be started automatically
• do a deploy of only parent => make sure container comes up and stays up
• do a bounce and redeploy of parent => both parent and child should be bounced and redeployed in the right order
• do a bounce and redeploy of child => only child should be bounced and redeployed, parent remains untouched
• stop child and do a bounce of container => make sure child remains down
• stopping container should automatically stop the child first
• make sure all of the above from UI and command line

[ypujante]

Other test case I just thought about:

1. deploy w1 with parent c1
2. change system so that w1 has parent c2

Expected result: w1 is undeployed completely and redeployed in c2

[ypujante]

Implemented with 3.0.0.RC1