chore(deployment): clarify TDX HW requirements are per-CVM, bump disk to 1TB#3449
Conversation
The listed 64GB/8-core/500GB specs are what a single CVM consumes, not the TDX host. Operators may run two CVMs concurrently during a launcher migration, so size the host for ~2x. Also bump the CVM disk to 1TB since 500GB is too small for a mainnet node. Closes #3448 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Pull request overviewClarifies that the TDX hardware requirements listed in the external operator guide are per-CVM, since operators may run two CVMs concurrently during a launcher migration. Also bumps the documented CVM disk from 500GB to 1TB (1000GB), which the PR description notes is too small for mainnet. Doc-only change, no code touched. Changes:
Reviewed changesPer-file summary
FindingsNon-blocking (nits, follow-ups, suggestions):
✅ Approved |
There was a problem hiding this comment.
Pull request overview
Updates the external TDX deployment guide to clarify that the stated compute/memory/storage requirements are per Confidential VM (CVM), and adjusts disk sizing guidance for mainnet operators who may run two CVMs concurrently during launcher migrations.
Changes:
- Clarify that resource figures are per-CVM and advise sizing the TDX host for ~2x during migrations.
- Increase the recommended CVM disk size from 500GB to ~1TB and update the VM HW settings accordingly.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Address review feedback: the per-CVM "2x the host" note no longer covers the host-level CPU/RAM-slot requirement, and the disk figure reads "1TB (1000 GB)" to match the VM setting and max_disk_size config. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Align the deployment configs with the 1TB per-CVM guidance: the cvm-deployment templates (default.env, sgx/kms configs, deploy-launcher-guide.md) and the testnet node envs (frodo, sam) all defaulted to DISK=500G. Localnet/test scaffolding left at 500G/128G. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
PR title type suggestion: This PR changes both documentation and deployment config files (.env), so the type prefix should probably be Suggested title: |
|
addressed the production side in 589eac5: bumped |
Closes #3448