Migration parameters (such as maximum bandwidth or maximum concurrent outgoing migrations) can only be configured at the moment by manipulating a VDSM configuration file on the hosts used for migration. It would be more convenient to be able to control these parameters from the engine.
This should probably be configured on a per VM basis - so while migrating a certain VM the user should be able to specify what is the migration network (if he would like to force a different one than the cluster's default) as well as the specific b/w parameters for the migration.
Will be addresses as part of BZ 1115171. I am leaving this BZ open to make sure we have this specific use case of controlling the migrations parameters tested.