Fabrice,

> scisql require a running MySQL instance in order to be installed.
> Indeed, it will insert stored procedures, contained in sql scripts,
> in MySQL.
> Nevertheless, eups procedure only build and install MySQL, but
> doesn't configure it.
> Indeed, MySQL configuration should be done during Qserv
> configuration procedure, and so once eups procedure is finished.
> 
> That's why it's currently not possible to launch scisql install
> procedure in eups.
> 
> Here's three proposals which could solve this issue :
> 
> - divide scisql install procedure in two phase : a build/install
> step managed by eups (for UDF) and a configuration step managed by
> Qserv configuration procedure (for SQL scripts and tests).

	I think this is correct.  Installing any code, including MySQL
server and the scisql shared libraries, should involve building it and
placing it in an installed location.  But starting a server should not
be an installation task; it should be a separate configuration and
startup task.

> - install zookeeper before scisql, and fill zookeeper with bootstrap
> informations (like MySQL credentials, and datadir) during its own
> installation,

	I don't think Zookeeper is a secure location for MySQL
credentials, but I may be wrong.

-- 
Kian-Tat Lim, LSST Data Management, [log in to unmask]

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