| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Codecov Report❌ Patch coverage is 26.08696% with 340 lines in your changes missing coverage. Please review. @@ Coverage Diff @@
## main #13270 +/- ##
============================================
+ Coverage 18.10% 18.11% +0.01%
- Complexity 16749 16789 +40
============================================
Files 6037 6038 +1
Lines 542796 543226 +430
Branches 66456 66507 +51
============================================
+ Hits 98268 98417 +149
- Misses 433492 433759 +267
- Partials 11036 11050 +14
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry.
|
Sorry, something went wrong.
|
@andrijapanicsb a [SL] Jenkins job has been kicked to build packages. It will be bundled with kvm SystemVM template(s). I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 18075 |
Sorry, something went wrong.
| private String datacenterName; | ||
| private String clusterName; | ||
| private String hostName; | ||
| private String vmwareMoref; |
There was a problem hiding this comment.
| private String vmwareMoref; | |
| private String vmwareMoRef; |
?
Sorry, something went wrong.
There was a problem hiding this comment.
snapshot internal ref of VMware as reported by vCenter
Sorry, something went wrong.
There was a problem hiding this comment.
public String getVmwareMoref() {
return vmwareMoref;
}
public void setVmwareMoref(String vmwareMoref) {
this.vmwareMoref = vmwareMoref;
"r" is lowewrcase, don't capitalise it - or do it everywher :) ? Or....? You would know better
Sorry, something went wrong.
|
|
||
| private String bootType; | ||
| private String bootMode; | ||
| private String vmwareMoref; |
There was a problem hiding this comment.
| private String vmwareMoref; | |
| private String vmwareMoRef; |
Sorry, something went wrong.
|
@andrijapanicsb a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
Sorry, something went wrong.
|
[SF] Trillian test result (tid-16214)
|
Sorry, something went wrong.
|
@andrijapanicsb [SL] I understand these words: "help", "hello", "thanks", "package", "test" Blessed contributors for kicking Trillian test jobs: ['rohityadavcloud', 'shwstppr', 'Damans227', 'vishesh92', 'Pearl1594', 'harikrishna-patnala', 'nvazquez', 'DaanHoogland', 'weizhouapache', 'borisstoyanov', 'vladimirpetrov', 'kiranchavala', 'andrijapanicsb', 'NuxRo', 'rajujith', 'sureshanaparti', 'abh1sar', 'sudo87', 'RosiKyu'] |
Sorry, something went wrong.
|
@andrijapanicsb a [SL] Jenkins job has been kicked to build packages. It will be bundled with kvm SystemVM template(s). I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result [SF]: ✖️ el8 ✖️ el9 ✔️ debian ✖️ suse15. SL-JID 18089 |
Sorry, something went wrong.
|
@andrijapanicsb a [SL] Jenkins job has been kicked to build packages. It will be bundled with kvm SystemVM template(s). I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 18094 |
Sorry, something went wrong.
|
@andrijapanicsb a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 18095 |
Sorry, something went wrong.
|
@andrijapanicsb a [SL] Jenkins job has been kicked to build packages. It will be bundled with kvm SystemVM template(s). I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 18102 |
Sorry, something went wrong.
|
@blueorangutan test ol8 kvm-ol8 keepEnv |
Sorry, something went wrong.
|
@andrijapanicsb a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
Sorry, something went wrong.
|
[SF] Trillian test result (tid-16230)
|
Sorry, something went wrong.
|
@blueorangutan test ol9 kvm-ol9 keepEnv |
Sorry, something went wrong.
|
@andrijapanicsb a [SL] Trillian-Jenkins test job (ol9 mgmt + kvm-ol9) has been kicked to run smoke tests |
Sorry, something went wrong.
|
[SF] Trillian test result (tid-16234)
|
Sorry, something went wrong.
|
Closing in favour of 4.22 due to forward merge process. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Companion 4.22 PR: #13294
This PR is intended to keep the main and 4.22 branches aligned for the VDDK-to-RBD import feature.
Description
This PR extends the existing VMware-to-KVM VDDK import flow with Ceph RBD support, while preserving the current VDDK/QCOW2 behaviour.
The existing VDDK/QCOW2 writer remains supported in both existing modes:
This change adds a destination-aware writer model for VDDK imports. The current file/QCOW2 writer path remains, and a new Ceph RBD/raw writer path is added. This gives the VDDK import flow a cleaner foundation for adding more destination-specific writers later.
For Ceph RBD, two modes are supported:
Direct RBD mode
When usevddk=true, forceconverttopool=true, and convertinstancepoolid points to an RBD primary storage pool, CloudStack can write the VMware disk data directly into raw RBD images.
This path does not use the normal virt-v2v -o local -of qcow2 writer, because RBD is not a local filesystem target. Instead, the conversion host:
The in-place finalization happens only on the destination RBD images. The VMware source disks are not modified.
Staged RBD mode
When usevddk=true and forceconverttopool=false, RBD can still be used as the final destination through the existing staged model.
In this mode:
This mode does not require in-place virt-v2v, because regular virt-v2v has already finalized the guest while creating the temporary QCOW2 disks.
Direct RBD mode requires newer conversion-host tooling. The practical recommended baseline is EL9-family KVM hosts, such as Oracle Linux 9, Rocky Linux 9, AlmaLinux 9, or RHEL 9, and Ubuntu 24.04-style hosts where virt-v2v-in-place or virt-v2v --in-place is available. EL8 and Ubuntu 22.04-style hosts should use staged RBD import unless compatible in-place tooling has been explicitly installed and detected by CloudStack.
The implementation adds KVM host capability detection for:
Direct RBD mode is rejected early when the selected conversion host does not support the required in-place finalization path. Staged RBD remains available in that case.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
N/A
How Has This Been Tested?
Focused compile and unit test coverage was run for the changed API/core/server/KVM paths, including:
The tests cover direct RBD host capability checks, rejection when direct RBD support is missing, staged RBD destination handling, RBD destination pool type propagation, RBD disk metadata, and server-side validation for RBD storage pools.
How did you try to break this feature and the system with this change?
Negative tests were added for hosts without direct VDDK/RBD support, and staged RBD import is validated separately so that lack of in-place virt-v2v blocks only direct RBD mode, not RBD import as a whole. Existing VDDK/QCOW2 direct and staged flows are kept on the existing writer path unless the selected forced conversion pool is RBD.