Print

---

SLAC Meeting :

• DWG and DSH can receive FJS and EMH at SLAC after the 01/14/2013 for a couple of day.
• FJS and EMH are working on a program for each day, it will be send next week, DWG and DSH will improve and agree to this program.
  • Improve knowledge of Qserv architecture, be able to easily indentify most current problems
  • Solve current blocking points :
    • runtTest.py fails,
    •  ???
  • Improve knowledge on code philosophy, particurlarly on new refactored code. How could we help ?
  • Discuss about other backend than MySQL, particurlarly on MonetDB integration
  • Hardware considerations and recommandations, advice about the CC-IN2P3 platform, would Cloud-Computing be interesting for new releases testing ?
  • Integration with existing tools to manage and supervise numerous workers (Puppet, Quattor, Chef, CFEngine, EC2 api, ...)

ticket/2416

• DSH is going to review the code committed by FJS and EMH in order to merge it in the master branch.
• Commit policy : can we commit soon, or not commit, and implements required features in a new ticket, related to scons, some jobs has already be done in this direction.

Scons and automated installation

• FJS and EMH are working on a distributed install process, using scons. DSH and DWG agree to that
• Define implemented features list and maintenance procedure :

Features :

DONE :

• Easier and documented install procedure
• Use of Scons
• A general and unique configuration file can be use to configure the whole application in mono-node (multi node to be done)
  • Data/log/binary can be separated on different partitions
  • TCP port can be changed
  • MySQL password management
  • automated procedure for PT1.1 Object data loading
  • automated procedure for PT1.1 meta generation

TODO :

• could be easilly generalized to PT1.1 Source table, and to other data-set
• runTests.py doesn't work. It could be completed with other tests related to PT1.1.
• Commit in the master branch

Maintenance contract :

The workflow could be the next :

The french team can adapt and validate this procedure for next Qserv official release, with the help of Qserv developpers. Furthermore, the french team proposes to insure maintenance on this installation procedure, for next Qserv official release, on a bi-node architecture. So, if system administrators encounter problems during installation of this release, the french team will help them to install it and to run tests.

For Qserv futures releases, the french team is very interested to continue to maintain and integrate this installation procedure, but they'll first do a serious study in order to define if this commitment can be respected depending on their manpower, and on complexity of source code evolution.

Remark : The quality of the procedure will be leveraged it will be easy to maintain.

Meta loading

- DSH is going to send a mail explaining of to load qserv meta. FJS and EMH are going to test this, and then try to automate it.

• Seems to work, but :

 mysql> select * from Object where objectid=402395485975435;
 Empty set (4.71 sec)
 mysql> select * from Object where objectid like '402395485975435';
 work fine 

Code refactoring

- DWG is working on a new version of qserv which will be more modular and will allow FJS and EMH to propose their help on qserv core.

Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1