[Discuss] broken link for globus-toolkit-repo-latest.noarch.rpm
Lisa Gerhardt
lgerhardt at lbl.gov
Wed Jul 10 20:38:57 CEST 2019
Hi Paul,
Thanks for the reply, that was what I was worried about. At our center
(NERSC at Lawrence Berkeley National Lab), we were previously relying on
the globus toolkit to supply globus-url-copy, globus-gridftp-server,
globus-job-run, etc. as well as Globus transfers. We need to upgrade to
Globus Connect Service v4, but we still want to support our users who
use grid based tools like xrootd, SPADE, and globus-url-copy. We have a
pool of 10 data transfer nodes, and right now it looks like we'll have
to split them up and run the GCT stack on one set and Globus on the
other (or change the default ports, which would make it hard for folks
to connect to us). Alternative suggestions are welcome.
Thanks,
Lisa
On 7/10/19 1:54 AM, Paul Millar via discuss wrote:
> Hi Lisa,
>
> On 09/07/2019 23:55, Lisa Gerhardt via discuss wrote:
>> A second question, has anyone had any experience installing these
>> packages on the same nodes as Globus Connect Service v4? I'm worried
>> there may be port clashes, etc. since these two software stacks are
>> so similar (for now).
>
> I think it is very likely that sites cannot run a GCT GridFTP server
> and Globus Connect Service on the same machine: both with try to
> listen on port 2811 -- at least, by default.
>
> It might be possible to configure one (or the other) to run on
> different ports. I believe most grid software should work with URLs
> where the port number is mentioned explicitly.
>
> Incidentally, are you aware of sites that want to deploy both services?
>
> Cheers,
>
> Paul.
> _______________________________________________
> discuss mailing list
> discuss at gridcf.org
> https://mailman.egi.eu/mailman/listinfo/discuss
More information about the discuss
mailing list