openstack
/
tripleo-docs
Code Issues Proposed changes

Predictable IPs, no resource_registry override 

Support for predictable IP addressing added to the
default port templates in Rocky. The resource
registry overrides are removed the depends-on.

Change-Id: Ib9410e6f6415d3f91a477414930a236f1dc284c8
Related-Bug: #1866215
Depends-On: https://review.opendev.org/711537
This commit is contained in:
Harald Jensås 2020-03-05 18:22:02 +01:00
parent c7db6069d6
commit 144e4d8e75
1 changed files with 7 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
deploy-guide/source/provisioning/node_placement.rst
View File

@ -112,21 +112,13 @@ Be sure to make a local copy of ``/usr/share/openstack-tripleo-heat-templates``
before making changes so the packaged files are not altered, as they will
be overwritten if the package is updated.
In ``ips-from-pool-all.yaml`` there are two major sections. The first is
a number of resource_registry overrides that tell TripleO you want to use
a specific IP for a given port on a node type. By default, this environment
sets all the default networks on all node types to use a pre-assigned IP.
To allow a particular network or node type to use default IP assignment instead,
simply remove the resource_registry entries related to that node type/network
from the environment file.
The second section is parameter_defaults, where the actual IP addresses are
assigned. Each node type has an associated parameter - ControllerIPs for
Controller nodes, ComputeIPs for Compute nodes, etc. Each parameter is
a map of network names to a list of addresses. Each network type must have
at least as many addresses as there will be nodes on that network. The
addresses will be assigned in order, so the first node of each type will get
the first address in each of the lists, the second node will get the second
The parameter_defaults section in ``ips-from-pool-all.yaml``, is where the IP
addresses are assigned. Each node type has an associated parameter -
ControllerIPs for Controller nodes, ComputeIPs for Compute nodes, etc. Each
parameter is a map of network names to a list of addresses. Each network type
must have at least as many addresses as there will be nodes on that network.
The addresses will be assigned in order, so the first node of each type will
get the first address in each of the lists, the second node will get the second
address in each of the lists, and so on.
For example, if three Ceph storage nodes were being deployed, the CephStorageIPs