 |
 |
I created a ticket related to configuring qserv ports: https://dev.lsstcorp.org/trac/ticket/2767 Not sure if is best to assign to Douglas or Fabrice. It belongs to Douglas right now, I hope you will sort it out who implements it. Thanks, Jacek On 03/27/2013 04:02 AM, Fabrice Jammes wrote: > Hello Jacek, > > Thanks for this proposal, I thinks it would be an excellent idea and > would ease continuous integration of Qserv. > > Tests are now working quite well but i still need to merge branch 2014 > in the master branch. > I will do it as soon as it is integrated well with unittest and scons. > Some jobs still remains. > > Then you proposal could be done quite easily, maybe in a new ticket ? > > W13 data are loaded in branch 2014 (with 10 stripes and substripes we > only get one chunk, could Douglas please gave us the partitioning > parameters neede to get 2 chunks), and some queries success, > but we still have to do some job to automated "partitionned" views > creation. This will be done in the W13 loading associated ticket. > We have not studied very well meta-data integration but we will do that > as soon as possible, we're very interested. > > Do we have a meeting tomorow ? Next week would be better for us. > > Thanks in advance for your answer, > > Fabrice > > > > On 03/27/2013 05:30 AM, Jacek Becla wrote: >> How about using adjacent numbers for ports for a given >> qserv installation. I am looking at an installation on >> lsst-db2 (W13_1K), and it is using: >> >> 7123 mysql >> 5040 proxy >> 2094 xrootd >> 2131 xrootd manager >> >> How about if we required that qserv needs say 10 adjacent >> port numbers (just to be safe), and we could fix the >> numbers to daemons, something like >> >> xxx1 mysql >> xxx2 proxy >> xxx3 xrootd >> xxx4 xrootd manager >> >> If we did that, we could even get away with defining >> just one "base" number somewhere in a central config >> file, and all other ports could be automatically derived. >> >> 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 > ######################################################################## 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