You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Chamila De Alwis <ch...@wso2.com> on 2014/09/23 17:04:09 UTC
MQTT Messaging + Python Cartridge Agent Testing Strategy
Hi,
For $subject, we decided to implement the following steps.
Following aspects need to be tested from agent's point of view.
1) Listening to and publishing instance related events
2) Managing artifacts
3) Managing tenants based on tenant related events
4) Managing log publishing
We chose the following three cartridge types to cover the above basic
scenarios.
1) PHP - Single tenant framework cartridge
2) MySQL - Single tenant data cartridge
3) WSO2AS - Multi tenant cartridge
The initial test cases are as follows.It is a work in progress, however
further test cases will be added in the future.
Please add your suggestions on any improvements.
Cartridge Agent successfully publishes instance status events
Prerequisites
Stratos InstalledPuppet master configuredStratos policies deployedA base
cartridge configuredMySQL cartridge definition deployed
Steps
StepExpected resultLog in to Stratos admin consoleMy Cartridges page will
be displayedSubscribe to MySQL cartridgeMySQL subscription page will be
loadedEnter a name for the cartridge and click SubscribeSubscription page
will be displayed with MySQL cartridge marked as subscribedWait until
cartridge is spawnedwso2carbon.log will output "Instance is successfully
starting up." when the instance is spawning.SSH in to the spawned
instance Successfully
SSH in to the instanceCheck the log file, /tmp/puppet_log /tmp/puppet_log
will out put "Initialization completed successfully." after puppet has
successfully configured the instanceCheck the wso2carbon.log for the
InstanceStartedEvent published from the cartridge agentwso2carbon.log will
output the received event details.Check the wso2carbon.log for the
InstanceActivatedEvent published from the cartridge agentwso2carbon.log
will output the received event details.
Cartridge Agent successfully listenes to instance notifier events
Prerequisites
Stratos InstalledPuppet master configuredStratos policies deployedA base
cartridge configuredPHP cartridge definition deployed
Steps
StepExpected resultLog in to Stratos admin consoleMy Cartridges page will
be displayedSubscribe to PHP cartridgePHP subscription page will be loadedEnter
a name and the repository for the cartridge and click SubscribeSubscription
page will be displayed with PHP cartridge marked as subscribedWait until
cartridge is spawnedwso2carbon.log will output "Instance is successfully
starting up." when the instance is spawning.SSH in to the spawned
instance Successfully
SSH in to the instanceCheck the log file, /tmp/puppet_log /tmp/puppet_log
will out put "Initialization completed successfully." after puppet has
successfully configured the instanceCheck for CompleteTopologyEvent and
CompleteTenantEvent being listened to by the
agent/var/log/apache-stratos/cartridge-agent-extensions.log
file will out put information received with the mentioned eventsUpdate the
remote repository with new files and check if the ArtifactUpdatedEvent was
received by the cartridge
agent/var/log/apache-stratos/cartridge-agent-extensions.log
file will out put information received with the mentioned eventsRefresh the
served pages and check if the updated pages are servedWeb application is
updated with the new artifacts
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
RE: MQTT Messaging + Python Cartridge Agent Testing Strategy
Posted by "Shaheedur Haque (shahhaqu)" <sh...@cisco.com>.
Oh yes, I could not agree more. I am delighted to see progress on this front.
You might be interested to know that just in order to have extensibility in Python with the current Java CA (for the Health Statistics plugin), I had to implement a bridging plugin in Jython, but I would hesitate to call that a general solution (wonderful though Jython 2.7b3 is).
From: Lakmal Warusawithana [mailto:lakmal@wso2.com]
Sent: 25 September 2014 09:31
To: dev@stratos.apache.org
Cc: Chamila De Alwis
Subject: Re: MQTT Messaging + Python Cartridge Agent Testing Strategy
Hi Shaheed,
All 3 mention thread has discussed lot of ideas. As far as my understand all [1][2][3] will address eventually. As a first step we need to written in python is very important, what i can see, when we moving to docker, containers can boot up within 1,2 second and light weight agent is must. Also python more devops friendly interpreter language, its easy to extent when and there. IMO, we have to start in somewhere and keep improving it, to our needs
thanks
On Thu, Sep 25, 2014 at 12:50 PM, Shaheed Haque <sh...@cisco.com>> wrote:
I knew that there was a Python Cartridge Agent in the works, but did I miss any recent the discussion of it? I provided some details comments/requirements on some related discussions in May/June [1],[2] but got no responses to suggest if those would be considered or not.
In case I have been asleep, one thing I would like to ensure the new agent supports is restartability. This is required because the CA is not stateless: at least in the start_servers extension point, when used in "proxy" mode [3], if the proxy server hosting the CAs for a bunch of proxied VMs dies, the current CA cannot be restarted on a failover server *in* the start_servers state.
Note that [3] was written originally in terms of the need to make a cartridge out of a VM that did not support Java: even with a Python CA the following two classes of equivalent problem still remain:
· VMs that don't have Python.
· "Hostile" VMs which are simply not open to having a CA inserted for Cartridgification.
These are surprisingly common in the NFV world.
Thanks, Shaheed
[1] Cartridge Agent Extension Points
[2] autoscaling - load average and memory consumption on docker/lxc instances
[3] Cartridge agent for a VM without Java
On Tuesday 23 Sep 2014 20:34:09 Chamila De Alwis wrote:
Hi,
For $subject, we decided to implement the following steps.
Following aspects need to be tested from agent's point of view.
1) Listening to and publishing instance related events
2) Managing artifacts
3) Managing tenants based on tenant related events
4) Managing log publishing
We chose the following three cartridge types to cover the above basic scenarios.
1) PHP - Single tenant framework cartridge
2) MySQL - Single tenant data cartridge
3) WSO2AS - Multi tenant cartridge
The initial test cases are as follows.It is a work in progress, however further test cases will be added in the future.
Please add your suggestions on any improvements.
Cartridge Agent successfully publishes instance status events
Prerequisites
Stratos Installed
Puppet master configured
Stratos policies deployed
A base cartridge configured
MySQL cartridge definition deployed
Steps
Step
Expected result
Log in to Stratos admin console
My Cartridges page will be displayed
Subscribe to MySQL cartridge
MySQL subscription page will be loaded
Enter a name for the cartridge and click Subscribe
Subscription page will be displayed with MySQL cartridge marked as subscribed
Wait until cartridge is spawned
wso2carbon.log will output "Instance is successfully starting up." when the instance is spawning.
SSH in to the spawned instance
Successfully SSH in to the instance
Check the log file, /tmp/puppet_log
/tmp/puppet_log will out put "Initialization completed successfully." after puppet has successfully configured the instance
Check the wso2carbon.log for the InstanceStartedEvent published from the cartridge agent
wso2carbon.log will output the received event details.
Check the wso2carbon.log for the InstanceActivatedEvent published from the cartridge agent
wso2carbon.log will output the received event details.
Cartridge Agent successfully listenes to instance notifier events
Prerequisites
Stratos Installed
Puppet master configured
Stratos policies deployed
A base cartridge configured
PHP cartridge definition deployed
Steps
Step
Expected result
Log in to Stratos admin console
My Cartridges page will be displayed
Subscribe to PHP cartridge
PHP subscription page will be loaded
Enter a name and the repository for the cartridge and click Subscribe
Subscription page will be displayed with PHP cartridge marked as subscribed
Wait until cartridge is spawned
wso2carbon.log will output "Instance is successfully starting up." when the instance is spawning.
SSH in to the spawned instance
Successfully SSH in to the instance
Check the log file, /tmp/puppet_log
/tmp/puppet_log will out put "Initialization completed successfully." after puppet has successfully configured the instance
Check for CompleteTopologyEvent and CompleteTenantEvent being listened to by the agent
/var/log/apache-stratos/cartridge-agent-extensions.log file will out put information received with the mentioned events
Update the remote repository with new files and check if the ArtifactUpdatedEvent was received by the cartridge agent
/var/log/apache-stratos/cartridge-agent-extensions.log file will out put information received with the mentioned events
Refresh the served pages and check if the updated pages are served
Web application is updated with the new artifacts
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163<tel:%2B94772207163>
Blog:
code.chamiladealwis.com<http://code.chamiladealwis.com>
--
Lakmal Warusawithana
Vice President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
Re: MQTT Messaging + Python Cartridge Agent Testing Strategy
Posted by Lakmal Warusawithana <la...@wso2.com>.
Hi Shaheed,
All 3 mention thread has discussed lot of ideas. As far as my understand
all [1][2][3] will address eventually. As a first step we need to written
in python is very important, what i can see, when we moving to docker,
containers can boot up within 1,2 second and light weight agent is must.
Also python more devops friendly interpreter language, its easy to extent
when and there. IMO, we have to start in somewhere and keep improving it,
to our needs
thanks
On Thu, Sep 25, 2014 at 12:50 PM, Shaheed Haque <sh...@cisco.com> wrote:
>
>
> I knew that there was a Python Cartridge Agent in the works, but did I
> miss any recent the discussion of it? I provided some details
> comments/requirements on some related discussions in May/June [1],[2] but
> got no responses to suggest if those would be considered or not.
>
>
>
> In case I have been asleep, one thing I would like to ensure the new agent
> supports is restartability. This is required because the CA is not
> stateless: at least in the start_servers extension point, when used in
> "proxy" mode [3], if the proxy server hosting the CAs for a bunch of
> proxied VMs dies, the current CA cannot be restarted on a failover server
> *in* the start_servers state.
>
>
>
> Note that [3] was written originally in terms of the need to make a
> cartridge out of a VM that did not support Java: even with a Python CA the
> following two classes of equivalent problem still remain:
>
> - VMs that don't have Python.
> - "Hostile" VMs which are simply not open to having a CA inserted for
> Cartridgification.
>
> These are surprisingly common in the NFV world.
>
>
>
> Thanks, Shaheed
>
>
>
> [1] Cartridge Agent Extension Points
>
> [2] autoscaling - load average and memory consumption on docker/lxc
> instances
>
> [3] Cartridge agent for a VM without Java
>
>
>
>
>
> On Tuesday 23 Sep 2014 20:34:09 Chamila De Alwis wrote:
>
> Hi,
>
> For $subject, we decided to implement the following steps.
>
> Following aspects need to be tested from agent's point of view.
>
> 1) Listening to and publishing instance related events
> 2) Managing artifacts
> 3) Managing tenants based on tenant related events
> 4) Managing log publishing
>
> We chose the following three cartridge types to cover the above basic
> scenarios.
>
> 1) PHP - Single tenant framework cartridge
> 2) MySQL - Single tenant data cartridge
> 3) WSO2AS - Multi tenant cartridge
>
> The initial test cases are as follows.It is a work in progress, however
> further test cases will be added in the future.
>
> Please add your suggestions on any improvements.
>
>
>
> Cartridge Agent successfully publishes instance status events
>
> Prerequisites
>
> Stratos Installed
>
> Puppet master configured
>
> Stratos policies deployed
>
> A base cartridge configured
>
> MySQL cartridge definition deployed
>
>
>
> Steps
>
> Step
>
> Expected result
>
> Log in to Stratos admin console
>
> My Cartridges page will be displayed
>
> Subscribe to MySQL cartridge
>
> MySQL subscription page will be loaded
>
> Enter a name for the cartridge and click Subscribe
>
> Subscription page will be displayed with MySQL cartridge marked as
> subscribed
>
> Wait until cartridge is spawned
>
> wso2carbon.log will output "Instance is successfully starting up." when
> the instance is spawning.
>
> SSH in to the spawned instance
>
> Successfully SSH in to the instance
>
> Check the log file, /tmp/puppet_log
>
> /tmp/puppet_log will out put "Initialization completed successfully."
> after puppet has successfully configured the instance
>
> Check the wso2carbon.log for the InstanceStartedEvent published from the
> cartridge agent
>
> wso2carbon.log will output the received event details.
>
> Check the wso2carbon.log for the InstanceActivatedEvent published from the
> cartridge agent
>
> wso2carbon.log will output the received event details.
>
>
>
>
>
>
>
> Cartridge Agent successfully listenes to instance notifier events
>
> Prerequisites
>
> Stratos Installed
>
> Puppet master configured
>
> Stratos policies deployed
>
> A base cartridge configured
>
> PHP cartridge definition deployed
>
>
>
> Steps
>
> Step
>
> Expected result
>
> Log in to Stratos admin console
>
> My Cartridges page will be displayed
>
> Subscribe to PHP cartridge
>
> PHP subscription page will be loaded
>
> Enter a name and the repository for the cartridge and click Subscribe
>
> Subscription page will be displayed with PHP cartridge marked as subscribed
>
> Wait until cartridge is spawned
>
> wso2carbon.log will output "Instance is successfully starting up." when
> the instance is spawning.
>
> SSH in to the spawned instance
>
> Successfully SSH in to the instance
>
> Check the log file, /tmp/puppet_log
>
> /tmp/puppet_log will out put "Initialization completed successfully."
> after puppet has successfully configured the instance
>
> Check for CompleteTopologyEvent and CompleteTenantEvent being listened to
> by the agent
>
> /var/log/apache-stratos/cartridge-agent-extensions.log file will out put
> information received with the mentioned events
>
> Update the remote repository with new files and check if the
> ArtifactUpdatedEvent was received by the cartridge agent
>
> /var/log/apache-stratos/cartridge-agent-extensions.log file will out put
> information received with the mentioned events
>
> Refresh the served pages and check if the updated pages are served
>
> Web application is updated with the new artifacts
>
>
>
> Regards,
>
> Chamila de Alwis
>
> Software Engineer | WSO2 | +94772207163
>
> Blog:
>
> code.chamiladealwis.com
>
>
>
>
>
>
--
Lakmal Warusawithana
Vice President, Apache Stratos
Director - Cloud Architecture; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
Re: MQTT Messaging + Python Cartridge Agent Testing Strategy
Posted by Shaheed Haque <sh...@cisco.com>.
I knew that there was a Python Cartridge Agent in the works, but did I miss any recent
the discussion of it? I provided some details comments/requirements on some related
discussions in May/June [1],[2] but got no responses to suggest if those would be
considered or not.
In case I have been asleep, one thing I would like to ensure the new agent supports is
restartability. This is required because the CA is not stateless: at least in the
start_servers extension point, when used in "proxy" mode [3], if the proxy server
hosting the CAs for a bunch of proxied VMs dies, the current CA cannot be restarted
on a failover server *in* the start_servers state.
Note that [3] was written originally in terms of the need to make a cartridge out of a
VM that did not support Java: even with a Python CA the following two classes of
equivalent problem still remain:
* VMs that don't have Python.
* "Hostile" VMs which are simply not open to having a CA inserted for
Cartridgification.
These are surprisingly common in the NFV world.
Thanks, Shaheed
[1] Cartridge Agent Extension Points
[2] autoscaling - load average and memory consumption on docker/lxc instances
[3] Cartridge agent for a VM without Java
On Tuesday 23 Sep 2014 20:34:09 Chamila De Alwis wrote:
Hi,
For $subject, we decided to implement the following steps.
Following aspects need to be tested from agent's point of view.
1) Listening to and publishing instance related events2) Managing artifacts3)
Managing tenants based on tenant related events4) Managing log publishing
We chose the following three cartridge types to cover the above basic scenarios.
1) PHP - Single tenant framework cartridge2) MySQL - Single tenant data cartridge3)
WSO2AS - Multi tenant cartridge
The initial test cases are as follows.It is a work in progress, however further test cases
will be added in the future.
Please add your suggestions on any improvements.
*Cartridge Agent successfully publishes instance status events*
*Prerequisites *
Stratos Installed
Puppet master configured
Stratos policies deployed
A base cartridge configured
MySQL cartridge definition deployed
*Steps*
*Step*
*Expected result*
Log in to Stratos admin console
My Cartridges page will be displayed
Subscribe to MySQL cartridge
MySQL subscription page will be loaded
Enter a name for the cartridge and click Subscribe
Subscription page will be displayed with MySQL cartridge marked as subscribed
Wait until cartridge is spawned
wso2carbon.log will output "Instance is successfully starting up." when the instance is
spawning.
SSH in to the spawned instance
Successfully SSH in to the instance
Check the log file, /tmp/puppet_log
/tmp/puppet_log will out put "Initialization completed successfully." after puppet has
successfully configured the instance
Check the wso2carbon.log for the InstanceStartedEvent published from the cartridge
agent
wso2carbon.log will output the received event details.
Check the wso2carbon.log for the InstanceActivatedEvent published from the cartridge
agent
wso2carbon.log will output the received event details.
*Cartridge Agent successfully listenes to instance notifier events*
*Prerequisites *
Stratos Installed
Puppet master configured
Stratos policies deployed
A base cartridge configured
PHP cartridge definition deployed
*Steps*
*Step*
*Expected result*
Log in to Stratos admin console
My Cartridges page will be displayed
Re: MQTT Messaging + Python Cartridge Agent Testing Strategy
Posted by Udara Liyanage <ud...@wso2.com>.
Hi Chamila,
Artifact deployment scenarios such as auto_commit should also be tested.
On Wed, Sep 24, 2014 at 12:59 PM, Gayan Gunarathne <ga...@wso2.com> wrote:
> +1 for this python cartridge testing
>
> But I guess for the future release testing it is really nice if we can
> make some automation testing to some extend.It will ease our testing
> workload and time. Also it will make sure our existing functionality not
> affected with those new changes.
>
> IMO we can use following technologies as a start up
>
> - Use selenium based test automation with Stratos web interface.
> - Use automation shell scripts for the back end API calls.
>
> Also for the REST API testing these are some frameworks exist as well
> ex:frisby .I guess we can also look on to this as well.
>
> As a start,we won't be able to cover all the test scenarios at once. But I
> suppose we will be able to cover some extend. WDYT?
>
> Please share your thoughts and suggestion on this.
>
> Thanks,
> Gayan
>
> On Wed, Sep 24, 2014 at 12:33 PM, Chamila De Alwis <ch...@wso2.com>
> wrote:
>
>> We are currently executing the tests manually, since we couldn't find any
>> automation context in Stratos.
>>
>> As the initial test run, we are testing the event publishing and
>> subscribing scopes, and consequently we are extending the scope to artifact
>> management and health statistics publishing.
>>
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>> On Wed, Sep 24, 2014 at 12:07 PM, Nirmal Fernando <nirmal070125@gmail.com
>> > wrote:
>>
>>> Nicely articulated Chamila! What's your plan to implement these tests?
>>>
>>> On Tue, Sep 23, 2014 at 8:34 PM, Chamila De Alwis <ch...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> For $subject, we decided to implement the following steps.
>>>>
>>>> Following aspects need to be tested from agent's point of view.
>>>>
>>>> 1) Listening to and publishing instance related events
>>>> 2) Managing artifacts
>>>> 3) Managing tenants based on tenant related events
>>>> 4) Managing log publishing
>>>>
>>>> We chose the following three cartridge types to cover the above basic
>>>> scenarios.
>>>>
>>>> 1) PHP - Single tenant framework cartridge
>>>> 2) MySQL - Single tenant data cartridge
>>>> 3) WSO2AS - Multi tenant cartridge
>>>>
>>>> The initial test cases are as follows.It is a work in progress, however
>>>> further test cases will be added in the future.
>>>>
>>>> Please add your suggestions on any improvements.
>>>>
>>>>
>>>> Cartridge Agent successfully publishes instance status events
>>>> Prerequisites
>>>> Stratos InstalledPuppet master configuredStratos policies deployedA
>>>> base cartridge configuredMySQL cartridge definition deployed
>>>>
>>>> Steps
>>>> StepExpected resultLog in to Stratos admin consoleMy Cartridges page
>>>> will be displayedSubscribe to MySQL cartridgeMySQL subscription page
>>>> will be loadedEnter a name for the cartridge and click SubscribeSubscription
>>>> page will be displayed with MySQL cartridge marked as subscribedWait
>>>> until cartridge is spawnedwso2carbon.log will output "Instance is
>>>> successfully starting up." when the instance is spawning.SSH in to the
>>>> spawned instance Successfully SSH in to the instanceCheck the log
>>>> file, /tmp/puppet_log /tmp/puppet_log will out put "Initialization
>>>> completed successfully." after puppet has successfully configured the
>>>> instanceCheck the wso2carbon.log for the InstanceStartedEvent
>>>> published from the cartridge agentwso2carbon.log will output the
>>>> received event details.Check the wso2carbon.log for the
>>>> InstanceActivatedEvent published from the cartridge agentwso2carbon.log
>>>> will output the received event details.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Cartridge Agent successfully listenes to instance notifier events
>>>> Prerequisites
>>>> Stratos InstalledPuppet master configuredStratos policies deployedA
>>>> base cartridge configuredPHP cartridge definition deployed
>>>>
>>>> Steps
>>>> StepExpected resultLog in to Stratos admin consoleMy Cartridges page
>>>> will be displayedSubscribe to PHP cartridgePHP subscription page will
>>>> be loadedEnter a name and the repository for the cartridge and click
>>>> SubscribeSubscription page will be displayed with PHP cartridge marked
>>>> as subscribedWait until cartridge is spawnedwso2carbon.log will output
>>>> "Instance is successfully starting up." when the instance is spawning.SSH
>>>> in to the spawned instance Successfully SSH in to the instanceCheck
>>>> the log file, /tmp/puppet_log /tmp/puppet_log will out put
>>>> "Initialization completed successfully." after puppet has successfully
>>>> configured the instanceCheck for CompleteTopologyEvent and
>>>> CompleteTenantEvent being listened to by the agent/var/log/apache-stratos/cartridge-agent-extensions.log
>>>> file will out put information received with the mentioned eventsUpdate
>>>> the remote repository with new files and check if the ArtifactUpdatedEvent
>>>> was received by the cartridge agent/var/log/apache-stratos/cartridge-agent-extensions.log
>>>> file will out put information received with the mentioned eventsRefresh
>>>> the served pages and check if the updated pages are servedWeb
>>>> application is updated with the new artifacts
>>>>
>>>> Regards,
>>>> Chamila de Alwis
>>>> Software Engineer | WSO2 | +94772207163
>>>> Blog: code.chamiladealwis.com
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Nirmal
>>>
>>> Nirmal Fernando.
>>> PPMC Member & Committer of Apache Stratos,
>>> Senior Software Engineer, WSO2 Inc.
>>>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>
>>
>
>
> --
> Best Regards,
>
> Gayan Gunarathne
> Technical Lead
> WSO2 Inc. (http://wso2.com)
> email : gayang@wso2.com | mobile : +94 766819985
>
>
--
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware
web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
Re: MQTT Messaging + Python Cartridge Agent Testing Strategy
Posted by Gayan Gunarathne <ga...@wso2.com>.
+1 for this python cartridge testing
But I guess for the future release testing it is really nice if we can make
some automation testing to some extend.It will ease our testing workload
and time. Also it will make sure our existing functionality not affected
with those new changes.
IMO we can use following technologies as a start up
- Use selenium based test automation with Stratos web interface.
- Use automation shell scripts for the back end API calls.
Also for the REST API testing these are some frameworks exist as well
ex:frisby .I guess we can also look on to this as well.
As a start,we won't be able to cover all the test scenarios at once. But I
suppose we will be able to cover some extend. WDYT?
Please share your thoughts and suggestion on this.
Thanks,
Gayan
On Wed, Sep 24, 2014 at 12:33 PM, Chamila De Alwis <ch...@wso2.com>
wrote:
> We are currently executing the tests manually, since we couldn't find any
> automation context in Stratos.
>
> As the initial test run, we are testing the event publishing and
> subscribing scopes, and consequently we are extending the scope to artifact
> management and health statistics publishing.
>
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Wed, Sep 24, 2014 at 12:07 PM, Nirmal Fernando <ni...@gmail.com>
> wrote:
>
>> Nicely articulated Chamila! What's your plan to implement these tests?
>>
>> On Tue, Sep 23, 2014 at 8:34 PM, Chamila De Alwis <ch...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> For $subject, we decided to implement the following steps.
>>>
>>> Following aspects need to be tested from agent's point of view.
>>>
>>> 1) Listening to and publishing instance related events
>>> 2) Managing artifacts
>>> 3) Managing tenants based on tenant related events
>>> 4) Managing log publishing
>>>
>>> We chose the following three cartridge types to cover the above basic
>>> scenarios.
>>>
>>> 1) PHP - Single tenant framework cartridge
>>> 2) MySQL - Single tenant data cartridge
>>> 3) WSO2AS - Multi tenant cartridge
>>>
>>> The initial test cases are as follows.It is a work in progress, however
>>> further test cases will be added in the future.
>>>
>>> Please add your suggestions on any improvements.
>>>
>>>
>>> Cartridge Agent successfully publishes instance status events
>>> Prerequisites
>>> Stratos InstalledPuppet master configuredStratos policies deployedA
>>> base cartridge configuredMySQL cartridge definition deployed
>>>
>>> Steps
>>> StepExpected resultLog in to Stratos admin consoleMy Cartridges page
>>> will be displayedSubscribe to MySQL cartridgeMySQL subscription page
>>> will be loadedEnter a name for the cartridge and click SubscribeSubscription
>>> page will be displayed with MySQL cartridge marked as subscribedWait
>>> until cartridge is spawnedwso2carbon.log will output "Instance is
>>> successfully starting up." when the instance is spawning.SSH in to the
>>> spawned instance Successfully SSH in to the instanceCheck the log file,
>>> /tmp/puppet_log /tmp/puppet_log will out put "Initialization completed
>>> successfully." after puppet has successfully configured the instanceCheck
>>> the wso2carbon.log for the InstanceStartedEvent published from the
>>> cartridge agentwso2carbon.log will output the received event details.Check
>>> the wso2carbon.log for the InstanceActivatedEvent published from the
>>> cartridge agentwso2carbon.log will output the received event details.
>>>
>>>
>>>
>>>
>>>
>>> Cartridge Agent successfully listenes to instance notifier events
>>> Prerequisites
>>> Stratos InstalledPuppet master configuredStratos policies deployedA
>>> base cartridge configuredPHP cartridge definition deployed
>>>
>>> Steps
>>> StepExpected resultLog in to Stratos admin consoleMy Cartridges page
>>> will be displayedSubscribe to PHP cartridgePHP subscription page will
>>> be loadedEnter a name and the repository for the cartridge and click
>>> SubscribeSubscription page will be displayed with PHP cartridge marked
>>> as subscribedWait until cartridge is spawnedwso2carbon.log will output
>>> "Instance is successfully starting up." when the instance is spawning.SSH
>>> in to the spawned instance Successfully SSH in to the instanceCheck the
>>> log file, /tmp/puppet_log /tmp/puppet_log will out put "Initialization
>>> completed successfully." after puppet has successfully configured the
>>> instanceCheck for CompleteTopologyEvent and CompleteTenantEvent being
>>> listened to by the agent/var/log/apache-stratos/cartridge-agent-extensions.log
>>> file will out put information received with the mentioned eventsUpdate
>>> the remote repository with new files and check if the ArtifactUpdatedEvent
>>> was received by the cartridge agent/var/log/apache-stratos/cartridge-agent-extensions.log
>>> file will out put information received with the mentioned eventsRefresh
>>> the served pages and check if the updated pages are servedWeb
>>> application is updated with the new artifacts
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Software Engineer | WSO2 | +94772207163
>>> Blog: code.chamiladealwis.com
>>>
>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Nirmal
>>
>> Nirmal Fernando.
>> PPMC Member & Committer of Apache Stratos,
>> Senior Software Engineer, WSO2 Inc.
>>
>> Blog: http://nirmalfdo.blogspot.com/
>>
>
>
--
Best Regards,
Gayan Gunarathne
Technical Lead
WSO2 Inc. (http://wso2.com)
email : gayang@wso2.com | mobile : +94 766819985
Re: MQTT Messaging + Python Cartridge Agent Testing Strategy
Posted by Chamila De Alwis <ch...@wso2.com>.
We are currently executing the tests manually, since we couldn't find any
automation context in Stratos.
As the initial test run, we are testing the event publishing and
subscribing scopes, and consequently we are extending the scope to artifact
management and health statistics publishing.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Wed, Sep 24, 2014 at 12:07 PM, Nirmal Fernando <ni...@gmail.com>
wrote:
> Nicely articulated Chamila! What's your plan to implement these tests?
>
> On Tue, Sep 23, 2014 at 8:34 PM, Chamila De Alwis <ch...@wso2.com>
> wrote:
>
>> Hi,
>>
>> For $subject, we decided to implement the following steps.
>>
>> Following aspects need to be tested from agent's point of view.
>>
>> 1) Listening to and publishing instance related events
>> 2) Managing artifacts
>> 3) Managing tenants based on tenant related events
>> 4) Managing log publishing
>>
>> We chose the following three cartridge types to cover the above basic
>> scenarios.
>>
>> 1) PHP - Single tenant framework cartridge
>> 2) MySQL - Single tenant data cartridge
>> 3) WSO2AS - Multi tenant cartridge
>>
>> The initial test cases are as follows.It is a work in progress, however
>> further test cases will be added in the future.
>>
>> Please add your suggestions on any improvements.
>>
>>
>> Cartridge Agent successfully publishes instance status events
>> Prerequisites
>> Stratos InstalledPuppet master configuredStratos policies deployedA base
>> cartridge configuredMySQL cartridge definition deployed
>>
>> Steps
>> StepExpected resultLog in to Stratos admin consoleMy Cartridges page
>> will be displayedSubscribe to MySQL cartridgeMySQL subscription page
>> will be loadedEnter a name for the cartridge and click SubscribeSubscription
>> page will be displayed with MySQL cartridge marked as subscribedWait
>> until cartridge is spawnedwso2carbon.log will output "Instance is
>> successfully starting up." when the instance is spawning.SSH in to the
>> spawned instance Successfully SSH in to the instanceCheck the log file,
>> /tmp/puppet_log /tmp/puppet_log will out put "Initialization completed
>> successfully." after puppet has successfully configured the instanceCheck
>> the wso2carbon.log for the InstanceStartedEvent published from the
>> cartridge agentwso2carbon.log will output the received event details.Check
>> the wso2carbon.log for the InstanceActivatedEvent published from the
>> cartridge agentwso2carbon.log will output the received event details.
>>
>>
>>
>>
>>
>> Cartridge Agent successfully listenes to instance notifier events
>> Prerequisites
>> Stratos InstalledPuppet master configuredStratos policies deployedA base
>> cartridge configuredPHP cartridge definition deployed
>>
>> Steps
>> StepExpected resultLog in to Stratos admin consoleMy Cartridges page
>> will be displayedSubscribe to PHP cartridgePHP subscription page will be
>> loadedEnter a name and the repository for the cartridge and click
>> SubscribeSubscription page will be displayed with PHP cartridge marked
>> as subscribedWait until cartridge is spawnedwso2carbon.log will output
>> "Instance is successfully starting up." when the instance is spawning.SSH
>> in to the spawned instance Successfully SSH in to the instanceCheck the
>> log file, /tmp/puppet_log /tmp/puppet_log will out put "Initialization
>> completed successfully." after puppet has successfully configured the
>> instanceCheck for CompleteTopologyEvent and CompleteTenantEvent being
>> listened to by the agent/var/log/apache-stratos/cartridge-agent-extensions.log
>> file will out put information received with the mentioned eventsUpdate
>> the remote repository with new files and check if the ArtifactUpdatedEvent
>> was received by the cartridge agent/var/log/apache-stratos/cartridge-agent-extensions.log
>> file will out put information received with the mentioned eventsRefresh
>> the served pages and check if the updated pages are servedWeb
>> application is updated with the new artifacts
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
Re: MQTT Messaging + Python Cartridge Agent Testing Strategy
Posted by Nirmal Fernando <ni...@gmail.com>.
Nicely articulated Chamila! What's your plan to implement these tests?
On Tue, Sep 23, 2014 at 8:34 PM, Chamila De Alwis <ch...@wso2.com> wrote:
> Hi,
>
> For $subject, we decided to implement the following steps.
>
> Following aspects need to be tested from agent's point of view.
>
> 1) Listening to and publishing instance related events
> 2) Managing artifacts
> 3) Managing tenants based on tenant related events
> 4) Managing log publishing
>
> We chose the following three cartridge types to cover the above basic
> scenarios.
>
> 1) PHP - Single tenant framework cartridge
> 2) MySQL - Single tenant data cartridge
> 3) WSO2AS - Multi tenant cartridge
>
> The initial test cases are as follows.It is a work in progress, however
> further test cases will be added in the future.
>
> Please add your suggestions on any improvements.
>
>
> Cartridge Agent successfully publishes instance status events
> Prerequisites
> Stratos InstalledPuppet master configuredStratos policies deployedA base
> cartridge configuredMySQL cartridge definition deployed
>
> Steps
> StepExpected resultLog in to Stratos admin consoleMy Cartridges page will
> be displayedSubscribe to MySQL cartridgeMySQL subscription page will be
> loadedEnter a name for the cartridge and click SubscribeSubscription page
> will be displayed with MySQL cartridge marked as subscribedWait until
> cartridge is spawnedwso2carbon.log will output "Instance is successfully
> starting up." when the instance is spawning.SSH in to the spawned
> instance Successfully SSH in to the instanceCheck the log file,
> /tmp/puppet_log /tmp/puppet_log will out put "Initialization completed
> successfully." after puppet has successfully configured the instanceCheck
> the wso2carbon.log for the InstanceStartedEvent published from the
> cartridge agentwso2carbon.log will output the received event details.Check
> the wso2carbon.log for the InstanceActivatedEvent published from the
> cartridge agentwso2carbon.log will output the received event details.
>
>
>
>
>
> Cartridge Agent successfully listenes to instance notifier events
> Prerequisites
> Stratos InstalledPuppet master configuredStratos policies deployedA base
> cartridge configuredPHP cartridge definition deployed
>
> Steps
> StepExpected resultLog in to Stratos admin consoleMy Cartridges page will
> be displayedSubscribe to PHP cartridgePHP subscription page will be loadedEnter
> a name and the repository for the cartridge and click SubscribeSubscription
> page will be displayed with PHP cartridge marked as subscribedWait until
> cartridge is spawnedwso2carbon.log will output "Instance is successfully
> starting up." when the instance is spawning.SSH in to the spawned
> instance Successfully SSH in to the instanceCheck the log file,
> /tmp/puppet_log /tmp/puppet_log will out put "Initialization completed
> successfully." after puppet has successfully configured the instanceCheck
> for CompleteTopologyEvent and CompleteTenantEvent being listened to by the
> agent/var/log/apache-stratos/cartridge-agent-extensions.log file will out
> put information received with the mentioned eventsUpdate the remote
> repository with new files and check if the ArtifactUpdatedEvent was
> received by the cartridge agent/var/log/apache-stratos/cartridge-agent-extensions.log
> file will out put information received with the mentioned eventsRefresh
> the served pages and check if the updated pages are servedWeb application
> is updated with the new artifacts
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: MQTT Messaging + Python Cartridge Agent Testing Strategy
Posted by Dinesh Bandara <di...@wso2.com>.
On Tue, Sep 23, 2014 at 9:25 PM, Manula Chathurika Thantriwatte <
manulac@wso2.com> wrote:
> Hi Chamila,
>
> +1 for test cases. Are you going to test auto-scaling as well ? What I
> mean here is publishing summarize health stats from python cartridge agent
> and according to those health stats we have to check whether the
> auto-scaling is functioning as expected.
>
AFAIK health stats need to be published in to CEP via thrift
>
> Thanks !
>
> On Tue, Sep 23, 2014 at 8:34 PM, Chamila De Alwis <ch...@wso2.com>
> wrote:
>
>> Hi,
>>
>> For $subject, we decided to implement the following steps.
>>
>> Following aspects need to be tested from agent's point of view.
>>
>> 1) Listening to and publishing instance related events
>> 2) Managing artifacts
>> 3) Managing tenants based on tenant related events
>> 4) Managing log publishing
>>
>> We chose the following three cartridge types to cover the above basic
>> scenarios.
>>
>> 1) PHP - Single tenant framework cartridge
>> 2) MySQL - Single tenant data cartridge
>> 3) WSO2AS - Multi tenant cartridge
>>
>> The initial test cases are as follows.It is a work in progress, however
>> further test cases will be added in the future.
>>
>> Please add your suggestions on any improvements.
>>
>>
>> Cartridge Agent successfully publishes instance status events
>> Prerequisites
>> Stratos InstalledPuppet master configuredStratos policies deployedA base
>> cartridge configuredMySQL cartridge definition deployed
>>
>> Steps
>> StepExpected resultLog in to Stratos admin consoleMy Cartridges page
>> will be displayedSubscribe to MySQL cartridgeMySQL subscription page
>> will be loadedEnter a name for the cartridge and click SubscribeSubscription
>> page will be displayed with MySQL cartridge marked as subscribedWait
>> until cartridge is spawnedwso2carbon.log will output "Instance is
>> successfully starting up." when the instance is spawning.SSH in to the
>> spawned instance Successfully SSH in to the instanceCheck the log file,
>> /tmp/puppet_log /tmp/puppet_log will out put "Initialization completed
>> successfully." after puppet has successfully configured the instanceCheck
>> the wso2carbon.log for the InstanceStartedEvent published from the
>> cartridge agentwso2carbon.log will output the received event details.Check
>> the wso2carbon.log for the InstanceActivatedEvent published from the
>> cartridge agentwso2carbon.log will output the received event details.
>>
>>
>>
>>
>>
>> Cartridge Agent successfully listenes to instance notifier events
>> Prerequisites
>> Stratos InstalledPuppet master configuredStratos policies deployedA base
>> cartridge configuredPHP cartridge definition deployed
>>
>> Steps
>> StepExpected resultLog in to Stratos admin consoleMy Cartridges page
>> will be displayedSubscribe to PHP cartridgePHP subscription page will be
>> loadedEnter a name and the repository for the cartridge and click
>> SubscribeSubscription page will be displayed with PHP cartridge marked
>> as subscribedWait until cartridge is spawnedwso2carbon.log will output
>> "Instance is successfully starting up." when the instance is spawning.SSH
>> in to the spawned instance Successfully SSH in to the instanceCheck the
>> log file, /tmp/puppet_log /tmp/puppet_log will out put "Initialization
>> completed successfully." after puppet has successfully configured the
>> instanceCheck for CompleteTopologyEvent and CompleteTenantEvent being
>> listened to by the agent/var/log/apache-stratos/cartridge-agent-extensions.log
>> file will out put information received with the mentioned eventsUpdate
>> the remote repository with new files and check if the ArtifactUpdatedEvent
>> was received by the cartridge agent/var/log/apache-stratos/cartridge-agent-extensions.log
>> file will out put information received with the mentioned eventsRefresh
>> the served pages and check if the updated pages are servedWeb
>> application is updated with the new artifacts
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>
>
> --
> Regards,
> Manula Chathurika Thantriwatte
> Software Engineer
> WSO2 Inc. : http://wso2.com
> lean . enterprise . middleware
>
> email : manulac@wso2.com / manula@apache.org
> phone : +94 772492511
> blog : http://manulachathurika.blogspot.com/
>
>
>
>
--
*Dinesh Bandara*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
Re: MQTT Messaging + Python Cartridge Agent Testing Strategy
Posted by Chamila De Alwis <ch...@wso2.com>.
Hi Manula,
Currently there's no plan to test auto scaling. The method, as we've
planned, is to test the publishing side of the health topic. Autoscaling as
an end to end test case will not be included in our scope.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Tue, Sep 23, 2014 at 9:25 PM, Manula Chathurika Thantriwatte <
manulac@wso2.com> wrote:
> Hi Chamila,
>
> +1 for test cases. Are you going to test auto-scaling as well ? What I
> mean here is publishing summarize health stats from python cartridge agent
> and according to those health stats we have to check whether the
> auto-scaling is functioning as expected.
>
> Thanks !
>
> On Tue, Sep 23, 2014 at 8:34 PM, Chamila De Alwis <ch...@wso2.com>
> wrote:
>
>> Hi,
>>
>> For $subject, we decided to implement the following steps.
>>
>> Following aspects need to be tested from agent's point of view.
>>
>> 1) Listening to and publishing instance related events
>> 2) Managing artifacts
>> 3) Managing tenants based on tenant related events
>> 4) Managing log publishing
>>
>> We chose the following three cartridge types to cover the above basic
>> scenarios.
>>
>> 1) PHP - Single tenant framework cartridge
>> 2) MySQL - Single tenant data cartridge
>> 3) WSO2AS - Multi tenant cartridge
>>
>> The initial test cases are as follows.It is a work in progress, however
>> further test cases will be added in the future.
>>
>> Please add your suggestions on any improvements.
>>
>>
>> Cartridge Agent successfully publishes instance status events
>> Prerequisites
>> Stratos InstalledPuppet master configuredStratos policies deployedA base
>> cartridge configuredMySQL cartridge definition deployed
>>
>> Steps
>> StepExpected resultLog in to Stratos admin consoleMy Cartridges page
>> will be displayedSubscribe to MySQL cartridgeMySQL subscription page
>> will be loadedEnter a name for the cartridge and click SubscribeSubscription
>> page will be displayed with MySQL cartridge marked as subscribedWait
>> until cartridge is spawnedwso2carbon.log will output "Instance is
>> successfully starting up." when the instance is spawning.SSH in to the
>> spawned instance Successfully SSH in to the instanceCheck the log file,
>> /tmp/puppet_log /tmp/puppet_log will out put "Initialization completed
>> successfully." after puppet has successfully configured the instanceCheck
>> the wso2carbon.log for the InstanceStartedEvent published from the
>> cartridge agentwso2carbon.log will output the received event details.Check
>> the wso2carbon.log for the InstanceActivatedEvent published from the
>> cartridge agentwso2carbon.log will output the received event details.
>>
>>
>>
>>
>>
>> Cartridge Agent successfully listenes to instance notifier events
>> Prerequisites
>> Stratos InstalledPuppet master configuredStratos policies deployedA base
>> cartridge configuredPHP cartridge definition deployed
>>
>> Steps
>> StepExpected resultLog in to Stratos admin consoleMy Cartridges page
>> will be displayedSubscribe to PHP cartridgePHP subscription page will be
>> loadedEnter a name and the repository for the cartridge and click
>> SubscribeSubscription page will be displayed with PHP cartridge marked
>> as subscribedWait until cartridge is spawnedwso2carbon.log will output
>> "Instance is successfully starting up." when the instance is spawning.SSH
>> in to the spawned instance Successfully SSH in to the instanceCheck the
>> log file, /tmp/puppet_log /tmp/puppet_log will out put "Initialization
>> completed successfully." after puppet has successfully configured the
>> instanceCheck for CompleteTopologyEvent and CompleteTenantEvent being
>> listened to by the agent/var/log/apache-stratos/cartridge-agent-extensions.log
>> file will out put information received with the mentioned eventsUpdate
>> the remote repository with new files and check if the ArtifactUpdatedEvent
>> was received by the cartridge agent/var/log/apache-stratos/cartridge-agent-extensions.log
>> file will out put information received with the mentioned eventsRefresh
>> the served pages and check if the updated pages are servedWeb
>> application is updated with the new artifacts
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>
>
> --
> Regards,
> Manula Chathurika Thantriwatte
> Software Engineer
> WSO2 Inc. : http://wso2.com
> lean . enterprise . middleware
>
> email : manulac@wso2.com / manula@apache.org
> phone : +94 772492511
> blog : http://manulachathurika.blogspot.com/
>
>
>
>
Re: MQTT Messaging + Python Cartridge Agent Testing Strategy
Posted by Dinesh Bandara <di...@wso2.com>.
On Tue, Sep 23, 2014 at 9:25 PM, Manula Chathurika Thantriwatte <
manulac@wso2.com> wrote:
> Hi Chamila,
>
> +1 for test cases. Are you going to test auto-scaling as well ? What I
> mean here is publishing summarize health stats from python cartridge agent
> and according to those health stats we have to check whether the
> auto-scaling is functioning as expected.
>
> Thanks !
>
> On Tue, Sep 23, 2014 at 8:34 PM, Chamila De Alwis <ch...@wso2.com>
> wrote:
>
>> Hi,
>>
>> For $subject, we decided to implement the following steps.
>>
>> Following aspects need to be tested from agent's point of view.
>>
>> 1) Listening to and publishing instance related events
>> 2) Managing artifacts
>> 3) Managing tenants based on tenant related events
>> 4) Managing log publishing
>>
>> We chose the following three cartridge types to cover the above basic
>> scenarios.
>>
>> 1) PHP - Single tenant framework cartridge
>> 2) MySQL - Single tenant data cartridge
>> 3) WSO2AS - Multi tenant cartridge
>>
>> The initial test cases are as follows.It is a work in progress, however
>> further test cases will be added in the future.
>>
>> Please add your suggestions on any improvements.
>>
>>
>> Cartridge Agent successfully publishes instance status events
>> Prerequisites
>> Stratos InstalledPuppet master configuredStratos policies deployedA base
>> cartridge configuredMySQL cartridge definition deployed
>>
>> Steps
>> StepExpected resultLog in to Stratos admin consoleMy Cartridges page
>> will be displayedSubscribe to MySQL cartridgeMySQL subscription page
>> will be loadedEnter a name for the cartridge and click SubscribeSubscription
>> page will be displayed with MySQL cartridge marked as subscribedWait
>> until cartridge is spawnedwso2carbon.log will output "Instance is
>> successfully starting up." when the instance is spawning.SSH in to the
>> spawned instance Successfully SSH in to the instanceCheck the log file,
>> /tmp/puppet_log /tmp/puppet_log will out put "Initialization completed
>> successfully." after puppet has successfully configured the instanceCheck
>> the wso2carbon.log for the InstanceStartedEvent published from the
>> cartridge agentwso2carbon.log will output the received event details.Check
>> the wso2carbon.log for the InstanceActivatedEvent published from the
>> cartridge agentwso2carbon.log will output the received event details.
>>
>>
>>
>>
>>
>> Cartridge Agent successfully listenes to instance notifier events
>> Prerequisites
>> Stratos InstalledPuppet master configuredStratos policies deployedA base
>> cartridge configuredPHP cartridge definition deployed
>>
>> Steps
>> StepExpected resultLog in to Stratos admin consoleMy Cartridges page
>> will be displayedSubscribe to PHP cartridgePHP subscription page will be
>> loadedEnter a name and the repository for the cartridge and click
>> SubscribeSubscription page will be displayed with PHP cartridge marked
>> as subscribedWait until cartridge is spawnedwso2carbon.log will output
>> "Instance is successfully starting up." when the instance is spawning.SSH
>> in to the spawned instance Successfully SSH in to the instanceCheck the
>> log file, /tmp/puppet_log /tmp/puppet_log will out put "Initialization
>> completed successfully." after puppet has successfully configured the
>> instanceCheck for CompleteTopologyEvent and CompleteTenantEvent being
>> listened to by the agent/var/log/apache-stratos/cartridge-agent-extensions.log
>> file will out put information received with the mentioned eventsUpdate
>> the remote repository with new files and check if the ArtifactUpdatedEvent
>> was received by the cartridge agent/var/log/apache-stratos/cartridge-agent-extensions.log
>> file will out put information received with the mentioned eventsRefresh
>> the served pages and check if the updated pages are servedWeb
>> application is updated with the new artifacts
>>
>> Regards,
>> Chamila de Alwis
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>
>
> --
> Regards,
> Manula Chathurika Thantriwatte
> Software Engineer
> WSO2 Inc. : http://wso2.com
> lean . enterprise . middleware
>
> email : manulac@wso2.com / manula@apache.org
> phone : +94 772492511
> blog : http://manulachathurika.blogspot.com/
>
>
>
>
--
*Dinesh Bandara*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
Re: MQTT Messaging + Python Cartridge Agent Testing Strategy
Posted by Manula Chathurika Thantriwatte <ma...@wso2.com>.
Hi Chamila,
+1 for test cases. Are you going to test auto-scaling as well ? What I mean
here is publishing summarize health stats from python cartridge agent and
according to those health stats we have to check whether the auto-scaling
is functioning as expected.
Thanks !
On Tue, Sep 23, 2014 at 8:34 PM, Chamila De Alwis <ch...@wso2.com> wrote:
> Hi,
>
> For $subject, we decided to implement the following steps.
>
> Following aspects need to be tested from agent's point of view.
>
> 1) Listening to and publishing instance related events
> 2) Managing artifacts
> 3) Managing tenants based on tenant related events
> 4) Managing log publishing
>
> We chose the following three cartridge types to cover the above basic
> scenarios.
>
> 1) PHP - Single tenant framework cartridge
> 2) MySQL - Single tenant data cartridge
> 3) WSO2AS - Multi tenant cartridge
>
> The initial test cases are as follows.It is a work in progress, however
> further test cases will be added in the future.
>
> Please add your suggestions on any improvements.
>
>
> Cartridge Agent successfully publishes instance status events
> Prerequisites
> Stratos InstalledPuppet master configuredStratos policies deployedA base
> cartridge configuredMySQL cartridge definition deployed
>
> Steps
> StepExpected resultLog in to Stratos admin consoleMy Cartridges page will
> be displayedSubscribe to MySQL cartridgeMySQL subscription page will be
> loadedEnter a name for the cartridge and click SubscribeSubscription page
> will be displayed with MySQL cartridge marked as subscribedWait until
> cartridge is spawnedwso2carbon.log will output "Instance is successfully
> starting up." when the instance is spawning.SSH in to the spawned
> instance Successfully SSH in to the instanceCheck the log file,
> /tmp/puppet_log /tmp/puppet_log will out put "Initialization completed
> successfully." after puppet has successfully configured the instanceCheck
> the wso2carbon.log for the InstanceStartedEvent published from the
> cartridge agentwso2carbon.log will output the received event details.Check
> the wso2carbon.log for the InstanceActivatedEvent published from the
> cartridge agentwso2carbon.log will output the received event details.
>
>
>
>
>
> Cartridge Agent successfully listenes to instance notifier events
> Prerequisites
> Stratos InstalledPuppet master configuredStratos policies deployedA base
> cartridge configuredPHP cartridge definition deployed
>
> Steps
> StepExpected resultLog in to Stratos admin consoleMy Cartridges page will
> be displayedSubscribe to PHP cartridgePHP subscription page will be loadedEnter
> a name and the repository for the cartridge and click SubscribeSubscription
> page will be displayed with PHP cartridge marked as subscribedWait until
> cartridge is spawnedwso2carbon.log will output "Instance is successfully
> starting up." when the instance is spawning.SSH in to the spawned
> instance Successfully SSH in to the instanceCheck the log file,
> /tmp/puppet_log /tmp/puppet_log will out put "Initialization completed
> successfully." after puppet has successfully configured the instanceCheck
> for CompleteTopologyEvent and CompleteTenantEvent being listened to by the
> agent/var/log/apache-stratos/cartridge-agent-extensions.log file will out
> put information received with the mentioned eventsUpdate the remote
> repository with new files and check if the ArtifactUpdatedEvent was
> received by the cartridge agent/var/log/apache-stratos/cartridge-agent-extensions.log
> file will out put information received with the mentioned eventsRefresh
> the served pages and check if the updated pages are servedWeb application
> is updated with the new artifacts
>
> Regards,
> Chamila de Alwis
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
--
Regards,
Manula Chathurika Thantriwatte
Software Engineer
WSO2 Inc. : http://wso2.com
lean . enterprise . middleware
email : manulac@wso2.com / manula@apache.org
phone : +94 772492511
blog : http://manulachathurika.blogspot.com/