Re: [Dev] My GSoC experience - GSoC students please read!

[Abhishek Tiwari]

Thanks Imesh.

Sincerely appreciate the response. The same guide also talks about
MENTORING [1]. Specifically and I quote

"*Don't Be That Guy*: No one likes dictators.  Work with your student on
the development of expectations, rather then barking out orders."

On my last call with Chamila, this is exactly what happened. He literally
shouted at me and threatened to fail me on the project. Forget mentorship,
is this even professional? I sent you PM to address this situation but you
never cared to reply it. You were creating Github issues even after that,
but you simply ignored my email.

The goal of the project never included K8 and I have evidence to support it
(design doc, project proposal and community bonding conversation). However,
when community asked about it, I started working on addressing that, I was
very close to complete it. I was pretty much done with that work, when I
started getting these chats and issues from Chamila about changing names
and params and so many things that were completely out of the scope
considering the timeline. The code in question had been in github for about
2 months and no one ever cared to bring it up until 2 days before the
deadline. Is this how software projects are managed ?

I was always willing to work on everything, and was very interested to work
even after GSoC period. My biggest problem is the way Chamila talked to me,
it was completely unprofessional and disrespectful.

Anyways, there is no point arguing over it, since at some point its going
to become my voice against your voice and nothing productive will come out
of it.  I just hope that I will receive an honest evaluation of my work!

[1]. http://write.flossmanuals.net/gsoc-mentoring/setting-expectations/

On Mon, Aug 22, 2016 at 7:59 PM, Imesh Gunaratne <im...@wso2.com> wrote:

> Hi Abhishek,
>
> Thanks for your feedback! We are really sorry to hear what you
> experienced.
>
> We at WSO2, participated in GSoC for many years now with the intention of
> giving students opportunities to contribute to open source projects for the
> benefit of the entire community. This allows students to learn how open
> source communities work, new technologies related to their academic
> pursuits, give exposure to real world software development processes, etc.
> In the open source world, there is no labour concept, no one is paid for
> doing open source work. If someone is willing to contribute, they are most
> welcome to share their ideas and send contributions. GSoC program is trying
> to give opportunities for students to experience this and be a part of it
> [3]. If you do not like that idea, you should have opted out of this
> project at the very early stages.
>
> The GSoC Student Guide [4] has explained clearly how students should work
> with mentors and what to expect from them. Mentors are voluntarily
> contributing their time to GSoC projects with the intention of adding value
> to open source projects. They do this while working on many other things.
> Therefore delays in meetings and such occurrences may happen due to
> unavoidable circumstances. Please accept our apologies for any
> inconveniences caused in that regard. Please feel free to refer [5], [6],
> [7], [8], [9], [10] on how WSO2 community and your mentors have appreciated
> your contributions then and there.
>
> Changing requirements is part and parcel of software projects and software
> world. However we believe that we did our very best to keep the high level
> requirements of the project fixed. On high level, the main goal of this
> project was to implement a test framework to invoke bash scripts provided
> in WSO2 Dockerfiles and K8S Artifacts repositories for verifying WSO2
> container images. As we believe that is a straightforward goal and nothing
> much need to be changed at the middle of the project except for refinements.
>
> [3] http://write.flossmanuals.net/gsocstudentguide/what-is-
> google-summer-of-code/
> [4] http://write.flossmanuals.net/gsocstudentguide/working-with-
> your-mentor/
> [5] [DEV] [GSoC Dockerfiles] Project update - Migration to Golang,
> http://mail.wso2.org/mailarchive/dev/2016-July/065571.html
> [6] [Dev] [GSoC Dockerfiles] Added ability to run smoke tests from test
> framework, http://mail.wso2.org/mailarchive/dev/2016-August/066879.html
> [7] [Dev] GSoC Dockerfiles weekly status meeting minutes,
> http://mail.wso2.org/mailarchive/dev/2016-May/063294.html
> [8] [Dev] [GSoC Dockerfiles] Status update, http://mail.wso2.org/
> mailarchive/dev/2016-June/065107.html
> [9] [Dev] [DEV] [GSoC] Meeting minutes from Dockerfiles test framework
> demo, http://mail.wso2.org/mailarchive/dev/2016-June/065162.html
> [10] [GSoC Dockerfiles] Meeting minutes, http://mail.wso2.org/
> mailarchive/dev/2016-July/066247.html
>
> Thanks
>
> On Mon, Aug 22, 20

[Dev] My GSoC experience - GSoC students please read!

[Abhishek Tiwari]

Hello Everyone,

There are some organizations that looks at GSoC as getting free labour and
use it to get as much done as they can within 3 months time, WSO2 is one of
them. I was working 60 hours a week and never received any appreciation
from mentors. It was very disappointing but I always kept a positive
attitude and tried to meet all the deadlines. Mentors were very
unprofessional, they would agree on a meeting time and then never show up,
or they would keep delaying the meeting saying there is another meeting (I
have chat and emails to prove that). They never even cared to send an email
about it, there were so many such incidents, where I ended up waiting
hours. New requirements kept coming as they wanted to get as much work as
possible. There was no feedback on code so I did not learn anything from
code perspective, then just before 2 days mentor provided comments which
changed everything and I had rewrite most of it. The expectations from WSO2
were completely unrealistic from a student point of view. I sincerely hope
that Google looks into it.

Yesterday I was having a hangout call (over a weekend) to discuss the newly
created issues and I was trying to convince that I should work on the high
priority issue rather than changing the whole codebase and architecture
because there is an extra JSON parameter [2]. My mentor shouted at me and
threatened to fail me in the evaluation. This is very disheartening as I
have worked so hard on this project. My college is already started and I am
taking  leaves to work on the project. If anyone else has experienced
similar situations in WSO2, I would recommend reaching out to GSoC
officials as I have done already.

I am a 19 year old, first year engineering student (Freshman). All these
skills I learnt by myself. In the span of GSoC project, I had to learn
Docker, Dockerfiles, Puppet, Kubernetes, Bash scripting, Go language, WSO2
codebase and many other things. It is evident from the code that I have
written so far [1]. It is very easy to judge someone without being in their
shoes, and I feel like my mentors have been pushing work and standards
without caring about my experience level, which in my opinion is completely
unfair.

I am sure there are so many other great mentors in the organization and my
experience might be just one off. However, if any other student has felt
similar situations, it should be investigated.

Thanks
Abhishek

[1]. https://github.com/abhishek0198/wso2dockerfiles-test-
framework/commits/master
[2]. https://github.com/abhishek0198/wso2dockerfiles-
test-framework/issues/22
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Open issues has been addressed

[Abhishek Tiwari]

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 1:17 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:

> 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 <chami...@wso2.com>
> wrote:
>
>> 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/@chamilad
>>
>>
>>
>> On Fri, Aug 19, 2016 at 3:38 AM, Abhishek Tiwari <
>> abhishek.tiwari0...@gmail.com> wrote:
>>
>>> 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-framework
>>>
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Open issues has been addressed

[Abhishek Tiwari]

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 <chami...@wso2.com>
wrote:

> 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/@chamilad
>
>
>
> On Fri, Aug 19, 2016 at 3:38 AM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> 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-framework
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GSoC Dockerfiles] Open issues has been addressed

[Abhishek Tiwari]

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-framework
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Added ability to run smoke tests from test framework

[Abhishek Tiwari]

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, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:

> 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 address all these shortly.
>
> Thanks
> Abhishek
>
> On Thu, Aug 18, 2016 at 2:39 AM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> 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,
>> there were no *ERROR* logs and it has 'error' as part of a word in
>> line[2].
>>
>> For this scenario, we should not make the test to be failed. I think
>> instead of simply grepping the 'error' word as in[3], we should grep the
>> *ERROR* logs.
>>
>> [1].
>> 2016/08/18 14:20:28 main.go:151: Starting test setup up
>> 2016/08/18 14:20:28 main.go:154: Completed test setup up
>> 2016/08/18 14:20:28 main.go:106: Running tests for wso2bps, 3.5.1, using
>> puppet provisioning, under default platform.
>> 2016/08/18 14:20:28 common-utils.go:37: Starting building image...
>> 2016/08/18 14:20:57 common-utils.go:45: Successfully built docker image.
>> 2016/08/18 14:20:57 common-utils.go:85: No errors were found in docker
>> build logs
>> 2016/08/18 14:20:57 common-utils.go:58: Running image...
>> 2016/08/18 14:20:59 common-utils.go:66: Successfully ran docker image.
>> 2016/08/18 14:20:59 common-utils.go:98: No errors were found in docker
>> run logs
>> 2016/08/18 14:20:59 common-utils.go:130: Attempt: 1. Port 9763 is not
>> open in the docker container.
>> 2016/08/18 14:20:59 common-utils.go:133: Sleeping for 2 seconds
>> 2016/08/18 14:21:01 common-utils.go:130: Attempt: 2. Port 9763 is not
>> open in the docker container.
>> 2016/08/18 14:21:01 common-utils.go:133: Sleeping for 4 seconds
>> 2016/08/18 14:21:05 common-utils.go:130: Attempt: 3. Port 9763 is not
>> open in the docker container.
>> 2016/08/18 14:21:05 common-utils.go:133: Sleeping for 6 seconds
>> 2016/08/18 14:21:11 common-utils.go:130: Attempt: 4. Port 9763 is not
>> open in the docker container.
>> 2016/08/18 14:21:11 common-utils.go:133: Sleeping for 8 seconds
>> 2016/08/18 14:21:19 common-utils.go:136: Port 9763 is open in the docker
>> container.
>> 2016/08/18 14:21:19 common-utils.go:136: Port 9443 is open in the docker
>> container.
>> 2016/08/18 14:21:20 common-utils.go:153: Carbon server is up and running.
>> 2016/08/18 14:21:20 common-utils.go:166: Checking Carbon server logs for
>> any errors
>> 2016/08/18 14:21:20 docker-utils.go:105: Successfully copied carbon
>> server logs from docker container
>> 2016/08/18 14:21:20 common-utils.go:173: Errors founds in carbon server
>> logs, please check them under wso2bps3.5.1logs
>> 2016/08/18 14:21:20 main.go:146: Test completed for wso2bps, 3.5.1.
>> 2016/08/18 14:21:20 main.go:158: Starting test clean up
>> 2016/08/18 14:21:20 docker-utils.go:61: Stopping and removing docker
>> container with id: 6f28d71772e6
>> 2016/08/18 14:21:31 docker-utils.go:67: Successfully stopped and removed
>> docker container
>> 2016/08/18 14:21:31 docker-utils.go:43: Removing docker image
>> wso2bps:3.5.1
>> 2016/08/18 14:21:31 docker-utils.go:47: Successfully removed docker image
>> 2016/08/18 14:21:31 main.go:161: Completed test clean up
>>
>> [2].
>> TID: [-1234] [] [2016-08-18 08:51:15,701]  INFO
>> {org.springframework.beans.factory.support.DefaultListableBeanFactory} -
>>  Pre-instantiating singletons in org.springframework.beans.fact
>> ory.support.DefaultListableBeanFactory@38d281d4: defining beans
>> [cxf,org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProce
>> ssor,org.apache.cxf.bus.spring.Jsr250BeanPostProcessor
>> ,org.apache.cxf.bus.spring.BusExtensionPostProcessor,deploym
>> entService,runtimeService,queryRuntimeService,historyService
>> ,formService,processDefinitionService,identityService,manage
>> ment

Re: [Dev] [GSoC Dockerfiles test framework] Updating repository name

[Abhishek Tiwari]

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 <abhishek.tiwari0...@gmail.com>
wrote:

> 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 looking.
>
> Thanks
> Abhishek
>
> [1]. https://github.com/abhishek0198/wso2dockerfiles-test-framework
>
> On Thu, Aug 18, 2016 at 12:45 PM, Chamila De Alwis <chami...@wso2.com
> <javascript:_e(%7B%7D,'cvml','chami...@wso2.com');>> wrote:
>
>> 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 - Apache Stratos
>> Senior Software Engineer | WSO2
>> Blog: https://medium.com/@chamilad
>>
>>
>>
>> On Thu, Aug 18, 2016 at 2:39 PM, Abhishek Tiwari <
>> abhishek.tiwari0...@gmail.com
>> <javascript:_e(%7B%7D,'cvml','abhishek.tiwari0...@gmail.com');>> wrote:
>>
>>> 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 try to see what is wrong
>>> with go get.
>>>
>>> Thanks
>>> Abhishek
>>>
>>> [1]. https://github.com/abhishek0198/wsodockerfiles-testframework
>>>
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles test framework] Updating repository name

[Abhishek Tiwari]

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 looking.

Thanks
Abhishek

[1]. https://github.com/abhishek0198/wso2dockerfiles-test-framework

On Thu, Aug 18, 2016 at 12:45 PM, Chamila De Alwis <chami...@wso2.com>
wrote:

> 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 - Apache Stratos
> Senior Software Engineer | WSO2
> Blog: https://medium.com/@chamilad
>
>
>
> On Thu, Aug 18, 2016 at 2:39 PM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> 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 try to see what is wrong with go get.
>>
>> Thanks
>> Abhishek
>>
>> [1]. https://github.com/abhishek0198/wsodockerfiles-testframework
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GSoC Dockerfiles test framework] Updating repository name

[Abhishek Tiwari]

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 try to see what is wrong with go get.

Thanks
Abhishek

[1]. https://github.com/abhishek0198/wsodockerfiles-testframework
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Added ability to run smoke tests from test framework

[Abhishek Tiwari]

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 address all these shortly.

Thanks
Abhishek

On Thu, Aug 18, 2016 at 2:39 AM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> 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, there were
> no *ERROR* logs and it has 'error' as part of a word in line[2].
>
> For this scenario, we should not make the test to be failed. I think
> instead of simply grepping the 'error' word as in[3], we should grep the
> *ERROR* logs.
>
> [1].
> 2016/08/18 14:20:28 main.go:151: Starting test setup up
> 2016/08/18 14:20:28 main.go:154: Completed test setup up
> 2016/08/18 14:20:28 main.go:106: Running tests for wso2bps, 3.5.1, using
> puppet provisioning, under default platform.
> 2016/08/18 14:20:28 common-utils.go:37: Starting building image...
> 2016/08/18 14:20:57 common-utils.go:45: Successfully built docker image.
> 2016/08/18 14:20:57 common-utils.go:85: No errors were found in docker
> build logs
> 2016/08/18 14:20:57 common-utils.go:58: Running image...
> 2016/08/18 14:20:59 common-utils.go:66: Successfully ran docker image.
> 2016/08/18 14:20:59 common-utils.go:98: No errors were found in docker run
> logs
> 2016/08/18 14:20:59 common-utils.go:130: Attempt: 1. Port 9763 is not open
> in the docker container.
> 2016/08/18 14:20:59 common-utils.go:133: Sleeping for 2 seconds
> 2016/08/18 14:21:01 common-utils.go:130: Attempt: 2. Port 9763 is not open
> in the docker container.
> 2016/08/18 14:21:01 common-utils.go:133: Sleeping for 4 seconds
> 2016/08/18 14:21:05 common-utils.go:130: Attempt: 3. Port 9763 is not open
> in the docker container.
> 2016/08/18 14:21:05 common-utils.go:133: Sleeping for 6 seconds
> 2016/08/18 14:21:11 common-utils.go:130: Attempt: 4. Port 9763 is not open
> in the docker container.
> 2016/08/18 14:21:11 common-utils.go:133: Sleeping for 8 seconds
> 2016/08/18 14:21:19 common-utils.go:136: Port 9763 is open in the docker
> container.
> 2016/08/18 14:21:19 common-utils.go:136: Port 9443 is open in the docker
> container.
> 2016/08/18 14:21:20 common-utils.go:153: Carbon server is up and running.
> 2016/08/18 14:21:20 common-utils.go:166: Checking Carbon server logs for
> any errors
> 2016/08/18 14:21:20 docker-utils.go:105: Successfully copied carbon server
> logs from docker container
> 2016/08/18 14:21:20 common-utils.go:173: Errors founds in carbon server
> logs, please check them under wso2bps3.5.1logs
> 2016/08/18 14:21:20 main.go:146: Test completed for wso2bps, 3.5.1.
> 2016/08/18 14:21:20 main.go:158: Starting test clean up
> 2016/08/18 14:21:20 docker-utils.go:61: Stopping and removing docker
> container with id: 6f28d71772e6
> 2016/08/18 14:21:31 docker-utils.go:67: Successfully stopped and removed
> docker container
> 2016/08/18 14:21:31 docker-utils.go:43: Removing docker image wso2bps:3.5.1
> 2016/08/18 14:21:31 docker-utils.go:47: Successfully removed docker image
> 2016/08/18 14:21:31 main.go:161: Completed test clean up
>
> [2].
> TID: [-1234] [] [2016-08-18 08:51:15,701]  INFO
> {org.springframework.beans.factory.support.DefaultListableBeanFactory} -
>  Pre-instantiating singletons in org.springframework.beans.
> factory.support.DefaultListableBeanFactory@38d281d4: defining beans
> [cxf,org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProces
> sor,org.apache.cxf.bus.spring.Jsr250BeanPostProcessor,org.
> apache.cxf.bus.spring.BusExtensionPostProcessor,deploymentService,
> runtimeService,queryRuntimeService,historyService,formService,
> processDefinitionService,identityService,managementService,statsService,
> authenticationBean,exceptionHandlerBean,errorHandlerBean,jacksonBean];
> root of factory hierarchy {org.springframework.beans.factory.support.
> DefaultListableBeanFactory}
>
> [3]. https://github.com/abhishek0198/test-framework/
> blob/master/common/common-utils.go#L169
>
> Thanks.
>
>
> On Fri, Aug 12, 2016 at 3:04 PM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> 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:

Re: [Dev] [GSoC Dockerfiles] Added ability to run smoke tests from test framework

[Abhishek Tiwari]

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/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
>> Abhishek
>>
>> On Thu, Aug 11, 2016 at 9:59 PM, Imesh Gunaratne <im...@wso2.com> 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 today
>>>> afternoon?
>>>>
>>>
>>> ​Would 2:30 PM IST work for you?
>>>
>>> Thanks​
>>>
>>>>
>>>> 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, 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 <
>>>>>> 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 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 up, the
>>>>>>> script does a login to WSO2 carbon server and maintains cookies so that 
>>>>>>> it
>>>>>>> can use logged in state in subsequent requests.
>>>>>>>
>>>>>>> 2. Creates a new pass-through proxy service. [1]
>>>>>>>
>>>>>>> 3. Validates the newly created proxy service is accessible
>>>>>>> (validates Http response code for the proxy testing url [2])
>>>>>>>
>>>>>>> 4. Removes the newly created proxy service. [3]
>>>>>>>
>>>>>>> I would like to demo the current state of the project, please
>>>>>>> provide your preferred date and time.
>>>>>>>
>>>>>>> Thanks
>>>>>>> Abhishek
>>>>>>>
>>>>>>> [1]. Http post using /carbon/proxyservices/template_pass-through.jsp
>>>>>>> [2]. Http get  using /carbon/services/?tryit
>>>>>>> [3]. Http get using /carbon/service-mgt/delete_service_groups.jsp
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Vishanth Balasubramaniam*
>>>>>> Committer & PMC Member, Apache Stratos,
>>>>>> Software Engineer, WSO2 Inc.; http://wso2.com
>>>>>>
>>>>>> mobile: *+94 77 17 377 18*
>>>>>> about me: *http://about.me/vishanth <http://about.me/vishanth>*
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Software Architect
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: https://medium.com/@imesh TW: @imesh
>>> lean. enterprise. middleware
>>>
>>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Added ability to run smoke tests from test framework

[Abhishek Tiwari]

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
> Abhishek
>
> On Thu, Aug 11, 2016 at 9:59 PM, Imesh Gunaratne <im...@wso2.com> 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 today
>>> afternoon?
>>>
>>
>> ​Would 2:30 PM IST work for you?
>>
>> Thanks​
>>
>>>
>>> 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, 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 <
>>>>> 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 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 up, the
>>>>>> script does a login to WSO2 carbon server and maintains cookies so that 
>>>>>> it
>>>>>> can use logged in state in subsequent requests.
>>>>>>
>>>>>> 2. Creates a new pass-through proxy service. [1]
>>>>>>
>>>>>> 3. Validates the newly created proxy service is accessible (validates
>>>>>> Http response code for the proxy testing url [2])
>>>>>>
>>>>>> 4. Removes the newly created proxy service. [3]
>>>>>>
>>>>>> I would like to demo the current state of the project, please provide
>>>>>> your preferred date and time.
>>>>>>
>>>>>> Thanks
>>>>>> Abhishek
>>>>>>
>>>>>> [1]. Http post using /carbon/proxyservices/template_pass-through.jsp
>>>>>> [2]. Http get  using /carbon/services/?tryit
>>>>>> [3]. Http get using /carbon/service-mgt/delete_service_groups.jsp
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Vishanth Balasubramaniam*
>>>>> Committer & PMC Member, Apache Stratos,
>>>>> Software Engineer, WSO2 Inc.; http://wso2.com
>>>>>
>>>>> mobile: *+94 77 17 377 18*
>>>>> about me: *http://about.me/vishanth <http://about.me/vishanth>*
>>>>>
>>>>
>>>>
>>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Software Architect
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: https://medium.com/@imesh TW: @imesh
>> lean. enterprise. middleware
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Added ability to run smoke tests from test framework

[Abhishek Tiwari]

Hi Imesh,

Yeah 2:30pm IST is perfect.

Thanks
Abhishek

On Thu, Aug 11, 2016 at 9:59 PM, Imesh Gunaratne <im...@wso2.com> 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 today
>> afternoon?
>>
>
> ​Would 2:30 PM IST work for you?
>
> Thanks​
>
>>
>> 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, 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 <
>>>> 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 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 up, the
>>>>> script does a login to WSO2 carbon server and maintains cookies so that it
>>>>> can use logged in state in subsequent requests.
>>>>>
>>>>> 2. Creates a new pass-through proxy service. [1]
>>>>>
>>>>> 3. Validates the newly created proxy service is accessible (validates
>>>>> Http response code for the proxy testing url [2])
>>>>>
>>>>> 4. Removes the newly created proxy service. [3]
>>>>>
>>>>> I would like to demo the current state of the project, please provide
>>>>> your preferred date and time.
>>>>>
>>>>> Thanks
>>>>> Abhishek
>>>>>
>>>>> [1]. Http post using /carbon/proxyservices/template_pass-through.jsp
>>>>> [2]. Http get  using /carbon/services/?tryit
>>>>> [3]. Http get using /carbon/service-mgt/delete_service_groups.jsp
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *Vishanth Balasubramaniam*
>>>> Committer & PMC Member, Apache Stratos,
>>>> Software Engineer, WSO2 Inc.; http://wso2.com
>>>>
>>>> mobile: *+94 77 17 377 18*
>>>> about me: *http://about.me/vishanth <http://about.me/vishanth>*
>>>>
>>>
>>>
>>
>
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Added ability to run smoke tests from test framework

[Abhishek Tiwari]

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, 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 <
>> 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 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 up, the
>>> script does a login to WSO2 carbon server and maintains cookies so that it
>>> can use logged in state in subsequent requests.
>>>
>>> 2. Creates a new pass-through proxy service. [1]
>>>
>>> 3. Validates the newly created proxy service is accessible (validates
>>> Http response code for the proxy testing url [2])
>>>
>>> 4. Removes the newly created proxy service. [3]
>>>
>>> I would like to demo the current state of the project, please provide
>>> your preferred date and time.
>>>
>>> Thanks
>>> Abhishek
>>>
>>> [1]. Http post using /carbon/proxyservices/template_pass-through.jsp
>>> [2]. Http get  using /carbon/services/?tryit
>>> [3]. Http get using /carbon/service-mgt/delete_service_groups.jsp
>>>
>>
>>
>>
>> --
>> *Vishanth Balasubramaniam*
>> Committer & PMC Member, Apache Stratos,
>> Software Engineer, WSO2 Inc.; http://wso2.com
>>
>> mobile: *+94 77 17 377 18*
>> about me: *http://about.me/vishanth <http://about.me/vishanth>*
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GSoC Dockerfiles] Weekly status meeting minutes

[Abhishek Tiwari]

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 manipulate ESB resources.

3. Vishanth also recommended to add overall test result at the end of test
run (along with logs) to specify which products we tested and what was the
end result (sort of what mvn test does).

4. Few naming changes on test config.

5. Agreed on doing a demo to a larger audience on this Friday afternoon
(3pm IST).

Thanks
Abhishek
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Added ability to run smoke tests from test framework

[Abhishek Tiwari]

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 <
> 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 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 up, the
>> script does a login to WSO2 carbon server and maintains cookies so that it
>> can use logged in state in subsequent requests.
>>
>> 2. Creates a new pass-through proxy service. [1]
>>
>> 3. Validates the newly created proxy service is accessible (validates
>> Http response code for the proxy testing url [2])
>>
>> 4. Removes the newly created proxy service. [3]
>>
>> I would like to demo the current state of the project, please provide
>> your preferred date and time.
>>
>> Thanks
>> Abhishek
>>
>> [1]. Http post using /carbon/proxyservices/template_pass-through.jsp
>> [2]. Http get  using /carbon/services/?tryit
>> [3]. Http get using /carbon/service-mgt/delete_service_groups.jsp
>>
>
>
>
> --
> *Vishanth Balasubramaniam*
> Committer & PMC Member, Apache Stratos,
> Software Engineer, WSO2 Inc.; http://wso2.com
>
> mobile: *+94 77 17 377 18*
> about me: *http://about.me/vishanth <http://about.me/vishanth>*
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GSoC Dockerfiles] Added ability to run smoke tests from test framework

[Abhishek Tiwari]

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 up, the script
does a login to WSO2 carbon server and maintains cookies so that it can use
logged in state in subsequent requests.

2. Creates a new pass-through proxy service. [1]

3. Validates the newly created proxy service is accessible (validates Http
response code for the proxy testing url [2])

4. Removes the newly created proxy service. [3]

I would like to demo the current state of the project, please provide your
preferred date and time.

Thanks
Abhishek

[1]. Http post using /carbon/proxyservices/template_pass-through.jsp
[2]. Http get  using /carbon/services/?tryit
[3]. Http get using /carbon/service-mgt/delete_service_groups.jsp
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [GSoC Dockerfiles] Project update - Migration to Golang

[Abhishek Tiwari]

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
> "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 <im...@wso2.com> wrote:
>
>> 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 successful. I am happy to offload many
>>> important features (logging, JSON parsing etc) to existing Golang packages.
>>>
>>
>>> I have also implemented interval based polling with linear backoff for
>>> exposed ports and carbon server status. The changes are committed to the
>>> repo [1], would love to get your feedback/comments.
>>>
>>
>> ​Very nice to hear this!​
>>
>> ​We will go through the code. May be you can arrange a session to review
>> this.
>>
>>
>>>
>>> Since I am totally new to this language and completely blank on its
>>> coding standards, I am following the coding standards used in the open
>>> source Kubernetes [2].
>>>
>>
>> ​+1 for following K8S coding standards. A bunch of Google developers are
>> involved in that​
>>
>> ​project and AFAIK coding standards are at their best.
>>
>>>
>>> I absolutely love Golang and those who are interested, I would highly
>>> recommend gobyexample [3], I was able to get up to speed within hours.
>>>
>>
>> ​Yeah [3] is really useful. We also did couple of sessions on Golang at
>> WSO2 [4]
>>
>> [4] http://www.slideshare.net/imesh/an-introduction-to-go-55991343
>>
>> Thanks
>> ​
>>
>>
>>>
>>> Thanks,
>>> Abhishek
>>>
>>> [1]. https://github.com/abhishek0198/test-framework/
>>> [2]. https://github.com/kubernetes/kubernetes
>>> [3]. https://gobyexample.com/
>>>
>>
>>
>>
>> --
>> *Imesh Gunaratne*
>> Software Architect
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: https://medium.com/@imesh TW: @imesh
>>
>>
>
>
> --
> *Vishanth Balasubramaniam*
> Committer & PMC Member, Apache Stratos,
> Software Engineer, WSO2 Inc.; http://wso2.com
>
> mobile: *+94 77 17 377 18*
> about me: *http://about.me/vishanth <http://about.me/vishanth>*
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Meeting minutes

[Abhishek Tiwari]

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 Gunaratne <im...@wso2.com> wrote:

>
>
> 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 on what I have read so
>> far). A quick search did not provide any solution so I will tackle this
>> later. If anyone has addressed this in the community, please let me know.
>>
>> ​Create a folder with the name that you want go give for the binary and
> move the .go file to that folder. That would create the binary using
> the folder name.
> ​
>
>
>> Import statement for common is fully qualified since that is the root
>> level package. If I try prefixing that with project name, that will not
>> work, as Go will try to look for the package in the following:
>> /src/
>>
>> I have also provided instruction to build the project without Eclipse
>> [1]. It looks like your GOPATH is missing the path of the source directory
>> of project. My GOPATH has following additional entry for the project:
>> /Users/abhishektiwari/dev/test-framework
>>
>
>> Could you please try adding the source root to GOPATH in your
>> bash_profile. Please let me know if you still face issues with the build.
>>
>
> I tend to disagree with your approach. Building a project should not be
> that much of a trouble. Ideally the project should build with the following
> commands:
>
> go get github.com//
> cd $GOPATH/src/
> github.com//
> go build
>
> Thanks
> ​
>
>
>> [1]. https://github.com/abhishek0198/test-framework#build-without-eclipse
>>
>> Thanks
>> Abhishek
>>
>> On Mon, Aug 1, 2016 at 2:46 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>>
>>> 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 compile fine. I will add complete
>>>> instructions on Github and update this thread.
>>>>
>>>
>>> ​I do not think we should use Eclipse specific build tools. The project
>>> should be able to build from the shell with standard go build commands.​
>>> I went through the updated README and still the given instructions seem
>>> to be not working:
>>>
>>> ~/dev/test-framework$ go install -v -gcflags "-N -l" ./...
>>> src/main/config_parser.go:24:2: cannot find package "common" in any of:
>>> /usr/local/go/src/common (from $GOROOT)
>>> /Users/imesh/dev/go/src/common (from $GOPATH)
>>>
>>> I see couple of problems in the code:
>>>
>>>- ​The executable name should be meaningful. I do not think main is
>>>much meaningful binary name.
>>>- Import statements which refer packages from the same project
>>>should use fully qualified package names [1]. See [2]. This might be the
>>>root cause of the above error.
>>>
>>> ​[1]
>>> https://github.com/abhishek0198/test-framework/
>>> blob/master/src/main/config_parser.go#L24
>>> [2] https://github.com/kubernetes/kubernetes/blob/
>>> master/pkg/proxy/iptables/proxier.go#L38
>>>
>>> Thanks​
>>> ​
>>>
>>>
>>>> Chamila,
>>>> The tests I am working on are custom tests which aims at verifying few
>>>> endpoints using CURL. I tried using existing tests for ESB, and that didn't
>>>> help either since setup steps of those tests requires a lot of efforts. If
>>>> developers from specific projects can help out with configuration, then we
>>>> can run existing full fledged tests.
>>>>
>>>> Thanks
>>>> Abhishek
>>>>
>>>> On Thu, Jul 28, 2016 at 9:08 PM, Chamila De Alwis <chami...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>> On Thu, Jul 28, 2016 at 4:19

Re: [Dev] Update on Kubernetes setup

[Abhishek Tiwari]

Hi Imesh,

I am not trying access container in K8S, this problem was while running
tests for regular container deployement (which we call default platform).

Thanks
Abhishek

On Wednesday, August 3, 2016, Imesh Gunaratne <im...@wso2.com> wrote:

>
> ​Hi Abhishek,​
>
> On Thu, Aug 4, 2016 at 9:39 AM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com
> <javascript:_e(%7B%7D,'cvml','abhishek.tiwari0...@gmail.com');>> wrote:
>
>> Hi Imesh,
>>
>> Most important issue was the IP address of docker container is not
>> accessibly directly, so I added a config in the test-config.json to specify
>> docker-machine ip address. If it is not present, I try to get the IP
>> address of the docker container.
>>
>
> ​Can you please explain why you are trying to access the containers on K8S
> using their IP addresses from the external network? What's your approach?
>
> Thanks
>
>>
>> Vishanth,
>> I am still working on completing smoke tests so that I can make the
>> end-to-end workflow. Once that is done, I will schedule the demo.
>>
>> Thanks
>> Abhishek
>>
>> On Wed, Aug 3, 2016 at 11:23 AM, Imesh Gunaratne <im...@wso2.com
>> <javascript:_e(%7B%7D,'cvml','im...@wso2.com');>> wrote:
>>
>>> Hi Abhishek,
>>>
>>> Please always send mails to WSO2 Dev except when you have sensitive
>>> information (such as credentials, etc) to share with us.
>>>
>>> On Wed, Aug 3, 2016 at 10:29 AM, Abhishek Tiwari <
>>> abhishek.tiwari0...@gmail.com
>>> <javascript:_e(%7B%7D,'cvml','abhishek.tiwari0...@gmail.com');>> wrote:
>>>
>>>> Hi Mentors,
>>>>
>>>> I am able to run Kubernetes cluster on my Mac now and currently working
>>>> on deploying ESB on it. I ran into few issues with test framework not
>>>> working on Mac.
>>>>
>>>
>>> ​
>>> I
>>> ​t would be better to be more specific on the errors.​
>>>
>>>>
>>>> Mac uses docker-machine (OSX specific util) to create virtual hosts
>>>> where it runs docker daemon, so its a bit different than Unix where daemon
>>>> runs directly on host. The IP address of deployed container is not directly
>>>> accessible, you need either create forwarding or go through
>>>> docker-machine's IP address. There were bunch of other small changes that I
>>>> had to do to make the test framework work across both Mac and Unix. Now
>>>> that its done, I am working on deployment.
>>>>
>>>
>>> ​What were the changes you did?
>>>
>>> Thanks
>>> ​
>>>
>>> --
>>> *Imesh Gunaratne*
>>> Software Architect
>>> WSO2 Inc: http://wso2.com
>>> T: +94 11 214 5345 M: +94 77 374 2057
>>> W: https://medium.com/@imesh TW: @imesh
>>> lean. enterprise. middleware
>>>
>>>
>>
>
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Update on Kubernetes setup

[Abhishek Tiwari]

Hi Imesh,

Most important issue was the IP address of docker container is not
accessibly directly, so I added a config in the test-config.json to specify
docker-machine ip address. If it is not present, I try to get the IP
address of the docker container.

Vishanth,
I am still working on completing smoke tests so that I can make the
end-to-end workflow. Once that is done, I will schedule the demo.

Thanks
Abhishek

On Wed, Aug 3, 2016 at 11:23 AM, Imesh Gunaratne <im...@wso2.com> wrote:

> Hi Abhishek,
>
> Please always send mails to WSO2 Dev except when you have sensitive
> information (such as credentials, etc) to share with us.
>
> On Wed, Aug 3, 2016 at 10:29 AM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> Hi Mentors,
>>
>> I am able to run Kubernetes cluster on my Mac now and currently working
>> on deploying ESB on it. I ran into few issues with test framework not
>> working on Mac.
>>
>
> ​
> I
> ​t would be better to be more specific on the errors.​
>
>>
>> Mac uses docker-machine (OSX specific util) to create virtual hosts where
>> it runs docker daemon, so its a bit different than Unix where daemon runs
>> directly on host. The IP address of deployed container is not directly
>> accessible, you need either create forwarding or go through
>> docker-machine's IP address. There were bunch of other small changes that I
>> had to do to make the test framework work across both Mac and Unix. Now
>> that its done, I am working on deployment.
>>
>
> ​What were the changes you did?
>
> Thanks
> ​
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Meeting minutes

[Abhishek Tiwari]

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 later. If
anyone has addressed this in the community, please let me know.

Import statement for common is fully qualified since that is the root level
package. If I try prefixing that with project name, that will not work, as
Go will try to look for the package in the following:
/src/

I have also provided instruction to build the project without Eclipse [1].
It looks like your GOPATH is missing the path of the source directory of
project. My GOPATH has following additional entry for the project:
/Users/abhishektiwari/dev/test-framework

Could you please try adding the source root to GOPATH in your bash_profile.
Please let me know if you still face issues with the build.

[1]. https://github.com/abhishek0198/test-framework#build-without-eclipse

Thanks
Abhishek

On Mon, Aug 1, 2016 at 2:46 PM, Imesh Gunaratne <im...@wso2.com> wrote:

> 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 compile fine. I will add complete
>> instructions on Github and update this thread.
>>
>
> ​I do not think we should use Eclipse specific build tools. The project
> should be able to build from the shell with standard go build commands.​
> I went through the updated README and still the given instructions seem to
> be not working:
>
> ~/dev/test-framework$ go install -v -gcflags "-N -l" ./...
> src/main/config_parser.go:24:2: cannot find package "common" in any of:
> /usr/local/go/src/common (from $GOROOT)
> /Users/imesh/dev/go/src/common (from $GOPATH)
>
> I see couple of problems in the code:
>
>- ​The executable name should be meaningful. I do not think main is
>much meaningful binary name.
>- Import statements which refer packages from the same project should
>use fully qualified package names [1]. See [2]. This might be the root
>cause of the above error.
>
> ​[1]
>
> https://github.com/abhishek0198/test-framework/blob/master/src/main/config_parser.go#L24
> [2]
> https://github.com/kubernetes/kubernetes/blob/master/pkg/proxy/iptables/proxier.go#L38
>
> Thanks​
> ​
>
>
>> Chamila,
>> The tests I am working on are custom tests which aims at verifying few
>> endpoints using CURL. I tried using existing tests for ESB, and that didn't
>> help either since setup steps of those tests requires a lot of efforts. If
>> developers from specific projects can help out with configuration, then we
>> can run existing full fledged tests.
>>
>> Thanks
>> Abhishek
>>
>> On Thu, Jul 28, 2016 at 9:08 PM, Chamila De Alwis <chami...@wso2.com>
>> wrote:
>>
>>>
>>> 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 can add smoke
>>>> tests. I will add smoke tests for ESB at this point.
>>>>
>>>
>>> Would these be custom tests that are specific to WSO2 Dockerfiles
>>> context or generic tests that aim to test the product code? It would be
>>> better if we can reuse the generic tests, as new tests would not be
>>> attractive to the developers.
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Committer and PMC Member - Apache Stratos
>>> Senior Software Engineer | WSO2
>>> Blog: https://medium.com/@chamilad
>>>
>>>
>>>
>>
>
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Meeting minutes

[Abhishek Tiwari]

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 are custom tests which aims at verifying few
> endpoints using CURL. I tried using existing tests for ESB, and that didn't
> help either since setup steps of those tests requires a lot of efforts. If
> developers from specific projects can help out with configuration, then we
> can run existing full fledged tests.
>
> Thanks
> Abhishek
>
> On Thu, Jul 28, 2016 at 9:08 PM, Chamila De Alwis <chami...@wso2.com>
> wrote:
>
>>
>> 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 can add smoke
>>> tests. I will add smoke tests for ESB at this point.
>>>
>>
>> Would these be custom tests that are specific to WSO2 Dockerfiles context
>> or generic tests that aim to test the product code? It would be better if
>> we can reuse the generic tests, as new tests would not be attractive to the
>> developers.
>>
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Senior Software Engineer | WSO2
>> Blog: https://medium.com/@chamilad
>>
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Meeting minutes

[Abhishek Tiwari]

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 are custom tests which aims at verifying few
endpoints using CURL. I tried using existing tests for ESB, and that didn't
help either since setup steps of those tests requires a lot of efforts. If
developers from specific projects can help out with configuration, then we
can run existing full fledged tests.

Thanks
Abhishek

On Thu, Jul 28, 2016 at 9:08 PM, Chamila De Alwis <chami...@wso2.com> wrote:

>
> 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 can add smoke
>> tests. I will add smoke tests for ESB at this point.
>>
>
> Would these be custom tests that are specific to WSO2 Dockerfiles context
> or generic tests that aim to test the product code? It would be better if
> we can reuse the generic tests, as new tests would not be attractive to the
> developers.
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Senior Software Engineer | WSO2
> Blog: https://medium.com/@chamilad
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GSoC Dockerfiles] Meeting minutes

[Abhishek Tiwari]

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 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 can add smoke tests. I
will add smoke tests for ESB at this point.

3. I am going to try to have kubernetes setup on Mac using vagrant and will
try to deploy ESB docker build on it. If all goes well, we will have a demo
next week to a much larger audience and collect some feedback.

4. I will also add instructions to install golang locally on ubuntu on the
git repo, so that other developers can use the test framework for future
releases.

Thanks
Abhishek
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Dockerfiles 1.2.0 Released !

[Abhishek Tiwari]

+1

Tested WSO2 Dockerfile with the new test framework for WSO2ESB and WSO2MB
products.
Carbon server starts fine for both the products and no errors were found in
Carbon logs.

Thanks,
Abhishek

On Tue, Jul 26, 2016 at 5:41 PM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> WSO2 PaaS team is pleased to announce the release of *WSO2 Dockerfiles
> 1.2.0*
>
>
> WSO2 Dockerfiles 1.2.0 is the successor of 1.1.0.
>
> *The main changes for this release:*
>
>-
>
>Created a WSO2 base image with the common packages installed.
>-
>
>Validated the profile and platform before building the Docker image.
>-
>
>Added a SVN Docker image.
>-
>
>Changed all ENTRYPOINTs in all Dockerfiles to use the exec form.
>-
>
>Added a script to push the Docker images to a specified registry.
>-
>
>Added the wso2cep init extension scripts.
>-
>
>Included the net-tools package into the wso2base image.
>-
>
>Added debug support for WSO2 servers.
>-
>
>Replaced localMemberPort with dynamic proxy port for the Mesos
>platform.
>-
>
>Added the platform name as a postfix to the Docker image name.
>-
>
>Introduced artifacts folder
>-
>
>Append host node IP to symlink path to create a unique path across a
>cluster in Mesos platform 
>
>
> *Release artifacts:*
>
> https://github.com/wso2/dockerfiles/releases/tag/v1.2.0
>
> *Documentation:*
>
> https://docs.wso2.com/display/DF120/WSO2+Dockerfiles+Documentation
>
>
> *Fixed Issues:*
> https://wso2.org/jira/issues/?filter=13159
>
> *Known Issues:*
>
> https://wso2.org/jira/issues/?filter=13160
>
> --
>
> Regards,
> WSO2 PaaS team
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [GSoC Dockerfiles] Issues with setting up Kubernetes using Vagrant

[Abhishek Tiwari]

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 <im...@wso2.com> wrote:

> Hi Abhishek,
>
> On Wed, Jul 20, 2016 at 9:49 AM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com
> <javascript:_e(%7B%7D,'cvml','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), however, those got resolved.
>>
>
> ​Can you please execute following to ssh into the master node and check
> the system log?
>
> vagrant ssh master
> journalctl -f​
>
>
>>
>> Now, when I launch the setup using run.sh, I get this error [2]. I tried
>> wiping out everything (vagrant destroy -f) and restart the whole process
>> again, I get the same issue.
>>
>> One thing to note is, my host os is Mac and I use VirtualBox for
>> development, so essentially I have virtualbox setup inside virtualbox. I
>> don't think it should matter, but would like to get other people's opinion
>> on this.
>>
>
> ​This works on OSX.​
>
>
>>
>> While this issue gets resolved, I am planning to complete another
>> milestone to add smoke tests for ESB and MB. I feel like, I should complete
>> the test workflow for default platform before moving to Kubernetes, since
>> the latter involves a lot of new technologies, more moving parts and other
>> unknowns. I do plan to address Kubernetes testing, but would like to do
>> that once default platform test workflow is complete. Thoughts?
>>
>
> ​+1
>
> If [1] does not work for you, please try following:
> http://kubernetes.io/docs/getting-started-guides/vagrant/
>
> Thanks​
>
>
>>
>> Thanks,
>> Abhishek
>>
>> [1]. https://github.com/imesh/kubernetes-vagrant-setup
>> [2].
>> master: Waiting for machine to boot. This may take a few minutes...
>> master: SSH address: 127.0.0.1:
>> master: SSH username: core
>> master: SSH auth method: private key
>>
>> Timed out while waiting for the machine to boot. This means that
>> Vagrant was unable to communicate with the guest machine within
>> the configured ("config.vm.boot_timeout" value) time period.
>>
>>
>>
>
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] [GSoC Dockerfiles] Issues with setting up Kubernetes using Vagrant

[Abhishek Tiwari]

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 out everything (vagrant destroy -f) and restart the whole process
again, I get the same issue.

One thing to note is, my host os is Mac and I use VirtualBox for
development, so essentially I have virtualbox setup inside virtualbox. I
don't think it should matter, but would like to get other people's opinion
on this.

While this issue gets resolved, I am planning to complete another milestone
to add smoke tests for ESB and MB. I feel like, I should complete the test
workflow for default platform before moving to Kubernetes, since the latter
involves a lot of new technologies, more moving parts and other unknowns. I
do plan to address Kubernetes testing, but would like to do that once
default platform test workflow is complete. Thoughts?

Thanks,
Abhishek

[1]. https://github.com/imesh/kubernetes-vagrant-setup
[2].
master: Waiting for machine to boot. This may take a few minutes...
master: SSH address: 127.0.0.1:
master: SSH username: core
master: SSH auth method: private key

Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] [GSoC Dockerfiles] Project update - Migration to Golang

[Abhishek Tiwari]

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 packages.

I have also implemented interval based polling with linear backoff for
exposed ports and carbon server status. The changes are committed to the
repo [1], would love to get your feedback/comments.

Since I am totally new to this language and completely blank on its coding
standards, I am following the coding standards used in the open source
Kubernetes [2].

I absolutely love Golang and those who are interested, I would highly
recommend gobyexample [3], I was able to get up to speed within hours.

Thanks,
Abhishek

[1]. https://github.com/abhishek0198/test-framework/
[2]. https://github.com/kubernetes/kubernetes
[3]. https://gobyexample.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] [GSoC] Meeting minutes from Dockerfiles test framework demo

[Abhishek Tiwari]

Hi All,

Thanks so much for attending the demo and providing great feedback.
Following are the meeting minutes:

1. Demo of testing WSO2ESB 4.9.0 with default profile, discussed output log
and few implementation details.

2. Feedback:
a) Test framework should add the ability to check docker logs as well.
b) Checking for exposed ports should happen periodically with a timeout,
instead of a static sleep.
c) Look into feasibility of classifying errors (in build or run) in terms
of specific module (e.g. build failed due to an issue with hieradata).
d) Check status code returned from build and run scripts.
e) Look into integrating the test results into Jenkins, to allow nightly
runs.
f) Support of Kubernetes platform as well as product profiles (worker,
manager nodes)

Please add if I missed something.

Thanks
Abhishek
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GSoC Dockerfiles] Status update

[Abhishek Tiwari]

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:

"products": {
"esb": {
"enabled":"true",
"name": "wso2esb",
"version": "4.9.0",
"provisioning_method": "puppet"
}
}


This is pretty rudimentary at this point and will get sophisticated as we
add more features.

2. Enhanced existing test framework to also account puppet provisioning.

3. Redirect test results from all the products to a final report-like log
file, which contains success/failure along with test run times.

The changes can be reviewed in the git repo [1], would love to get your
feedback/comments. I would schedule a hangout call for tomorrow (6/29) at
10am for demo.

Thanks,
Abhishek

[1]. https://github.com/abhishek0198/test-framework
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] [GSoC Dockerfiles] Meeting minutes

[Abhishek Tiwari]

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 deployed
product by potentially making some SOAP/REST API calls and ensuring that
the application server responds with expected results.

2. The test framework will be driven by config, where developers can
specify
a) What products they want to test (product name, version),
b) Under which provisioning method (default, puppet) and
c) Under what platform (default, kubernetes).
This will also us to do quick product level testing as well as add nightly
test runs which will be a lot more exhaustive.

3. The test framework will test all the products specified in the test
config, irrespective of failures in individual product builds. At the end
of test run, the framework will generate a report specifying the status of
test runs.

4. We plan to demo the current status of product this week to a relatively
larger audience, and hopefully get some great feedback.

Thanks
Abhishek
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Dockerfiles] Milestone plan for GSoC project

[Abhishek Tiwari]

Hi All,

Here is the milestone plan for Dockerfile test framework project:

https://docs.google.com/spreadsheets/d/1CYHS49s3g5XACofO4D-qIiaU8QomYcDUZX7meL8j1Ls/edit?usp=sharing

Thanks
Abhishek
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GSoC Dockerfiles]

[Abhishek Tiwari]

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/cgi-bin/mailman/listinfo/dev

[Dev] [GSoC Dockerfiles] Meeting minutes

[Abhishek Tiwari]

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 figure out existing ESB integration tests run
using docker containers.
4. Updated milestone plan [1].

*Discussion:*
1. Using product's existing integration tests is preferable since writing
our own will take a lot of time.
2. We should enhance the test framework to test other provisioning methods,
platforms and worker-manager type of setup as well.
3. I am facing an issue with console log redirection where console logs
coming from Docker commands are not getting redirected. I will search for
solutions.

Thanks,
Abhishek

[1].
https://docs.google.com/spreadsheets/d/1CYHS49s3g5XACofO4D-qIiaU8QomYcDUZX7meL8j1Ls/edit?usp=sharing
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 ESB tests

[Abhishek Tiwari]

Hi Irham,

Thanks Irham for the doc. For the purpose of my tests, I would like to use
the existing integration tests for ESB rather than write new ones (as I do
not have much context about ESB itself, my goal is to run existing tests
agains an ESB instance deployed in a docker container).

Looking at the test source in [1], I am envisioning the flow to be
something like:
1. Deploy WSO2 ESB to a docker container.
2. Start the ESB server, I can access the server through carbon [2].
3. Clone integration test repo [1] in the host (not on the container)
4. Change the automation.xml [3] of each test module to point to the ESB
running in container (I am not sure if this is the carbon URL or something
else).
5. Do other overrides required to point to the ESB running in container (I
don't know what they are).
6. Launch integration test using maven.

Is this test execution plan possible with the current integration tests?

Thanks
Abhishek

[1].
https://github.com/wso2/product-esb/tree/master/modules/integration/tests-integration
[2].
https://172.17.0.2:9443/carbon/log-view/index.jsp?region=region4=logs_menu
<https://172.2.0.2>
[3].
https://github.com/wso2/product-esb/blob/master/modules/integration/tests-integration/tests-sample/src/test/resources/automation.xml

On Mon, Jun 20, 2016 at 1:15 PM, Irham Iqbal <iq...@wso2.com> wrote:

> Hi Abhishek,
>
> You can refer the doc[1] to write ESB integration test and run.
>
> [1] https://docs.wso2.com/display/TA430/Writing+a+Test+Case+for+ESB
>
> Thanks,
> Iqbal
>
> On Sun, Jun 19, 2016 at 1:28 AM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> Hi Nuwan,
>>
>> Thanks a lot for your prompt response. Are there any docs on running
>> these tests in a standalone ESB deployment (without Docker) ? That will
>> give a clear idea on what configs to deploy and how to start these tests.
>>
>> Thanks
>> Abhishek
>>
>> On Fri, Jun 17, 2016 at 10:36 AM, Nuwan Pallewela <nuw...@wso2.com>
>> wrote:
>>
>>> Hi Abhishek,
>>>
>>> You can find the existing test cases from the product-esb source[1].
>>> What you may basically have to do is save proxy or API configs as files
>>> and then deploy them in ESB server and test by sending requests. By
>>> referring to already written test cases you can easily understand.
>>>
>>> [1]
>>> https://github.com/wso2/product-esb/tree/master/modules/integration/tests-integration
>>>
>>> Thanks,
>>> Nuwan
>>>
>>> On Fri, Jun 17, 2016 at 10:12 PM, Abhishek Tiwari <
>>> abhishek.tiwari0...@gmail.com> wrote:
>>>
>>>> Hi All,
>>>>
>>>> My name is Abhishek, and I am a GSoC student,  working on the test
>>>> framework for WSO2 Dockerfiles. As part of that, I am writing tests for
>>>> individual products once they have been deployed using Docker container.
>>>> Currently I am writing tests for ESB. I plan to write tests for
>>>> - Creating and testing proxy service
>>>> - Creating and testing APIs
>>>> - Applying WS-Security to proxy services and testing the applied
>>>> security
>>>>
>>>> Are there existing smoke tests in ESB which I can use as reference?
>>>> Where can I get the details around creating proxies, APIs programmatically?
>>>>
>>>> Thanks
>>>> Abhishek
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> --
>>>
>>> *Nuwan Chamara Pallewela*
>>>
>>>
>>> *Software Engineer*
>>>
>>> *WSO2, Inc. *http://wso2.com
>>> *lean . enterprise . middleware*
>>>
>>> Email   *nuw...@wso2.com <nuw...@wso2.com>*
>>> Mobile  *+94719079739 <%2B94719079739>@*
>>>
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Irham Iqbal
> Software Engineer - Test Automation
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
> phone: +94 777888452
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Add ability to silently run docker image

[Abhishek Tiwari]

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 <chami...@wso2.com> wrote:

>
> 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 input values
> when prompted.
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GSoC Dockerfiles] Project status update

[Abhishek Tiwari]

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 the container and report errors/exceptions

The changes are committed to the test framework repository [1]. I will demo
these on our next status meeting.  I am working towards tests specific for
ESB now.

Thanks
Abhishek

[1]. https://github.com/abhishek0198/test-framework
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GSoC Dockerfiles] Add ability to silently run docker image

[Abhishek Tiwari]

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 originates from Dockerfiles test framework. I have the
feature implemented, would like someone to review and merge the PR [1].
Thanks,
Abhishek

[1]. https://github.com/wso2/dockerfiles/pull/53
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 ESB tests

[Abhishek Tiwari]

Hi Nuwan,

Thanks a lot for your prompt response. Are there any docs on running these
tests in a standalone ESB deployment (without Docker) ? That will give a
clear idea on what configs to deploy and how to start these tests.

Thanks
Abhishek

On Fri, Jun 17, 2016 at 10:36 AM, Nuwan Pallewela <nuw...@wso2.com> wrote:

> Hi Abhishek,
>
> You can find the existing test cases from the product-esb source[1].
> What you may basically have to do is save proxy or API configs as files
> and then deploy them in ESB server and test by sending requests. By
> referring to already written test cases you can easily understand.
>
> [1]
> https://github.com/wso2/product-esb/tree/master/modules/integration/tests-integration
>
> Thanks,
> Nuwan
>
> On Fri, Jun 17, 2016 at 10:12 PM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> Hi All,
>>
>> My name is Abhishek, and I am a GSoC student,  working on the test
>> framework for WSO2 Dockerfiles. As part of that, I am writing tests for
>> individual products once they have been deployed using Docker container.
>> Currently I am writing tests for ESB. I plan to write tests for
>> - Creating and testing proxy service
>> - Creating and testing APIs
>> - Applying WS-Security to proxy services and testing the applied security
>>
>> Are there existing smoke tests in ESB which I can use as reference? Where
>> can I get the details around creating proxies, APIs programmatically?
>>
>> Thanks
>> Abhishek
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com <nuw...@wso2.com>*
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 ESB tests

[Abhishek Tiwari]

Hi All,

My name is Abhishek, and I am a GSoC student,  working on the test
framework for WSO2 Dockerfiles. As part of that, I am writing tests for
individual products once they have been deployed using Docker container.
Currently I am writing tests for ESB. I plan to write tests for
- Creating and testing proxy service
- Creating and testing APIs
- Applying WS-Security to proxy services and testing the applied security

Are there existing smoke tests in ESB which I can use as reference? Where
can I get the details around creating proxies, APIs programmatically?

Thanks
Abhishek
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Meeting minutes from Dockerfiles test framework project

[Abhishek Tiwari]

Hi All,

Following are the meeting minutes

*Agenda*
Demo the current implementation of Dockerfiles test framework

*Tasks completed:*
1. Test framework initiates a clean build and run of a WSO2 product
(currently ESB 4.9.0)
2. Validates that all the exposed ports are open
3. Validates that WSO2 carbon server has been started successfully on the
Docker container.

*Tasks planned before next sync up*
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 the container and report errors/exceptions

Thanks
Abhishek
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Docker command cheat sheet

[Abhishek Tiwari]

This was very helpful to me in ramping up with Docker:

https://github.com/wsargent/docker-cheat-sheet

Thanks
Abhishek
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Using curl to get http response code from SSL

[Abhishek Tiwari]

Hi Dilan,

Thanks for your prompt response. Specifying --insecure did the trick. Thanks

Cheers,
Abhishek

On Wed, Jun 15, 2016 at 12:32 PM, Dilan Udara Ariyaratne <dil...@wso2.com>
wrote:

> HI Abishek,
>
> If I understand your problem correctly, seems like you are trying to
> access simply an HTTPS endpoint from curl.
> Have you used curl with -k (or --insecure) option?, so that you can turn
> off curl's verification for server-side SSL certificates.
>
> Cheers,
> Dilan.
>
> *Dilan U. Ariyaratne*
> Senior Software Engineer
> WSO2 Inc. <http://wso2.com/>
> Mobile: +94766405580 <%2B94766405580>
> lean . enterprise . middleware
>
>
> On Wed, Jun 15, 2016 at 12:15 PM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> Hi All,
>>
>> I am trying to get HTTP response code from carbon server running in
>> docker container. The server runs on SSL with URL as
>> https://172.16.0.2:9443/. Currently, the response returned is 000
>> (client abort). Has anyone encountered this issue?
>>
>> Cheers,
>> Abhishek
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Using curl to get http response code from SSL

[Abhishek Tiwari]

Hi All,

I am trying to get HTTP response code from carbon server running in docker
container. The server runs on SSL with URL as https://172.16.0.2:9443/.
Currently, the response returned is 000 (client abort). Has anyone
encountered this issue?

Cheers,
Abhishek
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GSoC - Dockerfiles] initial test scripts

[Abhishek Tiwari]

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/abhishek0198/test-framework

Thanks,
Abhishek
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Messages on Dockerfiles build using default puppet provisioning

[Abhishek Tiwari]

Hi All,

I recently built wso2mb docker image using puppet provisioning (default).
The build was successful and I was able to launch the product, but I saw
the following messages [1], which seems to indicate that yaml files from
almost all the products were accessed.

I haven't gone through the implementation yet, but I am curious as to why
we are accessing yaml files from all the products while building a specific
product.

Thanks
Abhishek


[1].
172.17.0.2 - - [08/Jun/2016 11:41:08] "GET
/hieradata/dev/wso2/wso2dss/3.5.0/default/worker.yaml HTTP/1.1" 200 -
2016-06-08 06:11:08 URL:
http://172.17.0.1:8000/hieradata/dev/wso2/wso2dss/3.5.0/default/worker.yaml
[1466/1466] -> "hieradata/dev/wso2/wso2dss/3.5.0/default/worker.yaml" [2]
No data received.
172.17.0.2 - - [08/Jun/2016 11:41:09] "GET
/hieradata/dev/wso2/wso2dss/3.5.0/kubernetes/default.yaml HTTP/1.1" 200 -
2016-06-08 06:11:09 URL:
http://172.17.0.1:8000/hieradata/dev/wso2/wso2dss/3.5.0/kubernetes/default.yaml
[6804/6804] -> "hieradata/dev/wso2/wso2dss/3.5.0/kubernetes/default.yaml"
[2]
No data received.
172.17.0.2 - - [08/Jun/2016 11:41:10] "GET
/hieradata/dev/wso2/wso2dss/3.5.0/kubernetes/manager.yaml HTTP/1.1" 200 -
2016-06-08 06:11:10 URL:
http://172.17.0.1:8000/hieradata/dev/wso2/wso2dss/3.5.0/kubernetes/manager.yaml
[1497/1497] -> "hieradata/dev/wso2/wso2dss/3.5.0/kubernetes/manager.yaml"
[2]
No data received.
172.17.0.2 - - [08/Jun/2016 11:41:11] "GET
/hieradata/dev/wso2/wso2dss/3.5.0/kubernetes/worker.yaml HTTP/1.1" 200 -
2016-06-08 06:11:11 URL:
http://172.17.0.1:8000/hieradata/dev/wso2/wso2dss/3.5.0/kubernetes/worker.yaml
[1500/1500] -> "hieradata/dev/wso2/wso2dss/3.5.0/kubernetes/worker.yaml" [2]
No data received.
172.17.0.2 - - [08/Jun/2016 11:41:12] "GET
/hieradata/dev/wso2/wso2es/2.0.0/default/default.yaml HTTP/1.1" 200 -
2016-06-08 06:11:12 URL:
http://172.17.0.1:8000/hieradata/dev/wso2/wso2es/2.0.0/default/default.yaml
[10013/10013] -> "hieradata/dev/wso2/wso2es/2.0.0/default/default.yaml" [2]
No data received.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] GSoC Dockerfiles - Weekly status meeting minutes

[Abhishek Tiwari]

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 fast if docker daemon is not running has been merged.

Next steps:
1. Develop concrete milestone plan for test framework with focus on tasks to be 
completed within mid-term evaluation.
2. Utilize the current bash test script from Chamila as a basis for writing 
tests.

Thanks
Abhishek

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

[Dev] GSoC Dockerfiles weekly status meeting minutes

[Abhishek Tiwari]

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 environment.
3. Debugging and testing of docker-build and docker-run scripts.
4. Added ability to fail fast when docker daemon is not running in the host. 
Pull request [1].

Current tasks:
1. Deploy docker products using puppet provisioning modules [2].
2. Use puppet provisioning to configure manager and worker profiles for ESB.
3. Investigate suitable programming languages and technologies for the proposed 
test framework. 

Thanks,
Abhishek

[1]. https://github.com/wso2/dockerfiles/pull/44 

[2]. https://github.com/wso2/puppet-modules 


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

Re: [Dev] Running WSO2ESB in Clutered mode

[Abhishek Tiwari]

Thanks Chamila, I'll follow the steps in the given doc.

- Abhishek

On Mon, May 9, 2016 at 7:16 AM, Chamila De Alwis <chami...@wso2.com> wrote:

> Hi Abhishek,
>
> The guides on WSO2 product clustering are on a different doc space. Please
> find the guide for WSO2 ESB at [1].
>
> [1] -  https://docs.wso2.com/display/CLUSTER44x/Clustering+ESB+4.9.0
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Mon, May 9, 2016 at 7:14 AM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> Hi All,
>>
>> I have been trying to run ESB in clustered setup (one master and one
>> worker node). Here are the steps I followed:
>> 1) Have two copies of wso2esb-4.9.0 (esb-master and esb-worker).
>> 2) Started esb-master/bin/wso2server.sh
>> 3) Verified server start from logs and web management console.
>> 4) Started esb-workder/bin/wso2server.sh -DworkerNode (this gave port
>> already used exceptions for monitoring ports already in use)
>>
>> The above does not work, and unfortunately, I did not find
>> cluster/profile specific documentation in ESB documentation (
>> https://docs.wso2.com/display/ESB490/Getting+Started), and there weren't
>> any samples (https://docs.wso2.com/display/ESB490/Samples) either. So my
>> questions are:
>> 1) How do run master worker setup in localhost. Any Docs?
>> 2) Are there any predefined profiles for this use-case?
>>
>> Thanks
>> Abhishek
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Running WSO2ESB in Clutered mode

[Abhishek Tiwari]

Hi All,

I have been trying to run ESB in clustered setup (one master and one worker
node). Here are the steps I followed:
1) Have two copies of wso2esb-4.9.0 (esb-master and esb-worker).
2) Started esb-master/bin/wso2server.sh
3) Verified server start from logs and web management console.
4) Started esb-workder/bin/wso2server.sh -DworkerNode (this gave port
already used exceptions for monitoring ports already in use)

The above does not work, and unfortunately, I did not find cluster/profile
specific documentation in ESB documentation (
https://docs.wso2.com/display/ESB490/Getting+Started), and there weren't
any samples (https://docs.wso2.com/display/ESB490/Samples) either. So my
questions are:
1) How do run master worker setup in localhost. Any Docs?
2) Are there any predefined profiles for this use-case?

Thanks
Abhishek
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Meeting minutes on GSoC Dockerfiles

[Abhishek Tiwari]

Hi all,

Here are the notes from our meeting on Integration test framework for
Dockerfiles GSoC project.
https://docs.google.com/document/d/1hxx4isNnCx7YQGbZpnsx-ToAD-Vze6s40tm43akWrMY/edit?usp=sharing


Thanks
Abhishek
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Dockerfiles 1.1.0 RC1

[Abhishek Tiwari]

+1.

Have tested Dockerfiles with Message Broker.

- Abhishek

On Mon, May 2, 2016 at 5:12 AM, Vishanth Balasubramaniam  wrote:

> Hi Devs,
>
>
> This is the first release candidate (RC1) of WSO2 Dockerfiles 1.1.0
> release.
>
> Tag to be voted upon:
>
> https://github.com/wso2/dockerfiles/tree/v1.1.0-rc1
>
> Source and distribution packages:
>
> https://github.com/wso2/dockerfiles/releases/tag/v1.1.0-rc1
>
> Please download, test, and vote. The README file under the distribution
> contains guide and instructions on how to try it out locally.
>
> [ ] Broken - Do not release (explain why)
>
> [ ] Stable - Go ahead and release
>
> This vote will be open for 72 hours or as needed.
>
> Regards,
> Vishanth
> --
> *Vishanth Balasubramaniam*
> Committer & PMC Member, Apache Stratos,
> Software Engineer, WSO2 Inc.; http://wso2.com
>
> mobile: *+94 77 17 377 18*
> about me: *http://about.me/vishanth *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC - Dockerfiles

[Abhishek Tiwari]

Does 6pm IST work?

> On Apr 28, 2016, at 10:30 PM, Vishanth Balasubramaniam <vishan...@wso2.com> 
> 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 
> <abhishek.tiwari0...@gmail.com <mailto:abhishek.tiwari0...@gmail.com>> wrote:
> 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 will send a 
> meeting invite. 
> 
> Thanks
> Abhishek
> 
> 
> 
> -- 
> Vishanth Balasubramaniam
> Committer & PMC Member, Apache Stratos,
> Software Engineer, WSO2 Inc.; http://wso2.com <http://wso2.com/>
> 
> mobile: +94 77 17 377 18 <>
> about me: http://about.me/vishanth <http://about.me/vishanth>

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

[Dev] GSoC Proposal Submitted

[Abhishek Tiwari]

Dear Mentors,

I would like to thank you all for providing valuable feedback and support
during project proposal phase. I have submitted the proposal and am looking
forward to work on the project.

Thanks again!
Abhishek
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] GSoC Project - Integration test framework for Dockerfiles

[Abhishek Tiwari]

Hi All,

My name is Abhishek and I am working on the project to design and implement
an integration test framework for Dockerfiles, to ensure that changes to
Dockerfiles do not cause regressions.

I had very productive hangout meeting with mentors Chamila and Vishant. We
are still formalizing the concrete details, however, I have come up with
the following pipeline for the test suite. Please provide your feedback.

[image: Screen Shot 2016-03-24 at 10.27.47 PM.png]
Detect Change:

We need to check if the change affects everything in the Dockerfiles
repository or it only affects a specific product. The integration test
suites will run tests accordingly.

Environment Variables:

Test that all the required environments are set correctly. The required
variables can be stored in property files on in YAML files.

Test Permissions:

Test that required executable scripts has correct permissions. Also verify
that scripts and log files have correct owners and have correct
permissions. Again, this information can be stored in property files.

Launch Docker Build:

Launch docker build for WSO2 product (multiple products if the changes were
made to common codepath)

Verify Application Launch:

Ensure that WSO2 product is launched correctly, test requests to
application host:port are responded. Also verify that application launch
from logs.

Verify Ports:

Ensure that application is launched at the specific port. Also ensure that
there are no port

conflicts.

Verify in Supported OS: If WSO2 products are supported on multiple OS
platforms, repeat the above tests on all the supported platforms.

- Abhishek
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] GSoC Project - Dockerfiles integration test framework

[Abhishek Tiwari]

Hello Mentors,

I have shared my project proposal for review. Please provide your feedback.

Thanks
Abhishek
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev