Bug 1309960 - [RFE] Enable vdsm to detect openvswitch events
[RFE] Enable vdsm to detect openvswitch events
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: RFEs (Show other bugs)
Unspecified Unspecified
unspecified Severity high
: ovirt-4.0.0-alpha
: 4.0.0
Assigned To: Scott Herold
Gil Klein
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2016-02-19 01:03 EST by Bryan Yount
Modified: 2016-11-22 16:08 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-03-27 07:20:25 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Network
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bryan Yount 2016-02-19 01:03:03 EST
3. What is the nature and description of the request?

The ovsdb-client implements a monitoring capability and vdsm should use this capability allow to notified of changes changes to OVS configuration and state.

4. Why does the customer need this? (List the business requirements here)

This will eliminate the need to poll each hypervisor that has an open vswitch installed for state in information.

5. How would the customer like to achieve this? (List the functional requirements here)

vdsm should interface with the openvswitch database to detect changes and report those changes to RHEV-M

usage: ovsdb-client [OPTIONS] COMMAND [ARG...]

Valid commands are:

  list-dbs [SERVER]
    list databases available on SERVER

  get-schema [SERVER] [DATABASE]
    retrieve schema for DATABASE from SERVER

  get-schema-version [SERVER] [DATABASE]
    retrieve schema for DATABASE from SERVER and report only its
    version number on stdout

  list-tables [SERVER] [DATABASE]
    list tables for DATABASE on SERVER

  list-columns [SERVER] [DATABASE] [TABLE]
    list columns in TABLE (or all tables) in DATABASE on SERVER

    run TRANSACTION (a JSON array of operations) on SERVER
    and print the results as JSON on stdout

  monitor [SERVER] [DATABASE] TABLE [COLUMN,...]...
    monitor contents of COLUMNs in TABLE in DATABASE on SERVER.
    COLUMNs may include !initial, !insert, !delete, !modify
    to avoid seeing the specified kinds of changes.

    monitor all changes to all columns in all tables

    dump contents of DATABASE on SERVER to stdout

The default SERVER is unix:/var/run/openvswitch/db.sock.
The default DATABASE is Open_vSwitch.

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

RHEV-M will receive a notification of an event or change in the ovs topology. Additionally, RHEV-M will need functionality to act upon these events.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?


8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

RHEV 4.0

9. Is the sales team involved in this request and do they have any additional input?

Yes, the sales team is involved and may add additional comments later.

10. List any affected packages or components.


11. Would the customer be able to assist in testing this functionality if implemented?

Comment 2 Yaniv Lavi 2016-02-21 05:28:06 EST
Are they looking for being able to add themselves as a monitor or having their info collected by VDSM and sent to the management?
Comment 3 Bryan Yount 2016-02-29 13:42:13 EST
(In reply to Yaniv Dary from comment #2)
> Are they looking for being able to add themselves as a monitor or having
> their info collected by VDSM and sent to the management?

Customer response:
"We would want VDSM to collect the info and sent to RHEV-M. We would access via RHEV-M."

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