Hi Matthieu,
I think a CC-IN2P3 account is required to access Qserv cluster, isn't it?
Would it be possible, in a first time to access the build node from, by
order or importance:
- ccage.in2p3.fr
- LPC machines:
clrinfoport09.in2p3.fr
clrlsst-dbmaster-vm.in2p3.fr
clrlsstwn04.in2p3.fr
clrinfopc04.in2p3.fr
- SLAC visitor wireless network (while I'm at SLAC):
Destination Genmask
198.129.216.0 255.255.248.0
- SLAC machine:
lsst-db2.slac.stanford.edu
- NCSA machines:
lsst-sw.ncsa.illinois.edu
lsst-dbdev5.ncsa.illinois.edu
Maybe other member of the Qserv team want to provide some additional IP
adresses?
Thanks,
Fabrice
On 02/11/2015 01:41 AM, Mattieu Puel wrote:
> Hi Fabrice et all,
>
>> 1) a new qserv build / interactive machine with the following requirements:
>>
>> * SL7
>> * Public IP address. Note however that you will have to provide the IP adress of the clients (or a subnetwork @ SLAC) from which you plan to login to this build machine.
> could you please communicate the subnets from which you intend to
> initiate ssh connections to the build node ?
>
> Cheers,
>
>> * This machine will be used as the _only_ access point to the qserv cluster through SSH. If you need more interactive/build nodes, please let us know.
>> * password and kerberos (eg. principal: [log in to unmask]) authentications enabled.
>> * access to your AFS home directories (eg. /afs/in2p3.fr/home/f/fjammes).
>> * qserv local account (home directory: /home/qserv)
>> * sudo -u qserv enabled on this machine.
>> * SPS enabled.
>> * Screen package deployed on this machine.
>> * I guess that this machine will be used mainly to compile the qserv software, to check that the software is running correctly, and to generate RPMs. Anything else?
>
>
########################################################################
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
