1 / 8

Intro to GridFTP

John Bresnahan. Intro to GridFTP. Components. Control Channel (CC) Path between client and server used to exchange all information needed to establish data channels Data Channel (DC) The network pathway over which the 'files' flow Control Channel Interpreter (CCI)

toril
Download Presentation

Intro to GridFTP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. John Bresnahan Intro to GridFTP

  2. Components • Control Channel (CC) • Path between client and server used to exchange all information needed to establish data channels • Data Channel (DC) • The network pathway over which the 'files' flow • Control Channel Interpreter (CCI) • Often AKA: Fronted (but ignore that for now) • Server side implementation of the control channel functionality • Data Protocol Interpreter (DPI) • Handles the actual transferring of files • Often AKA: Backend (but ignore that too) • Client • Client side implementation of the control channel functionality CCI DPI Client

  3. CC DC Simple Two Party Transfer • Clear boxes represent process spaces • The Server Side • CCI and DPI are co-located in the same process space • The Client Side • Client and DPI are co-located in the same process • Interaction • The client connects forms a CC with the server • Information is exchanged to establish the DC • A file is transfered over the DC CCI DPI Client DPI

  4. CC DC CC Simple Third Party Transfer • Client forms CC with 2 servers. • Information is Exchanged to establish DC between the two servers. • Data flows directly between servers • The two party case is really just a special case of this. In the two party case the client IS a server (in a sense), however since it has the DPI in the same process space it does not have to form a formal CC. Instead it simply sets everything up via function calls etc. CCI DPI Client CCI DPI

  5. IPC CC DC CC IPC Separated Third Party Transfer • Same interactions as 3PT • The difference is that the CCI and the DPI are no longer in the same process space • A proprietary protocol (IPC) is used to control the DPI. CCI DPI Client CCI DPI

  6. IPC CC IPC IPC DC Proxy • The separation of processes buys the ability to proxy • Many DPIs that the CCI can choose for any given transfer • Allows for load balancing DPI CCI Client DPI DPI DPI

  7. IPC IPC IPC IPC CC DC DC DC DC CC IPC IPC IPC IPC IPC Striping CCI DPI DPI DPI DPI Client CCI DPI DPI DPI DPI

  8. Striping • A coordinated multi-host transfer • 1 CCI per server • Many DPIs per CCI • Each DPI does a partial file transfer • Allows for fast transfers • Can be M to N

More Related