https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-17166 Lustre <p>It appears that there was no rule added for NRS TBF to allow selecting the project ID for an RPC.</p> LU-17166

add TBF rule for projid

Improvement Minor Open Unresolved Etienne Aujames Andreas Dilger easy Wed, 4 Oct 2023 13:20:50 +0000 Tue, 10 Oct 2023 09:06:31 +0000 0 5 <p>YES! Would be great to have. We're interested to use this on a system instead of NRS TBF GID.</p> <p><a href="https://jira.whamcloud.com/secure/ViewProfile.jspa?name=sthiell" class="user-hover" rel="sthiell">sthiell</a>, contributions are of course welcome. I don't think this would be more than a cargo-cult copying of the uid/gid/jobid functionality that already exists, so likely very low complexity. </p> <p>Hi Andreas,</p> <p>projid is not in every RPCs (present in mdt_body but for the OSTs this used in quota requests only), so we can use a free field in ptlrpc_body (e.g: pb_padding64_1) to tag the requests and add a new compatibility flag.<br/> And unlike for uid/gid, we can not take the ids of the process because project id is only an attr. I think we can access to the projid via the inode information on the clients: (struct ll_inode_info *) -&gt;lli_projid</p> <p>The <tt>struct obdo::o_projid</tt> field should be included in almost every OST RPC? I could imagine that there may be cases where it is not set by the client, but that can be fixed in the client. </p> <p>Ok, that should work for ost_io service.<br/> For now, o_projid is set only for write request, but we can modify the client to send it for write and read.<br/> So for now, we could restrict the development to ost_io (that should be easy).<br/> But for ost and mdt services, that should require more work on the client to include projid in the requests.</p> Related LU-9658 Development Rank 1|i03xgv: Rank (Obsolete) 9223372036854775807 Severity