stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Eppel (meppel)" <mep...@cisco.com>
Subject RE: [Grouping] Issue with dependencies in nested grouping scenario (termination)
Date Mon, 17 Nov 2014 17:16:06 GMT
Ok,

Let you know how it goes,

Thanks

Martin

From: Reka Thirunavukkarasu [mailto:reka@wso2.com]
Sent: Monday, November 17, 2014 4:38 AM
To: dev
Subject: Re: [Grouping] Issue with dependencies in nested grouping scenario (termination)

Hi Martin,

I have fixed the issues found with current implementation and pushed the changes. Can you
take the pull and try out the same again?

This the result that i got from your definition.

1. Terminating "c1xxx" (deleting the VM through open stack UI) : member becomes obsolete,
VM is restarted – expected
2. terminating "c1alias51": Terminating VM "c1alias51" is restarted – as expected
3. terminating "c1alias61": 1. Terminating cluster "c1alias61" and Termination cluster "c1alias51"
in parallel,  2. Restarted cluster "c1alias61", 3. Restarted cluster "c1alias51"
4. terminating "c1alias71":  1. Terminating cluster "c1alias71", Termination cluster "c1alias61"
and Terminating cluster "c1alias51" in parallel, 2. Restart  cluster "c1alias71", 3. Restart
cluster "c1alias61", 4. Restart cluster "c1alias51"


If there is a start up dependent, then we will have to kill all the dependent instances and
bring them all again using start order. Please note that we have achieved it by terminating
the dependent clusters and recreate them again using the startOrder.

I'm also in the process of testing for terminate-all case. Will update you on that as well.


Thanks,
Reka

On Fri, Nov 14, 2014 at 5:42 PM, Reka Thirunavukkarasu <reka@wso2.com<mailto:reka@wso2.com>>
wrote:
Hi Martin,

I could get only the simple two dependent clusters working..When i tried with your sample,
i got few issues..I'm in the middle of testing the fix to make it working..

I will do more testing on this and update you..

Thanks,
Reka

On Fri, Nov 14, 2014 at 10:55 AM, Reka Thirunavukkarasu <reka@wso2.com<mailto:reka@wso2.com>>
wrote:
Hi Martin,

I will try with your samples and update on how is it going..

Thanks,
Reka

On Fri, Nov 14, 2014 at 5:30 AM, Martin Eppel (meppel) <meppel@cisco.com<mailto:meppel@cisco.com>>
wrote:
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



--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007<tel:%2B94776442007>




--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007<tel:%2B94776442007>




--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007

Mime
View raw message