Skip to content

Comments

Add vSAN I/O scheduling and workload management docs#398

Merged
rstark-verge merged 2 commits intomainfrom
fix/390-vsan-io-scheduling
Feb 19, 2026
Merged

Add vSAN I/O scheduling and workload management docs#398
rstark-verge merged 2 commits intomainfrom
fix/390-vsan-io-scheduling

Conversation

@jasnoyaeger
Copy link
Member

Summary

  • Add new product guide page documenting vSAN I/O fair queuing, capacity-based throttling (91%/96% thresholds), and explicitly stating that per-VM/tenant I/O limiting is not available
  • Include workarounds for workload isolation: tier separation, guest-level cgroups/Windows controls, resource right-sizing
  • Update Azure AD references to Entra ID in auth docs

Closes #390

Test plan

  • Verify page renders correctly on local mkdocs serve
  • Confirm nav placement under Storage > vSAN I/O Scheduling
  • Review content accuracy with engineering/support team
  • Verify all internal links resolve

🤖 Generated with Claude Code

Document how vSAN fair queuing distributes I/O across workloads,
capacity-based throttling thresholds (91%/96%), and explicitly
clarify that per-VM/tenant I/O limiting is not available.
Also update Azure AD references to Entra ID.

Closes #390

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@rstark-verge rstark-verge merged commit ad0bd7d into main Feb 19, 2026
2 checks passed
@rstark-verge rstark-verge deleted the fix/390-vsan-io-scheduling branch February 19, 2026 19:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs: vSAN I/O Fair Queuing and Workload Limiting

3 participants