Uploaded image for project: 'Migration Toolkit for Virtualization'
  1. Migration Toolkit for Virtualization
  2. MTV-3896

[DOC] Add explanatory text in the documentation clarifying namespace differences in migration plans

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected

      Addresses the user confusion about the differences between namespaces within a plan.

       

      The main objective of this ticket is to address a critical user pain point identified in the UX research related to the Learning Curve of the Migration Toolkit for Virtualization (MTV) Operator. Specifically, Virtualization Infrastructure (VI) Administrators struggle to understand the differences between the two namespaces (Source and Target) within a migration plan.
       
      This task requires reviewing the existing documentation, particularly the Planning your migration guide, and injecting clear, conceptual explanations to resolve this ambiguity.

      Key Documentation Tasks

      1. Clarify Namespace Differences in Migration Plans (Primary Focus):

      • Goal: Directly address the question: "How can VI admins understand the differences between these two namespaces within a plan?".
      • Action: Update the conceptual and procedural sections detailing the creation of a migration plan (e.g., in Planning your migration or Migrating your virtual machines) to explicitly define the function and purpose of the Source Namespace and the Target Namespace.
      • Explain the role of the namespaces in the context of OpenShift Virtualization, ensuring clarity for VI Admins who may be new to Kubernetes concepts.
         **

      2. Enhance Learning Curve Content:

      • Provide better explanations and differentiation for core migration concepts like Hot Migration, Warm Migration and Cold Migration to help Admins understand the implications of their choices.
      • Improve educational content around the overall complexity of the end-to-end migration process and prerequisite setup, particularly networking.{}

      3. Address Secondary UI/Technical Issues (As Scope Allows):

      • If necessary, briefly review and update guidance for known UI issues, such as clarifying that users can remove VMs but cannot add VMs to a plan in certain steps, and addressing the visibility of selected VMs.

       
      Content is logically placed within the official documentation (e.g., https://docs.redhat.com/en/documentation/migration_toolkit_for_virtualization/2.10/html/planning_your_migration_to_red_hat_openshift_virtualization).

              rhn-support-anarnold A Arnold
              rhn-support-anarnold A Arnold
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: