Hi Reka, Isuru, I was trying to model a nested dependency utilizing the dependency section in the group definition but I am unsure how to do it.
For example, I define a group1, group2 and group3
Group3 is a subgroup of group2,
Group2 is a sub group of group1
Group7 has a cartridge c3
Group6 has a cartridge c2
Group5 has a cartridge c1
Group1 (c1) should start up after group2, group2 (c2) should start up after
group3 (c3)
The only way to model the dependencies seemed to be to model it in the
dependency section in the application definition:
"dependencies": {
"startupOrders": [
"cartridge.c3alias51,group.group6alias",
"group.group5alias,group.group6alias"
],
"killBehaviour": "kill-dependents"
}
However, deploying the application didn’t start any cartridges (VMs), not even
the one without dependency (in group7, alias: “c3alias51”) ? Did I specify the
dependencies wrong or something else in the app / group defs ?
I attached the group / application definition to the email,
Thanks
Martin
From: Martin Eppel (meppel)
Sent: Monday, October 13, 2014 4:37 PM
To: Reka Thirunavukkarasu; Isuru Haththotuwa
Cc: dev; Udara Liyanage
Subject: RE: [Grouping][testing] Hierarchical Monitors with Composite
Application
Hi Reka,
I run a scenario similar to yours (see attached application json
(application_test_app5a, group5.json, group6.json) :
Deployed groups :
group5: cartridges: [c1, c2], subgroups: [group6]
group6: cartridges: [c2], subgroups: []
Deployed Application :
Dependencies: startupOrders: ["cartridge.c1xxx,group.group6alias"]
What I noticed is that all cartridges were started up although the cartridges
are not going into active state (which is an issue in my test environment).
I tested a similar scenario with only cartridges defined in the application:
Deployed Application (see attached json (application_test_app5b.json):
"subscribables": ["c1alias51", "c2alias51", "c1xxx"
"dependencies": {
"startupOrders": [
"cartridge.c1alias51,cartridge.c2alias51",
"cartridge.c2alias51,cartridge.c1xxx"
],
and the system correctly brings up c1alias51 and then blocks all other
cartridges (since they are not going active)
Thanks
Martin
From: Reka Thirunavukkarasu [mailto:r...@wso2.com]
Sent: Sunday, October 12, 2014 11:24 PM
To: Isuru Haththotuwa
Cc: dev; Martin Eppel (meppel); Udara Liyanage
Subject: Re: [Grouping][testing] Hierarchical Monitors with Composite
Application
Hi
I have fixed them and committed it. Now that hierarchical monitors with the
given definition is working fine..
Thanks,
Reka
On Mon, Oct 13, 2014 at 12:19 AM, Isuru Haththotuwa
<isu...@apache.org<mailto:isu...@apache.org>> wrote:
On Mon, Oct 13, 2014 at 12:03 AM, Reka Thirunavukkarasu
<r...@wso2.com<mailto:r...@wso2.com>> wrote:
Thanks Isuru for pointing out..
Since i got to restarted while i was testing, i didn't face this issue. When i
tried with the fresh setup, i faced the same issue..I did a fix for this. Will
test it and update on it..
Great! Thanks Reka.
Thanks,
Reka
On Sun, Oct 12, 2014 at 11:55 PM, Isuru Haththotuwa
<isu...@apache.org<mailto:isu...@apache.org>> wrote:
My Application is something similar to below:
[Inline image 1]
Both the cluster php1, php2 are notifying the parent as they are Activated.
Also the group1 is also notifying the parent as its Activated. However, seems
the group2 is not notifying the parent of its activation. Looking in to this
further.
On Sun, Oct 12, 2014 at 5:55 PM, Isuru Haththotuwa
<isu...@apache.org<mailto:isu...@apache.org>> wrote:
Hi Reka,
Great news!!
I tried with a similar Application, however there were no instance spawned for
the top level Cartridge. But, both the Groups were successfully activated.
Might be an issue with the definitions I used, have attached there here. Will
check on this more.
On Sun, Oct 12, 2014 at 11:09 AM, Reka Thirunavukkarasu
<r...@wso2.com<mailto:r...@wso2.com>> wrote:
Hi all,
I have tested the hierarchical monitors with the attached sample application
which has group2 and tomcat cartridge as in top level. group2 further refers to
tomcat and group1. group1 further refers to php. Their startup order has also
defined in the definitions as below mentioned:
For Eg:
app (group2, tomcat) implies that group2 should be started before tomcat.
The application structure is like:
--------------- app (group2,
tomcat)----------------
|
|
--------group2 (group1, tomcat)-------
tomcat
| |
tomcat group1
|
php
For the above composite application structure, Application successfully became
active after its children activated according to the start up order definied.
Please find the samples as attached. If you encounter any issue while testing,
can you update the thread?
Thanks,
Reka
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile:
+94776442007
--
<tel:%2B94776442007>
Thanks and Regards,
Isuru H.
<tel:%2B94776442007>
+94 716 358 048
--
<tel:%2B94776442007>
Thanks and Regards,
Isuru H.
<tel:%2B94776442007>
+94 716 358 048<tel:%2B94776442007>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
--
<tel:%2B94776442007>
Thanks and Regards,
Isuru H.
<tel:%2B94776442007>
+94 716 358 048<tel:%2B94776442007>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
group6.json
Description: group6.json
group7.json
Description: group7.json
application_test_app5.json
Description: application_test_app5.json
group5.json
Description: group5.json
