aaaaargh, automation!

Fixes should be in ovirt-3.4.0-beta2. Assignee please check.

Yes, all relevant patches are included in ovirt-3.4.0_beta2.

Verified downstream in rhevm-3.4.0-0.9.beta1.el6ev.noarch (av3.1).

Verification steps:
Terms:
- "VM downtime": migration donwtime set on VM; in GUI - VM dialog / Host: "Use custom migration downtime"
- "global downtime": parameter "DefaultMaximumMigrationDowntime" set via engine-config utility (in milliseconds); don't forget to restart engine service after every update

Verification:
1. Follow the matrix below and for each case set the VM downtime and global downtime values (6 cases in total).
2. Run the VM and migrate it from source host to destination host.
3. On *source* host open the vdsm.log and look up the "vmMigrate" command and inspect its parameters.


 # | VM downtime & global downtime = vmMigrate called w/ parameter
-- | ----------- | --------------- | -----------------------------
 1 |  disabled   |  0              |  no 'downtime' parameter present (*)
 2 |  0          |  0              |  no 'downtime' parameter present (*)
 3 |  125        |  0              |  'downtime': '125'
 4 |  disabled   |  250            |  'downtime': '250'
 5 |  0          |  250            |  no 'downtime' parameter present (*)
 6 |  125        |  250            |  'downtime': '125'


(*) When vmMigrate command doesn't contain the 'downtime' parameter, then value defined in VDSM is used, either defined in the VDSM config file or default 500 (milliseconds).

Example of VDSM log - vmMigrate command with downtime parameter:
-~-
Thread-13::DEBUG::2014-03-19 17:55:18,604::BindingXMLRPC::1067::vds::(wrapper) client [10.0.0.1]::call vmMigrate with ({'tunneled': 'false', 'src': '10.0.0.2', '
dst': '10.0.0.3:54321', 'vmId': 'b26a0729-10d7-456f-9c8d-8b54c6fc3129', 'abortOnError': 'true', 'downtime': '125', 'method': 'online'},) {} flowID [59c86a0d]
-~-

This is an automated message: moving to Closed CURRENT_RELEASE since oVirt 3.4.0 has been released.