Bug 1433533 (ovn_faulttolerance)
| Summary: | [RFE] [Neutron] [OVN] Fault tolerant ML2 -> OVN synchronization | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Assaf Muller <amuller> |
| Component: | python-networking-ovn | Assignee: | Lucas Alvares Gomes <lmartins> |
| Status: | CLOSED ERRATA | QA Contact: | Eran Kuris <ekuris> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 12.0 (Pike) | CC: | amuller, apevec, chrisw, dalvarez, ekuris, jlibosva, lhh, lmartins, majopela, mlopes, nyechiel, oblaut, samccann, sclewis, srevivo |
| Target Milestone: | Upstream M3 | Keywords: | FutureFeature, Triaged |
| Target Release: | 13.0 (Queens) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-networking-ovn-4.0.0-0.20180211021409.329d6d8.el7ost | Doc Type: | Enhancement |
| Doc Text: |
To help maintain consistency between the neutron and OVN databases, configuration changes are internally compared and verified in the backend. Each configuration change is assigned a revision number, and a scheduled task validates all create, update, and delete operations made to the databases.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-06-27 13:29:18 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: | 1498491, 1548947 | ||
|
Description
Assaf Muller
2017-03-17 23:16:03 UTC
Spec not yet posted, pushing to milestone 3. We need to sync with QE to prepare a testing plan for this, we could potentially reuse (as @nyechiel suggested) the ODL testing plans for this feature. (In reply to Miguel Angel Ajo from comment #10) > We need to sync with QE to prepare a testing plan for this, we could > potentially reuse (as @nyechiel suggested) the ODL testing plans for this > feature. Miguel, If its same test cases as ODL it will be easy to reuse the ODL testing plans for this feature. can you review the ODL testing plans to make sure its relevant to OVN? Following up with the weekly OSP networking call (Dec. 04 2017). The specification detailing the problem and proposing a solution for this problem can be found at: https://review.openstack.org/#/c/490834/ (Added to external references as well) This is the series of patches related to the FFE: https://review.openstack.org/#/q/topic:bug/1605089+(status:open+OR+status:merged) Backporting the functional tests that are run upstream to exercise the maintenance task [0], this is needed so that we can verify this RFE. [0] https://code.engineering.redhat.com/gerrit/#/c/137302/ Verified: [heat-admin@controller-0 ~]$ sudo rpm -qa | grep python-networking-ovn- python-networking-ovn-4.0.1-0.20180420150809.c7c16d4.el7ost.noarch (undercloud) [stack@undercloud-0 ~]$ cat /etc/yum.repos.d/latest-installed 13 -p 2018-05-02.5 Test run: https://polarion.engineering.redhat.com/polarion/#/project/RHELOpenStackPlatform/testrun?id=20180503-0655 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:2086 |