Skip to content

docs(vmware-migration): document StorageMap for VMs spanning multiple datastores#756

Open
jing2uo wants to merge 1 commit intomainfrom
docs/vmware-migration-multi-datastore-storagemap
Open

docs(vmware-migration): document StorageMap for VMs spanning multiple datastores#756
jing2uo wants to merge 1 commit intomainfrom
docs/vmware-migration-multi-datastore-storagemap

Conversation

@jing2uo
Copy link
Copy Markdown
Collaborator

@jing2uo jing2uo commented May 9, 2026

Summary

  • Expand the StorageMap section of the VMware → ACP migration guide (both ZH and EN) so it covers VMs whose disks live on more than one VMware datastore.
  • Split the section into Single Datastore / Multiple Datastores subsections, add a multi-datastore YAML example, document that each source datastore must appear in spec.map exactly once and may share or differ in destination.storageClass, and add a tip on how to discover a VM's datastore distribution (vCenter Edit Settings or Forklift inventory disks[*].datastore.id).

Test plan

  • Render docs/zh/solutions/How_to_Migrate_VirtualMachine_From_VMware.md and verify the new Single/Multiple Datastores subsections display correctly
  • Render docs/en/solutions/How_to_Migrate_VirtualMachine_From_VMware.md and verify the same
  • Sanity-check the multi-datastore StorageMap YAML against the forklift.konveyor.io/v1beta1 CRD

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Enhanced VMware migration guide with expanded StorageMap configuration requirements and practical examples
    • Added comprehensive guidance for single-datastore and multi-datastore migration scenarios
    • Included instructions for determining VM disk placement locations
    • Documentation updates available in English and Chinese

Review Change Stack

… datastores

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@jing2uo jing2uo deployed to translate May 9, 2026 11:25 — with GitHub Actions Active
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 9, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 12b8e1f0-c058-4654-a114-37c3d95b59a4

📥 Commits

Reviewing files that changed from the base of the PR and between 5376d74 and de5a88a.

📒 Files selected for processing (2)
  • docs/en/solutions/How_to_Migrate_VirtualMachine_From_VMware.md
  • docs/zh/solutions/How_to_Migrate_VirtualMachine_From_VMware.md

Walkthrough

This PR expands the VMware-to-Alauda migration documentation by clarifying StorageMap (spec.map) requirements in both English and Chinese guides. It emphasizes that spec.map is an array requiring entries for all VMware datastores holding VM disks, adds single- and multi-datastore guidance with YAML examples, and documents methods for identifying VM datastore placements.

Changes

StorageMap Documentation Expansion

Layer / File(s) Summary
Concept Clarification and Single-Datastore Guidance
docs/en/solutions/How_to_Migrate_VirtualMachine_From_VMware.md, docs/zh/solutions/How_to_Migrate_VirtualMachine_From_VMware.md
Clarifies that spec.map is an array and every VMware datastore containing VM disks must be represented to pass Plan validation. Introduces "Single Datastore" guidance in both English and Chinese versions.
Multi-Datastore Mapping Rules and Examples
docs/en/solutions/How_to_Migrate_VirtualMachine_From_VMware.md, docs/zh/solutions/How_to_Migrate_VirtualMachine_From_VMware.md
Provides rules for multi-datastore scenarios, concrete YAML examples for mapping to different or consolidated StorageClasses, and instructions for identifying VM datastore placements via vCenter UI or Forklift inventory API in both languages.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

  • alauda/knowledge#104: Initial introduction of the How_to_Migrate_VirtualMachine_From_VMware documentation that this PR expands.

Suggested reviewers

  • fanzy618
  • tyzhou111

Poem

🐰 A rabbit hops through docs so clear,
Maps and datastores, storage dear,
Examples flow, both old and new,
English, Chinese, guides so true,
Migration paths now shine anew! 🚀

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: documentation expansion of StorageMap configuration for VMware VMs spanning multiple datastores across both English and Chinese guides.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/vmware-migration-multi-datastore-storagemap

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant