Attendees: Bill, AndyH, AndyS, Daniel, Fabrice, Serge, Jacek
Round table status
==================
Jacek
- xldb-healthcare fires
- DMLT meeting
- prepared outstanding (big) tickets for merging
AndyH
- looking at HDFS
AndyS
- put together working recipe how to setup dev env, see DM-228
- debugging qserv build system
- issues found, see DM-546
- problem related to bug in SCons.Scanner
- workaround: re-implement scanner?
- not worth doing just for Qserv, but perhaps
might be worth doing for lsst dm?
Bill
- finalizing logging (exposed state, removed diagnostics context)
- looking at packaging logging
- first feedback from RHL (Seattle information discussions)
- would be nice to reconfigure logging interactively
- Bill thinks it is not hard
- would be nice to have more debug levels
- but incompatible with standard python logging
- rhl will check logging docs and code and will get back
to us with full comments shortly
- next task after logging?
- integrating with new xrootd client, or rearchitecting dependencies
- former better defined, so better
Daniel
- joined syntax: code tested, reviewed. Found & fixed
(non trivial) problems when running final tests
- Serge reviewing
- xrd client next
Fabrice
- improved init.d, in good shape, close to being
fully Linux-standard compliant
- tweaks to packaging zoo/kazoo/db
- need input about client/css structure, see DM-58
1) client
- current client = an admin client, it depend on kazoo
- long term, want client for users with no dependency
on kazoo
--> move current client to admin
- do at dev week, after CSS code pushed to master
2) watcher
- it is for managing qserv node
--> rename to "caretaker"
- we need a place (new module) for that
--> discuss at dev week
Serge
- mostly non-lsst work
- need to talk w/Daniel, next week. Topics:
- separate plugin vs extending existing table plugin
- how smart should we be about recognizing refmatch join
Merging for qserv release
=========================
1) Serge: review latest patch
2) Daniel: push code
3) Jacek: push code
* Fabrice code is independent, any time
FYIs
=====
- we need to start using sprints for real
- we should play with / start using hipchat
- both sprints and hipchat will be discussed
in more details next week at dev week
Goals for the dev meeting we have all next week
================================================
1) Qserv software that can be downloaded, built, installed,
configured, started and tested by a non-Qserv-expert, with
accompanying instructions. It is OK if some things are hacked,
not finished, not fully working and not in ideal state.
2) A plan for May-Aug (in a form of defined sprints) that
will get us to Qserv software that can be downloaded, built,
installed, configured, started and tested by a non-Qserv-expert,
with accompanying instructions WITHOUT hacks.
Question:
- is "easy configure/load data" part of the S14 deliverable?
--> discuss next week
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
|