Bug 1530675
Summary: | [RFE] ovn-localnet: Connect OVN network and oVirt Data Center Network | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Petr Horáček <phoracek> |
Component: | ovirt-engine | Assignee: | Petr Horáček <phoracek> |
Status: | CLOSED ERRATA | QA Contact: | Michael Burman <mburman> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | apinnick, danken, lsurette, mburman, mkalfon, myakove, rbalakri, Rhev-m-bugs, srevivo, ykaul, ylavi |
Target Milestone: | ovirt-4.2.1 | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
You can now create an OVN network that is connected to a physical host network. This feature enables virtual machines on the external network to be on the same network as the virtual machines within the Data Center.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-15 17:46:56 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: | 1532046 | ||
Bug Blocks: | 1548816 |
Description
Petr Horáček
2018-01-03 16:00:39 UTC
The code for this feature is already in 4.2.1, and its feature page is approved. Burman has already started testing it. Formally moving to ON_QA. Feature page was merged and is available on https://ovirt.org/develop/release-management/features/network/provider-physical-network/ Verified on - 4.2.1.1-0.1.el7 NOTE - If the ovn network has it's own subnet, then the VM will get the IP from ovn network subnet and not from the phys network. In order to get the IP from the phys network, the ovn network should be without subnet. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:1488 BZ<2>Jira Resync |