Skip to main content

Week 7 :- CERN-HSF @ GSoC 2018

This week, I worked on separating Job Status(s) from the common Jobs table (long overdue, I think for a year).

As I wrote previously, not all values linked to a JobID are not really accessed in the day to day functions of the DIRACGrid project. Last time, Job Attributes were shifted to ES backend for accessing it with similar efficiency as Job Parameters. For Job Status, a new table has been created keeping MySQL backend with the following entities:

  • JobID (primary key)
  • Status
  • Minor Status
  • Application Status
So, along with shifting the values to the new table (JobsStatus), functions are modified/added to access (read/write) the table:
  • "setJobStatus": The existing function is modified to write in the new table.
  • "getJobStatus": The new function has been added to access values in the new table. Along with this, it keeps back support to access the values that were already written in the Jobs table.
Commits related to the work can be found below:
Labels:

Comments

Post a Comment

Popular posts from this blog

Week 10 :- CERN-HSF @ GSoC 2018

This week, I started with the work that was optional and beyond the scope of the work as per the proposal. I started adapting the codes I modified or wrote for simultaneous support for Python2 and Python3. This needed first going through the guides which explain the porting process as well as following the guides as prescribed by the LHC project at CERN. I used the python-modernize library which supported this modification along with keeping the original support. Using this module, I modified most of the files involving ElasticSearch support as well as some of the codes I introduced/modified as part of the earlier works described in various posts of the blog. The series of commits can be found in Pull Request 3765 . Note: The work still needs to incorporate due to various other issues in automatic porting methods.
Post a Comment
Read more

Week 9 :- CERN-HSF @ GSoC 2018

This week I was involved with working on Pull Request 3744  where some changes were demanded by other members of the organization as per the requirements of other components of the project. Firstly, as we moved towards adding a Jobs Status table (discussed in another post of the blog), which has eased and increased efficiency for query processing, we need to take care of the modules that accessed that table during any of there functions. Hence, it became important to analyze and test every module available in the Workload Management System as well as other modules that are accessing the table. A string of commits can be found below for the work done during this week: 0b1a63594eec932c12669d3274d5da705d9e2ffb fdda6f1fa473f866f0b552b838761f1201bc3c5b All the commits related to this issue can be found in this Pull Request .
Post a Comment
Read more

My GSoC experience with CERN-HSF, Summer 2018

The Google Summer of Code (GSoC) program is one of the most prestigious programs for student developers, who are eager to work and demonstrate their skills in a full-fledged working environment. The program gives this opportunity to students all around the world and I feel good that I was selected for this program with the CERN-HSF organization, one of the pioneer organizations for nuclear research. My experience started before the GSoC program, with the first contact with the current mentor, Federico Stagni where we discussed the proposed project and my suitability for it by performing some tasks that are available here . Based on performance and my timelines, I submitted my proposal which went through multiple revisions with inputs from my mentor Federico and self-improvements. Finally, almost after a month of wait, students selected for GSoC 2018's program were announced and found myself fortunate to be selected with the following project with CERN-HSF:-  Monitoring and...
1 comment
Read more