Bug 615039

Summary: Define and implement API for reporting and using SRIOV devices.
Product: [Retired] oVirt Reporter: Dan Kenigsberg <danken>
Component: vdsmAssignee: Dan Kenigsberg <danken>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: unspecifiedCC: abaron, acathrow, bazulay, dyasny, iheim, mgoldboi, mkenneth, Rhev-m-bugs, syeghiay, ykaul
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: network
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 607609 Environment:
Last Closed: 2013-03-11 21:49:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 625530    
Bug Blocks: 641301    

Description Dan Kenigsberg 2010-07-15 20:10:12 UTC
1. getCapabilities - VDSM should report 2 additional properties:
         1. per nic:  SRIOV = VF/PF/unvirtualized
         2. per network: bridged/sriov

2. addNetwork - The interface today includes: bridge,vlan,bond,nics,options
      For 2.3 version, passing the option SRIOV=true/false tell if vdsm creates a bridge-based of sriov-based network.

3. getVdsStats - report how many VFs are available for each sriov-based network

4. create - no change in API. Implementation makes sure that only virtio interfaces are connected to sriov-based network. If no VF is available, connect the newly created VM through a bridge.

Comment 1 Itamar Heim 2013-03-11 21:49:44 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.