[integration-dev] Opendaylight Project: Test Dashboard For OpenDaylight


jaspreet singh
 

Hi,

I've submitted a patch to spectrometer for review(here). I wanted to discuss further about the project to be able to write a proposal.

On Thu, Dec 8, 2016 at 7:49 AM, Luis Gomez <ecelgp@...> wrote:
Hi Jaspreet,  see my answers below:

On Dec 7, 2016, at 5:30 AM, jaspreet singh <jaspreetsingh112@...> wrote:

Hi,

I am Jaspreet Singh, a final year Computer Science major at IIIT Hyderabad. I have successfully completed GSoC '14 and I am looking for a project to work on during summer 2017. I am interested in the project:Test Dashboard for Opendaylight. I deduce from the description that I don't have to pool every test while it's running but have to collect results and organise them neatly exploiting Spectrometer's offered framework for tables, charts and graphs. There are python API wrappers available to query the test-results of a completed build

It is a little more complicated, jenkins launches the test but the test results come from robot framework as a robot log or a CSV file, so you can effectively use the above tools to retrieve the test results but you still need to parse these results to a  data template (normally a json) to be stored in git or external DB. I updated the project description with this information.

Thanks for the update. As I understand, post-build scripting (I'll prefer python) can help collect, format and publish results to a database. I believe that the robot api will be helpful in playing with results including parsing the resulting files(output.xml etc.) and gathering run statistics out of them. There are ways of storing it in sqlite database which I can think of right now(using a defined schema). I'm not entirely sure how Spectrometer handles data apart from pulling all projects in a directory.

@spectrometer-devs Can you please explain briefly the datastore part of spectrometer.

I  wanted to get a more clear idea about the project,  it's scope and expected outcome. I have also pulled spectrometer's repo (https://github.com/opendaylight/spectrometer) (please confirm if this is the latest one) to take a look at it's code. Please suggest a beginner task/bug for me to complete to get to know the task.

Yes, this is the right spectrometer project. I will also ask you and other candidates to complete some small task before the selection, just wait for my mail.


Thanks

On Wed, Dec 7, 2016 at 6:54 PM, jaspreet singh <jaspreetsingh112@...> wrote:
Hi,

I am Jaspreet Singh, a final year Computer Science major at IIIT Hyderabad. I have successfully completed GSoC '14 and I am looking for a project to work on during summer 2017. I am interested in the project:Test Dashboard for Opendaylight. I deduce from the description that I don't have to pool every test while it's running but have to collect results and organise them neatly exploiting Spectrometer's offered framework for tables, charts and graphs. There are python API wrappers available to query the test-results of a completed build
https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+APII and other ways to do it in bash(https://coderwall.com/p/wwngfq/check-jenkins-for-build-status-via-a-shell-script) I wonder if we could use those. I wanted to get a more clear idea about the project,  it's scope and expected outcome. I have also pulled spectrometer's repo (https://github.com/opendaylight/spectrometer) (please confirm if this is the latest one) to take a look at it's code. Please suggest a beginner task/bug for me to complete to get to know the task.

Thanks
Jaspreet Singh


_______________________________________________
integration-dev mailing list
integration-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/integration-dev



jaspreet singh
 

Hi,

Please share a review on it. I've shared "suggesting mode" of doc above.
If need be, during the internship, I'll modify individual parts of my proposal to best serve the required purpose. 

Regards
Jaspreet

On Tue, Dec 27, 2016 at 2:29 AM, jaspreet singh <jaspreetsingh112@...> wrote:
Hi,

I've submitted a patch to spectrometer for review(here). I wanted to discuss further about the project to be able to write a proposal.

On Thu, Dec 8, 2016 at 7:49 AM, Luis Gomez <ecelgp@...> wrote:
Hi Jaspreet,  see my answers below:

On Dec 7, 2016, at 5:30 AM, jaspreet singh <jaspreetsingh112@...> wrote:

Hi,

I am Jaspreet Singh, a final year Computer Science major at IIIT Hyderabad. I have successfully completed GSoC '14 and I am looking for a project to work on during summer 2017. I am interested in the project:Test Dashboard for Opendaylight. I deduce from the description that I don't have to pool every test while it's running but have to collect results and organise them neatly exploiting Spectrometer's offered framework for tables, charts and graphs. There are python API wrappers available to query the test-results of a completed build

It is a little more complicated, jenkins launches the test but the test results come from robot framework as a robot log or a CSV file, so you can effectively use the above tools to retrieve the test results but you still need to parse these results to a  data template (normally a json) to be stored in git or external DB. I updated the project description with this information.

Thanks for the update. As I understand, post-build scripting (I'll prefer python) can help collect, format and publish results to a database. I believe that the robot api will be helpful in playing with results including parsing the resulting files(output.xml etc.) and gathering run statistics out of them. There are ways of storing it in sqlite database which I can think of right now(using a defined schema). I'm not entirely sure how Spectrometer handles data apart from pulling all projects in a directory.

@spectrometer-devs Can you please explain briefly the datastore part of spectrometer.

I  wanted to get a more clear idea about the project,  it's scope and expected outcome. I have also pulled spectrometer's repo (https://github.com/opendaylight/spectrometer) (please confirm if this is the latest one) to take a look at it's code. Please suggest a beginner task/bug for me to complete to get to know the task.

Yes, this is the right spectrometer project. I will also ask you and other candidates to complete some small task before the selection, just wait for my mail.


Thanks

On Wed, Dec 7, 2016 at 6:54 PM, jaspreet singh <jaspreetsingh112@...> wrote:
Hi,

I am Jaspreet Singh, a final year Computer Science major at IIIT Hyderabad. I have successfully completed GSoC '14 and I am looking for a project to work on during summer 2017. I am interested in the project:Test Dashboard for Opendaylight. I deduce from the description that I don't have to pool every test while it's running but have to collect results and organise them neatly exploiting Spectrometer's offered framework for tables, charts and graphs. There are python API wrappers available to query the test-results of a completed build
https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+APII and other ways to do it in bash(https://coderwall.com/p/wwngfq/check-jenkins-for-build-status-via-a-shell-script) I wonder if we could use those. I wanted to get a more clear idea about the project,  it's scope and expected outcome. I have also pulled spectrometer's repo (https://github.com/opendaylight/spectrometer) (please confirm if this is the latest one) to take a look at it's code. Please suggest a beginner task/bug for me to complete to get to know the task.

Thanks
Jaspreet Singh


_______________________________________________
integration-dev mailing list
integration-dev@...ight.org
https://lists.opendaylight.org/mailman/listinfo/integration-dev




Luis Gomez <ecelgp@...>
 

Hi Jaspreet, I just read the proposal and I think it is good high level so I do not have any comment at this point other than thanks for submitting this. I am sure we will find some problems on the road but we can also deal with them when they come.

BR/Luis

On Jan 5, 2017, at 11:39 AM, jaspreet singh <jaspreetsingh112@...> wrote:

Hi,

Please share a review on it. I've shared "suggesting mode" of doc above.
If need be, during the internship, I'll modify individual parts of my proposal to best serve the required purpose. 

Regards
Jaspreet

On Tue, Dec 27, 2016 at 2:29 AM, jaspreet singh <jaspreetsingh112@...> wrote:
Hi,

I've submitted a patch to spectrometer for review(here). I wanted to discuss further about the project to be able to write a proposal.

On Thu, Dec 8, 2016 at 7:49 AM, Luis Gomez <ecelgp@...> wrote:
Hi Jaspreet,  see my answers below:

On Dec 7, 2016, at 5:30 AM, jaspreet singh <jaspreetsingh112@...> wrote:

Hi,

I am Jaspreet Singh, a final year Computer Science major at IIIT Hyderabad. I have successfully completed GSoC '14 and I am looking for a project to work on during summer 2017. I am interested in the project:Test Dashboard for Opendaylight. I deduce from the description that I don't have to pool every test while it's running but have to collect results and organise them neatly exploiting Spectrometer's offered framework for tables, charts and graphs. There are python API wrappers available to query the test-results of a completed build

It is a little more complicated, jenkins launches the test but the test results come from robot framework as a robot log or a CSV file, so you can effectively use the above tools to retrieve the test results but you still need to parse these results to a  data template (normally a json) to be stored in git or external DB. I updated the project description with this information.

Thanks for the update. As I understand, post-build scripting (I'll prefer python) can help collect, format and publish results to a database. I believe that the robot api will be helpful in playing with results including parsing the resulting files(output.xml etc.) and gathering run statistics out of them. There are ways of storing it in sqlite database which I can think of right now(using a defined schema). I'm not entirely sure how Spectrometer handles data apart from pulling all projects in a directory.

@spectrometer-devs Can you please explain briefly the datastore part of spectrometer.

I  wanted to get a more clear idea about the project,  it's scope and expected outcome. I have also pulled spectrometer's repo (https://github.com/opendaylight/spectrometer) (please confirm if this is the latest one) to take a look at it's code. Please suggest a beginner task/bug for me to complete to get to know the task.

Yes, this is the right spectrometer project. I will also ask you and other candidates to complete some small task before the selection, just wait for my mail.


Thanks

On Wed, Dec 7, 2016 at 6:54 PM, jaspreet singh <jaspreetsingh112@...> wrote:
Hi,

I am Jaspreet Singh, a final year Computer Science major at IIIT Hyderabad. I have successfully completed GSoC '14 and I am looking for a project to work on during summer 2017. I am interested in the project:Test Dashboard for Opendaylight. I deduce from the description that I don't have to pool every test while it's running but have to collect results and organise them neatly exploiting Spectrometer's offered framework for tables, charts and graphs. There are python API wrappers available to query the test-results of a completed build
https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+APII and other ways to do it in bash(https://coderwall.com/p/wwngfq/check-jenkins-for-build-status-via-a-shell-script) I wonder if we could use those. I wanted to get a more clear idea about the project,  it's scope and expected outcome. I have also pulled spectrometer's repo (https://github.com/opendaylight/spectrometer) (please confirm if this is the latest one) to take a look at it's code. Please suggest a beginner task/bug for me to complete to get to know the task.

Thanks
Jaspreet Singh


_______________________________________________
integration-dev mailing list
integration-dev@...ight.org
https://lists.opendaylight.org/mailman/listinfo/integration-dev





jaspreet singh
 

Hi Luis,

Thanks for reviewing my proposal. Yeah, I am not sure about all the technical details right now, but I'm excited to explore as I go about doing the project and confident to figure out them during the course of the internship.

Regards
Jaspreet Singh

On Fri, Jan 6, 2017 at 11:09 PM, Luis Gomez <ecelgp@...> wrote:
Hi Jaspreet, I just read the proposal and I think it is good high level so I do not have any comment at this point other than thanks for submitting this. I am sure we will find some problems on the road but we can also deal with them when they come.

BR/Luis

On Jan 5, 2017, at 11:39 AM, jaspreet singh <jaspreetsingh112@...> wrote:

Hi,

Please share a review on it. I've shared "suggesting mode" of doc above.
If need be, during the internship, I'll modify individual parts of my proposal to best serve the required purpose. 

Regards
Jaspreet

On Tue, Dec 27, 2016 at 2:29 AM, jaspreet singh <jaspreetsingh112@...> wrote:
Hi,

I've submitted a patch to spectrometer for review(here). I wanted to discuss further about the project to be able to write a proposal.

On Thu, Dec 8, 2016 at 7:49 AM, Luis Gomez <ecelgp@...> wrote:
Hi Jaspreet,  see my answers below:

On Dec 7, 2016, at 5:30 AM, jaspreet singh <jaspreetsingh112@...> wrote:

Hi,

I am Jaspreet Singh, a final year Computer Science major at IIIT Hyderabad. I have successfully completed GSoC '14 and I am looking for a project to work on during summer 2017. I am interested in the project:Test Dashboard for Opendaylight. I deduce from the description that I don't have to pool every test while it's running but have to collect results and organise them neatly exploiting Spectrometer's offered framework for tables, charts and graphs. There are python API wrappers available to query the test-results of a completed build

It is a little more complicated, jenkins launches the test but the test results come from robot framework as a robot log or a CSV file, so you can effectively use the above tools to retrieve the test results but you still need to parse these results to a  data template (normally a json) to be stored in git or external DB. I updated the project description with this information.

Thanks for the update. As I understand, post-build scripting (I'll prefer python) can help collect, format and publish results to a database. I believe that the robot api will be helpful in playing with results including parsing the resulting files(output.xml etc.) and gathering run statistics out of them. There are ways of storing it in sqlite database which I can think of right now(using a defined schema). I'm not entirely sure how Spectrometer handles data apart from pulling all projects in a directory.

@spectrometer-devs Can you please explain briefly the datastore part of spectrometer.

I  wanted to get a more clear idea about the project,  it's scope and expected outcome. I have also pulled spectrometer's repo (https://github.com/opendaylight/spectrometer) (please confirm if this is the latest one) to take a look at it's code. Please suggest a beginner task/bug for me to complete to get to know the task.

Yes, this is the right spectrometer project. I will also ask you and other candidates to complete some small task before the selection, just wait for my mail.


Thanks

On Wed, Dec 7, 2016 at 6:54 PM, jaspreet singh <jaspreetsingh112@...> wrote:
Hi,

I am Jaspreet Singh, a final year Computer Science major at IIIT Hyderabad. I have successfully completed GSoC '14 and I am looking for a project to work on during summer 2017. I am interested in the project:Test Dashboard for Opendaylight. I deduce from the description that I don't have to pool every test while it's running but have to collect results and organise them neatly exploiting Spectrometer's offered framework for tables, charts and graphs. There are python API wrappers available to query the test-results of a completed build
https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+APII and other ways to do it in bash(https://coderwall.com/p/wwngfq/check-jenkins-for-build-status-via-a-shell-script) I wonder if we could use those. I wanted to get a more clear idea about the project,  it's scope and expected outcome. I have also pulled spectrometer's repo (https://github.com/opendaylight/spectrometer) (please confirm if this is the latest one) to take a look at it's code. Please suggest a beginner task/bug for me to complete to get to know the task.

Thanks
Jaspreet Singh


_______________________________________________
integration-dev mailing list
integration-dev@...ight.org
https://lists.opendaylight.org/mailman/listinfo/integration-dev