1 RPC 8: OST CONNECT - Client connection to an OST
2 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5 When a client initiates a connection to a specific target on an OSS,
6 it does so via an OST_CONNECT RPC ('pb_oc' = 8). From a previous
7 interaction with the MGS the client knows the UUID of the target OST,
8 and can fill that value into the 'obd_connect_client' message.
10 .OST_CONNECT Generic Packet Structure
11 image::ost-connect-generic.png["OST_CONNECT Generic Packet Structure",height=100]
13 //////////////////////////////////////////////////////////////////////
14 The ost-connect-generic.png diagram resembles this text art:
17 --request--------------------------------------------
18 | ptlrpc_body | obd_uuid | obd_uuid | lustre_handle |
19 -----------------------------------------------------
22 --reply---------------------------
23 | ptlrpc_body | obd_connect_data |
24 ----------------------------------
25 //////////////////////////////////////////////////////////////////////
31 UUIDs of the target (first) and client (second) entities. See
35 See <<struct-lustre-handle>>.
38 See <<struct-obd-connect-data>>.
40 In the OST_CONNECT RPC reply from the server the 'ptlrpc_body' field
41 'pb__handle' is set to uniquely identify the connection for subsequent
42 communication. The client notes that handle in its import for the