You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Imesh Gunaratne <im...@apache.org> on 2015/02/15 10:26:14 UTC
[Discuss] Fixing Grouping Functionality
Hi Devs,
I just did a quick test to verify grouping functionality with sample
applications and following is the current status:
ApplicationStatusNotescomplex-appNot Activatingcomplex-app-with-lbNot
Activatingdependent-scaling/sample-cartridgesActivates but found few
errorsArtifact
update event is not publisheddependent-scaling/sample-groupsNot Activating
group-cartridgesNot ActivatingArtifact update event is not published
group-scalingNot ActivatingArtifact update event is not published
group-scaling-v1Not Activatingmore-complex-appNot ActivatingArtifact update
event is not publishednested-groupNot ActivatingArtifact update event is
not publishedsingle-cartridgeOKsingle-group-group-scalingOKsingle-group-v1Not
ActivatingArtifact update event is not publishedsingle-group-v2Not
ActivatingArtifact update event is not publishedsingle-group-v3Not
ActivatingApplication deployment stops at some point
We have 14 sample applications now and only 2 of them get activated
properly. Please find more details in the below spread-sheet:
Sample Applications - Current Status.xlsx
<https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>
The above test was done with Mock IaaS and I see an issue in ADC where it
cannot find the application while trying to publish the Artifact Updated
event once Instance Started is received. I'm now investigating this.
Thanks
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Fixing Grouping Functionality
Posted by Imesh Gunaratne <im...@apache.org>.
Hi Reka,
A good point, yes when we use aliases in cartridge groups we can only use a
cartridge group once in an application. Yes as the next step we will
introduce logic to auto-generate aliases which will solve most of the
problems.
Thanks
On Sat, Feb 21, 2015 at 11:43 AM, Reka Thirunavukkarasu <re...@wso2.com>
wrote:
> Hi
>
> In that case, are we defining alias in the cartridge group as well as in
> application? If i need to use same group more than one, then do i need to
> create two cartridge group?
>
> Even when using group names in dependency section of the cartridge groups,
> we were able to define the a group more than once in the application as
> part of instantiating the group.
>
> If we are going with auto-generating the alias, then this issue will be
> solved with that..
>
> Thanks,
> Reka
>
> On Fri, Feb 20, 2015 at 11:06 PM, Imesh Gunaratne <im...@apache.org>
> wrote:
>
>> Hi Reka,
>>
>> Yes we are now allowing to define aliases for both groups and cartridges
>> now. The problem with using group names is that it restricts the user to
>> only define a group once in an application.
>>
>> BTW we have a plan to generate all the aliases in applications based on
>> the application alias/name.
>>
>> Thanks
>>
>> On Sat, Feb 21, 2015 at 10:38 AM, Reka Thirunavukkarasu <re...@wso2.com>
>> wrote:
>>
>>> Hi Imesh,
>>>
>>> On Fri, Feb 20, 2015 at 5:57 AM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Hi Devs,
>>>>
>>>> I fixed core grouping functionality in master branch. Now all grouping
>>>> features are working as expected. Following are the fixes done:
>>>>
>>>> - Added a validation to verify cartridges defined in cartridge groups
>>>> in applications against the cartridge group definitions.
>>>> - Fixed cartridge type/alias, group name/alias mixup in application
>>>> deployment process.
>>>> - Now we can define groups and cartridges more than once in an
>>>> application and use aliases to identify them.
>>>>
>>>
>>> AFAIK, we were able to define groups or cartridges more than one in
>>> earlier as well in pre-alpha. This functionality was working fine. In that
>>> case, we allowed users to define dependencies in the application using
>>> aliases and in the cartridge group using group names. Have we changed
>>> everywhere to use aliaes now? Are we allowing users to define alias in the
>>> cartridge group when defining the dependency section?
>>>
>>> Thanks,
>>> Reka
>>>
>>> - Dependency reference identifier is changed to alias:
>>>>
>>>> "dependencies": {
>>>>
>>>> "startupOrders": [
>>>> "group.mysql-php-group1,cartridge.tomcat1"
>>>> ],
>>>> "terminationBehaviour": "terminate-none"
>>>> }
>>>>
>>>> - Cartridge groups can use the same format for defining dependencies.
>>>> The only requirement is to use the same aliases in the application.
>>>> - Added informative logs to identify the steps in the application
>>>> deployment process:
>>>>
>>>> Monitor scheduled: [type] cluster [component] mysql1.mysql.domain
>>>> Starting monitor: [type] cluster [component] mysql1.mysql.domain
>>>> Monitor started successfully: [type] cluster [component]
>>>> mysql1.mysql.domain [dependents] php1.php.domain [startup-time] 1
>>>> seconds
>>>>
>>>> *Wordpress Sample Application:*
>>>>
>>>>
>>>> Wordpress application consists of a cartridge group which includes a
>>>> MySQL cartridge and PHP cartridge. The cartridge
>>>> group defines a startup dependency to first start MySQL cluster and
>>>> then the PHP cluster second once the MySQL cluster
>>>> is active. Group scaling has been disabled in MySQL, PHP group.
>>>>
>>>>
>>>> https://github.com/apache/stratos/tree/master/samples/applications/wordpress
>>>>
>>>> *Wordpress Extended V1 Application*
>>>>
>>>>
>>>>
>>>> Wordpress extended v1 application consists of a cartridge group which
>>>> includes a MySQL cartridge and PHP cartridge and
>>>> a Tomcat cartridge at the top level. The cartridge group defines a
>>>> startup dependency to first start MySQL cluster and
>>>> then the PHP cluster once the MySQL cluster is active. Group scaling
>>>> has been disabled in MySQL, PHP group. The
>>>> application has defined a startup dependency to first start the MySQL,
>>>> PHP group clusters and then the Tomcat cluster.
>>>>
>>>>
>>>> https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v1
>>>>
>>>> *Wordpress Extended V2 Application*
>>>>
>>>>
>>>>
>>>>
>>>> Wordpress extended v2 application consists of a cartridge group which
>>>> includes a MySQL cartridge and PHP cartridge and
>>>> a Tomcat cartridge at the top level. The cartridge group defines a
>>>> startup dependency to first start MySQL cluster and
>>>> then the PHP cluster once the MySQL cluster is active. Group scaling
>>>> has been enabled in MySQL, PHP group and the
>>>> maximum number of group instances has been set to two. The application
>>>> has defined a startup dependency to first start
>>>> the MySQL, PHP group clusters and then the Tomcat cluster.
>>>>
>>>>
>>>> https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v2
>>>>
>>>> Thanks
>>>>
>>>>
>>>> On Thu, Feb 19, 2015 at 12:53 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> I have now added a validation to verify cartridge groups in
>>>>> applications, commit revision: 9b0b3df2fd93024fe725b87a0c59fdfd672e3d50
>>>>>
>>>>> On Thu, Feb 19, 2015 at 9:54 AM, Reka Thirunavukkarasu <re...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> That's great Imesh..Yah..We didn't implement the validation in the
>>>>>> pre-alpha due to the time constraint..
>>>>>>
>>>>>> Thanks,
>>>>>> Reka
>>>>>>
>>>>>> On Wed, Feb 18, 2015 at 9:15 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Thanks Reka! Following are my current observations:
>>>>>>>
>>>>>>> - Currently there are no validations to verify whether a group added
>>>>>>> to an application has defined all the cartridges. At the moment this is not
>>>>>>> detected at any stage.
>>>>>>> - There are no validations to verify aliases.
>>>>>>> - IMO without validations, due to the complexity of the composite
>>>>>>> application model, it is nearly impossible for an user to figure out what's
>>>>>>> wrong with his application, which means validations are a must!
>>>>>>> - We need to use the term "Reference" when referring an already
>>>>>>> defined entity. For an example when using a cartridge group in an
>>>>>>> application we need to call it Group Reference. Otherwise users may think
>>>>>>> that they are defining the cartridge group inline.
>>>>>>> - Aliases, group names and ids are mixed in deployment process.
>>>>>>>
>>>>>>> I'm now in the process of fixing above.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Thu, Feb 19, 2015 at 9:26 AM, Reka Thirunavukkarasu <
>>>>>>> reka@wso2.com> wrote:
>>>>>>>
>>>>>>>> Yah Imesh, Grouping functionality has been tested in the pre-alpha
>>>>>>>> and most of the features were working fine. We will need to fix some other
>>>>>>>> edge cases..
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Reka
>>>>>>>>
>>>>>>>> On Wed, Feb 18, 2015 at 7:15 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I think I found the root cause of the most of the grouping
>>>>>>>>> functionality issues after debugging it for nearly a day.
>>>>>>>>>
>>>>>>>>> The problem seems to be with the usage of aliases and ids. AFAIK
>>>>>>>>> grouping functionality worked without a problem in pre-alpha there after it
>>>>>>>>> broke when we did some fixes related to aliases.
>>>>>>>>>
>>>>>>>>> I'm now review this and doing a fix.
>>>>>>>>>
>>>>>>>>> On Tue, Feb 17, 2015 at 6:36 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>> > wrote:
>>>>>>>>>
>>>>>>>>>> The above issue has occurred because of the time it takes to SM
>>>>>>>>>> to receive the application created event. Now I have fixed this my making a
>>>>>>>>>> service call from SM to AS to find cluster id of a given application,
>>>>>>>>>> cartridge alias rather than relying on the application events.
>>>>>>>>>>
>>>>>>>>>> This fix is now available in master branch.
>>>>>>>>>>
>>>>>>>>>> On Sun, Feb 15, 2015 at 5:15 PM, Imesh Gunaratne <
>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>> I think I found the reason for not publishing Artifact Updated
>>>>>>>>>>> event. It looks like the Mock IaaS is responding fast and SM is receiving
>>>>>>>>>>> the Instance Started event before receiving the Application Created event.
>>>>>>>>>>> I'm now fixing this.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne <
>>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>>
>>>>>>>>>>>> I just did a quick test to verify grouping functionality with
>>>>>>>>>>>> sample applications and following is the current status:
>>>>>>>>>>>>
>>>>>>>>>>>> ApplicationStatusNotescomplex-appNot Activating
>>>>>>>>>>>> complex-app-with-lbNot Activating
>>>>>>>>>>>> dependent-scaling/sample-cartridgesActivates but found few
>>>>>>>>>>>> errorsArtifact update event is not published
>>>>>>>>>>>> dependent-scaling/sample-groupsNot Activatinggroup-cartridgesNot
>>>>>>>>>>>> ActivatingArtifact update event is not publishedgroup-scalingNot
>>>>>>>>>>>> ActivatingArtifact update event is not published
>>>>>>>>>>>> group-scaling-v1Not Activatingmore-complex-appNot ActivatingArtifact
>>>>>>>>>>>> update event is not publishednested-groupNot ActivatingArtifact
>>>>>>>>>>>> update event is not publishedsingle-cartridgeOK
>>>>>>>>>>>> single-group-group-scalingOKsingle-group-v1Not ActivatingArtifact
>>>>>>>>>>>> update event is not publishedsingle-group-v2Not ActivatingArtifact
>>>>>>>>>>>> update event is not publishedsingle-group-v3Not ActivatingApplication
>>>>>>>>>>>> deployment stops at some point
>>>>>>>>>>>> We have 14 sample applications now and only 2 of them get
>>>>>>>>>>>> activated properly. Please find more details in the below spread-sheet:
>>>>>>>>>>>>
>>>>>>>>>>>> Sample Applications - Current Status.xlsx
>>>>>>>>>>>> <https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>
>>>>>>>>>>>>
>>>>>>>>>>>> The above test was done with Mock IaaS and I see an issue in
>>>>>>>>>>>> ADC where it cannot find the application while trying to publish the
>>>>>>>>>>>> Artifact Updated event once Instance Started is received. I'm now
>>>>>>>>>>>> investigating this.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>>
>>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Reka Thirunavukkarasu
>>>>>>>> Senior Software Engineer,
>>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>>> Mobile: +94776442007
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Reka Thirunavukkarasu
>>>>>> Senior Software Engineer,
>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>> Mobile: +94776442007
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Reka Thirunavukkarasu
>>> Senior Software Engineer,
>>> WSO2, Inc.:http://wso2.com,
>>> Mobile: +94776442007
>>>
>>>
>>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Fixing Grouping Functionality
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
Hi
In that case, are we defining alias in the cartridge group as well as in
application? If i need to use same group more than one, then do i need to
create two cartridge group?
Even when using group names in dependency section of the cartridge groups,
we were able to define the a group more than once in the application as
part of instantiating the group.
If we are going with auto-generating the alias, then this issue will be
solved with that..
Thanks,
Reka
On Fri, Feb 20, 2015 at 11:06 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi Reka,
>
> Yes we are now allowing to define aliases for both groups and cartridges
> now. The problem with using group names is that it restricts the user to
> only define a group once in an application.
>
> BTW we have a plan to generate all the aliases in applications based on
> the application alias/name.
>
> Thanks
>
> On Sat, Feb 21, 2015 at 10:38 AM, Reka Thirunavukkarasu <re...@wso2.com>
> wrote:
>
>> Hi Imesh,
>>
>> On Fri, Feb 20, 2015 at 5:57 AM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Hi Devs,
>>>
>>> I fixed core grouping functionality in master branch. Now all grouping
>>> features are working as expected. Following are the fixes done:
>>>
>>> - Added a validation to verify cartridges defined in cartridge groups in
>>> applications against the cartridge group definitions.
>>> - Fixed cartridge type/alias, group name/alias mixup in application
>>> deployment process.
>>> - Now we can define groups and cartridges more than once in an
>>> application and use aliases to identify them.
>>>
>>
>> AFAIK, we were able to define groups or cartridges more than one in
>> earlier as well in pre-alpha. This functionality was working fine. In that
>> case, we allowed users to define dependencies in the application using
>> aliases and in the cartridge group using group names. Have we changed
>> everywhere to use aliaes now? Are we allowing users to define alias in the
>> cartridge group when defining the dependency section?
>>
>> Thanks,
>> Reka
>>
>> - Dependency reference identifier is changed to alias:
>>>
>>> "dependencies": {
>>>
>>> "startupOrders": [
>>> "group.mysql-php-group1,cartridge.tomcat1"
>>> ],
>>> "terminationBehaviour": "terminate-none"
>>> }
>>>
>>> - Cartridge groups can use the same format for defining dependencies.
>>> The only requirement is to use the same aliases in the application.
>>> - Added informative logs to identify the steps in the application
>>> deployment process:
>>>
>>> Monitor scheduled: [type] cluster [component] mysql1.mysql.domain
>>> Starting monitor: [type] cluster [component] mysql1.mysql.domain
>>> Monitor started successfully: [type] cluster [component]
>>> mysql1.mysql.domain [dependents] php1.php.domain [startup-time] 1
>>> seconds
>>>
>>> *Wordpress Sample Application:*
>>>
>>>
>>> Wordpress application consists of a cartridge group which includes a
>>> MySQL cartridge and PHP cartridge. The cartridge
>>> group defines a startup dependency to first start MySQL cluster and then
>>> the PHP cluster second once the MySQL cluster
>>> is active. Group scaling has been disabled in MySQL, PHP group.
>>>
>>>
>>> https://github.com/apache/stratos/tree/master/samples/applications/wordpress
>>>
>>> *Wordpress Extended V1 Application*
>>>
>>>
>>>
>>> Wordpress extended v1 application consists of a cartridge group which
>>> includes a MySQL cartridge and PHP cartridge and
>>> a Tomcat cartridge at the top level. The cartridge group defines a
>>> startup dependency to first start MySQL cluster and
>>> then the PHP cluster once the MySQL cluster is active. Group scaling has
>>> been disabled in MySQL, PHP group. The
>>> application has defined a startup dependency to first start the MySQL,
>>> PHP group clusters and then the Tomcat cluster.
>>>
>>>
>>> https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v1
>>>
>>> *Wordpress Extended V2 Application*
>>>
>>>
>>>
>>>
>>> Wordpress extended v2 application consists of a cartridge group which
>>> includes a MySQL cartridge and PHP cartridge and
>>> a Tomcat cartridge at the top level. The cartridge group defines a
>>> startup dependency to first start MySQL cluster and
>>> then the PHP cluster once the MySQL cluster is active. Group scaling has
>>> been enabled in MySQL, PHP group and the
>>> maximum number of group instances has been set to two. The application
>>> has defined a startup dependency to first start
>>> the MySQL, PHP group clusters and then the Tomcat cluster.
>>>
>>>
>>> https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v2
>>>
>>> Thanks
>>>
>>>
>>> On Thu, Feb 19, 2015 at 12:53 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> I have now added a validation to verify cartridge groups in
>>>> applications, commit revision: 9b0b3df2fd93024fe725b87a0c59fdfd672e3d50
>>>>
>>>> On Thu, Feb 19, 2015 at 9:54 AM, Reka Thirunavukkarasu <re...@wso2.com>
>>>> wrote:
>>>>
>>>>> That's great Imesh..Yah..We didn't implement the validation in the
>>>>> pre-alpha due to the time constraint..
>>>>>
>>>>> Thanks,
>>>>> Reka
>>>>>
>>>>> On Wed, Feb 18, 2015 at 9:15 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Thanks Reka! Following are my current observations:
>>>>>>
>>>>>> - Currently there are no validations to verify whether a group added
>>>>>> to an application has defined all the cartridges. At the moment this is not
>>>>>> detected at any stage.
>>>>>> - There are no validations to verify aliases.
>>>>>> - IMO without validations, due to the complexity of the composite
>>>>>> application model, it is nearly impossible for an user to figure out what's
>>>>>> wrong with his application, which means validations are a must!
>>>>>> - We need to use the term "Reference" when referring an already
>>>>>> defined entity. For an example when using a cartridge group in an
>>>>>> application we need to call it Group Reference. Otherwise users may think
>>>>>> that they are defining the cartridge group inline.
>>>>>> - Aliases, group names and ids are mixed in deployment process.
>>>>>>
>>>>>> I'm now in the process of fixing above.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Thu, Feb 19, 2015 at 9:26 AM, Reka Thirunavukkarasu <reka@wso2.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Yah Imesh, Grouping functionality has been tested in the pre-alpha
>>>>>>> and most of the features were working fine. We will need to fix some other
>>>>>>> edge cases..
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Reka
>>>>>>>
>>>>>>> On Wed, Feb 18, 2015 at 7:15 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I think I found the root cause of the most of the grouping
>>>>>>>> functionality issues after debugging it for nearly a day.
>>>>>>>>
>>>>>>>> The problem seems to be with the usage of aliases and ids. AFAIK
>>>>>>>> grouping functionality worked without a problem in pre-alpha there after it
>>>>>>>> broke when we did some fixes related to aliases.
>>>>>>>>
>>>>>>>> I'm now review this and doing a fix.
>>>>>>>>
>>>>>>>> On Tue, Feb 17, 2015 at 6:36 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> The above issue has occurred because of the time it takes to SM to
>>>>>>>>> receive the application created event. Now I have fixed this my making a
>>>>>>>>> service call from SM to AS to find cluster id of a given application,
>>>>>>>>> cartridge alias rather than relying on the application events.
>>>>>>>>>
>>>>>>>>> This fix is now available in master branch.
>>>>>>>>>
>>>>>>>>> On Sun, Feb 15, 2015 at 5:15 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>> > wrote:
>>>>>>>>>
>>>>>>>>>> I think I found the reason for not publishing Artifact Updated
>>>>>>>>>> event. It looks like the Mock IaaS is responding fast and SM is receiving
>>>>>>>>>> the Instance Started event before receiving the Application Created event.
>>>>>>>>>> I'm now fixing this.
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>> On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne <
>>>>>>>>>> imesh@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi Devs,
>>>>>>>>>>>
>>>>>>>>>>> I just did a quick test to verify grouping functionality with
>>>>>>>>>>> sample applications and following is the current status:
>>>>>>>>>>>
>>>>>>>>>>> ApplicationStatusNotescomplex-appNot Activating
>>>>>>>>>>> complex-app-with-lbNot Activating
>>>>>>>>>>> dependent-scaling/sample-cartridgesActivates but found few
>>>>>>>>>>> errorsArtifact update event is not published
>>>>>>>>>>> dependent-scaling/sample-groupsNot Activatinggroup-cartridgesNot
>>>>>>>>>>> ActivatingArtifact update event is not publishedgroup-scalingNot
>>>>>>>>>>> ActivatingArtifact update event is not publishedgroup-scaling-v1Not
>>>>>>>>>>> Activatingmore-complex-appNot ActivatingArtifact update event
>>>>>>>>>>> is not publishednested-groupNot ActivatingArtifact update event
>>>>>>>>>>> is not publishedsingle-cartridgeOKsingle-group-group-scalingOK
>>>>>>>>>>> single-group-v1Not ActivatingArtifact update event is not
>>>>>>>>>>> publishedsingle-group-v2Not ActivatingArtifact update event is
>>>>>>>>>>> not publishedsingle-group-v3Not ActivatingApplication
>>>>>>>>>>> deployment stops at some point
>>>>>>>>>>> We have 14 sample applications now and only 2 of them get
>>>>>>>>>>> activated properly. Please find more details in the below spread-sheet:
>>>>>>>>>>>
>>>>>>>>>>> Sample Applications - Current Status.xlsx
>>>>>>>>>>> <https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>
>>>>>>>>>>>
>>>>>>>>>>> The above test was done with Mock IaaS and I see an issue in ADC
>>>>>>>>>>> where it cannot find the application while trying to publish the Artifact
>>>>>>>>>>> Updated event once Instance Started is received. I'm now investigating this.
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>>
>>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Reka Thirunavukkarasu
>>>>>>> Senior Software Engineer,
>>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>>> Mobile: +94776442007
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Reka Thirunavukkarasu
>>>>> Senior Software Engineer,
>>>>> WSO2, Inc.:http://wso2.com,
>>>>> Mobile: +94776442007
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Reka Thirunavukkarasu
>> Senior Software Engineer,
>> WSO2, Inc.:http://wso2.com,
>> Mobile: +94776442007
>>
>>
>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
RE: [Discuss] Fixing Grouping Functionality
Posted by "Martin Eppel (meppel)" <me...@cisco.com>.
No problem,
great to hear that we will be able to define same type cartridge dependencies
Thanks
Martin
From: Imesh Gunaratne [mailto:imesh@apache.org]
Sent: Tuesday, February 24, 2015 9:25 PM
To: dev
Subject: Re: [Discuss] Fixing Grouping Functionality
Hi Martin,
I'm sorry yes I missed this question, yes this modification allows us to define dependencies between same type of cartridges.
Thanks
On Wed, Feb 25, 2015 at 6:14 AM, Martin Eppel (meppel) <me...@cisco.com>> wrote:
Resending in case you missed it,
Thanks
Martin
From: Martin Eppel (meppel)
Sent: Saturday, February 21, 2015 9:53 AM
To: dev@stratos.apache.org<ma...@stratos.apache.org>
Subject: RE: [Discuss] Fixing Grouping Functionality
Hi Imesh,
Does this also allow of defining dependencies between same type cartridges (which previously was not possible using the cartridge name) ?
Thanks
Martin
From: Imesh Gunaratne [mailto:imesh@apache.org<ma...@apache.org>]
Sent: Friday, February 20, 2015 10:06 PM
To: dev
Subject: Re: [Discuss] Fixing Grouping Functionality
Hi Reka,
Yes we are now allowing to define aliases for both groups and cartridges now. The problem with using group names is that it restricts the user to only define a group once in an application.
BTW we have a plan to generate all the aliases in applications based on the application alias/name.
Thanks
On Sat, Feb 21, 2015 at 10:38 AM, Reka Thirunavukkarasu <re...@wso2.com>> wrote:
Hi Imesh,
On Fri, Feb 20, 2015 at 5:57 AM, Imesh Gunaratne <im...@apache.org>> wrote:
Hi Devs,
I fixed core grouping functionality in master branch. Now all grouping features are working as expected. Following are the fixes done:
- Added a validation to verify cartridges defined in cartridge groups in applications against the cartridge group definitions.
- Fixed cartridge type/alias, group name/alias mixup in application deployment process.
- Now we can define groups and cartridges more than once in an application and use aliases to identify them.
AFAIK, we were able to define groups or cartridges more than one in earlier as well in pre-alpha. This functionality was working fine. In that case, we allowed users to define dependencies in the application using aliases and in the cartridge group using group names. Have we changed everywhere to use aliaes now? Are we allowing users to define alias in the cartridge group when defining the dependency section?
Thanks,
Reka
- Dependency reference identifier is changed to alias:
"dependencies": {
"startupOrders": [
"group.mysql-php-group1,cartridge.tomcat1"
],
"terminationBehaviour": "terminate-none"
}
- Cartridge groups can use the same format for defining dependencies. The only requirement is to use the same aliases in the application.
- Added informative logs to identify the steps in the application deployment process:
Monitor scheduled: [type] cluster [component] mysql1.mysql.domain
Starting monitor: [type] cluster [component] mysql1.mysql.domain
Monitor started successfully: [type] cluster [component] mysql1.mysql.domain [dependents] php1.php.domain [startup-time] 1 seconds
Wordpress Sample Application:
[cid:image001.png@01D05078.D7676700]
Wordpress application consists of a cartridge group which includes a MySQL cartridge and PHP cartridge. The cartridge
group defines a startup dependency to first start MySQL cluster and then the PHP cluster second once the MySQL cluster
is active. Group scaling has been disabled in MySQL, PHP group.
https://github.com/apache/stratos/tree/master/samples/applications/wordpress
Wordpress Extended V1 Application
[cid:image002.png@01D05078.D7676700]
Wordpress extended v1 application consists of a cartridge group which includes a MySQL cartridge and PHP cartridge and
a Tomcat cartridge at the top level. The cartridge group defines a startup dependency to first start MySQL cluster and
then the PHP cluster once the MySQL cluster is active. Group scaling has been disabled in MySQL, PHP group. The
application has defined a startup dependency to first start the MySQL, PHP group clusters and then the Tomcat cluster.
https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v1
Wordpress Extended V2 Application
[cid:image003.png@01D05078.D7676700]
Wordpress extended v2 application consists of a cartridge group which includes a MySQL cartridge and PHP cartridge and
a Tomcat cartridge at the top level. The cartridge group defines a startup dependency to first start MySQL cluster and
then the PHP cluster once the MySQL cluster is active. Group scaling has been enabled in MySQL, PHP group and the
maximum number of group instances has been set to two. The application has defined a startup dependency to first start
the MySQL, PHP group clusters and then the Tomcat cluster.
https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v2
Thanks
On Thu, Feb 19, 2015 at 12:53 PM, Imesh Gunaratne <im...@apache.org>> wrote:
I have now added a validation to verify cartridge groups in applications, commit revision: 9b0b3df2fd93024fe725b87a0c59fdfd672e3d50
On Thu, Feb 19, 2015 at 9:54 AM, Reka Thirunavukkarasu <re...@wso2.com>> wrote:
That's great Imesh..Yah..We didn't implement the validation in the pre-alpha due to the time constraint..
Thanks,
Reka
On Wed, Feb 18, 2015 at 9:15 PM, Imesh Gunaratne <im...@apache.org>> wrote:
Thanks Reka! Following are my current observations:
- Currently there are no validations to verify whether a group added to an application has defined all the cartridges. At the moment this is not detected at any stage.
- There are no validations to verify aliases.
- IMO without validations, due to the complexity of the composite application model, it is nearly impossible for an user to figure out what's wrong with his application, which means validations are a must!
- We need to use the term "Reference" when referring an already defined entity. For an example when using a cartridge group in an application we need to call it Group Reference. Otherwise users may think that they are defining the cartridge group inline.
- Aliases, group names and ids are mixed in deployment process.
I'm now in the process of fixing above.
Thanks
On Thu, Feb 19, 2015 at 9:26 AM, Reka Thirunavukkarasu <re...@wso2.com>> wrote:
Yah Imesh, Grouping functionality has been tested in the pre-alpha and most of the features were working fine. We will need to fix some other edge cases..
Thanks,
Reka
On Wed, Feb 18, 2015 at 7:15 PM, Imesh Gunaratne <im...@apache.org>> wrote:
I think I found the root cause of the most of the grouping functionality issues after debugging it for nearly a day.
The problem seems to be with the usage of aliases and ids. AFAIK grouping functionality worked without a problem in pre-alpha there after it broke when we did some fixes related to aliases.
I'm now review this and doing a fix.
On Tue, Feb 17, 2015 at 6:36 PM, Imesh Gunaratne <im...@apache.org>> wrote:
The above issue has occurred because of the time it takes to SM to receive the application created event. Now I have fixed this my making a service call from SM to AS to find cluster id of a given application, cartridge alias rather than relying on the application events.
This fix is now available in master branch.
On Sun, Feb 15, 2015 at 5:15 PM, Imesh Gunaratne <im...@apache.org>> wrote:
I think I found the reason for not publishing Artifact Updated event. It looks like the Mock IaaS is responding fast and SM is receiving the Instance Started event before receiving the Application Created event. I'm now fixing this.
Thanks
On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne <im...@apache.org>> wrote:
Hi Devs,
I just did a quick test to verify grouping functionality with sample applications and following is the current status:
Application
Status
Notes
complex-app
Not Activating
complex-app-with-lb
Not Activating
dependent-scaling/sample-cartridges
Activates but found few errors
Artifact update event is not published
dependent-scaling/sample-groups
Not Activating
group-cartridges
Not Activating
Artifact update event is not published
group-scaling
Not Activating
Artifact update event is not published
group-scaling-v1
Not Activating
more-complex-app
Not Activating
Artifact update event is not published
nested-group
Not Activating
Artifact update event is not published
single-cartridge
OK
single-group-group-scaling
OK
single-group-v1
Not Activating
Artifact update event is not published
single-group-v2
Not Activating
Artifact update event is not published
single-group-v3
Not Activating
Application deployment stops at some point
We have 14 sample applications now and only 2 of them get activated properly. Please find more details in the below spread-sheet:
[https://ssl.gstatic.com/docs/doclist/images/icon_11_spreadsheet_list.png] Sample Applications - Current Status.xlsx<https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>
The above test was done with Mock IaaS and I see an issue in ADC where it cannot find the application while trying to publish the Artifact Updated event once Instance Started is received. I'm now investigating this.
Thanks
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007<tel:%2B94776442007>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007<tel:%2B94776442007>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007<tel:%2B94776442007>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Fixing Grouping Functionality
Posted by Imesh Gunaratne <im...@apache.org>.
Hi Martin,
I'm sorry yes I missed this question, yes this modification allows us to
define dependencies between same type of cartridges.
Thanks
On Wed, Feb 25, 2015 at 6:14 AM, Martin Eppel (meppel) <me...@cisco.com>
wrote:
> Resending in case you missed it,
>
>
>
> Thanks
>
>
>
> Martin
>
>
>
> *From:* Martin Eppel (meppel)
> *Sent:* Saturday, February 21, 2015 9:53 AM
> *To:* dev@stratos.apache.org
> *Subject:* RE: [Discuss] Fixing Grouping Functionality
>
>
>
> Hi Imesh,
>
>
>
> Does this also allow of defining dependencies between same type cartridges
> (which previously was not possible using the cartridge name) ?
>
>
>
> Thanks
>
>
>
> Martin
>
>
>
> *From:* Imesh Gunaratne [mailto:imesh@apache.org]
> *Sent:* Friday, February 20, 2015 10:06 PM
> *To:* dev
> *Subject:* Re: [Discuss] Fixing Grouping Functionality
>
>
>
> Hi Reka,
>
>
>
> Yes we are now allowing to define aliases for both groups and cartridges
> now. The problem with using group names is that it restricts the user to
> only define a group once in an application.
>
>
>
> BTW we have a plan to generate all the aliases in applications based on
> the application alias/name.
>
>
>
> Thanks
>
>
>
> On Sat, Feb 21, 2015 at 10:38 AM, Reka Thirunavukkarasu <re...@wso2.com>
> wrote:
>
> Hi Imesh,
>
>
>
> On Fri, Feb 20, 2015 at 5:57 AM, Imesh Gunaratne <im...@apache.org> wrote:
>
> Hi Devs,
>
>
>
> I fixed core grouping functionality in master branch. Now all grouping
> features are working as expected. Following are the fixes done:
>
>
>
> - Added a validation to verify cartridges defined in cartridge groups in
> applications against the cartridge group definitions.
>
> - Fixed cartridge type/alias, group name/alias mixup in application
> deployment process.
>
> - Now we can define groups and cartridges more than once in an application
> and use aliases to identify them.
>
>
>
> AFAIK, we were able to define groups or cartridges more than one in
> earlier as well in pre-alpha. This functionality was working fine. In that
> case, we allowed users to define dependencies in the application using
> aliases and in the cartridge group using group names. Have we changed
> everywhere to use aliaes now? Are we allowing users to define alias in the
> cartridge group when defining the dependency section?
>
> Thanks,
>
> Reka
>
>
>
> - Dependency reference identifier is changed to alias:
>
>
>
> *"dependencies"*: {
>
> *"startupOrders"*: [
>
> *"group.mysql-php-group1,cartridge.tomcat1" *],
> *"terminationBehaviour"*:
> *"terminate-none"*}
>
> - Cartridge groups can use the same format for defining dependencies.
> The only requirement is to use the same aliases in the application.
>
> - Added informative logs to identify the steps in the application
> deployment process:
>
>
>
> Monitor scheduled: [type] cluster [component] mysql1.mysql.domain
>
> Starting monitor: [type] cluster [component] mysql1.mysql.domain
>
> Monitor started successfully: [type] cluster [component]
> mysql1.mysql.domain [dependents] php1.php.domain [startup-time] 1 seconds
>
>
>
> *Wordpress Sample Application:*
>
>
>
>
>
> Wordpress application consists of a cartridge group which includes a MySQL
> cartridge and PHP cartridge. The cartridge
>
> group defines a startup dependency to first start MySQL cluster and then
> the PHP cluster second once the MySQL cluster
>
> is active. Group scaling has been disabled in MySQL, PHP group.
>
>
>
>
> https://github.com/apache/stratos/tree/master/samples/applications/wordpress
>
>
>
> *Wordpress Extended V1 Application*
>
>
>
>
>
>
> Wordpress extended v1 application consists of a cartridge group which
> includes a MySQL cartridge and PHP cartridge and
>
> a Tomcat cartridge at the top level. The cartridge group defines a startup
> dependency to first start MySQL cluster and
>
> then the PHP cluster once the MySQL cluster is active. Group scaling has
> been disabled in MySQL, PHP group. The
>
> application has defined a startup dependency to first start the MySQL, PHP
> group clusters and then the Tomcat cluster.
>
>
>
>
> https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v1
>
>
>
> *Wordpress Extended V2 Application*
>
>
>
>
>
>
>
>
> Wordpress extended v2 application consists of a cartridge group which
> includes a MySQL cartridge and PHP cartridge and
>
> a Tomcat cartridge at the top level. The cartridge group defines a startup
> dependency to first start MySQL cluster and
>
> then the PHP cluster once the MySQL cluster is active. Group scaling has
> been enabled in MySQL, PHP group and the
>
> maximum number of group instances has been set to two. The application has
> defined a startup dependency to first start
>
> the MySQL, PHP group clusters and then the Tomcat cluster.
>
>
>
>
> https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v2
>
>
>
> Thanks
>
>
>
>
>
> On Thu, Feb 19, 2015 at 12:53 PM, Imesh Gunaratne <im...@apache.org>
> wrote:
>
> I have now added a validation to verify cartridge groups in applications,
> commit revision: 9b0b3df2fd93024fe725b87a0c59fdfd672e3d50
>
>
>
> On Thu, Feb 19, 2015 at 9:54 AM, Reka Thirunavukkarasu <re...@wso2.com>
> wrote:
>
> That's great Imesh..Yah..We didn't implement the validation in the
> pre-alpha due to the time constraint..
>
> Thanks,
> Reka
>
>
>
> On Wed, Feb 18, 2015 at 9:15 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
> Thanks Reka! Following are my current observations:
>
>
>
> - Currently there are no validations to verify whether a group added to an
> application has defined all the cartridges. At the moment this is not
> detected at any stage.
>
> - There are no validations to verify aliases.
>
> - IMO without validations, due to the complexity of the composite
> application model, it is nearly impossible for an user to figure out what's
> wrong with his application, which means validations are a must!
>
> - We need to use the term "Reference" when referring an already defined
> entity. For an example when using a cartridge group in an application we
> need to call it Group Reference. Otherwise users may think that they are
> defining the cartridge group inline.
>
> - Aliases, group names and ids are mixed in deployment process.
>
>
>
> I'm now in the process of fixing above.
>
>
>
> Thanks
>
>
>
> On Thu, Feb 19, 2015 at 9:26 AM, Reka Thirunavukkarasu <re...@wso2.com>
> wrote:
>
> Yah Imesh, Grouping functionality has been tested in the pre-alpha and
> most of the features were working fine. We will need to fix some other edge
> cases..
>
> Thanks,
> Reka
>
>
>
> On Wed, Feb 18, 2015 at 7:15 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
> I think I found the root cause of the most of the grouping functionality
> issues after debugging it for nearly a day.
>
>
>
> The problem seems to be with the usage of aliases and ids. AFAIK grouping
> functionality worked without a problem in pre-alpha there after it broke
> when we did some fixes related to aliases.
>
>
>
> I'm now review this and doing a fix.
>
>
>
> On Tue, Feb 17, 2015 at 6:36 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
> The above issue has occurred because of the time it takes to SM to receive
> the application created event. Now I have fixed this my making a service
> call from SM to AS to find cluster id of a given application, cartridge
> alias rather than relying on the application events.
>
>
>
> This fix is now available in master branch.
>
>
>
> On Sun, Feb 15, 2015 at 5:15 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
> I think I found the reason for not publishing Artifact Updated event. It
> looks like the Mock IaaS is responding fast and SM is receiving the
> Instance Started event before receiving the Application Created event. I'm
> now fixing this.
>
>
>
> Thanks
>
>
>
> On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
> Hi Devs,
>
>
>
> I just did a quick test to verify grouping functionality with sample
> applications and following is the current status:
>
>
>
> *Application*
>
> *Status*
>
> *Notes*
>
> complex-app
>
> Not Activating
>
> complex-app-with-lb
>
> Not Activating
>
> dependent-scaling/sample-cartridges
>
> Activates but found few errors
>
> Artifact update event is not published
>
> dependent-scaling/sample-groups
>
> Not Activating
>
> group-cartridges
>
> Not Activating
>
> Artifact update event is not published
>
> group-scaling
>
> Not Activating
>
> Artifact update event is not published
>
> group-scaling-v1
>
> Not Activating
>
> more-complex-app
>
> Not Activating
>
> Artifact update event is not published
>
> nested-group
>
> Not Activating
>
> Artifact update event is not published
>
> single-cartridge
>
> OK
>
> single-group-group-scaling
>
> OK
>
> single-group-v1
>
> Not Activating
>
> Artifact update event is not published
>
> single-group-v2
>
> Not Activating
>
> Artifact update event is not published
>
> single-group-v3
>
> Not Activating
>
> Application deployment stops at some point
>
>
>
> We have 14 sample applications now and only 2 of them get activated
> properly. Please find more details in the below spread-sheet:
>
>
>
> * Sample Applications - Current Status.xlsx
> <https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>*
>
>
>
> The above test was done with Mock IaaS and I see an issue in ADC where it
> cannot find the application while trying to publish the Artifact Updated
> event once Instance Started is received. I'm now investigating this.
>
>
>
> Thanks
>
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
>
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
>
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
>
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
>
>
> --
>
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
>
> Mobile: +94776442007
>
>
>
>
>
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
>
>
>
> --
>
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
>
> Mobile: +94776442007
>
>
>
>
>
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
>
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
>
>
>
> --
>
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
>
> Mobile: +94776442007
>
>
>
>
>
>
>
>
> --
>
> Imesh Gunaratne
>
>
>
> Technical Lead, WSO2
>
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
RE: [Discuss] Fixing Grouping Functionality
Posted by "Martin Eppel (meppel)" <me...@cisco.com>.
Resending in case you missed it,
Thanks
Martin
From: Martin Eppel (meppel)
Sent: Saturday, February 21, 2015 9:53 AM
To: dev@stratos.apache.org
Subject: RE: [Discuss] Fixing Grouping Functionality
Hi Imesh,
Does this also allow of defining dependencies between same type cartridges (which previously was not possible using the cartridge name) ?
Thanks
Martin
From: Imesh Gunaratne [mailto:imesh@apache.org]
Sent: Friday, February 20, 2015 10:06 PM
To: dev
Subject: Re: [Discuss] Fixing Grouping Functionality
Hi Reka,
Yes we are now allowing to define aliases for both groups and cartridges now. The problem with using group names is that it restricts the user to only define a group once in an application.
BTW we have a plan to generate all the aliases in applications based on the application alias/name.
Thanks
On Sat, Feb 21, 2015 at 10:38 AM, Reka Thirunavukkarasu <re...@wso2.com>> wrote:
Hi Imesh,
On Fri, Feb 20, 2015 at 5:57 AM, Imesh Gunaratne <im...@apache.org>> wrote:
Hi Devs,
I fixed core grouping functionality in master branch. Now all grouping features are working as expected. Following are the fixes done:
- Added a validation to verify cartridges defined in cartridge groups in applications against the cartridge group definitions.
- Fixed cartridge type/alias, group name/alias mixup in application deployment process.
- Now we can define groups and cartridges more than once in an application and use aliases to identify them.
AFAIK, we were able to define groups or cartridges more than one in earlier as well in pre-alpha. This functionality was working fine. In that case, we allowed users to define dependencies in the application using aliases and in the cartridge group using group names. Have we changed everywhere to use aliaes now? Are we allowing users to define alias in the cartridge group when defining the dependency section?
Thanks,
Reka
- Dependency reference identifier is changed to alias:
"dependencies": {
"startupOrders": [
"group.mysql-php-group1,cartridge.tomcat1"
],
"terminationBehaviour": "terminate-none"
}
- Cartridge groups can use the same format for defining dependencies. The only requirement is to use the same aliases in the application.
- Added informative logs to identify the steps in the application deployment process:
Monitor scheduled: [type] cluster [component] mysql1.mysql.domain
Starting monitor: [type] cluster [component] mysql1.mysql.domain
Monitor started successfully: [type] cluster [component] mysql1.mysql.domain [dependents] php1.php.domain [startup-time] 1 seconds
Wordpress Sample Application:
[cid:image001.png@01D05050.B2A66740]
Wordpress application consists of a cartridge group which includes a MySQL cartridge and PHP cartridge. The cartridge
group defines a startup dependency to first start MySQL cluster and then the PHP cluster second once the MySQL cluster
is active. Group scaling has been disabled in MySQL, PHP group.
https://github.com/apache/stratos/tree/master/samples/applications/wordpress
Wordpress Extended V1 Application
[cid:image002.png@01D05050.B2A66740]
Wordpress extended v1 application consists of a cartridge group which includes a MySQL cartridge and PHP cartridge and
a Tomcat cartridge at the top level. The cartridge group defines a startup dependency to first start MySQL cluster and
then the PHP cluster once the MySQL cluster is active. Group scaling has been disabled in MySQL, PHP group. The
application has defined a startup dependency to first start the MySQL, PHP group clusters and then the Tomcat cluster.
https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v1
Wordpress Extended V2 Application
[cid:image003.png@01D05050.B2A66740]
Wordpress extended v2 application consists of a cartridge group which includes a MySQL cartridge and PHP cartridge and
a Tomcat cartridge at the top level. The cartridge group defines a startup dependency to first start MySQL cluster and
then the PHP cluster once the MySQL cluster is active. Group scaling has been enabled in MySQL, PHP group and the
maximum number of group instances has been set to two. The application has defined a startup dependency to first start
the MySQL, PHP group clusters and then the Tomcat cluster.
https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v2
Thanks
On Thu, Feb 19, 2015 at 12:53 PM, Imesh Gunaratne <im...@apache.org>> wrote:
I have now added a validation to verify cartridge groups in applications, commit revision: 9b0b3df2fd93024fe725b87a0c59fdfd672e3d50
On Thu, Feb 19, 2015 at 9:54 AM, Reka Thirunavukkarasu <re...@wso2.com>> wrote:
That's great Imesh..Yah..We didn't implement the validation in the pre-alpha due to the time constraint..
Thanks,
Reka
On Wed, Feb 18, 2015 at 9:15 PM, Imesh Gunaratne <im...@apache.org>> wrote:
Thanks Reka! Following are my current observations:
- Currently there are no validations to verify whether a group added to an application has defined all the cartridges. At the moment this is not detected at any stage.
- There are no validations to verify aliases.
- IMO without validations, due to the complexity of the composite application model, it is nearly impossible for an user to figure out what's wrong with his application, which means validations are a must!
- We need to use the term "Reference" when referring an already defined entity. For an example when using a cartridge group in an application we need to call it Group Reference. Otherwise users may think that they are defining the cartridge group inline.
- Aliases, group names and ids are mixed in deployment process.
I'm now in the process of fixing above.
Thanks
On Thu, Feb 19, 2015 at 9:26 AM, Reka Thirunavukkarasu <re...@wso2.com>> wrote:
Yah Imesh, Grouping functionality has been tested in the pre-alpha and most of the features were working fine. We will need to fix some other edge cases..
Thanks,
Reka
On Wed, Feb 18, 2015 at 7:15 PM, Imesh Gunaratne <im...@apache.org>> wrote:
I think I found the root cause of the most of the grouping functionality issues after debugging it for nearly a day.
The problem seems to be with the usage of aliases and ids. AFAIK grouping functionality worked without a problem in pre-alpha there after it broke when we did some fixes related to aliases.
I'm now review this and doing a fix.
On Tue, Feb 17, 2015 at 6:36 PM, Imesh Gunaratne <im...@apache.org>> wrote:
The above issue has occurred because of the time it takes to SM to receive the application created event. Now I have fixed this my making a service call from SM to AS to find cluster id of a given application, cartridge alias rather than relying on the application events.
This fix is now available in master branch.
On Sun, Feb 15, 2015 at 5:15 PM, Imesh Gunaratne <im...@apache.org>> wrote:
I think I found the reason for not publishing Artifact Updated event. It looks like the Mock IaaS is responding fast and SM is receiving the Instance Started event before receiving the Application Created event. I'm now fixing this.
Thanks
On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne <im...@apache.org>> wrote:
Hi Devs,
I just did a quick test to verify grouping functionality with sample applications and following is the current status:
Application
Status
Notes
complex-app
Not Activating
complex-app-with-lb
Not Activating
dependent-scaling/sample-cartridges
Activates but found few errors
Artifact update event is not published
dependent-scaling/sample-groups
Not Activating
group-cartridges
Not Activating
Artifact update event is not published
group-scaling
Not Activating
Artifact update event is not published
group-scaling-v1
Not Activating
more-complex-app
Not Activating
Artifact update event is not published
nested-group
Not Activating
Artifact update event is not published
single-cartridge
OK
single-group-group-scaling
OK
single-group-v1
Not Activating
Artifact update event is not published
single-group-v2
Not Activating
Artifact update event is not published
single-group-v3
Not Activating
Application deployment stops at some point
We have 14 sample applications now and only 2 of them get activated properly. Please find more details in the below spread-sheet:
[https://ssl.gstatic.com/docs/doclist/images/icon_11_spreadsheet_list.png] Sample Applications - Current Status.xlsx<https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>
The above test was done with Mock IaaS and I see an issue in ADC where it cannot find the application while trying to publish the Artifact Updated event once Instance Started is received. I'm now investigating this.
Thanks
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007<tel:%2B94776442007>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007<tel:%2B94776442007>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007<tel:%2B94776442007>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
RE: [Discuss] Fixing Grouping Functionality
Posted by "Martin Eppel (meppel)" <me...@cisco.com>.
Hi Imesh,
Does this also allow of defining dependencies between same type cartridges (which previously was not possible using the cartridge name) ?
Thanks
Martin
From: Imesh Gunaratne [mailto:imesh@apache.org]
Sent: Friday, February 20, 2015 10:06 PM
To: dev
Subject: Re: [Discuss] Fixing Grouping Functionality
Hi Reka,
Yes we are now allowing to define aliases for both groups and cartridges now. The problem with using group names is that it restricts the user to only define a group once in an application.
BTW we have a plan to generate all the aliases in applications based on the application alias/name.
Thanks
On Sat, Feb 21, 2015 at 10:38 AM, Reka Thirunavukkarasu <re...@wso2.com>> wrote:
Hi Imesh,
On Fri, Feb 20, 2015 at 5:57 AM, Imesh Gunaratne <im...@apache.org>> wrote:
Hi Devs,
I fixed core grouping functionality in master branch. Now all grouping features are working as expected. Following are the fixes done:
- Added a validation to verify cartridges defined in cartridge groups in applications against the cartridge group definitions.
- Fixed cartridge type/alias, group name/alias mixup in application deployment process.
- Now we can define groups and cartridges more than once in an application and use aliases to identify them.
AFAIK, we were able to define groups or cartridges more than one in earlier as well in pre-alpha. This functionality was working fine. In that case, we allowed users to define dependencies in the application using aliases and in the cartridge group using group names. Have we changed everywhere to use aliaes now? Are we allowing users to define alias in the cartridge group when defining the dependency section?
Thanks,
Reka
- Dependency reference identifier is changed to alias:
"dependencies": {
"startupOrders": [
"group.mysql-php-group1,cartridge.tomcat1"
],
"terminationBehaviour": "terminate-none"
}
- Cartridge groups can use the same format for defining dependencies. The only requirement is to use the same aliases in the application.
- Added informative logs to identify the steps in the application deployment process:
Monitor scheduled: [type] cluster [component] mysql1.mysql.domain
Starting monitor: [type] cluster [component] mysql1.mysql.domain
Monitor started successfully: [type] cluster [component] mysql1.mysql.domain [dependents] php1.php.domain [startup-time] 1 seconds
Wordpress Sample Application:
[cid:image002.png@01D04DBC.2472AD30]
Wordpress application consists of a cartridge group which includes a MySQL cartridge and PHP cartridge. The cartridge
group defines a startup dependency to first start MySQL cluster and then the PHP cluster second once the MySQL cluster
is active. Group scaling has been disabled in MySQL, PHP group.
https://github.com/apache/stratos/tree/master/samples/applications/wordpress
Wordpress Extended V1 Application
[cid:image004.png@01D04DBC.2472AD30]
Wordpress extended v1 application consists of a cartridge group which includes a MySQL cartridge and PHP cartridge and
a Tomcat cartridge at the top level. The cartridge group defines a startup dependency to first start MySQL cluster and
then the PHP cluster once the MySQL cluster is active. Group scaling has been disabled in MySQL, PHP group. The
application has defined a startup dependency to first start the MySQL, PHP group clusters and then the Tomcat cluster.
https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v1
Wordpress Extended V2 Application
[cid:image006.png@01D04DBC.2472AD30]
Wordpress extended v2 application consists of a cartridge group which includes a MySQL cartridge and PHP cartridge and
a Tomcat cartridge at the top level. The cartridge group defines a startup dependency to first start MySQL cluster and
then the PHP cluster once the MySQL cluster is active. Group scaling has been enabled in MySQL, PHP group and the
maximum number of group instances has been set to two. The application has defined a startup dependency to first start
the MySQL, PHP group clusters and then the Tomcat cluster.
https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v2
Thanks
On Thu, Feb 19, 2015 at 12:53 PM, Imesh Gunaratne <im...@apache.org>> wrote:
I have now added a validation to verify cartridge groups in applications, commit revision: 9b0b3df2fd93024fe725b87a0c59fdfd672e3d50
On Thu, Feb 19, 2015 at 9:54 AM, Reka Thirunavukkarasu <re...@wso2.com>> wrote:
That's great Imesh..Yah..We didn't implement the validation in the pre-alpha due to the time constraint..
Thanks,
Reka
On Wed, Feb 18, 2015 at 9:15 PM, Imesh Gunaratne <im...@apache.org>> wrote:
Thanks Reka! Following are my current observations:
- Currently there are no validations to verify whether a group added to an application has defined all the cartridges. At the moment this is not detected at any stage.
- There are no validations to verify aliases.
- IMO without validations, due to the complexity of the composite application model, it is nearly impossible for an user to figure out what's wrong with his application, which means validations are a must!
- We need to use the term "Reference" when referring an already defined entity. For an example when using a cartridge group in an application we need to call it Group Reference. Otherwise users may think that they are defining the cartridge group inline.
- Aliases, group names and ids are mixed in deployment process.
I'm now in the process of fixing above.
Thanks
On Thu, Feb 19, 2015 at 9:26 AM, Reka Thirunavukkarasu <re...@wso2.com>> wrote:
Yah Imesh, Grouping functionality has been tested in the pre-alpha and most of the features were working fine. We will need to fix some other edge cases..
Thanks,
Reka
On Wed, Feb 18, 2015 at 7:15 PM, Imesh Gunaratne <im...@apache.org>> wrote:
I think I found the root cause of the most of the grouping functionality issues after debugging it for nearly a day.
The problem seems to be with the usage of aliases and ids. AFAIK grouping functionality worked without a problem in pre-alpha there after it broke when we did some fixes related to aliases.
I'm now review this and doing a fix.
On Tue, Feb 17, 2015 at 6:36 PM, Imesh Gunaratne <im...@apache.org>> wrote:
The above issue has occurred because of the time it takes to SM to receive the application created event. Now I have fixed this my making a service call from SM to AS to find cluster id of a given application, cartridge alias rather than relying on the application events.
This fix is now available in master branch.
On Sun, Feb 15, 2015 at 5:15 PM, Imesh Gunaratne <im...@apache.org>> wrote:
I think I found the reason for not publishing Artifact Updated event. It looks like the Mock IaaS is responding fast and SM is receiving the Instance Started event before receiving the Application Created event. I'm now fixing this.
Thanks
On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne <im...@apache.org>> wrote:
Hi Devs,
I just did a quick test to verify grouping functionality with sample applications and following is the current status:
Application
Status
Notes
complex-app
Not Activating
complex-app-with-lb
Not Activating
dependent-scaling/sample-cartridges
Activates but found few errors
Artifact update event is not published
dependent-scaling/sample-groups
Not Activating
group-cartridges
Not Activating
Artifact update event is not published
group-scaling
Not Activating
Artifact update event is not published
group-scaling-v1
Not Activating
more-complex-app
Not Activating
Artifact update event is not published
nested-group
Not Activating
Artifact update event is not published
single-cartridge
OK
single-group-group-scaling
OK
single-group-v1
Not Activating
Artifact update event is not published
single-group-v2
Not Activating
Artifact update event is not published
single-group-v3
Not Activating
Application deployment stops at some point
We have 14 sample applications now and only 2 of them get activated properly. Please find more details in the below spread-sheet:
[https://ssl.gstatic.com/docs/doclist/images/icon_11_spreadsheet_list.png] Sample Applications - Current Status.xlsx<https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>
The above test was done with Mock IaaS and I see an issue in ADC where it cannot find the application while trying to publish the Artifact Updated event once Instance Started is received. I'm now investigating this.
Thanks
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007<tel:%2B94776442007>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007<tel:%2B94776442007>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007<tel:%2B94776442007>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Fixing Grouping Functionality
Posted by Imesh Gunaratne <im...@apache.org>.
Hi Reka,
Yes we are now allowing to define aliases for both groups and cartridges
now. The problem with using group names is that it restricts the user to
only define a group once in an application.
BTW we have a plan to generate all the aliases in applications based on the
application alias/name.
Thanks
On Sat, Feb 21, 2015 at 10:38 AM, Reka Thirunavukkarasu <re...@wso2.com>
wrote:
> Hi Imesh,
>
> On Fri, Feb 20, 2015 at 5:57 AM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Hi Devs,
>>
>> I fixed core grouping functionality in master branch. Now all grouping
>> features are working as expected. Following are the fixes done:
>>
>> - Added a validation to verify cartridges defined in cartridge groups in
>> applications against the cartridge group definitions.
>> - Fixed cartridge type/alias, group name/alias mixup in application
>> deployment process.
>> - Now we can define groups and cartridges more than once in an
>> application and use aliases to identify them.
>>
>
> AFAIK, we were able to define groups or cartridges more than one in
> earlier as well in pre-alpha. This functionality was working fine. In that
> case, we allowed users to define dependencies in the application using
> aliases and in the cartridge group using group names. Have we changed
> everywhere to use aliaes now? Are we allowing users to define alias in the
> cartridge group when defining the dependency section?
>
> Thanks,
> Reka
>
> - Dependency reference identifier is changed to alias:
>>
>> "dependencies": {
>>
>> "startupOrders": [
>> "group.mysql-php-group1,cartridge.tomcat1"
>> ],
>> "terminationBehaviour": "terminate-none"
>> }
>>
>> - Cartridge groups can use the same format for defining dependencies. The
>> only requirement is to use the same aliases in the application.
>> - Added informative logs to identify the steps in the application
>> deployment process:
>>
>> Monitor scheduled: [type] cluster [component] mysql1.mysql.domain
>> Starting monitor: [type] cluster [component] mysql1.mysql.domain
>> Monitor started successfully: [type] cluster [component]
>> mysql1.mysql.domain [dependents] php1.php.domain [startup-time] 1 seconds
>>
>> *Wordpress Sample Application:*
>>
>>
>> Wordpress application consists of a cartridge group which includes a
>> MySQL cartridge and PHP cartridge. The cartridge
>> group defines a startup dependency to first start MySQL cluster and then
>> the PHP cluster second once the MySQL cluster
>> is active. Group scaling has been disabled in MySQL, PHP group.
>>
>>
>> https://github.com/apache/stratos/tree/master/samples/applications/wordpress
>>
>> *Wordpress Extended V1 Application*
>>
>>
>>
>> Wordpress extended v1 application consists of a cartridge group which
>> includes a MySQL cartridge and PHP cartridge and
>> a Tomcat cartridge at the top level. The cartridge group defines a
>> startup dependency to first start MySQL cluster and
>> then the PHP cluster once the MySQL cluster is active. Group scaling has
>> been disabled in MySQL, PHP group. The
>> application has defined a startup dependency to first start the MySQL,
>> PHP group clusters and then the Tomcat cluster.
>>
>>
>> https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v1
>>
>> *Wordpress Extended V2 Application*
>>
>>
>>
>>
>> Wordpress extended v2 application consists of a cartridge group which
>> includes a MySQL cartridge and PHP cartridge and
>> a Tomcat cartridge at the top level. The cartridge group defines a
>> startup dependency to first start MySQL cluster and
>> then the PHP cluster once the MySQL cluster is active. Group scaling has
>> been enabled in MySQL, PHP group and the
>> maximum number of group instances has been set to two. The application
>> has defined a startup dependency to first start
>> the MySQL, PHP group clusters and then the Tomcat cluster.
>>
>>
>> https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v2
>>
>> Thanks
>>
>>
>> On Thu, Feb 19, 2015 at 12:53 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> I have now added a validation to verify cartridge groups in
>>> applications, commit revision: 9b0b3df2fd93024fe725b87a0c59fdfd672e3d50
>>>
>>> On Thu, Feb 19, 2015 at 9:54 AM, Reka Thirunavukkarasu <re...@wso2.com>
>>> wrote:
>>>
>>>> That's great Imesh..Yah..We didn't implement the validation in the
>>>> pre-alpha due to the time constraint..
>>>>
>>>> Thanks,
>>>> Reka
>>>>
>>>> On Wed, Feb 18, 2015 at 9:15 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Thanks Reka! Following are my current observations:
>>>>>
>>>>> - Currently there are no validations to verify whether a group added
>>>>> to an application has defined all the cartridges. At the moment this is not
>>>>> detected at any stage.
>>>>> - There are no validations to verify aliases.
>>>>> - IMO without validations, due to the complexity of the composite
>>>>> application model, it is nearly impossible for an user to figure out what's
>>>>> wrong with his application, which means validations are a must!
>>>>> - We need to use the term "Reference" when referring an already
>>>>> defined entity. For an example when using a cartridge group in an
>>>>> application we need to call it Group Reference. Otherwise users may think
>>>>> that they are defining the cartridge group inline.
>>>>> - Aliases, group names and ids are mixed in deployment process.
>>>>>
>>>>> I'm now in the process of fixing above.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Thu, Feb 19, 2015 at 9:26 AM, Reka Thirunavukkarasu <re...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Yah Imesh, Grouping functionality has been tested in the pre-alpha
>>>>>> and most of the features were working fine. We will need to fix some other
>>>>>> edge cases..
>>>>>>
>>>>>> Thanks,
>>>>>> Reka
>>>>>>
>>>>>> On Wed, Feb 18, 2015 at 7:15 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> I think I found the root cause of the most of the grouping
>>>>>>> functionality issues after debugging it for nearly a day.
>>>>>>>
>>>>>>> The problem seems to be with the usage of aliases and ids. AFAIK
>>>>>>> grouping functionality worked without a problem in pre-alpha there after it
>>>>>>> broke when we did some fixes related to aliases.
>>>>>>>
>>>>>>> I'm now review this and doing a fix.
>>>>>>>
>>>>>>> On Tue, Feb 17, 2015 at 6:36 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> The above issue has occurred because of the time it takes to SM to
>>>>>>>> receive the application created event. Now I have fixed this my making a
>>>>>>>> service call from SM to AS to find cluster id of a given application,
>>>>>>>> cartridge alias rather than relying on the application events.
>>>>>>>>
>>>>>>>> This fix is now available in master branch.
>>>>>>>>
>>>>>>>> On Sun, Feb 15, 2015 at 5:15 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I think I found the reason for not publishing Artifact Updated
>>>>>>>>> event. It looks like the Mock IaaS is responding fast and SM is receiving
>>>>>>>>> the Instance Started event before receiving the Application Created event.
>>>>>>>>> I'm now fixing this.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne <imesh@apache.org
>>>>>>>>> > wrote:
>>>>>>>>>
>>>>>>>>>> Hi Devs,
>>>>>>>>>>
>>>>>>>>>> I just did a quick test to verify grouping functionality with
>>>>>>>>>> sample applications and following is the current status:
>>>>>>>>>>
>>>>>>>>>> ApplicationStatusNotescomplex-appNot Activating
>>>>>>>>>> complex-app-with-lbNot Activating
>>>>>>>>>> dependent-scaling/sample-cartridgesActivates but found few errorsArtifact
>>>>>>>>>> update event is not publisheddependent-scaling/sample-groupsNot
>>>>>>>>>> Activatinggroup-cartridgesNot ActivatingArtifact update event is
>>>>>>>>>> not publishedgroup-scalingNot ActivatingArtifact update event is
>>>>>>>>>> not publishedgroup-scaling-v1Not Activatingmore-complex-appNot
>>>>>>>>>> ActivatingArtifact update event is not publishednested-groupNot
>>>>>>>>>> ActivatingArtifact update event is not publishedsingle-cartridge
>>>>>>>>>> OKsingle-group-group-scalingOKsingle-group-v1Not ActivatingArtifact
>>>>>>>>>> update event is not publishedsingle-group-v2Not ActivatingArtifact
>>>>>>>>>> update event is not publishedsingle-group-v3Not ActivatingApplication
>>>>>>>>>> deployment stops at some point
>>>>>>>>>> We have 14 sample applications now and only 2 of them get
>>>>>>>>>> activated properly. Please find more details in the below spread-sheet:
>>>>>>>>>>
>>>>>>>>>> Sample Applications - Current Status.xlsx
>>>>>>>>>> <https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>
>>>>>>>>>>
>>>>>>>>>> The above test was done with Mock IaaS and I see an issue in ADC
>>>>>>>>>> where it cannot find the application while trying to publish the Artifact
>>>>>>>>>> Updated event once Instance Started is received. I'm now investigating this.
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Imesh Gunaratne
>>>>>>>>>>
>>>>>>>>>> Technical Lead, WSO2
>>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Reka Thirunavukkarasu
>>>>>> Senior Software Engineer,
>>>>>> WSO2, Inc.:http://wso2.com,
>>>>>> Mobile: +94776442007
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Reka Thirunavukkarasu
>>>> Senior Software Engineer,
>>>> WSO2, Inc.:http://wso2.com,
>>>> Mobile: +94776442007
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Fixing Grouping Functionality
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
Hi Imesh,
On Fri, Feb 20, 2015 at 5:57 AM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi Devs,
>
> I fixed core grouping functionality in master branch. Now all grouping
> features are working as expected. Following are the fixes done:
>
> - Added a validation to verify cartridges defined in cartridge groups in
> applications against the cartridge group definitions.
> - Fixed cartridge type/alias, group name/alias mixup in application
> deployment process.
> - Now we can define groups and cartridges more than once in an application
> and use aliases to identify them.
>
AFAIK, we were able to define groups or cartridges more than one in earlier
as well in pre-alpha. This functionality was working fine. In that case, we
allowed users to define dependencies in the application using aliases and
in the cartridge group using group names. Have we changed everywhere to use
aliaes now? Are we allowing users to define alias in the cartridge group
when defining the dependency section?
Thanks,
Reka
- Dependency reference identifier is changed to alias:
>
> "dependencies": {
>
> "startupOrders": [
> "group.mysql-php-group1,cartridge.tomcat1"
> ],
> "terminationBehaviour": "terminate-none"
> }
>
> - Cartridge groups can use the same format for defining dependencies. The
> only requirement is to use the same aliases in the application.
> - Added informative logs to identify the steps in the application
> deployment process:
>
> Monitor scheduled: [type] cluster [component] mysql1.mysql.domain
> Starting monitor: [type] cluster [component] mysql1.mysql.domain
> Monitor started successfully: [type] cluster [component]
> mysql1.mysql.domain [dependents] php1.php.domain [startup-time] 1 seconds
>
> *Wordpress Sample Application:*
>
>
> Wordpress application consists of a cartridge group which includes a MySQL
> cartridge and PHP cartridge. The cartridge
> group defines a startup dependency to first start MySQL cluster and then
> the PHP cluster second once the MySQL cluster
> is active. Group scaling has been disabled in MySQL, PHP group.
>
>
> https://github.com/apache/stratos/tree/master/samples/applications/wordpress
>
> *Wordpress Extended V1 Application*
>
>
>
> Wordpress extended v1 application consists of a cartridge group which
> includes a MySQL cartridge and PHP cartridge and
> a Tomcat cartridge at the top level. The cartridge group defines a startup
> dependency to first start MySQL cluster and
> then the PHP cluster once the MySQL cluster is active. Group scaling has
> been disabled in MySQL, PHP group. The
> application has defined a startup dependency to first start the MySQL, PHP
> group clusters and then the Tomcat cluster.
>
>
> https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v1
>
> *Wordpress Extended V2 Application*
>
>
>
>
> Wordpress extended v2 application consists of a cartridge group which
> includes a MySQL cartridge and PHP cartridge and
> a Tomcat cartridge at the top level. The cartridge group defines a startup
> dependency to first start MySQL cluster and
> then the PHP cluster once the MySQL cluster is active. Group scaling has
> been enabled in MySQL, PHP group and the
> maximum number of group instances has been set to two. The application has
> defined a startup dependency to first start
> the MySQL, PHP group clusters and then the Tomcat cluster.
>
>
> https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v2
>
> Thanks
>
>
> On Thu, Feb 19, 2015 at 12:53 PM, Imesh Gunaratne <im...@apache.org>
> wrote:
>
>> I have now added a validation to verify cartridge groups in applications,
>> commit revision: 9b0b3df2fd93024fe725b87a0c59fdfd672e3d50
>>
>> On Thu, Feb 19, 2015 at 9:54 AM, Reka Thirunavukkarasu <re...@wso2.com>
>> wrote:
>>
>>> That's great Imesh..Yah..We didn't implement the validation in the
>>> pre-alpha due to the time constraint..
>>>
>>> Thanks,
>>> Reka
>>>
>>> On Wed, Feb 18, 2015 at 9:15 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Thanks Reka! Following are my current observations:
>>>>
>>>> - Currently there are no validations to verify whether a group added to
>>>> an application has defined all the cartridges. At the moment this is not
>>>> detected at any stage.
>>>> - There are no validations to verify aliases.
>>>> - IMO without validations, due to the complexity of the composite
>>>> application model, it is nearly impossible for an user to figure out what's
>>>> wrong with his application, which means validations are a must!
>>>> - We need to use the term "Reference" when referring an already defined
>>>> entity. For an example when using a cartridge group in an application we
>>>> need to call it Group Reference. Otherwise users may think that they are
>>>> defining the cartridge group inline.
>>>> - Aliases, group names and ids are mixed in deployment process.
>>>>
>>>> I'm now in the process of fixing above.
>>>>
>>>> Thanks
>>>>
>>>> On Thu, Feb 19, 2015 at 9:26 AM, Reka Thirunavukkarasu <re...@wso2.com>
>>>> wrote:
>>>>
>>>>> Yah Imesh, Grouping functionality has been tested in the pre-alpha and
>>>>> most of the features were working fine. We will need to fix some other edge
>>>>> cases..
>>>>>
>>>>> Thanks,
>>>>> Reka
>>>>>
>>>>> On Wed, Feb 18, 2015 at 7:15 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> I think I found the root cause of the most of the grouping
>>>>>> functionality issues after debugging it for nearly a day.
>>>>>>
>>>>>> The problem seems to be with the usage of aliases and ids. AFAIK
>>>>>> grouping functionality worked without a problem in pre-alpha there after it
>>>>>> broke when we did some fixes related to aliases.
>>>>>>
>>>>>> I'm now review this and doing a fix.
>>>>>>
>>>>>> On Tue, Feb 17, 2015 at 6:36 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> The above issue has occurred because of the time it takes to SM to
>>>>>>> receive the application created event. Now I have fixed this my making a
>>>>>>> service call from SM to AS to find cluster id of a given application,
>>>>>>> cartridge alias rather than relying on the application events.
>>>>>>>
>>>>>>> This fix is now available in master branch.
>>>>>>>
>>>>>>> On Sun, Feb 15, 2015 at 5:15 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I think I found the reason for not publishing Artifact Updated
>>>>>>>> event. It looks like the Mock IaaS is responding fast and SM is receiving
>>>>>>>> the Instance Started event before receiving the Application Created event.
>>>>>>>> I'm now fixing this.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi Devs,
>>>>>>>>>
>>>>>>>>> I just did a quick test to verify grouping functionality with
>>>>>>>>> sample applications and following is the current status:
>>>>>>>>>
>>>>>>>>> ApplicationStatusNotescomplex-appNot Activatingcomplex-app-with-lbNot
>>>>>>>>> Activatingdependent-scaling/sample-cartridgesActivates but found
>>>>>>>>> few errorsArtifact update event is not published
>>>>>>>>> dependent-scaling/sample-groupsNot Activatinggroup-cartridgesNot
>>>>>>>>> ActivatingArtifact update event is not publishedgroup-scalingNot
>>>>>>>>> ActivatingArtifact update event is not publishedgroup-scaling-v1Not
>>>>>>>>> Activatingmore-complex-appNot ActivatingArtifact update event is
>>>>>>>>> not publishednested-groupNot ActivatingArtifact update event is
>>>>>>>>> not publishedsingle-cartridgeOKsingle-group-group-scalingOK
>>>>>>>>> single-group-v1Not ActivatingArtifact update event is not
>>>>>>>>> publishedsingle-group-v2Not ActivatingArtifact update event is
>>>>>>>>> not publishedsingle-group-v3Not ActivatingApplication deployment
>>>>>>>>> stops at some point
>>>>>>>>> We have 14 sample applications now and only 2 of them get
>>>>>>>>> activated properly. Please find more details in the below spread-sheet:
>>>>>>>>>
>>>>>>>>> Sample Applications - Current Status.xlsx
>>>>>>>>> <https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>
>>>>>>>>>
>>>>>>>>> The above test was done with Mock IaaS and I see an issue in ADC
>>>>>>>>> where it cannot find the application while trying to publish the Artifact
>>>>>>>>> Updated event once Instance Started is received. I'm now investigating this.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Imesh Gunaratne
>>>>>>>>>
>>>>>>>>> Technical Lead, WSO2
>>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Reka Thirunavukkarasu
>>>>> Senior Software Engineer,
>>>>> WSO2, Inc.:http://wso2.com,
>>>>> Mobile: +94776442007
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Reka Thirunavukkarasu
>>> Senior Software Engineer,
>>> WSO2, Inc.:http://wso2.com,
>>> Mobile: +94776442007
>>>
>>>
>>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
Re: [Discuss] Fixing Grouping Functionality
Posted by Imesh Gunaratne <im...@apache.org>.
Hi Devs,
I fixed core grouping functionality in master branch. Now all grouping
features are working as expected. Following are the fixes done:
- Added a validation to verify cartridges defined in cartridge groups in
applications against the cartridge group definitions.
- Fixed cartridge type/alias, group name/alias mixup in application
deployment process.
- Now we can define groups and cartridges more than once in an application
and use aliases to identify them.
- Dependency reference identifier is changed to alias:
"dependencies": {
"startupOrders": [
"group.mysql-php-group1,cartridge.tomcat1"
],
"terminationBehaviour": "terminate-none"
}
- Cartridge groups can use the same format for defining dependencies. The
only requirement is to use the same aliases in the application.
- Added informative logs to identify the steps in the application
deployment process:
Monitor scheduled: [type] cluster [component] mysql1.mysql.domain
Starting monitor: [type] cluster [component] mysql1.mysql.domain
Monitor started successfully: [type] cluster [component]
mysql1.mysql.domain [dependents] php1.php.domain [startup-time] 1 seconds
*Wordpress Sample Application:*
Wordpress application consists of a cartridge group which includes a MySQL
cartridge and PHP cartridge. The cartridge
group defines a startup dependency to first start MySQL cluster and then
the PHP cluster second once the MySQL cluster
is active. Group scaling has been disabled in MySQL, PHP group.
https://github.com/apache/stratos/tree/master/samples/applications/wordpress
*Wordpress Extended V1 Application*
Wordpress extended v1 application consists of a cartridge group which
includes a MySQL cartridge and PHP cartridge and
a Tomcat cartridge at the top level. The cartridge group defines a startup
dependency to first start MySQL cluster and
then the PHP cluster once the MySQL cluster is active. Group scaling has
been disabled in MySQL, PHP group. The
application has defined a startup dependency to first start the MySQL, PHP
group clusters and then the Tomcat cluster.
https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v1
*Wordpress Extended V2 Application*
Wordpress extended v2 application consists of a cartridge group which
includes a MySQL cartridge and PHP cartridge and
a Tomcat cartridge at the top level. The cartridge group defines a startup
dependency to first start MySQL cluster and
then the PHP cluster once the MySQL cluster is active. Group scaling has
been enabled in MySQL, PHP group and the
maximum number of group instances has been set to two. The application has
defined a startup dependency to first start
the MySQL, PHP group clusters and then the Tomcat cluster.
https://github.com/apache/stratos/tree/master/samples/applications/wordpress-extended-v2
Thanks
On Thu, Feb 19, 2015 at 12:53 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I have now added a validation to verify cartridge groups in applications,
> commit revision: 9b0b3df2fd93024fe725b87a0c59fdfd672e3d50
>
> On Thu, Feb 19, 2015 at 9:54 AM, Reka Thirunavukkarasu <re...@wso2.com>
> wrote:
>
>> That's great Imesh..Yah..We didn't implement the validation in the
>> pre-alpha due to the time constraint..
>>
>> Thanks,
>> Reka
>>
>> On Wed, Feb 18, 2015 at 9:15 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Thanks Reka! Following are my current observations:
>>>
>>> - Currently there are no validations to verify whether a group added to
>>> an application has defined all the cartridges. At the moment this is not
>>> detected at any stage.
>>> - There are no validations to verify aliases.
>>> - IMO without validations, due to the complexity of the composite
>>> application model, it is nearly impossible for an user to figure out what's
>>> wrong with his application, which means validations are a must!
>>> - We need to use the term "Reference" when referring an already defined
>>> entity. For an example when using a cartridge group in an application we
>>> need to call it Group Reference. Otherwise users may think that they are
>>> defining the cartridge group inline.
>>> - Aliases, group names and ids are mixed in deployment process.
>>>
>>> I'm now in the process of fixing above.
>>>
>>> Thanks
>>>
>>> On Thu, Feb 19, 2015 at 9:26 AM, Reka Thirunavukkarasu <re...@wso2.com>
>>> wrote:
>>>
>>>> Yah Imesh, Grouping functionality has been tested in the pre-alpha and
>>>> most of the features were working fine. We will need to fix some other edge
>>>> cases..
>>>>
>>>> Thanks,
>>>> Reka
>>>>
>>>> On Wed, Feb 18, 2015 at 7:15 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> I think I found the root cause of the most of the grouping
>>>>> functionality issues after debugging it for nearly a day.
>>>>>
>>>>> The problem seems to be with the usage of aliases and ids. AFAIK
>>>>> grouping functionality worked without a problem in pre-alpha there after it
>>>>> broke when we did some fixes related to aliases.
>>>>>
>>>>> I'm now review this and doing a fix.
>>>>>
>>>>> On Tue, Feb 17, 2015 at 6:36 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> The above issue has occurred because of the time it takes to SM to
>>>>>> receive the application created event. Now I have fixed this my making a
>>>>>> service call from SM to AS to find cluster id of a given application,
>>>>>> cartridge alias rather than relying on the application events.
>>>>>>
>>>>>> This fix is now available in master branch.
>>>>>>
>>>>>> On Sun, Feb 15, 2015 at 5:15 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> I think I found the reason for not publishing Artifact Updated
>>>>>>> event. It looks like the Mock IaaS is responding fast and SM is receiving
>>>>>>> the Instance Started event before receiving the Application Created event.
>>>>>>> I'm now fixing this.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne <im...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Devs,
>>>>>>>>
>>>>>>>> I just did a quick test to verify grouping functionality with
>>>>>>>> sample applications and following is the current status:
>>>>>>>>
>>>>>>>> ApplicationStatusNotescomplex-appNot Activatingcomplex-app-with-lbNot
>>>>>>>> Activatingdependent-scaling/sample-cartridgesActivates but found
>>>>>>>> few errorsArtifact update event is not published
>>>>>>>> dependent-scaling/sample-groupsNot Activatinggroup-cartridgesNot
>>>>>>>> ActivatingArtifact update event is not publishedgroup-scalingNot
>>>>>>>> ActivatingArtifact update event is not publishedgroup-scaling-v1Not
>>>>>>>> Activatingmore-complex-appNot ActivatingArtifact update event is
>>>>>>>> not publishednested-groupNot ActivatingArtifact update event is
>>>>>>>> not publishedsingle-cartridgeOKsingle-group-group-scalingOK
>>>>>>>> single-group-v1Not ActivatingArtifact update event is not published
>>>>>>>> single-group-v2Not ActivatingArtifact update event is not published
>>>>>>>> single-group-v3Not ActivatingApplication deployment stops at some
>>>>>>>> point
>>>>>>>> We have 14 sample applications now and only 2 of them get activated
>>>>>>>> properly. Please find more details in the below spread-sheet:
>>>>>>>>
>>>>>>>> Sample Applications - Current Status.xlsx
>>>>>>>> <https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>
>>>>>>>>
>>>>>>>> The above test was done with Mock IaaS and I see an issue in ADC
>>>>>>>> where it cannot find the application while trying to publish the Artifact
>>>>>>>> Updated event once Instance Started is received. I'm now investigating this.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Imesh Gunaratne
>>>>>>>>
>>>>>>>> Technical Lead, WSO2
>>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Reka Thirunavukkarasu
>>>> Senior Software Engineer,
>>>> WSO2, Inc.:http://wso2.com,
>>>> Mobile: +94776442007
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Reka Thirunavukkarasu
>> Senior Software Engineer,
>> WSO2, Inc.:http://wso2.com,
>> Mobile: +94776442007
>>
>>
>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Fixing Grouping Functionality
Posted by Imesh Gunaratne <im...@apache.org>.
I have now added a validation to verify cartridge groups in applications,
commit revision: 9b0b3df2fd93024fe725b87a0c59fdfd672e3d50
On Thu, Feb 19, 2015 at 9:54 AM, Reka Thirunavukkarasu <re...@wso2.com>
wrote:
> That's great Imesh..Yah..We didn't implement the validation in the
> pre-alpha due to the time constraint..
>
> Thanks,
> Reka
>
> On Wed, Feb 18, 2015 at 9:15 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Thanks Reka! Following are my current observations:
>>
>> - Currently there are no validations to verify whether a group added to
>> an application has defined all the cartridges. At the moment this is not
>> detected at any stage.
>> - There are no validations to verify aliases.
>> - IMO without validations, due to the complexity of the composite
>> application model, it is nearly impossible for an user to figure out what's
>> wrong with his application, which means validations are a must!
>> - We need to use the term "Reference" when referring an already defined
>> entity. For an example when using a cartridge group in an application we
>> need to call it Group Reference. Otherwise users may think that they are
>> defining the cartridge group inline.
>> - Aliases, group names and ids are mixed in deployment process.
>>
>> I'm now in the process of fixing above.
>>
>> Thanks
>>
>> On Thu, Feb 19, 2015 at 9:26 AM, Reka Thirunavukkarasu <re...@wso2.com>
>> wrote:
>>
>>> Yah Imesh, Grouping functionality has been tested in the pre-alpha and
>>> most of the features were working fine. We will need to fix some other edge
>>> cases..
>>>
>>> Thanks,
>>> Reka
>>>
>>> On Wed, Feb 18, 2015 at 7:15 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> I think I found the root cause of the most of the grouping
>>>> functionality issues after debugging it for nearly a day.
>>>>
>>>> The problem seems to be with the usage of aliases and ids. AFAIK
>>>> grouping functionality worked without a problem in pre-alpha there after it
>>>> broke when we did some fixes related to aliases.
>>>>
>>>> I'm now review this and doing a fix.
>>>>
>>>> On Tue, Feb 17, 2015 at 6:36 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> The above issue has occurred because of the time it takes to SM to
>>>>> receive the application created event. Now I have fixed this my making a
>>>>> service call from SM to AS to find cluster id of a given application,
>>>>> cartridge alias rather than relying on the application events.
>>>>>
>>>>> This fix is now available in master branch.
>>>>>
>>>>> On Sun, Feb 15, 2015 at 5:15 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> I think I found the reason for not publishing Artifact Updated event.
>>>>>> It looks like the Mock IaaS is responding fast and SM is receiving the
>>>>>> Instance Started event before receiving the Application Created event. I'm
>>>>>> now fixing this.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne <im...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Devs,
>>>>>>>
>>>>>>> I just did a quick test to verify grouping functionality with sample
>>>>>>> applications and following is the current status:
>>>>>>>
>>>>>>> ApplicationStatusNotescomplex-appNot Activatingcomplex-app-with-lbNot
>>>>>>> Activatingdependent-scaling/sample-cartridgesActivates but found
>>>>>>> few errorsArtifact update event is not published
>>>>>>> dependent-scaling/sample-groupsNot Activatinggroup-cartridgesNot
>>>>>>> ActivatingArtifact update event is not publishedgroup-scalingNot
>>>>>>> ActivatingArtifact update event is not publishedgroup-scaling-v1Not
>>>>>>> Activatingmore-complex-appNot ActivatingArtifact update event is
>>>>>>> not publishednested-groupNot ActivatingArtifact update event is not
>>>>>>> publishedsingle-cartridgeOKsingle-group-group-scalingOK
>>>>>>> single-group-v1Not ActivatingArtifact update event is not published
>>>>>>> single-group-v2Not ActivatingArtifact update event is not published
>>>>>>> single-group-v3Not ActivatingApplication deployment stops at some
>>>>>>> point
>>>>>>> We have 14 sample applications now and only 2 of them get activated
>>>>>>> properly. Please find more details in the below spread-sheet:
>>>>>>>
>>>>>>> Sample Applications - Current Status.xlsx
>>>>>>> <https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>
>>>>>>>
>>>>>>> The above test was done with Mock IaaS and I see an issue in ADC
>>>>>>> where it cannot find the application while trying to publish the Artifact
>>>>>>> Updated event once Instance Started is received. I'm now investigating this.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Imesh Gunaratne
>>>>>>>
>>>>>>> Technical Lead, WSO2
>>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Reka Thirunavukkarasu
>>> Senior Software Engineer,
>>> WSO2, Inc.:http://wso2.com,
>>> Mobile: +94776442007
>>>
>>>
>>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Fixing Grouping Functionality
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
That's great Imesh..Yah..We didn't implement the validation in the
pre-alpha due to the time constraint..
Thanks,
Reka
On Wed, Feb 18, 2015 at 9:15 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Thanks Reka! Following are my current observations:
>
> - Currently there are no validations to verify whether a group added to an
> application has defined all the cartridges. At the moment this is not
> detected at any stage.
> - There are no validations to verify aliases.
> - IMO without validations, due to the complexity of the composite
> application model, it is nearly impossible for an user to figure out what's
> wrong with his application, which means validations are a must!
> - We need to use the term "Reference" when referring an already defined
> entity. For an example when using a cartridge group in an application we
> need to call it Group Reference. Otherwise users may think that they are
> defining the cartridge group inline.
> - Aliases, group names and ids are mixed in deployment process.
>
> I'm now in the process of fixing above.
>
> Thanks
>
> On Thu, Feb 19, 2015 at 9:26 AM, Reka Thirunavukkarasu <re...@wso2.com>
> wrote:
>
>> Yah Imesh, Grouping functionality has been tested in the pre-alpha and
>> most of the features were working fine. We will need to fix some other edge
>> cases..
>>
>> Thanks,
>> Reka
>>
>> On Wed, Feb 18, 2015 at 7:15 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> I think I found the root cause of the most of the grouping functionality
>>> issues after debugging it for nearly a day.
>>>
>>> The problem seems to be with the usage of aliases and ids. AFAIK
>>> grouping functionality worked without a problem in pre-alpha there after it
>>> broke when we did some fixes related to aliases.
>>>
>>> I'm now review this and doing a fix.
>>>
>>> On Tue, Feb 17, 2015 at 6:36 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> The above issue has occurred because of the time it takes to SM to
>>>> receive the application created event. Now I have fixed this my making a
>>>> service call from SM to AS to find cluster id of a given application,
>>>> cartridge alias rather than relying on the application events.
>>>>
>>>> This fix is now available in master branch.
>>>>
>>>> On Sun, Feb 15, 2015 at 5:15 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> I think I found the reason for not publishing Artifact Updated event.
>>>>> It looks like the Mock IaaS is responding fast and SM is receiving the
>>>>> Instance Started event before receiving the Application Created event. I'm
>>>>> now fixing this.
>>>>>
>>>>> Thanks
>>>>>
>>>>> On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne <im...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Hi Devs,
>>>>>>
>>>>>> I just did a quick test to verify grouping functionality with sample
>>>>>> applications and following is the current status:
>>>>>>
>>>>>> ApplicationStatusNotescomplex-appNot Activatingcomplex-app-with-lbNot
>>>>>> Activatingdependent-scaling/sample-cartridgesActivates but found few
>>>>>> errorsArtifact update event is not published
>>>>>> dependent-scaling/sample-groupsNot Activatinggroup-cartridgesNot
>>>>>> ActivatingArtifact update event is not publishedgroup-scalingNot
>>>>>> ActivatingArtifact update event is not publishedgroup-scaling-v1Not
>>>>>> Activatingmore-complex-appNot ActivatingArtifact update event is not
>>>>>> publishednested-groupNot ActivatingArtifact update event is not
>>>>>> publishedsingle-cartridgeOKsingle-group-group-scalingOK
>>>>>> single-group-v1Not ActivatingArtifact update event is not published
>>>>>> single-group-v2Not ActivatingArtifact update event is not published
>>>>>> single-group-v3Not ActivatingApplication deployment stops at some
>>>>>> point
>>>>>> We have 14 sample applications now and only 2 of them get activated
>>>>>> properly. Please find more details in the below spread-sheet:
>>>>>>
>>>>>> Sample Applications - Current Status.xlsx
>>>>>> <https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>
>>>>>>
>>>>>> The above test was done with Mock IaaS and I see an issue in ADC
>>>>>> where it cannot find the application while trying to publish the Artifact
>>>>>> Updated event once Instance Started is received. I'm now investigating this.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Imesh Gunaratne
>>>>>>
>>>>>> Technical Lead, WSO2
>>>>>> Committer & PMC Member, Apache Stratos
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Reka Thirunavukkarasu
>> Senior Software Engineer,
>> WSO2, Inc.:http://wso2.com,
>> Mobile: +94776442007
>>
>>
>>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
Re: [Discuss] Fixing Grouping Functionality
Posted by Imesh Gunaratne <im...@apache.org>.
Thanks Reka! Following are my current observations:
- Currently there are no validations to verify whether a group added to an
application has defined all the cartridges. At the moment this is not
detected at any stage.
- There are no validations to verify aliases.
- IMO without validations, due to the complexity of the composite
application model, it is nearly impossible for an user to figure out what's
wrong with his application, which means validations are a must!
- We need to use the term "Reference" when referring an already defined
entity. For an example when using a cartridge group in an application we
need to call it Group Reference. Otherwise users may think that they are
defining the cartridge group inline.
- Aliases, group names and ids are mixed in deployment process.
I'm now in the process of fixing above.
Thanks
On Thu, Feb 19, 2015 at 9:26 AM, Reka Thirunavukkarasu <re...@wso2.com>
wrote:
> Yah Imesh, Grouping functionality has been tested in the pre-alpha and
> most of the features were working fine. We will need to fix some other edge
> cases..
>
> Thanks,
> Reka
>
> On Wed, Feb 18, 2015 at 7:15 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I think I found the root cause of the most of the grouping functionality
>> issues after debugging it for nearly a day.
>>
>> The problem seems to be with the usage of aliases and ids. AFAIK grouping
>> functionality worked without a problem in pre-alpha there after it broke
>> when we did some fixes related to aliases.
>>
>> I'm now review this and doing a fix.
>>
>> On Tue, Feb 17, 2015 at 6:36 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> The above issue has occurred because of the time it takes to SM to
>>> receive the application created event. Now I have fixed this my making a
>>> service call from SM to AS to find cluster id of a given application,
>>> cartridge alias rather than relying on the application events.
>>>
>>> This fix is now available in master branch.
>>>
>>> On Sun, Feb 15, 2015 at 5:15 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> I think I found the reason for not publishing Artifact Updated event.
>>>> It looks like the Mock IaaS is responding fast and SM is receiving the
>>>> Instance Started event before receiving the Application Created event. I'm
>>>> now fixing this.
>>>>
>>>> Thanks
>>>>
>>>> On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne <im...@apache.org>
>>>> wrote:
>>>>
>>>>> Hi Devs,
>>>>>
>>>>> I just did a quick test to verify grouping functionality with sample
>>>>> applications and following is the current status:
>>>>>
>>>>> ApplicationStatusNotescomplex-appNot Activatingcomplex-app-with-lbNot
>>>>> Activatingdependent-scaling/sample-cartridgesActivates but found few
>>>>> errorsArtifact update event is not published
>>>>> dependent-scaling/sample-groupsNot Activatinggroup-cartridgesNot
>>>>> ActivatingArtifact update event is not publishedgroup-scalingNot
>>>>> ActivatingArtifact update event is not publishedgroup-scaling-v1Not
>>>>> Activatingmore-complex-appNot ActivatingArtifact update event is not
>>>>> publishednested-groupNot ActivatingArtifact update event is not
>>>>> publishedsingle-cartridgeOKsingle-group-group-scalingOKsingle-group-v1Not
>>>>> ActivatingArtifact update event is not publishedsingle-group-v2Not
>>>>> ActivatingArtifact update event is not publishedsingle-group-v3Not
>>>>> ActivatingApplication deployment stops at some point
>>>>> We have 14 sample applications now and only 2 of them get activated
>>>>> properly. Please find more details in the below spread-sheet:
>>>>>
>>>>> Sample Applications - Current Status.xlsx
>>>>> <https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>
>>>>>
>>>>> The above test was done with Mock IaaS and I see an issue in ADC where
>>>>> it cannot find the application while trying to publish the Artifact Updated
>>>>> event once Instance Started is received. I'm now investigating this.
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>> --
>>>>> Imesh Gunaratne
>>>>>
>>>>> Technical Lead, WSO2
>>>>> Committer & PMC Member, Apache Stratos
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Reka Thirunavukkarasu
> Senior Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Fixing Grouping Functionality
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
Yah Imesh, Grouping functionality has been tested in the pre-alpha and most
of the features were working fine. We will need to fix some other edge
cases..
Thanks,
Reka
On Wed, Feb 18, 2015 at 7:15 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I think I found the root cause of the most of the grouping functionality
> issues after debugging it for nearly a day.
>
> The problem seems to be with the usage of aliases and ids. AFAIK grouping
> functionality worked without a problem in pre-alpha there after it broke
> when we did some fixes related to aliases.
>
> I'm now review this and doing a fix.
>
> On Tue, Feb 17, 2015 at 6:36 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> The above issue has occurred because of the time it takes to SM to
>> receive the application created event. Now I have fixed this my making a
>> service call from SM to AS to find cluster id of a given application,
>> cartridge alias rather than relying on the application events.
>>
>> This fix is now available in master branch.
>>
>> On Sun, Feb 15, 2015 at 5:15 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> I think I found the reason for not publishing Artifact Updated event. It
>>> looks like the Mock IaaS is responding fast and SM is receiving the
>>> Instance Started event before receiving the Application Created event. I'm
>>> now fixing this.
>>>
>>> Thanks
>>>
>>> On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Hi Devs,
>>>>
>>>> I just did a quick test to verify grouping functionality with sample
>>>> applications and following is the current status:
>>>>
>>>> ApplicationStatusNotescomplex-appNot Activatingcomplex-app-with-lbNot
>>>> Activatingdependent-scaling/sample-cartridgesActivates but found few
>>>> errorsArtifact update event is not published
>>>> dependent-scaling/sample-groupsNot Activatinggroup-cartridgesNot
>>>> ActivatingArtifact update event is not publishedgroup-scalingNot
>>>> ActivatingArtifact update event is not publishedgroup-scaling-v1Not
>>>> Activatingmore-complex-appNot ActivatingArtifact update event is not
>>>> publishednested-groupNot ActivatingArtifact update event is not
>>>> publishedsingle-cartridgeOKsingle-group-group-scalingOKsingle-group-v1Not
>>>> ActivatingArtifact update event is not publishedsingle-group-v2Not
>>>> ActivatingArtifact update event is not publishedsingle-group-v3Not
>>>> ActivatingApplication deployment stops at some point
>>>> We have 14 sample applications now and only 2 of them get activated
>>>> properly. Please find more details in the below spread-sheet:
>>>>
>>>> Sample Applications - Current Status.xlsx
>>>> <https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>
>>>>
>>>> The above test was done with Mock IaaS and I see an issue in ADC where
>>>> it cannot find the application while trying to publish the Artifact Updated
>>>> event once Instance Started is received. I'm now investigating this.
>>>>
>>>> Thanks
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Reka Thirunavukkarasu
Senior Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007
Re: [Discuss] Fixing Grouping Functionality
Posted by Imesh Gunaratne <im...@apache.org>.
s/review/reviewing/g
On Thu, Feb 19, 2015 at 7:45 AM, Imesh Gunaratne <im...@apache.org> wrote:
> I think I found the root cause of the most of the grouping functionality
> issues after debugging it for nearly a day.
>
> The problem seems to be with the usage of aliases and ids. AFAIK grouping
> functionality worked without a problem in pre-alpha there after it broke
> when we did some fixes related to aliases.
>
> I'm now review this and doing a fix.
>
> On Tue, Feb 17, 2015 at 6:36 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> The above issue has occurred because of the time it takes to SM to
>> receive the application created event. Now I have fixed this my making a
>> service call from SM to AS to find cluster id of a given application,
>> cartridge alias rather than relying on the application events.
>>
>> This fix is now available in master branch.
>>
>> On Sun, Feb 15, 2015 at 5:15 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> I think I found the reason for not publishing Artifact Updated event. It
>>> looks like the Mock IaaS is responding fast and SM is receiving the
>>> Instance Started event before receiving the Application Created event. I'm
>>> now fixing this.
>>>
>>> Thanks
>>>
>>> On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne <im...@apache.org>
>>> wrote:
>>>
>>>> Hi Devs,
>>>>
>>>> I just did a quick test to verify grouping functionality with sample
>>>> applications and following is the current status:
>>>>
>>>> ApplicationStatusNotescomplex-appNot Activatingcomplex-app-with-lbNot
>>>> Activatingdependent-scaling/sample-cartridgesActivates but found few
>>>> errorsArtifact update event is not published
>>>> dependent-scaling/sample-groupsNot Activatinggroup-cartridgesNot
>>>> ActivatingArtifact update event is not publishedgroup-scalingNot
>>>> ActivatingArtifact update event is not publishedgroup-scaling-v1Not
>>>> Activatingmore-complex-appNot ActivatingArtifact update event is not
>>>> publishednested-groupNot ActivatingArtifact update event is not
>>>> publishedsingle-cartridgeOKsingle-group-group-scalingOKsingle-group-v1Not
>>>> ActivatingArtifact update event is not publishedsingle-group-v2Not
>>>> ActivatingArtifact update event is not publishedsingle-group-v3Not
>>>> ActivatingApplication deployment stops at some point
>>>> We have 14 sample applications now and only 2 of them get activated
>>>> properly. Please find more details in the below spread-sheet:
>>>>
>>>> Sample Applications - Current Status.xlsx
>>>> <https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>
>>>>
>>>> The above test was done with Mock IaaS and I see an issue in ADC where
>>>> it cannot find the application while trying to publish the Artifact Updated
>>>> event once Instance Started is received. I'm now investigating this.
>>>>
>>>> Thanks
>>>>
>>>>
>>>> --
>>>> Imesh Gunaratne
>>>>
>>>> Technical Lead, WSO2
>>>> Committer & PMC Member, Apache Stratos
>>>>
>>>
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Fixing Grouping Functionality
Posted by Imesh Gunaratne <im...@apache.org>.
I think I found the root cause of the most of the grouping functionality
issues after debugging it for nearly a day.
The problem seems to be with the usage of aliases and ids. AFAIK grouping
functionality worked without a problem in pre-alpha there after it broke
when we did some fixes related to aliases.
I'm now review this and doing a fix.
On Tue, Feb 17, 2015 at 6:36 PM, Imesh Gunaratne <im...@apache.org> wrote:
> The above issue has occurred because of the time it takes to SM to receive
> the application created event. Now I have fixed this my making a service
> call from SM to AS to find cluster id of a given application, cartridge
> alias rather than relying on the application events.
>
> This fix is now available in master branch.
>
> On Sun, Feb 15, 2015 at 5:15 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> I think I found the reason for not publishing Artifact Updated event. It
>> looks like the Mock IaaS is responding fast and SM is receiving the
>> Instance Started event before receiving the Application Created event. I'm
>> now fixing this.
>>
>> Thanks
>>
>> On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne <im...@apache.org>
>> wrote:
>>
>>> Hi Devs,
>>>
>>> I just did a quick test to verify grouping functionality with sample
>>> applications and following is the current status:
>>>
>>> ApplicationStatusNotescomplex-appNot Activatingcomplex-app-with-lbNot
>>> Activatingdependent-scaling/sample-cartridgesActivates but found few
>>> errorsArtifact update event is not published
>>> dependent-scaling/sample-groupsNot Activatinggroup-cartridgesNot
>>> ActivatingArtifact update event is not publishedgroup-scalingNot
>>> ActivatingArtifact update event is not publishedgroup-scaling-v1Not
>>> Activatingmore-complex-appNot ActivatingArtifact update event is not
>>> publishednested-groupNot ActivatingArtifact update event is not
>>> publishedsingle-cartridgeOKsingle-group-group-scalingOKsingle-group-v1Not
>>> ActivatingArtifact update event is not publishedsingle-group-v2Not
>>> ActivatingArtifact update event is not publishedsingle-group-v3Not
>>> ActivatingApplication deployment stops at some point
>>> We have 14 sample applications now and only 2 of them get activated
>>> properly. Please find more details in the below spread-sheet:
>>>
>>> Sample Applications - Current Status.xlsx
>>> <https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>
>>>
>>> The above test was done with Mock IaaS and I see an issue in ADC where
>>> it cannot find the application while trying to publish the Artifact Updated
>>> event once Instance Started is received. I'm now investigating this.
>>>
>>> Thanks
>>>
>>>
>>> --
>>> Imesh Gunaratne
>>>
>>> Technical Lead, WSO2
>>> Committer & PMC Member, Apache Stratos
>>>
>>
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Fixing Grouping Functionality
Posted by Imesh Gunaratne <im...@apache.org>.
The above issue has occurred because of the time it takes to SM to receive
the application created event. Now I have fixed this my making a service
call from SM to AS to find cluster id of a given application, cartridge
alias rather than relying on the application events.
This fix is now available in master branch.
On Sun, Feb 15, 2015 at 5:15 PM, Imesh Gunaratne <im...@apache.org> wrote:
> I think I found the reason for not publishing Artifact Updated event. It
> looks like the Mock IaaS is responding fast and SM is receiving the
> Instance Started event before receiving the Application Created event. I'm
> now fixing this.
>
> Thanks
>
> On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne <im...@apache.org> wrote:
>
>> Hi Devs,
>>
>> I just did a quick test to verify grouping functionality with sample
>> applications and following is the current status:
>>
>> ApplicationStatusNotescomplex-appNot Activatingcomplex-app-with-lbNot
>> Activatingdependent-scaling/sample-cartridgesActivates but found few
>> errorsArtifact update event is not published
>> dependent-scaling/sample-groupsNot Activatinggroup-cartridgesNot
>> ActivatingArtifact update event is not publishedgroup-scalingNot
>> ActivatingArtifact update event is not publishedgroup-scaling-v1Not
>> Activatingmore-complex-appNot ActivatingArtifact update event is not
>> publishednested-groupNot ActivatingArtifact update event is not published
>> single-cartridgeOKsingle-group-group-scalingOKsingle-group-v1Not
>> ActivatingArtifact update event is not publishedsingle-group-v2Not
>> ActivatingArtifact update event is not publishedsingle-group-v3Not
>> ActivatingApplication deployment stops at some point
>> We have 14 sample applications now and only 2 of them get activated
>> properly. Please find more details in the below spread-sheet:
>>
>> Sample Applications - Current Status.xlsx
>> <https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>
>>
>> The above test was done with Mock IaaS and I see an issue in ADC where it
>> cannot find the application while trying to publish the Artifact Updated
>> event once Instance Started is received. I'm now investigating this.
>>
>> Thanks
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
Re: [Discuss] Fixing Grouping Functionality
Posted by Imesh Gunaratne <im...@apache.org>.
I think I found the reason for not publishing Artifact Updated event. It
looks like the Mock IaaS is responding fast and SM is receiving the
Instance Started event before receiving the Application Created event. I'm
now fixing this.
Thanks
On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi Devs,
>
> I just did a quick test to verify grouping functionality with sample
> applications and following is the current status:
>
> ApplicationStatusNotescomplex-appNot Activatingcomplex-app-with-lbNot
> Activatingdependent-scaling/sample-cartridgesActivates but found few
> errorsArtifact update event is not published
> dependent-scaling/sample-groupsNot Activatinggroup-cartridgesNot
> ActivatingArtifact update event is not publishedgroup-scalingNot
> ActivatingArtifact update event is not publishedgroup-scaling-v1Not
> Activatingmore-complex-appNot ActivatingArtifact update event is not
> publishednested-groupNot ActivatingArtifact update event is not published
> single-cartridgeOKsingle-group-group-scalingOKsingle-group-v1Not
> ActivatingArtifact update event is not publishedsingle-group-v2Not
> ActivatingArtifact update event is not publishedsingle-group-v3Not
> ActivatingApplication deployment stops at some point
> We have 14 sample applications now and only 2 of them get activated
> properly. Please find more details in the below spread-sheet:
>
> Sample Applications - Current Status.xlsx
> <https://docs.google.com/spreadsheets/d/1GBIQuitW4w8G_zXFArgaUBo8P5p0KHql7Aef-XNqg3o/edit?usp=drive_web>
>
> The above test was done with Mock IaaS and I see an issue in ADC where it
> cannot find the application while trying to publish the Artifact Updated
> event once Instance Started is received. I'm now investigating this.
>
> Thanks
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos