Hello,
During our last Qserv meeting we decide to install scisql database
using non-root account, just after mysql has been installed.
But i've just discovered a new issue in doing that, indeed before
installing scisql, you have to launch :
$install_dir/bin/mysql_install_db
--defaults-file=$install_dir/etc/my.cnf --user=$prod_user
This command will use the datadir value of my.cnf file to
set the directory containing the mysql databases.
But, with eups, you can't set this datadir value, indeed, setting
this value is part of the configuration step, and not of the
install step, and that's why it isn't covered by eups features.
Nevertheless, it is not possible to fill scisql database if
mysql_install_db hasn't been runned yet , and so, with current
scisql install procedure, it is not possible to
install scisql at all. I think that mixing build/install and
configuration may give new issues of this kind.
Next proposal could work better, (furthermore it seems K.T. aggree
with it), but isn't doable now :
1. run "eups install qserv" and do, among other things, next tasks
:
- install mysql in $QSERV_INSTALL_DIR/Linux64/mysql/
- build scisql libscisql-scisql_0.3.so plugin file and install it
in $QSERV_INSTALL_DIR/Linux64/scisql/lib/mysql/plugin/
then run "setup scisql" which would then create next symlink :
ln -s $QSERV_INSTALL_DIR/Linux64/scisql/lib/mysql/plugin/
libscisql-scisql_0.3.so
$QSERV_INSTALL_DIR/Linux64/mysql/
Please note that symlink management aren't supported by eups for
now.
2. Configure Qserv, and do, among other things, next tasks :
- configure mysql : i.e. fill my.cnf with correct values
- run mysql_install_db
- create and fill scisql database.
Nevertheless, this procedure is quite complex, doesn't allow to
easilly remove scisql, and isn't completely supported at the
moment by eups.
That's why i propose that scisql is for now, fully installed
during Qserv configuration step, and isn't managed by eups.
So installing scisql would be part of mysql configuration step. It
seems reasonable as plugin installation may be considered as a
configuration step.
Would you agree this this ? Any other proposal is welcome.
Fabrice
On 01/06/2014 07:28 PM, Jacek Becla wrote:
[log in to unmask]"
type="cite">I'd not keep credentials in Zookeeper.
Let's discuss at the next meeting on Thursday.
Jacek
- 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.