Hide Forgot
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): openstack-tripleo-heat-templates-7.0.0-0.20170706121722.el7ost.noarch How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
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