Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1695470 - [RFE]UI changes to conversion host configuration wizard
Summary: [RFE]UI changes to conversion host configuration wizard
Keywords:
Status: NEW
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: V2V
Version: 5.10.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: cfme-future
Assignee: Fabien Dupont
QA Contact: Sudhir Mallamprabhakara
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-03 07:49 UTC by Avital Pinnick
Modified: 2019-04-10 19:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)

Description Avital Pinnick 2019-04-03 07:49:41 UTC
1. Change text of error message that appears in conversion host configuration wizard Results screen (https://user-images.githubusercontent.com/811963/53612202-61e8db00-3b9f-11e9-85f3-b191aa65b48c.png)

Change to "The conversion host cannot be configured. Check your settings and try again."

2. Change tooltip of "Maximum concurrent migrations per conversion host" because it could imply that the UI imposes a constraint, when it's the user's responsibility not to set the number too high.

Change to "For VDDK transformation, the maximum concurrent migrations per conversion host should not exceed 20, to avoid network overload."

I don't see any point in referring to the product documentation because the document doesn't have much more info.

Comment 2 Mike Turley 2019-04-10 19:32:20 UTC
Changes here: https://github.com/ManageIQ/manageiq-v2v/pull/931


Note You need to log in before you can comment on or make changes to this bug.