[gpfsug-discuss] GPFS Routers

[Marc A Kaplan]

Perhaps if you clearly describe what equipment and connections you have in 
place and what you're trying to accomplish, someone on this board can 
propose a solution.

In principle, it's always possible to insert proxies/routers to "fake" any 
two endpoints into "believing" they are communicating directly.





From:   Aaron Knister <aaron.s.knister at nasa.gov>
To:     <gpfsug-discuss at spectrumscale.org>
Date:   09/11/2016 08:01 PM
Subject:        Re: [gpfsug-discuss] GPFS Routers
Sent by:        gpfsug-discuss-bounces at spectrumscale.org



After some googling around, I wonder if perhaps what I'm thinking of was 
an I/O forwarding layer that I understood was being developed for x86_64 
type machines rather than some type of GPFS protocol router or proxy.

-Aaron

On 9/11/16 5:02 PM, Knister, Aaron S. (GSFC-606.2)[COMPUTER SCIENCE 
CORP] wrote:
> Hi Everyone,
>
> A while back I seem to recall hearing about a mechanism being developed
> that would function similarly to Lustre's LNET routers and effectively
> allow a single set of NSD servers to talk to multiple RDMA fabrics
> without requiring the NSD servers to have infiniband interfaces on each
> RDMA fabric. Rather, one would have a set of GPFS gateway nodes on each
> fabric that would in effect proxy the RDMA requests to the NSD server.
> Does anyone know what I'm talking about? Just curious if it's still on
> the roadmap.
>
> -Aaron
>
>
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
>

-- 
Aaron Knister
NASA Center for Climate Simulation (Code 606.2)
Goddard Space Flight Center
(301) 286-2776
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160912/e03e6ab0/attachment-0002.htm>