Bug 1552441
Summary: | DVR enable should be the default configuration for OVN deployments with L3HA | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Eran Kuris <ekuris> |
Component: | documentation | Assignee: | RHOS Documentation Team <rhos-docs> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | RHOS Documentation Team <rhos-docs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 13.0 (Queens) | CC: | apevec, bhaley, dalvarez, ekuris, lbopf, lhh, majopela, nyechiel, samccann, srevivo |
Target Milestone: | --- | Keywords: | Triaged, ZStream |
Target Release: | 13.0 (Queens) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-06-28 15:22:14 UTC | Type: | Bug |
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: | |||
Bug Blocks: | 1548947 |
Description
Eran Kuris
2018-03-07 07:21:31 UTC
To clarify the description: On OVN DVR should be enabled by default with L3HA. It's effect on SNAT use case. SNAT - VM without floating IP access to the external network passes through Controller node. This is an ongoing discussion and the details need to be flushed out, being done on the mailing list currently. Most of the work will probably be in the TripleO component. Hi Nir, As a PM of OVN project, can we get your inputs about this BZ? (In reply to Eran Kuris from comment #3) > Hi Nir, > > As a PM of OVN project, can we get your inputs about this BZ? From a user point of view I think we should default to DVR. @Daniel, @Russell, do you see any reason why we should not? /Nir I think there's agreement on this, we need to update the deployment documents to point to that instead. Would that be enough in your opinion? It looks like we only need to update the documentation (also upstream). Moving to 'NEW' to allow proper scoping by the documentation team. |