MTV 2.12.0 release notes#935
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughThis PR retargets release notes to 2.12: bumps OpenShift and project attributes, rewires the master release-notes assembly to include 2.12 modules, and adds new 2.12 reference modules for technical changes, new features, known issues, and resolved issues. ChangesRelease Notes Transition to 2.12
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@documentation/modules/ref_known-issues-2-12.adoc`:
- Around line 12-15: This entry under the “Known issues” heading should be
rewritten to state the current limitation rather than implying a past failure:
update the paragraph titled "Virtual machine migrations with XFS v4 file
systems..." to explicitly say that migrations are rejected when
xfsCompatibility: true is combined with virt_v2v_memsize or virt_v2v_smp (e.g.,
"Migrations are now blocked when `xfsCompatibility: true` is used together with
`virt_v2v_memsize` or `virt_v2v_smp`; {project-short} will prevent these
incompatible configurations."), or move the item out of Known issues into the
resolved/behavior-change section so it reads as a deliberate validation change;
keep the {project-short} placeholder and the MTV-5595 link intact.
In `@documentation/modules/ref_resolved-issues-2-12-0.adoc`:
- Around line 12-21: The two identical entries titled "RDM disks converted to a
LUN now have the correct SCSI interface type" should be reconciled: inspect the
two issue references (link MTV-5610 and MTV-5620) and either (a) merge them into
a single entry that lists both links if they are the same fix, or (b) if they
are distinct, update each entry to state the unique scope or difference (e.g.,
component, affected release, or additional details) so both are justified;
remove the duplicated paragraph if they are truly the same. Locate the
duplicated block by searching for the exact heading text and the two link
identifiers (MTV-5610, MTV-5620) to apply the change.
- Line 13: The sentence describing RDM-to-LUN behavior in MigrationPlan contains
stray reference markers "[1, 2]"; edit the paragraph that mentions
"spec.rdmAsLun=true" and "MigrationPlan" to remove all occurrences of "[1, 2]"
so the text reads naturally (e.g., "…kept the virtio interface instead of
changing it to Small Computer System Interface (SCSI)." and "…have the required
SCSI interface type.") and ensure no leftover bracketed numbers remain.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 4b76da7b-8d7a-4e20-8b59-72a5e95c429a
📒 Files selected for processing (17)
documentation/doc-Release_notes/master.adocdocumentation/modules/common-attributes.adocdocumentation/modules/ref_known-issues-2-11.adocdocumentation/modules/ref_known-issues-2-12.adocdocumentation/modules/ref_new-features-and-enhancements-2-11.adocdocumentation/modules/ref_new-features-and-enhancements-2-12.adocdocumentation/modules/ref_resolved-issues-2-11-0.adocdocumentation/modules/ref_resolved-issues-2-11-1.adocdocumentation/modules/ref_resolved-issues-2-11-3.adocdocumentation/modules/ref_resolved-issues-2-11-4.adocdocumentation/modules/ref_resolved-issues-2-11-5.adocdocumentation/modules/ref_resolved-issues-2-11-6.adocdocumentation/modules/ref_resolved-issues-2-11-7.adocdocumentation/modules/ref_resolved-issues-2-12-0.adocdocumentation/modules/ref_rn-2-12.adocdocumentation/modules/ref_technical-changes-2-11.adocdocumentation/modules/ref_technical-changes-2-12.adoc
💤 Files with no reviewable changes (10)
- documentation/modules/ref_known-issues-2-11.adoc
- documentation/modules/ref_resolved-issues-2-11-6.adoc
- documentation/modules/ref_resolved-issues-2-11-3.adoc
- documentation/modules/ref_resolved-issues-2-11-1.adoc
- documentation/modules/ref_resolved-issues-2-11-5.adoc
- documentation/modules/ref_technical-changes-2-11.adoc
- documentation/modules/ref_resolved-issues-2-11-4.adoc
- documentation/modules/ref_new-features-and-enhancements-2-11.adoc
- documentation/modules/ref_resolved-issues-2-11-0.adoc
- documentation/modules/ref_resolved-issues-2-11-7.adoc
d73ddd1 to
41c5ea2
Compare
| :ocp-version: 4.21 | ||
| :ocp-y-version: 4.21, 4.20, 4.19 | ||
| :ocp-version: 4.22 | ||
| :ocp-y-version: 4.22, 4.21, 4.20, 4.19 |
There was a problem hiding this comment.
are these OCP versions supported for MTV 2.12? If so, the please remove 4.19
Signed-off-by: A.Arnold <anarnold@redhat.com>
Signed-off-by: A.Arnold <anarnold@redhat.com> and Richard Hoch <rhoch@redhat.com>
90278c0 to
8ba1dae
Compare
| id: network-21 | ||
| ---- | ||
| + | ||
| link:https://issues.redhat.com/browse/MTV-5511[MTV-5511] |
There was a problem hiding this comment.
@solenoci & @RichardHoch - please can we add the NetApp integration as a New Feature - WDYT?
| link:https://issues.redhat.com/browse/MTV-5511[MTV-5511] | |
| link:https://issues.redhat.com/browse/MTV-5511[MTV-5511] | |
| Zero-copy migrations via NetApp SHIFT integration:: | |
| Migration Toolkit for Virtualization (MTV) 2.12 provides integration with NetApp SHIFT for VMware environments. This feature enables "zero-copy" cold migrations to dramatically minimize migration downtime. As a result, you can achieve near-instantaneous data transfers. | |
| + | |
| The MTV user interface (UI) automates the process by generating specially labeled persistent volume claims (PVCs). These PVCs signal the NetApp Trident Container Storage Interface (CSI) to perform the disk transfer. When the transfer completes, MTV automatically executes the guest conversion, applies necessary boot permissions, and provisions the final virtual machine (VM) on OpenShift. | |
| + | |
| Review the following prerequisites and limitations for zero-copy migrations: | |
| * You must install the NetApp SHIFT add-on on the OpenShift cluster alongside the Trident Operator. | |
| * Source disks must reside on an ONTAP NFS datastore. Basic VMFS datastores are not supported. | |
| * You must annotate the applicable storage classes within the MTV UI to identify them as NetApp SHIFT-capable. | |
| * Source VMs cannot have active snapshots. You must flatten all disks before initiating the migration. | |
| * Only cold migrations from VMware sources are supported. If a source VM is powered on when the migration starts, MTV automatically powers it off. |
I was very kind and wrote a first draft for you! :)
MTV 2.12.0 release notes
This PR continues the work started in #934 by @anarnold97.
Resolves https://redhat.atlassian.net/browse/MTV-4408
Changes
Co-authored-by: Andy Arnold anarnold97@users.noreply.github.com
Summary by CodeRabbit
New Features
Documentation