Bug 1397685

Summary: [RFE] Display VLans with Virt Infra networking and make VLans taggable
Product: Red Hat CloudForms Management Engine Reporter: Loic Avenel <lavenel>
Component: UI - OPSAssignee: Harpreet Kataria <hkataria>
Status: CLOSED WONTFIX QA Contact: Kedar Kulkarni <kkulkarn>
Severity: medium Docs Contact:
Priority: high    
Version: 5.7.0CC: gblomqui, hkataria, jfrey, jhardy, lavenel, mpovolny, mshriver, obarenbo, rspagnol
Target Milestone: GAKeywords: FutureFeature, RFE
Target Release: 5.11.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sdn:tag
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-14 19:12:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Feature
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Attachments:
Description Flags
Infra/Networking with standard switches/lans
none
vSphere Client with standard switches/lans none

Description Loic Avenel 2016-11-23 07:49:34 UTC 
Description of problem: [RC1] Vlans are not available as object in Infrastructure Networking only DVS are visible and taggable.


Version-Release number of selected component (if applicable):5.7.0.10-beta3.20161109111947_9a61b18


How reproducible: Always

Additional info: As we are not representing all networks, this will be very confusing for customers.
Comment 2 Adam Grare 2016-11-30 20:55:42 UTC 
Created attachment 1226504 [details]
Infra/Networking with standard switches/lans
Comment 3 Adam Grare 2016-11-30 20:56:15 UTC 
When adding the UI for VDS we didn't add standard VM Network LANs because the logic for displaying them is quite different.  If using the same logic VDS you would see at least one additional vSwitch per host and each VM Network under that, where in the vSphere client it combines all VM Networks with the same name and doesn't show the vSwitch.

I'll upload screenshots of what this would look like if we showed standard switches and LANs compared to what vSphere displays.
Comment 4 Adam Grare 2016-11-30 20:56:39 UTC 
Created attachment 1226505 [details]
vSphere Client with standard switches/lans
Comment 5 Adam Grare 2016-11-30 21:01:54 UTC 
I think it would be confusing to show the standard switches/lans without trying to match how the vSphere client mangles^Wmassages the inventory objects.

We have all the data from the provider so to display it the same way as vSphere would be a UI enhancement, and since you're combining multiple network objects into one display item I'm not sure how tagging would work.
Comment 8 Greg Blomquist 2016-12-04 19:04:41 UTC 
I updated the summary to reflect what seems to match the "ask" (and changed to an RFE).

It sounds like (based on Adam's comment #3 and comment #5) MIQ would need a new page to show VLans apart from Distributed Virtual Switches (DVS).  Intermingling them sounds like it makes it overly complicated for implementation *and* for the user ... a double whammy!

My suggestion is to either pull in UX help here, or just create a new page for VLans.

Leaving this on Web UI for now...