Hi Abhishek,
Reported two more issues for the usage of grep command [1, 2]. The fixes
are straightforward.
[1].
https://github.com/abhishek0198/wso2dockerfiles-test-framework/issues/29
[2].
https://github.com/abhishek0198/wso2dockerfiles-test-framework/issues/30
On Fri, Aug 19, 2016 at 1:47 PM,
Hi All,
I have fixed the important issues raised on github, however, I haven't
closed any of them. Please review the fix and closes issues/provide
feedback accordingly.
I am working on adding a different logging framework which has concept of
log levels.
Thanks
Abhishek
On Sat, Aug 20, 2016 at
Thanks Chamila. I am working on the addressing comments and issues, will
update once I complete these.
- Abhishek
On Sat, Aug 20, 2016 at 12:11 AM, Chamila De Alwis
wrote:
> Hi Abhishek,
>
> Good work! I've provided some more feedback through issues and a few
> comments on commits. We need to i
Hi Abhishek,
Good work! I've provided some more feedback through issues and a few
comments on commits. We need to improve the documentation aspect of the
framework.
Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Senior Software Engineer | WSO2
Blog: https://medium.com/@chami
Hi All,
I have addressed all the open issues (except for smoketest separation and
adding kubernetes testing). Please test and let me know if the fix that I
added addresses the concerned raised before.
Repository URL [1].
Thanks
Abhishek
[1]. https://github.com/abhishek0198/wso2dockerfiles-test-
Hi Thanuja,
I have added the fix to look for ERROR level rather than any error keyword.
Please test it and let me know if it fixes the issue.
The new repository URL is [1].
Thanks
Abhishek
[1]. https://github.com/abhishek0198/wso2dockerfiles-test-framework
On Thu, Aug 18, 2016 at 10:49 AM, Abh
I think I have found the issue, it was due to fully qualified path
referring to old project name so go get tried to clone that as well.
Thanks
Abhishek
On Thursday, August 18, 2016, Abhishek Tiwari
wrote:
> Thanks Chamila.
>
> Updated repository URL [1]. I have also added instructions specific
Thanks Chamila.
Updated repository URL [1]. I have also added instructions specific to Mac,
Windows and Linux users.
I do not have any setting on local git config, I even cleaned everything
did a restart, still no luck. The weird part is, git clone works fine with
the changed repo name. Will keep
Hi Abhishek,
I think the proper name should be wso2dockerfiles-test-framework.
Check the git remotes that are in the git config in your local when doing
go get. It might have the old remote name that gets temporary redirected to
the new one.
Regards,
Chamila de Alwis
Committer and PMC Member -
Hi All,
I have changed the name of github repository from "test-framework" to
"wsodockerfiles-testframework". The updated URL is [1].
For some reason, when I do "go get ", it is cloning both old
and new repo with same content. However, when I do "git clone ",
I get the renamed repo cloned. I will
Hi Thanuja,
Thanks a lot of using the test framework and pointing out the issue. The
check of errors in carbon log is dumb at this point. I will change it look
for the correct logging level to find errors.
Imesh,
Sincerely appreciate code level feedback and creating issues on Github. I
will addre
Hi Abhishek,
Great work on Dockerfiles test framework!!! I have used the test framework
to check the flow of building and running WSO2 BPS 3.5.1 docker image.
According to the framework log[1], the test fails because of an error in
the carbon server log. But when I check the carbon server log, the
Here is the correct link:
https://hangouts.google.com/call/krqijl3e4fc4xa4bpd2vct3quqe
On Fri, Aug 12, 2016 at 2:03 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> The meeting got rescheduled to 3:00pm. Here is the updated hangout link:
>
> https://hangouts.google.com/call/g5q25lay
The meeting got rescheduled to 3:00pm. Here is the updated hangout link:
https://hangouts.google.com/call/g5q25layaremzfhyli6vbqsv2ye
Thanks
Abhishek
On Thu, Aug 11, 2016 at 10:37 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> Hi Imesh,
>
> Yeah 2:30pm IST is perfect.
>
> Thanks
Hi Imesh,
Yeah 2:30pm IST is perfect.
Thanks
Abhishek
On Thu, Aug 11, 2016 at 9:59 PM, Imesh Gunaratne wrote:
>
>
> On Fri, Aug 12, 2016 at 10:08 AM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> Hi Mentors,
>>
>> Just a quick reminder for the Dockerfiles test framework demo t
On Fri, Aug 12, 2016 at 10:08 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> Hi Mentors,
>
> Just a quick reminder for the Dockerfiles test framework demo today
> afternoon?
>
​Would 2:30 PM IST work for you?
Thanks​
>
> Thanks
> Abhishek
>
> On Tue, Aug 9, 2016 at 11:00 PM, Abhi
Hi Mentors,
Just a quick reminder for the Dockerfiles test framework demo today
afternoon?
Thanks
Abhishek
On Tue, Aug 9, 2016 at 11:00 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> HI Vishanth,
>
> Friday afternoon works fine with me.
>
> Thanks
> Abhishek
>
> On Wed, Aug 10, 2
Hi All,
I just had a meeting with Vishanth for our weekly status update. Following
are the meeting minutes:
1. Had a quick demo of current status of test framework and focused on
smoke tests.
2. Did a code walkthrough of the smoke tests, Vishanth recommended to find
admin endpoints to access and
HI Vishanth,
Friday afternoon works fine with me.
Thanks
Abhishek
On Wed, Aug 10, 2016 at 10:52 AM, Vishanth Balasubramaniam <
vishan...@wso2.com> wrote:
> Hi,
>
> Shall we have the demo on Friday Afternoon (IST)?
>
> Regards,
> Vishanth
>
> On Tue, Aug 9, 2016 at 4:28 PM, Abhishek Tiwari <
> a
Hi,
Shall we have the demo on Friday Afternoon (IST)?
Regards,
Vishanth
On Tue, Aug 9, 2016 at 4:28 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> Hi Mentors,
>
> Dockerfiles test framework is now able to run smoke tests, with smoke
> tests for ESB added at this point. Developers
Hi Mentors,
Dockerfiles test framework is now able to run smoke tests, with smoke tests
for ESB added at this point. Developers can extend the framework to add
product specific smoke tests.
Smoke test for ESB are implemented as follows:
1. Once a new docker image is deployed and the container is
Hi Vishanth,
Thanks for pointing this, I have updated the config path to be relative to
the source root.
Thanks
Abhishek
On Thu, Aug 4, 2016 at 10:36 AM, Vishanth Balasubramaniam <
vishan...@wso2.com> wrote:
> Hi Abhishek,
>
> I see that you have given absolute path for "TestConfigPath" in
> "c
Hi Imesh,
Thanks for the feedback on build setup. Its certainly very clean way to
organize a go project. I have incorporated the suggested changes and
updated the readme accordingly [1].
Thanks
Abhishek
[1]. https://github.com/abhishek0198/test-framework
On Wed, Aug 3, 2016 at 11:17 AM, Imesh G
Hi Abhishek,
I see that you have given absolute path for "TestConfigPath" in
"common/test-context.go". Why don't we give relative path from the project
directory for this?
Regards,
Vishanth
On Mon, Jul 11, 2016 at 5:22 PM, Imesh Gunaratne wrote:
> Hi Abhishek,
>
> On Mon, Jul 11, 2016 at 1:53
On Mon, Aug 1, 2016 at 3:34 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> Hi Imesh,
>
> Thanks for the feedback. I completely agree with the naming of executable.
> Unfortunately, go install builds executable using module name and main()
> has to be inside main module name (based o
Hi Imesh,
Thanks for the feedback. I completely agree with the naming of executable.
Unfortunately, go install builds executable using module name and main()
has to be inside main module name (based on what I have read so far). A
quick search did not provide any solution so I will tackle this late
Hi Abhishek,
On Mon, Aug 1, 2016 at 6:15 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> Hi Imesh,
>
> The project is currently structured around standard Golang project created
> by eclipse, you can add eclipse plugin, create a new project with existing
> sources and it should comp
Hi All,
I have updated the instructions to build and run the test framework [1]. I
am also able to build kubernetes platform on Mac OSX.
[1]. https://github.com/abhishek0198/test-framework
Thanks
Abhishek
On Mon, Aug 1, 2016 at 6:15 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
>
Hi Imesh,
The project is currently structured around standard Golang project created
by eclipse, you can add eclipse plugin, create a new project with existing
sources and it should compile fine. I will add complete instructions on
Github and update this thread.
Chamila,
The tests I am working on
On Thu, Jul 28, 2016 at 4:19 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> 2. I am currently working on adding the ability to run smoke tests from
> the framework. The idea is to have the capability of having product
> specific smoke tests, then teams with more product knowledge ca
Hi Abhishek,
On Thursday, July 28, 2016, Abhishek Tiwari
wrote:
> Hi All,
>
> We had a meeting on the progress and next steps of Dockerfiles test
> framework. Here are the meeting minutes:
>
> 1. We are currently able to test default and puppet provisioning of WSO2
> products. I did a test of ne
Hi,
Good work so far Abhishek. We'll focus on getting the Kubernetes setup done
soon and test it on that.
Regards,
Vishanth
On Thu, Jul 28, 2016 at 2:49 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> Hi All,
>
> We had a meeting on the progress and next steps of Dockerfiles test
Hi All,
We had a meeting on the progress and next steps of Dockerfiles test
framework. Here are the meeting minutes:
1. We are currently able to test default and puppet provisioning of WSO2
products. I did a test of next Dockerfiles stable release 1.2.0 and did not
find any issue.
2. I am curren
Hi Abhishek,
How can we build your latest code in [1]?
[1] https://github.com/abhishek0198/test-framework.git
Thanks
On Wed, Jul 20, 2016 at 11:12 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> Hi Imesh,
>
> Thanks a lot for the instructions, I will try the setup on OSX itself on
Hi Imesh,
Thanks a lot for the instructions, I will try the setup on OSX itself once
I am done with the smoke tests.
- Abhishek
On Wednesday, July 20, 2016, Imesh Gunaratne wrote:
> Hi Abhishek,
>
> On Wed, Jul 20, 2016 at 9:49 AM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com
> > wrote:
>
Hi Abhishek,
On Wed, Jul 20, 2016 at 9:49 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> Hi Mentors,
>
> I have been working on setting up Kubernetes cluster using vagrant and
> docker using [1]. I ran into multiple issues (coreos download taking hours,
> nfsd not being setup etc),
Hi Mentors,
I have been working on setting up Kubernetes cluster using vagrant and
docker using [1]. I ran into multiple issues (coreos download taking hours,
nfsd not being setup etc), however, those got resolved.
Now, when I launch the setup using run.sh, I get this error [2]. I tried
wiping ou
Hi Abhishek,
On Mon, Jul 11, 2016 at 1:53 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> Hi Mentors,
>
> I have been working on migrating the WSO2 Dockerfiles test framework from
> bash and python to use Golang. I must say, its been quite a ride but
> finally the migration has been
Hi Mentors,
I have been working on migrating the WSO2 Dockerfiles test framework from
bash and python to use Golang. I must say, its been quite a ride but
finally the migration has been successful. I am happy to offload many
important features (logging, JSON parsing etc) to existing Golang package
Great work Abhishek.
On Tue, Jun 28, 2016 at 1:12 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> Dear Mentors,
>
> I have implemented the following components after our last discussion:
>
> 1. Ability to configure product testing, to specify multiple products to
> test, versions, p
Dear Mentors,
I have implemented the following components after our last discussion:
1. Ability to configure product testing, to specify multiple products to
test, versions, provisioning methods and various deployment platform. The
config is implemented using JSON and looks something like this:
Hi All,
Another super exciting week of GSoC. I had a meeting with Chamila on Sat
(6/25) and with Vishanth today (6/27). Following are the meeting minutes:
1. We plan on adding smoke tests for individual products (rather than
exhaustive product level tests). The goal is to test the health of deplo
Dear Mentors,
Following is the github repository for Dockerfiles integration test
framework. Comments/Thoughts/Scolds are always welcome.
https://github.com/abhishek0198/test-framework
Thanks,
Abhishek
___
Dev mailing list
Dev@wso2.org
http://wso2.org/
Hi All,
Following are the meeting notes from GSoC Dockerfile test framework weekly
meeting:
*Tasks completed*
1. Ability to check for errors in Docker build and run logs.
2. Added the work around to pass answers to interactive prompt without
having to add silent mode.
3. Working with community to
Hi Chamila,
That's a neat idea as well, I will incorporate this in the current
implementation.
Thanks,
Abhishek
On Mon, Jun 20, 2016 at 6:12 AM, Chamila De Alwis wrote:
>
> On Mon, Jun 20, 2016 at 1:17 PM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> It would be nice to have
On Mon, Jun 20, 2016 at 1:17 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> It would be nice to have the ability to silent the questioning so that the
> test scripts can continue without having to pause for the input.
Alternatively you could try an expect script to automatically i
Hi All,
I have completed the following tasks planned from last week:
1. Add the ability to read exposed ports from the Dockerfile
2. Modify the launch script to silence console log and redirect them to a
log file, which will later be parsed for any errors/warnings
3. Access WSO2 carbon logs from
Hi All,
Currently, running wso2 product images with just default profile, asks the
user if they wish to connect to the running container. It would be nice to
have the ability to silent the questioning so that the test scripts can
continue without having to pause for the input.
This requirement or
Dear Mentors,
I have checked in the initial test code, which calls and runs a specified
dockerfiles product and currently able to test open ports. I am working on
adding the capability to test running product server (carbon).
You can take a look at the current script here:
https://github.com/abhi
Hello Everyone,
Below are the meeting minutes from our weekly status meeting on Wed May 25,
2016.
Tasks completed:
1. Deployed WSO2MB product using puppet provisioning.
2. Completed code walk though of puppet-modules with understanding of Hiera and
related dependencies.
3. Pull request to fail
Hi,
That's great Abhishek.
You can build the docker images using puppet provisioning for Kubernetes
platform and try to deploy in Kubernetes,
you can follow the steps provided in the docs [1]. It is very easy to
follow.
[1] -
https://docs.wso2.com/display/KA100/Deploying+a+WSO2+Product+in+Kubern
Hi All,
Following are the meeting notes from our weekly status update meeting:
Tasks completed:
1. Completed code walk-through of Dockerfiles project.
2. Understanding and build of clustered configuration for WSO2 ESB. This was a
huge step in understanding various profiles for clustered environm
Hi Abhishek,
Try increasing the MySQL connection limit. This source will be useful [1].
[1] http://stackoverflow.com/questions/22297773/increase-mysql-connections
Thank You.
On Fri, May 13, 2016 at 10:01 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> Hi Mentors,
>
> I have been
Hi Abhishek,
Provide the call notes here.
Regards,
Vishanth
On Mon, May 2, 2016 at 10:44 AM, Vishanth Balasubramaniam <
vishan...@wso2.com> wrote:
> Hi,
>
> Yes the time is fine with both myself and Chamila. We can go ahead.
>
> Regards,
> Vishanth
>
> On Fri, Apr 29, 2016 at 11:16 AM, Abhishek
Hi,
Yes the time is fine with both myself and Chamila. We can go ahead.
Regards,
Vishanth
On Fri, Apr 29, 2016 at 11:16 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> Does 6pm IST work?
>
> On Apr 28, 2016, at 10:30 PM, Vishanth Balasubramaniam
> wrote:
>
> Hi Abhishek,
>
> That
Does 6pm IST work?
> On Apr 28, 2016, at 10:30 PM, Vishanth Balasubramaniam
> wrote:
>
> Hi Abhishek,
>
> That's great. We can have the call on Monday (2nd May), preferably in the
> evening.
>
> Regards,
> Vishanth
>
> On Fri, Apr 29, 2016 at 9:37 AM, Abhishek Tiwari
> mailto:abhishek.tiwa
Hi Abhishek,
That's great. We can have the call on Monday (2nd May), preferably in the
evening.
Regards,
Vishanth
On Fri, Apr 29, 2016 at 9:37 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:
> Hi Mentors,
>
> I have the local build setup and have started going through the current
>
Hi Mentors,
I have the local build setup and have started going through the current
codebase of Dockerfiles project. It would be very helpful to get a code
walk-through to understand the current design and architecture of the
system. Please let me know your availability for the next week and I wil
58 matches
Mail list logo
