Fix Version/s: Summer 2014
Team:Data Access and Database
Creation of qserv_distrib and distribution of Qserv via official LSST repositories have to be taken into account in Qserv documentation and automatic install script.
I tested instructions in "Quick start guide", everything works perfectly.
One thing that I noticed when i ran qserv-configure.py is that you also install ~/.my.cnf file. Why is that needed? I think we should avoid generating per-user configuration files if possible, especially for things that we do not own (mysql).
Quick question about eups tags (still trying to learn eups) - if I install qserv_distrib with tag qserv and then you publish new version on a distrib server and move qserv tag to that new version, will my local installation be updated next time I try to install qserv_distrib with the same tag qserv (which already exists in my local stack)?
Review complete, removing myself.
I agree that generating ~/.my.cnf is bad form. If such a file is required, instructions on how to create it should be printed for the user. If this is the mechanism for worker database access, we should rethink how this is done.
The distribution server tag is consulted each time eups distrib install -t tag is executed. So moving the qserv tag (or stable or beta or whatever) on the distribution server does cause updates on reinstallation.
About the ~/.my.cnf issue, i've created
I wanted a review of AndyS, OR you. But JIRA only allow 'AND' between reviewers. Andy review looks fine, that's why I think it is reasonable to mark this ticket as reviewed. Sorry for this misundestanding.
Hi Andy Salnikov,
Documentation is now testable as qserv_distrib is now published on LSST distribution server. Could you review it please?
Please note that we should merge this ticket to master before tagging and publishing 2014_09.0, so that the documentation is compliant with the Qserv code.