Hide Forgot
1. Proposed title of this feature request Engine should apply a sensible overall timeout to the live migration of guests. 2. Who is the customer behind the request? N/A 3. What is the nature and description of the request? With the introduction of RFE BZ#1034871 engine will become the right place to calculate and apply a sensible overall timeout for live migrations per VM. This timeout should take both guest (CPU, IO and memory) and host (network) load into account when calculating this value. 4. Why does the customer need this? (List the business requirements here) Allows a more accurate timeout to be calculated given guest and host loads before the migration starts. 5. How would the customer like to achieve this? (List the functional requirements here) Extend engine to calculate and set an overall migration timeout. 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Does engine set a sensible migration timeout value per VM? 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? No. 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? RHEV 3.4 9. Is the sales team involved in this request and do they have any additional input? No 10. List any affected packages or components. vdsm and ovirt-engine-backend. 11. Would the customer be able to assist in testing this functionality if implemented? Yes GSS can help with testing this.
not likely to be feasible. Let's see what autoconvergence brings us and maybe tweak the migration downtime algorithm in vdsm (http://gerrit.ovirt.org/#/c/25820/)
still want to consider this "soon"
will address as part of bug 1252426 *** This bug has been marked as a duplicate of bug 1252426 ***