Outline the proposed title of this feature request.
Provide a way to configure mclock at install time{}
What is the nature and problem description of the request?
OSD bench tool for ssd is too low (80K) for new hardware leading to inconsistent configuration in default deployments. We recently had a partner which had several deployment where for the same type of disk we had some NVME SSDs using the default 21500 while others were set at ~70K-80K. This leads to significant performance issues.
Why does the customer need this? (List the business requirements here)
Due the the performance issues the mclock configuration needs to be updated after install. This can be done manually but that means extra operations which would not be required if we can configure this at install time. Manual work requires extra time which generates extra costs which a ZTP install would not require.
Are there any Documentation Requirements for this request?
Is the request coming from a specific customer or subset of customers (on prem only, cloud only, etc). Please don't mention any customer related sensitive information.
All telco customers that use baremetal installation will hit this as their blueprint changes and they use more newer and performant disks.
What is the urgency of the request?
Right now we already have partners that have hit performance issues due to the fact that we cannot configure this at install time and we had to change this manually
Please provide contact information, in case of follow up questions.
Feature Request
Undefined
