Bug 1535322 - [UI] - Networks - Add info tooltip (blue i icon) next to the 'Custom' field in the External section
Summary: [UI] - Networks - Add info tooltip (blue i icon) next to the 'Custom' field i...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.2.1.1
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ovirt-4.3.5
: 4.3.5.4
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-17 06:29 UTC by Michael Burman
Modified: 2019-07-30 14:08 UTC (History)
5 users (show)

Fixed In Version: ovirt-engine-4.3.5.4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-30 14:08:36 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.3+


Attachments (Terms of Use)
screenshot (39.10 KB, image/png)
2018-01-17 06:29 UTC, Michael Burman
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 100800 0 master MERGED webadmin: Add info icon to Network popup 2019-07-01 05:09:01 UTC
oVirt gerrit 101380 0 ovirt-engine-4.3 MERGED webadmin: Add info icon to Network popup 2019-07-09 08:29:04 UTC

Description Michael Burman 2018-01-17 06:29:19 UTC
Created attachment 1382224 [details]
screenshot

Description of problem:
[UI] - Networks - Add info tooltip (blue i icon) next to the 'Custom' field in the External section.

Now that we have the ovn localnet feature, we can choose data center networks for the ovn network attachment or we can set a Custom value, what it this custom value? 
Custom for the physnet feature means, you can set an external network(not managed by rhv) in this field or set the network's VDSM name as well.
Without adding the blue 'i' icon tooltip, no one will understand the for what custom is used.

Version-Release number of selected component (if applicable):
4.2.1.1-0.1.el7

How reproducible:
100%

Comment 1 Petr Horáček 2018-11-15 12:54:03 UTC
I feel like this should not be on me (?).

Comment 2 Dan Kenigsberg 2018-11-26 13:33:51 UTC
You should be the one suggesting the text. I think that Ales can take it from there.

Comment 3 Petr Horáček 2019-06-04 16:40:19 UTC
Do you think following tooltip would do the job? 

"Set `provider:physical_network` attribute of the Network to a custom value"

More about the dialog is documented in [1] and Network API described in [2].

Thanks a lot.

[1] https://github.com/oVirt/ovirt-site/pull/1362/files#diff-8a0407030610153fb181177d9dba287bR63
[2] https://developer.openstack.org/api-ref/network/v2/index.html

Comment 4 Laura Wright 2019-06-05 13:57:33 UTC
My first suggestion is to change the label to 'Custom Network'. For the infotip text does something like the following make sense, "Custom network allows you to add an external network or set the network's VDSM name."?

Comment 5 Petr Horáček 2019-06-07 13:42:44 UTC
Thanks. I think it should be 'Custom Physical Network' to distinguish it from logical Networks mentioned in the rest of the dialog.

Not sure about the infotip. It doesn't add any network, actually the effect is completely dependent on the external network provider.

Also, let's not mention VDSM there. Although it is possible to use it for custom VDSM network, it is already available through the drop-down, there is no added value duplicating it.

I can see it being too low-level for a infotip. Maybe "Custom physical network allows you to specify custom physical network attribute on the provider network".

Comment 6 Laura Wright 2019-06-07 14:07:33 UTC
That label name works for me, just looking to provide the user with enough information about the network type. 

A more general description in the info tip works for me.

Comment 7 Petr Horáček 2019-06-10 16:13:12 UTC
So which description should we pick?

Comment 8 Michael Burman 2019-07-14 05:41:39 UTC
Verified on - rhvm-4.3.5.4-0.1.el7.noarch

Comment 9 Sandro Bonazzola 2019-07-30 14:08:36 UTC
This bugzilla is included in oVirt 4.3.5 release, published on July 30th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.5 release, it has been closed with a resolution of CURRENT RELEASE.

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


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