andrijapanicsb opened a new pull request, #13164:
URL: https://github.com/apache/cloudstack/pull/13164

   ## Summary
   
   This draft adds the first CloudStack-side implementation path for VMware 
CBT-assisted migration from VMware to KVM, building on the existing full-copy 
VDDK/virt-v2v import flow.
   
   - Adds API entry points, response objects, service interfaces, and state 
tracking for VMware CBT migration sessions, disks, and sync cycles.
   - Adds database model/DAO wiring for migration, disk, and cycle state, using 
the 4.23 upgrade path placeholder.
   - Adds KVM agent command contracts and libvirt-side wrappers for prepare, 
sync, cutover, and cleanup orchestration.
   - Adds sync planning helpers/tests for changed-block range validation and 
coalescing.
   - Extends the import UI with CBT/VDDK migration mode handling and disk 
target registration, plus a CBT migration management view.
   - Adds a Windows-safe build helper for local CloudStack Maven/UI work and 
ignores local `settings.toml` secrets/config.
   
   ## Current Scope
   
   This is intentionally a draft PR. The goal is to make the architecture 
reviewable and testable incrementally before wiring the final production-grade 
VMware/VDDK/libnbd data path.
   
   The current branch focuses on CloudStack API/state/orchestration boundaries, 
UI flow, KVM command contracts, and delta sync planning behavior.
   
   ## Testing
   
   Previously verified on this branch:
   
   - `powershell -NoProfile -ExecutionPolicy Bypass -File 
tools\cloudstack-build.ps1 -Modules server,plugins\hypervisors\kvm -Test 
VmwareCbtMigrationCutoverPolicyTest,VmwareCbtSyncPlanTest,LibvirtVmwareCbtSyncCommandWrapperTest`
   - UI lint via `node node_modules\@vue\cli-service\bin\vue-cli-service.js 
lint`
   - UI production build with `NODE_OPTIONS=--openssl-legacy-provider`
   
   A cleanup-only follow-up commit added `settings.toml` to `.gitignore`; tests 
were not rerun after that ignore-only change.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to