Re: [Dev] GSoC 2017 - JMeter Test Manager for Distributed Deployments of WSO2 Servers

[Yasassri Ratnayake]

Hi Thilina,

As explained offline. You can decouple the docker image creation logic from
the web app. But the image creation should be automated. Please have a look
at existing Docker file creation scripts.

Please let us know if you have more queries.

With Regards,
Yasassri

On Fri, Mar 31, 2017 at 3:51 PM, Thilina Manamgoda 
wrote:

> Hi Yasassri,
>
> What If we configure the web app such that we can add Deployment profiles
> as we go on. We can build this for existing profiles and if there is a
> profile we can build docker images and Kubernetes artifacts and configure
> them in the web app. Is this approach acceptable ?
>
> regards,
> Thilina
>
> On Fri, Mar 31, 2017 at 8:32 AM, Yasassri Ratnayake 
> wrote:
>
>> On Thu, Mar 30, 2017 at 6:19 PM, Thilina Manamgoda > > wrote:
>>
>>> Hi Yasassri,
>>>
>>> I think if we can build docker files  for each profile and kept in a
>>> private registry it would be easy. If this is possible no need to build
>>> Docker images in web app. Also we need to build Kubernetes artifacts for
>>> those profile as well.
>>>
>>
>> What you need to take into cosideration is, that the pack (e.g : ESB
>> 4.9.0) is going to change, we are planning to use this to Test packs
>> released with WUM (WSO2 Update Manager) as well. WUM gives a new
>> distribution pack with the latest fixes. So we need to cater this as well.
>>
>>
>>>
>>> regards,
>>> Thilina
>>>
>>> On Mon, Mar 27, 2017 at 8:49 AM, Yasassri Ratnayake 
>>> wrote:
>>>
 Hi Thilina,

 On Sun, Mar 26, 2017 at 4:07 AM, Thilina Manamgoda <
 maanafun...@gmail.com> wrote:

> Hi Yasassri,
>
> Please find my comments inline.
>
> On Wed, Mar 22, 2017 at 8:12 PM, Yasassri Ratnayake  > wrote:
>
>> Hi Thilina,
>>
>> We have missed some requirements. Please consider the following as
>> well.
>>
>> 1. We need a Tomcat instance to host the Backends(Weapps) which are
>> required by the Test Scripts. So we need another instance spawned with
>> Tomcat. After spawning the instance you can deploy the prerequisite web
>> apps. (These web apps will be available in the Test-Repo under resources)
>>
>
>  Yes of course we can archieve this as well.
>
> 2. Also when deploying Jmeter we need to copy 3rd party Jars to
>> Jmeter. (These are also available in the repository)
>>
>
>
>> This can be done by copying these files to docker image in Jmeter
>> docker image building stage.
>>
>
>
>> Also answering your question about the Deployment profiles. We have
>> identified several components to make the scope manageable.
>>
>> *Products*
>> ESB | V4.9 & V5.0
>> APIM | V1.9 & V2.0
>>
>> *JDK*
>> JAVA | V1.7 & V1.8
>>
>> *DataBase*
>> MySQL
>>
>> *Third Party Servers*
>> Brokers | ActiveMQ 5.10 | WSO2 MB 3.1 (Only applicable when ESB is
>> used)
>>
>> So a Sample Profile would be, *ESB 4.9 + JAVA 1.7 + MYSQL + ActiveMQ*.
>> For now, you can concentrate on the above components when determining a
>> deployment profile. But your solution should be scalable.
>>
>> Is this a profile described here:https://docs.wso2.com/dis
> play/KA100/Clustered+Deployment+of+WSO2+Products+on+Kubernetes . If
> it is, then do I need to configure the product with third party servers or
> it's already done and I only have to deploy selected profile's servers 
> into
> kubernetes cluster. For example let's take the above profile, in order to
> run this delpoyment ESB should be configured with MYSQL and Active MQ API
> endpoints. Do i need to change the configuration files of ESB or it's
> already taken care of and deployment is done once i deploy Kubernetes
> artifacts under the selected profile.
>

 Existing scripts doesn't allow us to configure thirdparty dependencies
 like Message Brokers. So yes we need to change ESB configurations depending
 on the Broker, you can refer [1
 ] for
 ActiveMQ configurations.


>
> Is this a profile of ESB : https://github.com/wso2/kube
> rnetes-artifacts/tree/master/wso2esb ?
>

 Yes this script supports two profiles, default ESB profile and worker
 manager profile, but as mentioned we neeed to tweek these scripts to
 support mesage brokers as well.


> Also can't we have a private docker registry to hold our deplyment's
> images instead of building docker images via the web app ?.
>
>>
>>
 We can use a private registry to store the docker images but you need
 to comeup with some scripts to Auomate the process in that case.


 [1] - https://docs.wso2.com/display/ESB490/Configure+with+ActiveMQ
 --
 

Re: [Dev] GSoC 2017 - JMeter Test Manager for Distributed Deployments of WSO2 Servers

[Thilina Manamgoda]

Hi Yasassri,

What If we configure the web app such that we can add Deployment profiles
as we go on. We can build this for existing profiles and if there is a
profile we can build docker images and Kubernetes artifacts and configure
them in the web app. Is this approach acceptable ?

regards,
Thilina

On Fri, Mar 31, 2017 at 8:32 AM, Yasassri Ratnayake 
wrote:

> On Thu, Mar 30, 2017 at 6:19 PM, Thilina Manamgoda 
> wrote:
>
>> Hi Yasassri,
>>
>> I think if we can build docker files  for each profile and kept in a
>> private registry it would be easy. If this is possible no need to build
>> Docker images in web app. Also we need to build Kubernetes artifacts for
>> those profile as well.
>>
>
> What you need to take into cosideration is, that the pack (e.g : ESB
> 4.9.0) is going to change, we are planning to use this to Test packs
> released with WUM (WSO2 Update Manager) as well. WUM gives a new
> distribution pack with the latest fixes. So we need to cater this as well.
>
>
>>
>> regards,
>> Thilina
>>
>> On Mon, Mar 27, 2017 at 8:49 AM, Yasassri Ratnayake 
>> wrote:
>>
>>> Hi Thilina,
>>>
>>> On Sun, Mar 26, 2017 at 4:07 AM, Thilina Manamgoda <
>>> maanafun...@gmail.com> wrote:
>>>
 Hi Yasassri,

 Please find my comments inline.

 On Wed, Mar 22, 2017 at 8:12 PM, Yasassri Ratnayake 
 wrote:

> Hi Thilina,
>
> We have missed some requirements. Please consider the following as
> well.
>
> 1. We need a Tomcat instance to host the Backends(Weapps) which are
> required by the Test Scripts. So we need another instance spawned with
> Tomcat. After spawning the instance you can deploy the prerequisite web
> apps. (These web apps will be available in the Test-Repo under resources)
>

  Yes of course we can archieve this as well.

 2. Also when deploying Jmeter we need to copy 3rd party Jars to Jmeter.
> (These are also available in the repository)
>


> This can be done by copying these files to docker image in Jmeter
> docker image building stage.
>


> Also answering your question about the Deployment profiles. We have
> identified several components to make the scope manageable.
>
> *Products*
> ESB | V4.9 & V5.0
> APIM | V1.9 & V2.0
>
> *JDK*
> JAVA | V1.7 & V1.8
>
> *DataBase*
> MySQL
>
> *Third Party Servers*
> Brokers | ActiveMQ 5.10 | WSO2 MB 3.1 (Only applicable when ESB is
> used)
>
> So a Sample Profile would be, *ESB 4.9 + JAVA 1.7 + MYSQL + ActiveMQ*.
> For now, you can concentrate on the above components when determining a
> deployment profile. But your solution should be scalable.
>
> Is this a profile described here:https://docs.wso2.com/dis
 play/KA100/Clustered+Deployment+of+WSO2+Products+on+Kubernetes . If it
 is, then do I need to configure the product with third party servers or
 it's already done and I only have to deploy selected profile's servers into
 kubernetes cluster. For example let's take the above profile, in order to
 run this delpoyment ESB should be configured with MYSQL and Active MQ API
 endpoints. Do i need to change the configuration files of ESB or it's
 already taken care of and deployment is done once i deploy Kubernetes
 artifacts under the selected profile.

>>>
>>> Existing scripts doesn't allow us to configure thirdparty dependencies
>>> like Message Brokers. So yes we need to change ESB configurations depending
>>> on the Broker, you can refer [1
>>> ] for
>>> ActiveMQ configurations.
>>>
>>>

 Is this a profile of ESB : https://github.com/wso2/kube
 rnetes-artifacts/tree/master/wso2esb ?

>>>
>>> Yes this script supports two profiles, default ESB profile and worker
>>> manager profile, but as mentioned we neeed to tweek these scripts to
>>> support mesage brokers as well.
>>>
>>>
 Also can't we have a private docker registry to hold our deplyment's
 images instead of building docker images via the web app ?.

>
>
>>> We can use a private registry to store the docker images but you need to
>>> comeup with some scripts to Auomate the process in that case.
>>>
>>>
>>> [1] - https://docs.wso2.com/display/ESB490/Configure+with+ActiveMQ
>>> --
>>> Yasassri Ratnayake
>>> Senior Software Engineer - QA
>>> WSO2 Inc ; http://wso2.com
>>> lean.enterprise.middleware
>>> *Mobile : +94715933168 <+94%2071%20593%203168>*
>>> *Blogs : http://yasassriratnayake.blogspot.com
>>> *
>>> *http://wso2logs.blogspot.com *
>>>
>>
>>
>
>
> --
> Yasassri Ratnayake
> Senior Software Engineer - QA
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
> *Mobile : +94715933168 

Re: [Dev] GSoC 2017 - JMeter Test Manager for Distributed Deployments of WSO2 Servers

[Yasassri Ratnayake]

On Thu, Mar 30, 2017 at 6:19 PM, Thilina Manamgoda 
wrote:

> Hi Yasassri,
>
> I think if we can build docker files  for each profile and kept in a
> private registry it would be easy. If this is possible no need to build
> Docker images in web app. Also we need to build Kubernetes artifacts for
> those profile as well.
>

What you need to take into cosideration is, that the pack (e.g : ESB 4.9.0)
is going to change, we are planning to use this to Test packs released with
WUM (WSO2 Update Manager) as well. WUM gives a new distribution pack with
the latest fixes. So we need to cater this as well.


>
> regards,
> Thilina
>
> On Mon, Mar 27, 2017 at 8:49 AM, Yasassri Ratnayake 
> wrote:
>
>> Hi Thilina,
>>
>> On Sun, Mar 26, 2017 at 4:07 AM, Thilina Manamgoda > > wrote:
>>
>>> Hi Yasassri,
>>>
>>> Please find my comments inline.
>>>
>>> On Wed, Mar 22, 2017 at 8:12 PM, Yasassri Ratnayake 
>>> wrote:
>>>
 Hi Thilina,

 We have missed some requirements. Please consider the following as well.

 1. We need a Tomcat instance to host the Backends(Weapps) which are
 required by the Test Scripts. So we need another instance spawned with
 Tomcat. After spawning the instance you can deploy the prerequisite web
 apps. (These web apps will be available in the Test-Repo under resources)

>>>
>>>  Yes of course we can archieve this as well.
>>>
>>> 2. Also when deploying Jmeter we need to copy 3rd party Jars to Jmeter.
 (These are also available in the repository)

>>>
>>>
 This can be done by copying these files to docker image in Jmeter
 docker image building stage.

>>>
>>>
 Also answering your question about the Deployment profiles. We have
 identified several components to make the scope manageable.

 *Products*
 ESB | V4.9 & V5.0
 APIM | V1.9 & V2.0

 *JDK*
 JAVA | V1.7 & V1.8

 *DataBase*
 MySQL

 *Third Party Servers*
 Brokers | ActiveMQ 5.10 | WSO2 MB 3.1 (Only applicable when ESB is used)

 So a Sample Profile would be, *ESB 4.9 + JAVA 1.7 + MYSQL + ActiveMQ*.
 For now, you can concentrate on the above components when determining a
 deployment profile. But your solution should be scalable.

 Is this a profile described here:https://docs.wso2.com/dis
>>> play/KA100/Clustered+Deployment+of+WSO2+Products+on+Kubernetes . If it
>>> is, then do I need to configure the product with third party servers or
>>> it's already done and I only have to deploy selected profile's servers into
>>> kubernetes cluster. For example let's take the above profile, in order to
>>> run this delpoyment ESB should be configured with MYSQL and Active MQ API
>>> endpoints. Do i need to change the configuration files of ESB or it's
>>> already taken care of and deployment is done once i deploy Kubernetes
>>> artifacts under the selected profile.
>>>
>>
>> Existing scripts doesn't allow us to configure thirdparty dependencies
>> like Message Brokers. So yes we need to change ESB configurations depending
>> on the Broker, you can refer [1
>> ] for
>> ActiveMQ configurations.
>>
>>
>>>
>>> Is this a profile of ESB : https://github.com/wso2/kube
>>> rnetes-artifacts/tree/master/wso2esb ?
>>>
>>
>> Yes this script supports two profiles, default ESB profile and worker
>> manager profile, but as mentioned we neeed to tweek these scripts to
>> support mesage brokers as well.
>>
>>
>>> Also can't we have a private docker registry to hold our deplyment's
>>> images instead of building docker images via the web app ?.
>>>


>> We can use a private registry to store the docker images but you need to
>> comeup with some scripts to Auomate the process in that case.
>>
>>
>> [1] - https://docs.wso2.com/display/ESB490/Configure+with+ActiveMQ
>> --
>> Yasassri Ratnayake
>> Senior Software Engineer - QA
>> WSO2 Inc ; http://wso2.com
>> lean.enterprise.middleware
>> *Mobile : +94715933168 <+94%2071%20593%203168>*
>> *Blogs : http://yasassriratnayake.blogspot.com
>> *
>> *http://wso2logs.blogspot.com *
>>
>
>


-- 
Yasassri Ratnayake
Senior Software Engineer - QA
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
*Mobile : +94715933168 <+94%2071%20593%203168>*
*Blogs : http://yasassriratnayake.blogspot.com
*
*http://wso2logs.blogspot.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC 2017 - JMeter Test Manager for Distributed Deployments of WSO2 Servers

[Thilina Manamgoda]

Hi Yasassri,

I think if we can build docker files  for each profile and kept in a
private registry it would be easy. If this is possible no need to build
Docker images in web app. Also we need to build Kubernetes artifacts for
those profile as well.

regards,
Thilina

On Mon, Mar 27, 2017 at 8:49 AM, Yasassri Ratnayake 
wrote:

> Hi Thilina,
>
> On Sun, Mar 26, 2017 at 4:07 AM, Thilina Manamgoda 
> wrote:
>
>> Hi Yasassri,
>>
>> Please find my comments inline.
>>
>> On Wed, Mar 22, 2017 at 8:12 PM, Yasassri Ratnayake 
>> wrote:
>>
>>> Hi Thilina,
>>>
>>> We have missed some requirements. Please consider the following as well.
>>>
>>> 1. We need a Tomcat instance to host the Backends(Weapps) which are
>>> required by the Test Scripts. So we need another instance spawned with
>>> Tomcat. After spawning the instance you can deploy the prerequisite web
>>> apps. (These web apps will be available in the Test-Repo under resources)
>>>
>>
>>  Yes of course we can archieve this as well.
>>
>> 2. Also when deploying Jmeter we need to copy 3rd party Jars to Jmeter.
>>> (These are also available in the repository)
>>>
>>
>>
>>> This can be done by copying these files to docker image in Jmeter docker
>>> image building stage.
>>>
>>
>>
>>> Also answering your question about the Deployment profiles. We have
>>> identified several components to make the scope manageable.
>>>
>>> *Products*
>>> ESB | V4.9 & V5.0
>>> APIM | V1.9 & V2.0
>>>
>>> *JDK*
>>> JAVA | V1.7 & V1.8
>>>
>>> *DataBase*
>>> MySQL
>>>
>>> *Third Party Servers*
>>> Brokers | ActiveMQ 5.10 | WSO2 MB 3.1 (Only applicable when ESB is used)
>>>
>>> So a Sample Profile would be, *ESB 4.9 + JAVA 1.7 + MYSQL + ActiveMQ*.
>>> For now, you can concentrate on the above components when determining a
>>> deployment profile. But your solution should be scalable.
>>>
>>> Is this a profile described here:https://docs.wso2.com/dis
>> play/KA100/Clustered+Deployment+of+WSO2+Products+on+Kubernetes . If it
>> is, then do I need to configure the product with third party servers or
>> it's already done and I only have to deploy selected profile's servers into
>> kubernetes cluster. For example let's take the above profile, in order to
>> run this delpoyment ESB should be configured with MYSQL and Active MQ API
>> endpoints. Do i need to change the configuration files of ESB or it's
>> already taken care of and deployment is done once i deploy Kubernetes
>> artifacts under the selected profile.
>>
>
> Existing scripts doesn't allow us to configure thirdparty dependencies
> like Message Brokers. So yes we need to change ESB configurations depending
> on the Broker, you can refer [1
> ] for
> ActiveMQ configurations.
>
>
>>
>> Is this a profile of ESB : https://github.com/wso2/kube
>> rnetes-artifacts/tree/master/wso2esb ?
>>
>
> Yes this script supports two profiles, default ESB profile and worker
> manager profile, but as mentioned we neeed to tweek these scripts to
> support mesage brokers as well.
>
>
>> Also can't we have a private docker registry to hold our deplyment's
>> images instead of building docker images via the web app ?.
>>
>>>
>>>
> We can use a private registry to store the docker images but you need to
> comeup with some scripts to Auomate the process in that case.
>
>
> [1] - https://docs.wso2.com/display/ESB490/Configure+with+ActiveMQ
> --
> Yasassri Ratnayake
> Senior Software Engineer - QA
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
> *Mobile : +94715933168 <+94%2071%20593%203168>*
> *Blogs : http://yasassriratnayake.blogspot.com
> *
> *http://wso2logs.blogspot.com *
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC 2017 - JMeter Test Manager for Distributed Deployments of WSO2 Servers

[Yasassri Ratnayake]

Hi Thilina,

On Sun, Mar 26, 2017 at 4:07 AM, Thilina Manamgoda 
wrote:

> Hi Yasassri,
>
> Please find my comments inline.
>
> On Wed, Mar 22, 2017 at 8:12 PM, Yasassri Ratnayake 
> wrote:
>
>> Hi Thilina,
>>
>> We have missed some requirements. Please consider the following as well.
>>
>> 1. We need a Tomcat instance to host the Backends(Weapps) which are
>> required by the Test Scripts. So we need another instance spawned with
>> Tomcat. After spawning the instance you can deploy the prerequisite web
>> apps. (These web apps will be available in the Test-Repo under resources)
>>
>
>  Yes of course we can archieve this as well.
>
> 2. Also when deploying Jmeter we need to copy 3rd party Jars to Jmeter.
>> (These are also available in the repository)
>>
>
>
>> This can be done by copying these files to docker image in Jmeter docker
>> image building stage.
>>
>
>
>> Also answering your question about the Deployment profiles. We have
>> identified several components to make the scope manageable.
>>
>> *Products*
>> ESB | V4.9 & V5.0
>> APIM | V1.9 & V2.0
>>
>> *JDK*
>> JAVA | V1.7 & V1.8
>>
>> *DataBase*
>> MySQL
>>
>> *Third Party Servers*
>> Brokers | ActiveMQ 5.10 | WSO2 MB 3.1 (Only applicable when ESB is used)
>>
>> So a Sample Profile would be, *ESB 4.9 + JAVA 1.7 + MYSQL + ActiveMQ*.
>> For now, you can concentrate on the above components when determining a
>> deployment profile. But your solution should be scalable.
>>
>> Is this a profile described here:https://docs.wso2.com/dis
> play/KA100/Clustered+Deployment+of+WSO2+Products+on+Kubernetes . If it
> is, then do I need to configure the product with third party servers or
> it's already done and I only have to deploy selected profile's servers into
> kubernetes cluster. For example let's take the above profile, in order to
> run this delpoyment ESB should be configured with MYSQL and Active MQ API
> endpoints. Do i need to change the configuration files of ESB or it's
> already taken care of and deployment is done once i deploy Kubernetes
> artifacts under the selected profile.
>

Existing scripts doesn't allow us to configure thirdparty dependencies like
Message Brokers. So yes we need to change ESB configurations depending on
the Broker, you can refer [1
] for
ActiveMQ configurations.


>
> Is this a profile of ESB : https://github.com/wso2/kube
> rnetes-artifacts/tree/master/wso2esb ?
>

Yes this script supports two profiles, default ESB profile and worker
manager profile, but as mentioned we neeed to tweek these scripts to
support mesage brokers as well.


> Also can't we have a private docker registry to hold our deplyment's
> images instead of building docker images via the web app ?.
>
>>
>>
We can use a private registry to store the docker images but you need to
comeup with some scripts to Auomate the process in that case.


[1] - https://docs.wso2.com/display/ESB490/Configure+with+ActiveMQ
-- 
Yasassri Ratnayake
Senior Software Engineer - QA
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
*Mobile : +94715933168*
*Blogs : http://yasassriratnayake.blogspot.com
*
*http://wso2logs.blogspot.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC 2017 - JMeter Test Manager for Distributed Deployments of WSO2 Servers

[Yasassri Ratnayake]

Hi Thilina,

We have missed some requirements. Please consider the following as well.

1. We need a Tomcat instance to host the Backends(Weapps) which are
required by the Test Scripts. So we need another instance spawned with
Tomcat. After spawning the instance you can deploy the prerequisite web
apps. (These web apps will be available in the Test-Repo under resources)
2. Also when deploying Jmeter we need to copy 3rd party Jars to Jmeter.
(These are also available in the repository)

Also answering your question about the Deployment profiles. We have
identified several components to make the scope manageable.

*Products*
ESB | V4.9 & V5.0
APIM | V1.9 & V2.0

*JDK*
JAVA | V1.7 & V1.8

*DataBase*
MySQL

*Third Party Servers*
Brokers | ActiveMQ 5.10 | WSO2 MB 3.1 (Only applicable when ESB is used)

So a Sample Profile would be, *ESB 4.9 + JAVA 1.7 + MYSQL + ActiveMQ*. For
now, you can concentrate on the above components when determining a
deployment profile. But your solution should be scalable.

Please let us know if you have more queries regarding this.

With Regards,

On Wed, Mar 22, 2017 at 4:01 AM, Thilina Manamgoda 
wrote:

> Hi Yasassri,
>
> This the order of operations,
>
>
>1.
>
>Get WSO2 product profile
>2.
>
>Build DB Docker images
>3.
>
>Deploy DB in Kubernetes cluster
>4.
>
>Get DB Deployment details from Kubernetes cluster
>5.
>
>Build the WSO2 product docker images with DB info
>6.
>
>Deploy products in Kubernetes cluster
>7.
>
>Get products Deployment details from Kubernetes cluster
>8.
>
>Build Log DB Docker Image
>9.
>
>Deploy Log DB in Kubernetes cluster
>10.
>
>Get Log DB Deployment details from Kubernetes cluster
>11.
>
>Get Jmeter profile
>12.
>
>Build the Docker image with Log DB
>13.
>
>Deploy Jmeter server in Kubernetes cluster
>14.
>
>Get Deployment details from Kubernetes cluster
>15.
>
>Run the Jmeter Scripts
>16.
>
>Store logs in the Log DB
>17.
>
>Get logs from Log DB
>18.
>
>Generate HTML Report
>
>
>
> Can you plese explain a example product deployment profile?.
>
>
> regards,
>
> Thilina Manamgoda
>
>
> On Tue, Mar 21, 2017 at 5:27 PM, Yasassri Ratnayake 
> wrote:
>
>> Hi Thilina,
>>
>> Please find my comments inline.
>>
>> On Mon, Mar 20, 2017 at 6:57 PM, Thilina Manamgoda > > wrote:
>>
>>> Hi Yasassri,
>>>
>>> First of all, sorry for the late reply. What we can do in a Jmeter
>>> cluster mode is run a test with more users. So if we have to run Jmeter
>>> Scripts parallel we have to do it using separate  Jmeter instances. Yes of
>>> course I will consider the requirements that you mentioned.
>>>
>>>   Is a Java web app good way to go ?
>>>
>>
>> Yes you can develop this as a WebApp.
>>
>>
>>> It will contain the UI, Kubernetes client and Docker client. Now, after
>>> the tests are done the logic in the Java class  HTMLReportGenereater, is
>>> executed . Similarly we have to export the final logs(Application logs,
>>> Jmeter logs, Test result logs) to a external database. Then we can import
>>> those logs to the web app and do the HTML Generating. This is a simple
>>> diagram that shows main tasks in this approach,
>>>
>>> [image: jmeter.png]
>>>
>>> Please let me know whether this approach is fine or not.
>>>
>>
>> Overrall architecture seems ok, but the order of oeprations are not
>> clear. Also how are we adding deployment profile to the webapp?
>>
>> With Regards,
>> --
>> Yasassri Ratnayake
>> Senior Software Engineer - QA
>> WSO2 Inc ; http://wso2.com
>> lean.enterprise.middleware
>> *Mobile : +94715933168 <+94%2071%20593%203168>*
>> *Blogs : http://yasassriratnayake.blogspot.com
>> *
>> *http://wso2logs.blogspot.com *
>>
>
>


-- 
Yasassri Ratnayake
Senior Software Engineer - QA
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
*Mobile : +94715933168*
*Blogs : http://yasassriratnayake.blogspot.com
*
*http://wso2logs.blogspot.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC 2017 - JMeter Test Manager for Distributed Deployments of WSO2 Servers

[Thilina Manamgoda]

Hi Yasassri,

This the order of operations,


   1.

   Get WSO2 product profile
   2.

   Build DB Docker images
   3.

   Deploy DB in Kubernetes cluster
   4.

   Get DB Deployment details from Kubernetes cluster
   5.

   Build the WSO2 product docker images with DB info
   6.

   Deploy products in Kubernetes cluster
   7.

   Get products Deployment details from Kubernetes cluster
   8.

   Build Log DB Docker Image
   9.

   Deploy Log DB in Kubernetes cluster
   10.

   Get Log DB Deployment details from Kubernetes cluster
   11.

   Get Jmeter profile
   12.

   Build the Docker image with Log DB
   13.

   Deploy Jmeter server in Kubernetes cluster
   14.

   Get Deployment details from Kubernetes cluster
   15.

   Run the Jmeter Scripts
   16.

   Store logs in the Log DB
   17.

   Get logs from Log DB
   18.

   Generate HTML Report



Can you plese explain a example product deployment profile?.


regards,

Thilina Manamgoda


On Tue, Mar 21, 2017 at 5:27 PM, Yasassri Ratnayake 
wrote:

> Hi Thilina,
>
> Please find my comments inline.
>
> On Mon, Mar 20, 2017 at 6:57 PM, Thilina Manamgoda 
> wrote:
>
>> Hi Yasassri,
>>
>> First of all, sorry for the late reply. What we can do in a Jmeter
>> cluster mode is run a test with more users. So if we have to run Jmeter
>> Scripts parallel we have to do it using separate  Jmeter instances. Yes of
>> course I will consider the requirements that you mentioned.
>>
>>   Is a Java web app good way to go ?
>>
>
> Yes you can develop this as a WebApp.
>
>
>> It will contain the UI, Kubernetes client and Docker client. Now, after
>> the tests are done the logic in the Java class  HTMLReportGenereater, is
>> executed . Similarly we have to export the final logs(Application logs,
>> Jmeter logs, Test result logs) to a external database. Then we can import
>> those logs to the web app and do the HTML Generating. This is a simple
>> diagram that shows main tasks in this approach,
>>
>> [image: jmeter.png]
>>
>> Please let me know whether this approach is fine or not.
>>
>
> Overrall architecture seems ok, but the order of oeprations are not clear.
> Also how are we adding deployment profile to the webapp?
>
> With Regards,
> --
> Yasassri Ratnayake
> Senior Software Engineer - QA
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
> *Mobile : +94715933168 <+94%2071%20593%203168>*
> *Blogs : http://yasassriratnayake.blogspot.com
> *
> *http://wso2logs.blogspot.com *
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC 2017 - JMeter Test Manager for Distributed Deployments of WSO2 Servers

[Yasassri Ratnayake]

Hi Thilina,

Please find my comments inline.

On Mon, Mar 20, 2017 at 6:57 PM, Thilina Manamgoda 
wrote:

> Hi Yasassri,
>
> First of all, sorry for the late reply. What we can do in a Jmeter cluster
> mode is run a test with more users. So if we have to run Jmeter Scripts
> parallel we have to do it using separate  Jmeter instances. Yes of course I
> will consider the requirements that you mentioned.
>
>   Is a Java web app good way to go ?
>

Yes you can develop this as a WebApp.


> It will contain the UI, Kubernetes client and Docker client. Now, after
> the tests are done the logic in the Java class  HTMLReportGenereater, is
> executed . Similarly we have to export the final logs(Application logs,
> Jmeter logs, Test result logs) to a external database. Then we can import
> those logs to the web app and do the HTML Generating. This is a simple
> diagram that shows main tasks in this approach,
>
> [image: jmeter.png]
>
> Please let me know whether this approach is fine or not.
>

Overrall architecture seems ok, but the order of oeprations are not clear.
Also how are we adding deployment profile to the webapp?

With Regards,
-- 
Yasassri Ratnayake
Senior Software Engineer - QA
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
*Mobile : +94715933168 <+94%2071%20593%203168>*
*Blogs : http://yasassriratnayake.blogspot.com
*
*http://wso2logs.blogspot.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC 2017 - JMeter Test Manager for Distributed Deployments of WSO2 Servers

[Thilina Manamgoda]

Hi Yasassri,

First of all, sorry for the late reply. What we can do in a Jmeter cluster
mode is run a test with more users. So if we have to run Jmeter Scripts
parallel we have to do it using separate  Jmeter instances. Yes of course I
will consider the requirements that you mentioned.

  Is a Java web app good way to go ?. It will contain the UI, Kubernetes
client and Docker client. Now, after the tests are done the logic in the
Java class  HTMLReportGenereater, is executed . Similarly we have to export
the final logs(Application logs, Jmeter logs, Test result logs) to a
external database. Then we can import those logs to the web app and do the
HTML Generating. This is a simple diagram that shows main tasks in this
approach,

[image: jmeter.png]

Please let me know whether this approach is fine or not.

Regards,

Thilina Manamgoda


On Mon, Mar 13, 2017 at 11:08 AM, Yasassri Ratnayake 
wrote:

> Hi Thilina,
>
> Glad to see your interest in the JMeter Test Management tool. Your
> understanding of the requirements seems to be correct.
>
> Answering your query. At the moment JMeter is not running in cluster mode,
> but running JMeter in cluster mode will be a good addition to the solution
> if we can run JMeter scripts in parallel. Also, please consider following
> points as well.
>
>- A user should be able to add multiple JMeter scripts for a given
>Deployment Profile.
>- Simmilarly, a user should be able to add multiple deployment
>profiles with multiple JMeter scripts. (e.g: Deployment01==> JmeterScript1,
>JMeterScript2  Deployment02 ==> JmeterScript4, JMeterScript3)
>
> Please reach out to us if you have more queries regarding the requirements.
>
> With Regards,
> Yasassri
>
> On Sat, Mar 11, 2017 at 1:14 AM, Thilina Manamgoda 
> wrote:
>
>> Hi all,
>>
>> I have studied the resources that you have provided and there are
>> Kubernetes configurations for wso2 products  already defined at
>> kubernetes-artifacts  as
>> well as Jmeter  Scripts qa-tooling-smoketester
>> . As far as I
>> understand, what needs to be done is, bring these implementations together
>> and automate the process once configurations are selected via an UI. In
>> order to achieve those goals following things need to be implemented:
>>
>>
>>-
>>
>>UI
>>-
>>
>>   User should be able to select the Product, version and the profile
>>   -
>>
>>   User should be able to Select 3rd party prerequisites such as
>>   databases
>>   -
>>
>>   User should be able to select the which Jmeter scripts to run
>>   -
>>
>>   Final test results
>>   -
>>
>>Backend
>>-
>>
>>   Build the product’s Docker image according to provided profile.
>>   For example consider the wso2as as the product. Then these steps
>>   mentioned here[1] should be executed. What is done by the build.sh can 
>> be
>>   achieved by a Docker client [2]. So we can build the Docker images in 
>> host
>>   where the app is hosted.
>>   -
>>
>>   Build the 3rd party prerequisites Docker images  like above
>>   mentioned
>>   -
>>
>>   Then we push the docker images that we have built to a private
>>   docker registry where Kubernetes cluster can pull those images
>>   -
>>
>>   Connect to the Kubernetes cluster through a client library like fabric8
>>   [2] and deploy the product in the cluster(what is done in the
>>   deploy.sh script)
>>   -
>>
>>   Build the Jmeter docker Image with the given profile and the
>>   deployment configurations(ex: fill the server properties file with the
>>   respective values).
>>   -
>>
>>   Build and Push Jmeter docker image with given profile to the
>>   private Docker registry
>>   -
>>
>>   Deploy the Jmeter image in Kubernetes cluster and run the tests
>>   -
>>
>>   Show results in the UI
>>
>>
>> Also in Smoke tester is Jmeter run in cluster mode or not ?. Please let
>> me know whether I understood the requirements correctly or not. If correct,
>> Is this approach correct ?.
>>
>>
>> [1] https://github.com/wso2/kubernetes-artifacts/tree/master/
>> wso2as#1-build-docker-images
>>
>> [2] https://github.com/docker-java/docker-java
>>
>> [3] https://fabric8.io
>>
>> Regards,
>>
>> Thilina Manamgoda
>>
>>
>> On Fri, Mar 10, 2017 at 1:51 PM, Thilina Manamgoda > > wrote:
>>
>>> Hi all,
>>>
>>> I am Thilina Manamgoda an undergraduate of department of Computer
>>> Engineering, University of Peradeniya Sri lanka. I am looking forward to
>>> participate in GSOC 2017. This is my second time participating Google
>>> summer of code. Previously I have worked with Apache Taverna where I added
>>> the CWL tool browsing support to the Taverna suite. After completing the
>>> project, I continued to work with the 

Re: [Dev] GSoC 2017 - JMeter Test Manager for Distributed Deployments of WSO2 Servers

[Yasassri Ratnayake]

Hi Thilina,

Glad to see your interest in the JMeter Test Management tool. Your
understanding of the requirements seems to be correct.

Answering your query. At the moment JMeter is not running in cluster mode,
but running JMeter in cluster mode will be a good addition to the solution
if we can run JMeter scripts in parallel. Also, please consider following
points as well.

   - A user should be able to add multiple JMeter scripts for a given
   Deployment Profile.
   - Simmilarly, a user should be able to add multiple deployment profiles
   with multiple JMeter scripts. (e.g: Deployment01==> JmeterScript1,
   JMeterScript2  Deployment02 ==> JmeterScript4, JMeterScript3)

Please reach out to us if you have more queries regarding the requirements.

With Regards,
Yasassri

On Sat, Mar 11, 2017 at 1:14 AM, Thilina Manamgoda 
wrote:

> Hi all,
>
> I have studied the resources that you have provided and there are
> Kubernetes configurations for wso2 products  already defined at
> kubernetes-artifacts  as
> well as Jmeter  Scripts qa-tooling-smoketester
> . As far as I
> understand, what needs to be done is, bring these implementations together
> and automate the process once configurations are selected via an UI. In
> order to achieve those goals following things need to be implemented:
>
>
>-
>
>UI
>-
>
>   User should be able to select the Product, version and the profile
>   -
>
>   User should be able to Select 3rd party prerequisites such as
>   databases
>   -
>
>   User should be able to select the which Jmeter scripts to run
>   -
>
>   Final test results
>   -
>
>Backend
>-
>
>   Build the product’s Docker image according to provided profile. For
>   example consider the wso2as as the product. Then these steps
>   mentioned here[1] should be executed. What is done by the build.sh can 
> be
>   achieved by a Docker client [2]. So we can build the Docker images in 
> host
>   where the app is hosted.
>   -
>
>   Build the 3rd party prerequisites Docker images  like above
>   mentioned
>   -
>
>   Then we push the docker images that we have built to a private
>   docker registry where Kubernetes cluster can pull those images
>   -
>
>   Connect to the Kubernetes cluster through a client library like fabric8
>   [2] and deploy the product in the cluster(what is done in the
>   deploy.sh script)
>   -
>
>   Build the Jmeter docker Image with the given profile and the
>   deployment configurations(ex: fill the server properties file with the
>   respective values).
>   -
>
>   Build and Push Jmeter docker image with given profile to the
>   private Docker registry
>   -
>
>   Deploy the Jmeter image in Kubernetes cluster and run the tests
>   -
>
>   Show results in the UI
>
>
> Also in Smoke tester is Jmeter run in cluster mode or not ?. Please let me
> know whether I understood the requirements correctly or not. If correct, Is
> this approach correct ?.
>
>
> [1] https://github.com/wso2/kubernetes-artifacts/tree/
> master/wso2as#1-build-docker-images
>
> [2] https://github.com/docker-java/docker-java
>
> [3] https://fabric8.io
>
> Regards,
>
> Thilina Manamgoda
>
>
> On Fri, Mar 10, 2017 at 1:51 PM, Thilina Manamgoda 
> wrote:
>
>> Hi all,
>>
>> I am Thilina Manamgoda an undergraduate of department of Computer
>> Engineering, University of Peradeniya Sri lanka. I am looking forward to
>> participate in GSOC 2017. This is my second time participating Google
>> summer of code. Previously I have worked with Apache Taverna where I added
>> the CWL tool browsing support to the Taverna suite. After completing the
>> project, I continued to work with the community and then became an Apache
>> committer on  that project. This is my gsoc blog:
>> http://maanadevgsoc2016.blogspot.com , here you can get all the details
>> of my previous work.
>>
>> I am really interested in the project “JMeter Test Manager for
>> Distributed Deployments of WSO2 Servers”. I have contributed to the project
>> “wso2 app-cloud” and have worked with Kubernetes framework previously when
>> I was an Intern at wso2. Now I am going through  the documentation of
>> Jmeter and qa-tooling-smoketester. Will come back with more questions.
>>
>> Regards,
>> Thilina Manamgoda
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Yasassri Ratnayake
Senior Software Engineer - QA
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
*Mobile : +94715933168*
*Blogs : http://yasassriratnayake.blogspot.com
*
*http://wso2logs.blogspot.com *

Re: [Dev] GSoC 2017 - JMeter Test Manager for Distributed Deployments of WSO2 Servers

[Thilina Manamgoda]

Hi all,

I have studied the resources that you have provided and there are
Kubernetes configurations for wso2 products  already defined at
kubernetes-artifacts  as well
as Jmeter  Scripts qa-tooling-smoketester
. As far as I
understand, what needs to be done is, bring these implementations together
and automate the process once configurations are selected via an UI. In
order to achieve those goals following things need to be implemented:


   -

   UI
   -

  User should be able to select the Product, version and the profile
  -

  User should be able to Select 3rd party prerequisites such as
  databases
  -

  User should be able to select the which Jmeter scripts to run
  -

  Final test results
  -

   Backend
   -

  Build the product’s Docker image according to provided profile. For
  example consider the wso2as as the product. Then these steps
  mentioned here[1] should be executed. What is done by the build.sh can be
  achieved by a Docker client [2]. So we can build the Docker
images in host
  where the app is hosted.
  -

  Build the 3rd party prerequisites Docker images  like above mentioned
  -

  Then we push the docker images that we have built to a private docker
  registry where Kubernetes cluster can pull those images
  -

  Connect to the Kubernetes cluster through a client library like fabric8
  [2] and deploy the product in the cluster(what is done in the
  deploy.sh script)
  -

  Build the Jmeter docker Image with the given profile and the
  deployment configurations(ex: fill the server properties file with the
  respective values).
  -

  Build and Push Jmeter docker image with given profile to the private
  Docker registry
  -

  Deploy the Jmeter image in Kubernetes cluster and run the tests
  -

  Show results in the UI


Also in Smoke tester is Jmeter run in cluster mode or not ?. Please let me
know whether I understood the requirements correctly or not. If correct, Is
this approach correct ?.


[1]
https://github.com/wso2/kubernetes-artifacts/tree/master/wso2as#1-build-docker-images

[2] https://github.com/docker-java/docker-java

[3] https://fabric8.io

Regards,

Thilina Manamgoda


On Fri, Mar 10, 2017 at 1:51 PM, Thilina Manamgoda 
wrote:

> Hi all,
>
> I am Thilina Manamgoda an undergraduate of department of Computer
> Engineering, University of Peradeniya Sri lanka. I am looking forward to
> participate in GSOC 2017. This is my second time participating Google
> summer of code. Previously I have worked with Apache Taverna where I added
> the CWL tool browsing support to the Taverna suite. After completing the
> project, I continued to work with the community and then became an Apache
> committer on  that project. This is my gsoc blog: http://maanadevgsoc2016.
> blogspot.com , here you can get all the details of my previous work.
>
> I am really interested in the project “JMeter Test Manager for Distributed
> Deployments of WSO2 Servers”. I have contributed to the project “wso2
> app-cloud” and have worked with Kubernetes framework previously when I was
> an Intern at wso2. Now I am going through  the documentation of Jmeter and 
> qa-tooling-smoketester.
> Will come back with more questions.
>
> Regards,
> Thilina Manamgoda
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC 2017 - JMeter Test Manager for Distributed Deployments of WSO2 Servers

[Nuwan Silva]

Hi Thilina,

Glad you are interested in working on Jmeter Test Manager. As you might
have seen a sample description is available in [1].
If you have any questions regarding this please let us know.

[1] https://docs.wso2.com/display/GSoC/Project+Proposals+
for+2017#ProjectProposalsfor2017-Proposal14:JMeterTestManage
rforDistributedDeploymentsofWSO2Servers

Regards,
Nuwan.

On Fri, Mar 10, 2017 at 3:21 AM, Thilina Manamgoda 
wrote:

> Hi all,
>
> I am Thilina Manamgoda an undergraduate of department of Computer
> Engineering, University of Peradeniya Sri lanka. I am looking forward to
> participate in GSOC 2017. This is my second time participating Google
> summer of code. Previously I have worked with Apache Taverna where I added
> the CWL tool browsing support to the Taverna suite. After completing the
> project, I continued to work with the community and then became an Apache
> committer on  that project. This is my gsoc blog: http://maanadevgsoc2016.
> blogspot.com , here you can get all the details of my previous work.
>
> I am really interested in the project “JMeter Test Manager for Distributed
> Deployments of WSO2 Servers”. I have contributed to the project “wso2
> app-cloud” and have worked with Kubernetes framework previously when I was
> an Intern at wso2. Now I am going through  the documentation of Jmeter and 
> qa-tooling-smoketester.
> Will come back with more questions.
>
> Regards,
> Thilina Manamgoda
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 


*Nuwan Silva*
*Senior Software Engineer*
Mobile: +9477 980 4543

WSO2 Inc.
lean . enterprise . middlewear.
http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] GSoC 2017 - JMeter Test Manager for Distributed Deployments of WSO2 Servers

[Thilina Manamgoda]

Hi all,

I am Thilina Manamgoda an undergraduate of department of Computer
Engineering, University of Peradeniya Sri lanka. I am looking forward to
participate in GSOC 2017. This is my second time participating Google
summer of code. Previously I have worked with Apache Taverna where I added
the CWL tool browsing support to the Taverna suite. After completing the
project, I continued to work with the community and then became an Apache
committer on  that project. This is my gsoc blog:
http://maanadevgsoc2016.blogspot.com , here you can get all the details of
my previous work.

I am really interested in the project “JMeter Test Manager for Distributed
Deployments of WSO2 Servers”. I have contributed to the project “wso2
app-cloud” and have worked with Kubernetes framework previously when I was
an Intern at wso2. Now I am going through  the documentation of Jmeter
and qa-tooling-smoketester.
Will come back with more questions.

Regards,
Thilina Manamgoda
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev