Description of problem: 1. Is there a way to replace the controller node and keep the same index? 2. Same question for a compute node. The documentation [1] does not explicitly cover the case of replacing a networking node. Can we use the same procedure used for compute nodes? [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/director_installation_and_usage/sect-scaling_the_overcloud#sect-Replacing_Compute_Nodes
Hi, Question No. 1 was already answered in BZ 1384301 (there is no way to reuse an index entry). So, let's focus on the last question - there is no documentation for replacing netoworker node. Aviv
I have an initial draft in asciidoc ready for review next week.
In order to verify this Doc Bug, In any documentation we would need to address -> https://bugzilla.redhat.com/show_bug.cgi?id=1600178 (or to find a Fix/Solution to this bug) see Bz dependency
Created attachment 1490903 [details] Proposed Networker Node Replacement Doc Please review the proposed doc and comment.
Created attachment 1496892 [details] Networker Node Replacement Procedure for Telecom Italia This is a tar.gz archive of the procedure for replacing a Networker node for RHEL OSP 10. It requires the hotfix for for Bugzilla #1600178.
Created attachment 1497583 [details] Networker Node Replacement Procedure for Telecom Italia Networker Node Replacement Procedure for Telecom Italia This is a tar.gz archive of the procedure for replacing a Networker node for RHEL OSP 10. It requires the hotfix for for Bugzilla #1600178. This tar.gz replaces the preceding one and has the following changes: it adds steps for adding a new node, and introspection. It also provides hyperlinks to other relevant sections of the documentation. tar -xzf to unzip.