Add Lustre Layout documentation to Storage Profile #174
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds documentation for the Lustre layout fields in the NnfStorageProfile. Signed-off-by: Matt Richerson <[email protected]>
| @@ -232,6 +232,55 @@ data: | |||
| [...] | |||
| ``` | |||
|
|
|||
| ### Target Layout | |||
|
|
|||
| Users may want Lustre file systems with different performance characteristics. For example, a user job with a single compute node accessing the Lustre file system would see acceptable performance from a single OSS. A FPP workload might want as many OSSs as posible to avoid contention. | |||
There was a problem hiding this comment.
Suggested change
| Users may want Lustre file systems with different performance characteristics. For example, a user job with a single compute node accessing the Lustre file system would see acceptable performance from a single OSS. A FPP workload might want as many OSSs as posible to avoid contention. | |
| Users may want Lustre file systems with different performance characteristics. For example, a user job with a single compute node accessing the Lustre file system would see acceptable performance from a single OSS. An FPP workload might want as many OSSs as possible to avoid contention. |
bdevcich
reviewed
Jul 2, 2024
|
|
||
| Only one of `scale` and `count` can be set for a particular target type. | ||
|
|
||
| The `DirectiveBreakdown` for "create_persistent" #DWs won't include the constraint from `colocateCompute=true` since there may not be any compute nodes associated with the job. |
There was a problem hiding this comment.
Suggested change
| The `DirectiveBreakdown` for "create_persistent" #DWs won't include the constraint from `colocateCompute=true` since there may not be any compute nodes associated with the job. | |
| The `DirectiveBreakdown` for `create_persistent` #DWs won't include the constraint from `colocateCompute=true` since there may not be any compute nodes associated with the job. |
You wrap create_presistent in backticks below, so it makes sense to be consistent here
bdevcich
reviewed
Jul 2, 2024
|
|
||
| `colocatedComputes=false` may be useful for placing MDTs on NNF nodes without an OST (within the same file system). | ||
|
|
||
| The `count` fields may be useful when creating a persistent file system since the job with the `create_persistent` directive may only have a single compute node. |
bdevcich
approved these changes
Jul 2, 2024
roehrich-hpe
approved these changes
Jul 2, 2024
Signed-off-by: Matt Richerson <[email protected]>
ajfloeder
approved these changes
Jul 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds documentation for the Lustre layout fields in the NnfStorageProfile.