Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1397686 - [RFE] Vmware Provisioning Dialog should clearly represent Vlans & DVS in Networking Dialog
[RFE] Vmware Provisioning Dialog should clearly represent Vlans & DVS in Netw...
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning (Show other bugs)
5.8.0
Unspecified Unspecified
medium Severity medium
: GA
: 5.8.0
Assigned To: drew uhlmann
Leo Khomenko
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-11-23 02:52 EST by Loic Avenel
Modified: 2017-05-31 10:24 EDT (History)
6 users (show)

See Also:
Fixed In Version: 5.8.0.1
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-05-31 10:24:31 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1367 normal SHIPPED_LIVE Moderate: CFME 5.8.0 security, bug, and enhancement update 2017-05-31 14:16:03 EDT

  None (edit)
Description Loic Avenel 2016-11-23 02:52:23 EST
Description of problem: Vmware Provisioning Dialog should clearly represent Vlans & DVS in Networking Dialog. Today, the drop list is call vLans and all is listed.
Comment 2 Greg McCullough 2016-11-29 15:43:42 EST
Loic, Are you asking for a simple text change to the description of the drop-down?  (https://github.com/ManageIQ/manageiq/blob/076385ccea94424d153bebcdaddaf9ddcf96a49d/product/dialogs/miq_dialogs/miq_provision_vmware_dialogs_template.yaml#L670)

Or is there more to this request than that?
Comment 3 Loic Avenel 2016-11-29 16:12:19 EST
(In reply to Greg McCullough from comment #2)
> Loic, Are you asking for a simple text change to the description of the
> drop-down? 
> (https://github.com/ManageIQ/manageiq/blob/
> 076385ccea94424d153bebcdaddaf9ddcf96a49d/product/dialogs/miq_dialogs/
> miq_provision_vmware_dialogs_template.yaml#L670)
> 
> Or is there more to this request than that?

There are 2 things:

- the name of the DropDown is called "Vlan" which is misleading on Vmware, it should be called "Virtual Network"
- In the drop list it will be nice to differentiate DVS from vLans.... OR there is a first filter DVS/Vlan..
Comment 4 Greg McCullough 2017-01-27 14:04:18 EST
After discussing with Adam I think the first thing we should address is renaming the field in the provision dialog from "Vlan" to "Virtual Network".  We can use that simple change to address this ticket.

Loic - If you think we should create a separate drop-down to allow UI filtering of the networks please open a separate RFE and we can look into addressing it.  At the moment, unless there is real user need, I would like to delay this until we move the provisioning dialogs to use the same dialog system as services.
Comment 5 Loic Avenel 2017-01-30 10:57:07 EST
(In reply to Greg McCullough from comment #4)
> After discussing with Adam I think the first thing we should address is
> renaming the field in the provision dialog from "Vlan" to "Virtual Network".
> We can use that simple change to address this ticket.
> 
> Loic - If you think we should create a separate drop-down to allow UI
> filtering of the networks please open a separate RFE and we can look into
> addressing it.  At the moment, unless there is real user need, I would like
> to delay this until we move the provisioning dialogs to use the same dialog
> system as services.

Hi Greg,

   I think Renaming to "Virtual Network" is the first part, I think the UI filtering will be great, at minima if we have only one drop down, we should clearly distinguish both type.
Comment 6 drew uhlmann 2017-02-02 12:44:03 EST
https://github.com/ManageIQ/manageiq/pull/13747
Comment 7 Leo Khomenko 2017-03-21 06:07:42 EDT
verified on 5.8.0.6
Comment 9 errata-xmlrpc 2017-05-31 10:24:31 EDT
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/RHSA-2017:1367

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