Daniel email should also be taken in account :

FYI, for those trying to do the disconnected installation there are a couple things to note.

I'm following the directions as noted here:

http://lsst-web.ncsa.illinois.edu/~fjammes/qserv-doc/2014_09.0/install/internet-free.html

* Before the instructions on that page can work, you need to prepare the tarball as described in:

http://lsst-web.ncsa.illinois.edu/~fjammes/qserv-doc/2014_09.0/devel/package-internet-free-distserver.html

(Fabrice kindly offered to generate it, but I think it's a bit much to ask him to generate it each time.)

* Corrections are needed in order for newinstall.sh to work. (FYI, newinstall.sh is located in the distserver tarball: distserver/production/newinstall.sh that was generated by tarring up distserver/ populated by following the steps in the second link)

** pkgroot needs to point at "production subdirectory"

export EUPS_PKGROOT=$NEWINSTALL_URL/production

** EUPS_GITREPO and EUPS_GITREV need to be set before calling newinstall.sh, otherwise it will try curl'ing from Mario's github.

EUPS_GITREPO=$NEWINSTALL_URL/eups.git EUPS_GITREV=master sh newinstall.sh

I think the instructions work after that. I'm currently trying "eups distrib install qserv", which looks productive so far.

Have a nice day,

-Daniel

Please note that ssh://git@git.lsstcorp.org/LSST/DMS/devenv/lsst has also a u/fjammes/DM-1258 branch.

First, please note that this documentation is related to Qserv 2014_09.0 version, which is not published on distribution server (see DM-1314).

Doc is available here :
http://lsst-web.ncsa.illinois.edu/~fjammes/qserv-doc/

Please note that i've removed documentation for previous versions, which where using my own distribution server (http://lsst-web.ncsa.illinois.edu/~fjammes/qserv/). Indeed, I no more maintain this distribution server.

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.

Thanks,

Fabrice

Hi Fabrice,

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.

Cheers,
Andy

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 DM-1363.

Hi Jacek,

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.

Cheers,

Fabrice