Hi Matthieur,
It works fine now.
I have some issues but I'll put them in OTRS tickets, it will be simpler.
Thanks,
Fabrice
On 02/19/2015 11:02 AM, Dominique Boutigny wrote:
>
>
>
> -------- Forwarded Message --------
> Subject: Re: [QSERV-L] Requirements
> Date: Tue, 17 Feb 2015 09:48:37 +0100
> From: Mattieu Puel <[log in to unmask]>
> To: Fabrice Jammes <[log in to unmask]>
> CC: Fabrice Jammes <[log in to unmask]>, Yvan Calas
> <[log in to unmask]>, [log in to unmask] <[log in to unmask]>,
> qserv-l <[log in to unmask]>
>
>
>
> Fabrice Jammes>
> > Hi Matthieu and Yvan,
> >
> > On our side we're ready to play with the cluster. Can we ssh Qserv
> > build node? If yes, can you please confirm me its name is ccqserv100
> > and give me the ssh options (-K)?
>
> All should be in place on our side also, please check that you are able to
> connect to ccqservbuild (it's not a machine of the cluster). From there,
> you can ssh to the nodes: ccqserv{100..124}.
>
> For the connection, you can use either your password or your krb5 ticket
> seamlessly.
>
> Cheers,
>
> > Thanks,
> >
> > Fabrice
> >
> >
> > Le 13/02/2015 14:53, Daniel L. Wang a écrit :
> > >Would it be too much to add the internal SLAC subnet? Only
> > >SLAC-owned machines (or SLAC users through VPN) can be on this
> > >subnet: 134.79.0.0/16 . SLAC desktops/workstations/servers will be
> > >in this subnet, and it might be easier to manage than a bunch of
> > >single IPs.
> > >
> > >Thanks,
> > >-Daniel
> > >
> > >On 02/12/2015 01:00 PM, Jacek Becla wrote:
> > >>Would it be a problem to add the 6 machines we use at ncsa?
> > >>
> > >> lsst-dbdev1.ncsa.illinois.edu (141.142.237.33)
> > >> lsst-dbdev2.ncsa.illinois.edu (141.142.237.34)
> > >> lsst-dbdev3.ncsa.illinois.edu (141.142.237.35)
> > >> lsst-dbdev4.ncsa.illinois.edu (141.142.237.36)
> > >> lsst-dbdev5.ncsa.illinois.edu (141.142.237.37)
> > >> lsst-dbdev6.ncsa.illinois.edu (141.142.237.38)
> > >>
> > >>(only ncsa admin and the qserv team has login there)
> > >>
> > >>Jacek
> > >>
> > >>
> > >>On 02/12/2015 11:07 AM, Fabrice Jammes wrote:
> > >>>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
> > >>
> > >>########################################################################
> > >>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
> > >
> >
>
> --
> Mattieu Puel
> Sysadmins team manager
> IN2P3 Computing Centre
> http://cc.in2p3.fr
> +33 (0)4 78 93 08 80
>
>
########################################################################
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
