Description of problem: This bug is to act as a placeholder for creating a documentation note on how to adjust the limit of parallel migrations per conversion host. Per https://bugzilla.redhat.com/show_bug.cgi?id=1600152 this will be set to 10 but may need to be adjusted. Steps on how to make this adjustment should be clearly explained in the documentation on how the migrations are limited per host and how this can be adjusted via cli commands. Version-Release number of selected component (if applicable): 5.9.4 How reproducible: Yes Steps to Reproduce: 1.Create plan of 22 VMs using 2 conversion hosts 2.Execute plan Actual results: No documentation on how to change migration limit. Expected results: Documentation to explain how the limit can be changed. Additional info: Document URL: Section Number and Name: Describe the issue: Suggestions for improvement: Additional information:
When executing a migration plan, the default number of concurrent migration is 10 per conversion host and 10 per provider. This can be customized by adding a custom attribute either on the conversion host or the provider, or both. You should keep in mind that the limit set at the provider level will have priority on the limit at the conversion host level, eg. setting 20 concurrent migrations at the provider level while having 3 conversion hosts will effectively limit to 20. The customer attribute to set is "Max Transformation Runners". To set it, you currently have to use rails console on the CloudForms appliance. The following example sets the max concurrent migration on host1.example.com to 20: # vmdb # rails console irb(main):001:0> $evm = MiqAeMethodService::MiqAeService.new(MiqAeEngine::MiqAeWorkspaceRuntime.new) irb(main):002:0> $evm.vmdb(:host).find_by(:name => 'host1.example.com').custom_set("Max Transformation Runners", 20) To set the max concurrent migrations to 30 on a provider named 'My RHV', this will be: # vmdb # rails console irb(main):001:0> $evm = MiqAeMethodService::MiqAeService.new(MiqAeEngine::MiqAeWorkspaceRuntime.new) irb(main):002:0> $evm.vmdb(:ext_management_system).find_by(:name => 'My RHV').custom_set("Max Transformation Runners", 30)
Fabian, So currently default is 10 parallel per provider? Meaning if I have 2 hosts we will get 5 parallel per host? - This is actually what we see now at our tests... Can you please write the command to Get the current config per host and provider
The following examples show how to get the current configuration of Max Transformation Runners using the custom_get method. This method returns either the current configuration value or nil, if the value has not been set. To get the configuration of Max Transformation Runners for conversion host 'host1.example.com': # vmdb # rails console irb(main):001:0> $evm = MiqAeMethodService::MiqAeService.new(MiqAeEngine::MiqAeWorkspaceRuntime.new) irb(main):002:0> $evm.vmdb(:host).find_by(:name => "host1.example.com").custom_get("Max Transformation Runners") To get the configuration of Max Transformation Runners for provider 'My RHV': # vmdb # rails console irb(main):001:0> $evm = MiqAeMethodService::MiqAeService.new(MiqAeEngine::MiqAeWorkspaceRuntime.new) irb(main):002:0> $evm.vmdb(:ext_management_system).find_by(:name => "My RHV").custom_get("Max Transformation Runners")
Avital please add the Get commands to you V2V doc and I thing you can move this bug to on-qa so we could validate
They have been added and are ready for validation: http://file.tlv.redhat.com/~apinnick/_V2V_Guide/#Configuring_the_maximum_number_of_concurrent_migrations
Verified.
These changes are live on the Customer Portal. Closing.