Bug 1314375

Summary: [RFE] - Provide external network partners API
Product: [oVirt] ovirt-engine Reporter: Yaniv Lavi <ylavi>
Component: RFEsAssignee: Marcin Mirecki <mmirecki>
Status: CLOSED CURRENTRELEASE QA Contact: Meni Yakove <myakove>
Severity: high Docs Contact:
Priority: high    
Version: 3.6.0CC: bugs, danken, gklein, juwu, mburman, mmirecki, sbonazzo
Target Milestone: ovirt-4.0.0-betaKeywords: FutureFeature
Target Release: 4.0.0Flags: rule-engine: ovirt-4.0.0+
ylavi: priority_rfe_tracking+
myakove: testing_plan_complete+
ylavi: planning_ack+
danken: devel_ack+
myakove: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Previously, to use external network providers, only OpenStack Networking (Neutron) is supported. With this update, any external network provider that implements the OpenStack Neutron REST API can be added to Red Hat Virtualization. The external network provider does not use the Neutron agent as the virtual interface driver implementation on the host. Instead, the virtual interface driver should be provided by the implementer of the external network provider. A read-only feature is also available to prevent users from modifying the external network provider from the Manager.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-05 07:41:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1216991, 1255620, 1314371, 1316021, 1317581, 1318543    
Bug Blocks: 1353388    

Description Yaniv Lavi 2016-03-03 13:20:31 UTC 
Description of problem:
Currently the Openstack Neutron integration allows oVirt to integrate with Openstack Neutron. This purpose of this feature is to simplify this to make it easier to add support for networks supplied by external providers. The providers will be able to provide networks using a simplified Neutron-like API.

Many organizations use centralized network management systems to handle all their networking, and would like them to manage the network topology of their oVirt environments. Currently the only option of using external networks in oVirt is to used the OpenStack Neutron integration, which allows the import of OpenStack Neutron networks and the provisioning of VM's connected to these networks. This feature is however very specific to OpenStack Neutron. We would like to extend this API to other external network providers, by making it simpler, more general and less dependant on OpenStack Neutron features. The result should be an API over which oVirt can communicate with external network management systems, and use the networks defined in them in provisioned VMs.
Comment 1 Dan Kenigsberg 2016-03-27 11:42:44 UTC 
Marcin, please add relevant patches to this RFE.
Comment 2 Sandro Bonazzola 2016-05-02 09:49:58 UTC 
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
Comment 3 Michael Burman 2016-06-29 08:35:47 UTC 
Verified on - 4.0.0.6-0.1.el7ev and vdsm-4.18.4-2.el7ev.x86_64 using Marcin's latest mock-provider and vif-driver RPMs.

vdsmdummy-driver-0-1.noarch
provider-mock-0-1.noarch 

- NOTE, each provider should provide an information about the required iptables rule/port.
Comment 4 Sandro Bonazzola 2016-07-05 07:41:14 UTC 
oVirt 4.0.0 has been released, closing current release.