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 <[email protected]> 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 <[email protected]> > 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 <https://github.com/wso2/kubernetes-artifacts> as >> well as Jmeter Scripts qa-tooling-smoketester >> <https://github.com/wso2-incubator/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 <[email protected] >> > 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 >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > 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://yasassriratnayake.blogspot.com/>* > * http://wso2logs.blogspot.com <http://wso2logs.blogspot.com>* >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
