Hi Reka, Isuru, I was testing a scenario with nested groups:
"standalone" cartridge "cisco_sample_vm" (alias "c1xxx") - not defined in a
group, only in application
group7: has a cartridge "cisco_sample_vm" (alias "c1alias71") , no dependencies
group6: has a cartridge "cisco_sample_vm" ("c1alias61"), dependency on group7,
"terminationBehaviour": "terminate-dependents"
group5: has a cartridge "cisco_sample_vm" ("c1alias51"), dependency on group6,
"terminationBehaviour": "terminate-dependents"
startup works as expected : 1. "c1alias71", 2. "c1alias61", 3. "c1alias51"
Termination shows the following:
1. Terminating "c1xxx" (deleting the VM through open stack UI) : member becomes
obsolete, VM is restarted - expected
2. terminating "c1alias51": VM "c1alias51" is restarted - as expected
3. terminating "c1alias61": no change - expected result: 1. Termination of
"c1alias51", 2. Restart of "c1alias61",
4. terminating "c1alias71": no change - expected result: 1. Termination of
"c1alias61", 2. Termination of "c1alias51", 3. Restart of "c1alias71", 4.
Restart of "c1alias61", 5. Restart of "c1alias51"
I attached the group definitions, application definitions (I can provide logs
with debug enabled per request, didn't want to send them to everyone on the
mailer)
Let me know I am wrong in my assumptions or the jsons are incorrect,
Thanks
Martin
group6c.json
Description: group6c.json
group7c.json
Description: group7c.json
application_test_app5c.json
Description: application_test_app5c.json
group5c.json
Description: group5c.json
