Bug 1473316 - [HA] TripleO should support Node replacement of OpenDaylight controller
Summary: [HA] TripleO should support Node replacement of OpenDaylight controller
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
Target Milestone: ga
: 12.0 (Pike)
Assignee: Janki
QA Contact: Itzik Brown
Depends On:
Blocks: 1414313
TreeView+ depends on / blocked
Reported: 2017-07-20 13:11 UTC by Itzik Brown
Modified: 2018-10-18 07:21 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 21:43:17 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Itzik Brown 2017-07-20 13:11:11 UTC
Description of problem:
There is a procedure to replace an OpenStack controller node but not one for 
OpenDaylight controller.
TripleO should support this case.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Nir Yechiel 2017-07-20 18:04:05 UTC
Itzik, have you discussed this with Tim? Is there an upstream bug for this?

Comment 2 Itzik Brown 2017-07-23 07:35:07 UTC
No,I'll discuss it with him.

Comment 10 Tim Rozet 2017-08-18 16:18:00 UTC
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.

Comment 22 errata-xmlrpc 2017-12-13 21:43:17 UTC
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.


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