Bug 1686874

Summary: Add default setting for CPU and network limits per conversion host
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: V2VAssignee: Fabien Dupont <fdupont>
Status: CLOSED ERRATA QA Contact: Yadnyawalk Tale <ytale>
Severity: medium Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: high    
Version: 5.10.1CC: bthurber
Target Milestone: GAKeywords: ZStream
Target Release: 5.10.2   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: 5.10.2.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1686169 Environment:
Last Closed: 2019-04-02 07:46:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: V2V Target Upstream Version:
Embargoed:
Bug Depends On: 1686169    
Bug Blocks:    
Attachments:
Description Flags
default_values.png none

Comment 2 CFME Bot 2019-03-08 15:16:18 UTC 
New commit detected on ManageIQ/manageiq/hammer:

https://github.com/ManageIQ/manageiq/commit/a1b667b45fbc38ef4a169d16f1fa6a513433c1a8
commit a1b667b45fbc38ef4a169d16f1fa6a513433c1a8
Author:     Adam Grare <agrare>
AuthorDate: Thu Mar  7 11:11:44 2019 -0500
Commit:     Adam Grare <agrare>
CommitDate: Thu Mar  7 11:11:44 2019 -0500

    Merge pull request #18528 from fdupont-redhat/v2v_add_default_throttling_setting_cpu_and_network

    [V2V] Add default setting for CPU and network limits per conversion host, and max concurrent tasks per EMS

    (cherry picked from commit a921fcfd995c1bda55b54b2d7bc43f1a6176530e)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1686874

 config/settings.yml | 3 +
 1 file changed, 3 insertions(+)
Comment 3 Yadnyawalk Tale 2019-03-18 13:14:10 UTC 
Created attachment 1545214 [details]
default_values.png
Comment 4 Yadnyawalk Tale 2019-03-18 13:17:50 UTC 
Fixed, verified on 5.10.2.0.20190311164858_455d270.
Comment 6 errata-xmlrpc 2019-04-02 07:46:17 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0694