[LUDOC-221] Document Token Bucket Filter (TBF) NRS policy

• Status: Closed
• Project: Lustre Documentation
• Type: New Feature
• Priority: Blocker
• Reporter: Andreas Dilger
• Assignee: Jodi Levi (Inactive)
• Resolution: Fixed
• Labels: releases

Description

Document the TBF NRS policy for the feature added in LU-3558.

Issue Links

• is related to: LU-3558 NRS TBF policy for QoS purposes
• is related to: LUDOC-328 documentation updates for complex TBF...

Comments

[Li Xi (Inactive)]

The attachment is the document for TBF.

I'd really appriciate it if some one can give me a brief introduction about how to add a manual patch. What I need to do? Thanks!

[Andreas Dilger]

Please see https://wiki.hpdd.intel.com/display/PUB/Making+changes+to+the+Lustre+Manual

Hopefully that will get you started. If the page is lacking in detail, please ask further questions and/or update the page, since it is difficult for us to know what information is lacking.

[Li Xi (Inactive)]

Hi Andreas,

Thank you very much! I will start working on it.

[Andreas Dilger]

Li Xi, is there any progress on adding this documentation to the manual? Is there someone else at DDN/Clogeny that could help you with this effort?

[Li Xi (Inactive)]

Hi Andreas, we've push a manual patch a month ago. Sorry, we didn't post a comment here. Please let us know if there is anything else we need to do.

http://review.whamcloud.com/#/c/11302/

[Malcolm Cowe (Inactive)]

Can the jobid be wildcarded? e.g. *:<uid>.

[Li Xi (Inactive)]

Nope, a rule is matched by comparing the exact string of jobid. But it is allowed to set multiple jobid for each rule. And it is not hard to add extension if wildcards are necessary. nrs_tbf_jobid_list_match() is the function that we need to change.

[Malcolm Cowe (Inactive)]

Thanks. I thought that might be the answer . I was talking to someone the other day about managing resources at a per-user or per project / group level and I wanted to make sure I understood the TBF feature before I made any further reply .