From f89bd03171b01e557beb315e737e37d057ddd76b Mon Sep 17 00:00:00 2001 From: Ben Nemec Date: Thu, 7 Sep 2017 22:00:49 +0000 Subject: [PATCH] Clarify predictable ip behavior for deleted nodes Entries should never be removed from the predictable ip lists, even if a node is deleted. This is because the index into the list is based on the Heat resource index, which doesn't change when a node is deleted. This has come up a number of times in real-world deployments so we should make this behavior clear in the docs. Change-Id: I455a1e15bfc3cef07f6fd3c8462428985f12c0da --- .../install/advanced_deployment/node_placement.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/doc/source/install/advanced_deployment/node_placement.rst b/doc/source/install/advanced_deployment/node_placement.rst index be6e657b..2ff99c03 100644 --- a/doc/source/install/advanced_deployment/node_placement.rst +++ b/doc/source/install/advanced_deployment/node_placement.rst @@ -132,6 +132,16 @@ The first Ceph node would have two addresses: 172.16.1.100 and 172.16.3.100. Th second would have 172.16.1.101 and 172.16.3.101, and the third would have 172.16.1.102 and 172.16.3.102. The same pattern applies to the other node types. +.. important:: + Even if an overcloud node is deleted, its entry in the IP lists should + *not* be removed. The IP list is based on the underlying Heat indices, + which do not change even if nodes are deleted. To indicate that a given + entry in the list is no longer used, the IP value can be replaced with a + value such as "DELETED" or "UNUSED". + + In short, entries should never be removed from the IP lists, only changed + or added. + To apply this configuration during a deployment, pass the environment file to the deploy command. For example, if you copied tripleo-heat-templates to ~/my-templates, the extra parameter would look like::