Bug 1473316
Summary: | [HA] TripleO should support Node replacement of OpenDaylight controller | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Itzik Brown <itbrown> |
Component: | puppet-tripleo | Assignee: | Janki <jchhatba> |
Status: | CLOSED ERRATA | QA Contact: | Itzik Brown <itbrown> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 12.0 (Pike) | CC: | itbrown, jchhatba, jcoufal, jjoyce, jschluet, lpeer, lruzicka, nyechiel, oblaut, slinaber, trozet, tvignaud |
Target Milestone: | ga | Keywords: | TestOnly, Triaged |
Target Release: | 12.0 (Pike) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: |
N/A
|
|
Last Closed: | 2017-12-13 21:43:17 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: | 1414313 |
Description
Itzik Brown
2017-07-20 13:11:11 UTC
Itzik, have you discussed this with Tim? Is there an upstream bug for this? No,I'll discuss it with him. The document for Node replacement: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_openstack_platform/7/html/director_installation_and_usage/sect-replacing_controller_nodes After reading the instructions I believe that this method with OpenDaylight as a service on the controller should just work. ODL is not managed by pacemaker and does not rely on the other services that require manual intervention. The puppet-opendaylight module should fix the config files to use the new node as part of the cluster and restart all ODLs during the update. That means there is likely < 5 min of downtime for ODL during the operation, but dataplane should remain up. 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-2017:3462 |