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

[DOC] Enhance documentation for configuring networking prerequisites and migration environment setup

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected

      Addresses the difficulty users have in configuring networking as part of the setup.

      This ticket addresses a significant pain point identified in the UX research's Learning Curve category: Customers and consultants find setting up the migration environment, including configuring networking, is not easy. The task is to improve the usability of the documentation by ensuring this critical setup information is clear, complete, and easy to find.

      Key Documentation Tasks

      1. Networking Prerequisites:

      • Review and significantly enhance the content that explains the required network configuration for MTV to successfully migrate VMs from VMware to OpenShift Virtualization.
      • This content should clarify all prerequisites to minimize migration failures related to network setup.

      2. Migration Environment Setup:

      • Improve the clarity and flow of instructions for the end-to-end migration process setup, as the process is currently perceived as complex.
      • Provide essential background or instructional information, particularly addressing the fact that a lack of understanding of automation (e.g., Ansible) could pose a challenge.

       
       

      To help you move forward with the MTV-3895 documentation overhaul, I’ve drafted a Job-To-Be-Done (JTBD) statement and defined the key personas involved. These tools will help ensure the updated documentation addresses the "Learning Curve" pain points identified in your UX research.

       

      Job-To-Be-Done (JTBD) Statement

      The JTBD framework focuses on the motivation and the outcome rather than just the task.

      "When I am preparing our infrastructure for a large-scale migration from VMware to OpenShift Virtualization, I want to clearly understand the networking prerequisites and the step-by-step setup logic, so that I can configure the environment correctly the first time and avoid migration failures caused by preventable connectivity or automation gaps."

      Target Personas

       

      Persona Role & Responsibility Pain Points & Needs
      Infrastructure Architect (Alex) Designs the overall migration strategy; ensures security and compliance standards are met. Needs high-level clarity on port requirements and network topology to approve firewall changes and internal security tickets.
      Virtualization Admin (Sam) The "boots on the ground" executing the migration; expert in VMware but perhaps new to OpenShift. Needs a pre-flight checklist for networking and clear instructions on how MTV interacts with the source and target.
      DevOps Engineer (Jordan) Manages the automation and scaling of the migration process. Might struggle if the documentation assumes deep Ansible knowledge. Needs "low-floor" entry points into the automation aspects.

       
       

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

                Created:
                Updated: