Created attachment 895421 [details] screenshot Description of problem: TUI is strange. Status tab: Networking: Connected rhevm IPv4: 10.34.63.222 Network tab: Available NICs lists not only real physical ifaces but also pseudo-ifaces like bonds. But no bridges. But why is there no bridge, especially when 'rhevm' is currectly the iface holding known IPv4 address as displayed in 'Status' tab. This is odd. I think people would like to see under 'Network' tab how networking really works on their host. Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization Hypervisor release 6.5 (20140508.0.el6ev) How reproducible: 100% Steps to Reproduce: 1. have your host in RHEV env 2. check Status tab 3. check Network tab Actual results: Network tab does not show current networking configuration, in fact it hides bridges. Expected results: IPv4 used by rhevm bridge should be visible in Network tab and we should see it is binded to a rhevm bridge. Additional info: 'Managed' is irrelevant in this context. Network tab should see network configuration reality on the host.
This is a broader topic. In general we need to identify how we handle networking on Node. Historically this was very limited. And the current design quickly approaches it's limits. Instead of supporting a fully fledged solution to setup arbitary network configurations, I am more in favor of being able to configure a number of layouts. If managed then we should probably just list the physical nics and mark them as managed. That might make the most sense.
In general, I would suspect that we don't show the ovirtmgmt or rhevm bridges because reconfiguring them would disconnect the node from the engine. It's possible to show the bridges and prevent reconfiguration, but the networking page is intended to give an overview of what's necessary to connect to the engine, which then manages everything. We don't even present the option to create bridges, which is why they are not visible. Additionally, other hypervisors do not allow you to see every network (guest, neutron, bridged, or otherwise) defined inside the management engine, which quickly gets unwieldy and cannot be effectively managed from the hypervisor side in any case. Not that I'm necessarily saying that because other vendors don't do it we shouldn't do it, but there is some rationale behind the decision. Given this, what outcome would you like ot see in the TUI?
I wanted to see reality, no lies, no obfuscation, no hidden details about networking. Expected results: IPv4 used by rhevm bridge should be visible in Network tab and we should see it is binded to a rhevm bridge.
Re-targeting for 3.6
This functionality will move to cockpit, and thus this bug does not apply there anymore.