Bug 1038550 - [RFE] RHEV-M portal should highlight primary interface in bond configured using 'primary' option in custom mode.
Summary: [RFE] RHEV-M portal should highlight primary interface in bond configured usi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ovirt-4.1.0-beta
: ---
Assignee: Dominik Holler
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-05 10:23 UTC by Nikhil Gupta
Modified: 2019-04-28 10:46 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
-
Clone Of:
Environment:
Last Closed: 2017-04-25 00:54:28 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:
nyechiel: Triaged+
gklein: testing_plan_complete+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 635503 0 None None None Never
Red Hat Product Errata RHEA-2017:0997 0 normal SHIPPED_LIVE Red Hat Virtualization Manager (ovirt-engine) 4.1 GA 2017-04-18 20:11:26 UTC
oVirt gerrit 65408 0 None None None 2016-10-13 11:52:22 UTC

Description Nikhil Gupta 2013-12-05 10:23:40 UTC
[RFE] RHEV-M portal should highlight primary interface in bond configured using 'primary' option in custom mode.

For example:

There are two NIC in bond0 - nic1 and nic2. In custom bond setting, nic1 is configured as primary, however on admin portal there is no way to differentiate between primary and other interface.

Can we add any special representation for primary interface in a bond?

Comment 7 Lior Vernia 2015-02-24 14:59:51 UTC
vdsm already reports this as part of the bond entry under the bondings dictionary, under the key 'active_slave' - all that remains is for engine to persist this information (likely as part of the vds_interface table) and for the GUI to somehow represent this in the host/interfaces subtab and in the Host Setup Networks dialog. I would also expose this information via REST.

Comment 9 Michael Burman 2016-11-06 07:43:28 UTC
- The active_slave property of the bond in modes that support it (active-backup(1), balance-alb(6) and balance-tlb(5)).  
This parameter is read only. Setting it will have no effect on the bond. It is retrieved from /sys/class/net/bondX/bonding/active_slave file on the system where the bond is located.

For example:

GET /ovirt-engine/api/hosts/123/nics/321

Will respond:

<host_nic href="/ovirt-engine/api/hosts/123/nics/321" id="321">
  ...
  <bonding>
    <slaves>
      <host_nic href="/ovirt-engine/api/hosts/123/nics/456" id="456" />
      ...
    </slaves>
    <active_slave href="/ovirt-engine/api/hosts/123/nics/456" id="456" />
  </bonding>
  ...
</host_nic>


- In the UI, the primary/active slave is shown in the 'Network Interfaces' subtab of the 'Hosts' main tab as a tool tip.

Comment 10 Michael Burman 2017-01-04 12:17:37 UTC
Verified on - 4.1.0-0.3.beta2.el7


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