XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • None
    • None
    • storage-offload: Large scale
    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • In Progress
    • 20% To Do, 40% In Progress, 40% Done

      Goal

      Today, the storage offload fails in lot of places in the large-scale migrations, for example, 50 VMs.  

      After this epic, MTV should be able to perform at least 50 VM migrations at once with the storage offload. If there are limitations on the ESXi we should add a mechanism to balance, wait, retry. Mainly, we should not fail migration unless there is an error that breaks the clone.

      User Stories

      • As a cluster administrator,
        I want to select a large number of VMs to be migrated, all of the VMs with the storage offload, so that I can rely on the time of the migration.

      Non-Requirements

      • <anything that we explicitly exclude>

      Notes

      • <references to existing docs or mailinglists etc>

              rgolan1@redhat.com Roy Golan
              mnecas@redhat.com Martin Necas
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: