Hi Martin,
On Tue, Oct 14, 2014 at 5:07 AM, Martin Eppel (meppel) <[email protected]>
wrote:
> 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"]
>
I think that the issue here is, startup order didn't get specified properly
for the group. We expected to have the startup order in the group
definition itself for the group as needed. We can define the startuporder
for top level groups or cartridges in the application. Since your
application-a uses group5 and c1 as in top level, you can define the
startup order for those two only in the
application(application_test_app5a.json) as below. Also, we will have to
use alias to define startup order in the application.
startupOrders: ["cartridge.c1xxx","group. group5alias"]
Then in your group5 (group.json), you can define the startup order as
below. Group will have to use the group name when defining startup order as
the alias is not known when we write the group definition.
startupOrders: ["group.group6, cartridge.c1, cartridge.c2"]
In this case, when stratos chooses group5 to start up, group6 will bring up
first among group5's children. Once group6 becomes active, C1 will be
brought up according to startup order. Once C1 becomes active, C2 will be
brought up.
Please share your thought on this..
>
>
> 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)
>
As i explained above, since you have defined the startup order for the top
level cartridges which directly used in application, it is working fine.
Thanks,
Reka
>
>
> Thanks
>
>
>
> Martin
>
> *From:* Reka Thirunavukkarasu [mailto:[email protected]]
> *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 <[email protected]>
> wrote:
>
>
>
>
>
> On Mon, Oct 13, 2014 at 12:03 AM, Reka Thirunavukkarasu <[email protected]>
> 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 <[email protected]>
> wrote:
>
> My Application is something similar to below:
>
>
>
>
>
> [image: 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 <[email protected]>
> 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 <[email protected]>
> 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
>
> --
> <%2B94776442007>
>
> <%2B94776442007>
>
>
>
>
>
> *Thanks and Regards, Isuru H. <%2B94776442007>*
>
>
>
> +94 716 358 048
>
> --
> <%2B94776442007>
>
> <%2B94776442007>
>
>
>
>
>
> *Thanks and Regards, Isuru H. <%2B94776442007>*
>
>
>
> +94 716 358 048 <%2B94776442007>
>
>
>
>
>
>
>
> --
>
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
>
> Mobile: +94776442007
>
> --
> <%2B94776442007>
>
> <%2B94776442007>
>
>
>
>
>
> *Thanks and Regards, Isuru H. <%2B94776442007>*
>
>
>
> +94 716 358 048 <%2B94776442007>
>
>
>
>
>
>
>
> --
>
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
>
> Mobile: +94776442007
>
>
>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
