[LUDOC-366] Document NRS Delay

• Status: Resolved
• Project: Lustre Documentation
• Type: New Feature
• Priority: Minor
• Reporter: Chris Horn
• Assignee: Chris Horn
• Resolution: Fixed

Description

NRS Delay is a new feature slated for Lustre 2.10. It probably does not need extensive documentation because it is intended for use in development and testing, however we should probably at least document how it can be configured via the lctl command.

The commit comment for the patch contains a number of examples. Patch is here https://review.whamcloud.com/#/c/14701

The development ticket is LU-6283

Issue Links

• is related to: LU-6283 NRS Delay Policy

Comments

[Peter Jones]

Chris

Could you please provide a patch to cover the explanation of how this feature works for the manual? If it is problematic for you to work out the syntax for the formatting then please just attach a text file and we can find someone to help with the formatting aspect

Thanks

Peter

[Chris Horn]

Yes, I'll provide a patch

[Gerrit Updater]

Chris Horn ([e-mail]) uploaded a new patch: https://review.whamcloud.com/27501
Subject: LUDOC-366 nrs: Add delay policy document
Project: doc/manual
Branch: master
Current Patch Set: 1
Commit: 05202973255b4f2d4a75238012bf2730d54a82e5

[Gerrit Updater]

Andreas Dilger ([e-mail]) merged in patch https://review.whamcloud.com/27501/
Subject: LUDOC-366 nrs: Add delay policy document
Project: doc/manual
Branch: master
Current Patch Set:
Commit: be36f62196439346aada3008072120a54d59e4a3

[Colin Faber [X] (Inactive)]

Hi,

Can we get some attention here? This has been lingering for quite a while and appears ready to land..

[Peter Jones]

Wrong ticket?

[Colin Faber [X] (Inactive)]

I'm looking at the last activity here, it's been stale since '17 and this work was long ago completed.

[Peter Jones]

Could you please be more specific? The above change looks like it landed a couple of years ago. The ticket is marked as RESOLVED. What else are you expecting to happen.

[Colin Faber [X] (Inactive)]

This is in regards to resolved vs closed. so you can ignore. I now understand that for you guys, resolved is a closed state that you all utilize. We generally mark bugs "closed" once they land as "resolved" would mean, work is complete, landing is happening and once landed it will be transitioned into closed. We utilize labels to keep track of which branches it's landing into and which branches are requested for it.

 

Cheers.