Bug 1366899 - [RFE][Tech-Preview] - overlay networks using OVN: allow to define virtual networks that can be encapsulated between hosts on nicless networks
Summary: [RFE][Tech-Preview] - overlay networks using OVN: allow to define virtual net...
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.0.0
Hardware: x86_64
OS: Linux
Target Milestone: ovirt-4.1.0-alpha
: ---
Assignee: Marcin Mirecki
QA Contact: Mor
Depends On: OpenVswitch_Support 1362495 1368043 1369362 1386514 1390938 1394555 1397502 1397504 1416748 1475772 1477658 1496194
Blocks: 988285 overlay_networks_support 1420169
TreeView+ depends on / blocked
Reported: 2016-08-14 12:08 UTC by Yaniv Lavi
Modified: 2019-04-28 14:05 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
This release adds support for overlay networks using Open Virtual Network (OVN) as a Technology Preview. This feature allows you to add OVN as an external network provider, and import or create networks from it in the Red Hat Virtualization Manager. You can then provision virtual machines with network interfaces connected using these logical overlays (OVN networks).
Clone Of: overlay_networks_support
Last Closed: 2017-02-15 15:01:22 UTC
oVirt Team: Network
ylavi: ovirt-4.1?
bmcclain: priority_rfe_tracking+
mkalfon: testing_plan_complete+
rule-engine: planning_ack?
danken: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)

Description Yaniv Lavi 2016-08-14 12:08:03 UTC
+++ This bug was initially created as a clone of Bug #1254213 +++

Description of problem:

It would be very useful to be able to define virtual networks encapsulated a-la OSP,  where not mapped networks to existing physical nics on hosts, could allows vm's to communicate between each other while isolating traffic.

This could allow to define set of vm's with backend/frontend networks with Vm's on different hosts .

Comment 1 Mor 2016-11-22 14:12:39 UTC
As per our last OVN session:
In oVirt engine, when we try to create OVN network subnet, without specifying IP gateway, the engine throws unfriendly (generic) error. In the background, OVN provider throws exception for missing IP gateway. In Neutron, the behaviour is different. We don't need to specify a gateway and it is calculated from the given CIDR. If we don't want to handle this scenario, we should at least document that the provider requires IP gateway address.

Comment 2 Mor 2017-01-18 09:49:23 UTC
Verified on version:

Comment 3 Tahlia Richardson 2017-02-06 08:04:29 UTC
I've added doc text appropriate for a release note based on the text in the feature page. Marcin, can you please check that it is correct? 

I'll create a docs bug with the links from the original doc text shortly.

Comment 4 Marcin Mirecki 2017-02-06 09:47:08 UTC
" and import networks from it to Red Hat Virtualization"

We can both import networks, or create new ones from RHV.
Maybe something like: ", import network into RHV, or create new external OVN networks from RHV"

"You can then define logical overlays"

I would say a network represents a logical overlay.
Maybe: "You can then use these logical overlays (OVN networks) to provision ..."

Comment 5 Tahlia Richardson 2017-02-07 00:00:55 UTC
Thanks Marcin. Text updated.

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