Attendees: AndyS, Serge, Fabrice, AndyH, Bill, Daniel, Jacek


Agenda:
  - round table status report
  - post 3/15/2014 Qserv activities



round table status report
=========================

Serge
  - wrapping up WISE work, will be done this week
  - SciDB tests and LSST next


Jacek
  - MariaDB (Aria/MyISAM tests)
    https://dev.lsstcorp.org/trac/wiki/db/tests/MySql/AriaVsMyISAM
    - suggestion: wait until "10.0.8 release candidate" will become
      an official release, then switch (just Qserv), then when it
      becomes "stable" release, switch lsst10.
  - revisited all W14 tasks
  - work on 2 XLDB workshops


Bill
  - have all environment set up based on new qserv,
    in some places hacked old Douglas' config/startup scripts
    - document on trac
    - clean and commit the fixes
  - discussion: ideally would like logging prototype in
    separate package, but setting up no trivial, mostly
    because of swig, so for now continue using a qserv branch


Daniel
  - most time spent on join syntax, have draft implementation,
    hopefully will have it working this week, then need feedback
    from Serge about api
  - tweaks to xldb report


AndyH
  - new xrootd client 80% done, on track to deliver by 3/31
  - getting busy (cern trip, organizing workshop)


Fabrice
  - need to integrate install system (done by Fabrice) with
    build system (done by Daniel)
    - Daniel is going to pull Fabrice's proposed code for
      custom.py into the build system
    - Daniel will implement "prefix", need to open ticket for it.
  - phone call Monday 1pm pacific (Daniel/Fabrice/AndyS/Jacek)
    to discuss install/build integration


AndyS
  - talked to Daniel about build system


post 3/15/2014 Qserv activities (extracted from pmcs)
=====================================================

finish before 3/15:
  * downselect db technology
  * Write XLDB 2013 report
  * New XRootD RPC interface implementation, --> split, open new
    task "test" 3/16-3/31
  * Qserv design: distributed metadata/state
  * Qserv: query representation
     --> join syntax work is part of that, but we also wanted
      to do cleanup Serge suggested, open new task for S14
  * Qserv design: data ingest and loading, serge will look
  * Qserv: Logging (software API)
  * Qserv: packaging, build install yes, but config in S14
  * Qserv documentation
  * W14 database tune up


move to S14:
  * Integrating Ref*Match into qserv
  * Develop new master-worker result system
  * Plug in new xrootd client
  * Qserv: setup new cluster at IN2P3 for continuous integration/testing
    --> check with Dominique when hardware arrives [Jacek]
  * MySQL wrapper


delete:
  * Prepare to deploy qserv for small number of users (~10)
  * Qserv: User-friendly communication (syntax support)


others:
  * Data ingest from pipeline – code refurbishing
    - not sure if there is enough interest from Apps Team,
     --> check with Mario/K-T [Jacek]

  * Qserv: Logging (distributed log collection)
    - perhaps NCSA could take lead on that?

  * Qserv: automated testbed
  * Qserv: setup infrastructure for continuous integration
    - this heavily depends on config script
    - config scripts need major refresh
      --> move to S14

  * Qserv: unit testing (controller module)
    - this is not just about adding unit tests, but
      need to understand  how to do unit tests,
      eg, build dummy version of the whole world
      that controller controls?
    --> move to S14

  * Qserv: unit testing (query execution)
    --> maybe S14

  * Qserv: unit testing (admin/loading)
   - think about it when planning S14

Jacek

########################################################################
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