openstack/tripleo-docs
Code Issues Proposed changes

Document profile and node placement redundancy

Browse Source 
It is unnecessary and unwise to use both profile matching and
predictable node placement in the same deployment.  This change
adds a note explaining that.

Closes-Bug: #1565844

Change-Id: Ia24158f2b3779e3f20bbf5fedaef4e18e4270ee8
Signed-off-by: Cyril Lopez <cylopez@redhat.com>
This commit is contained in:
Cyril Lopez 2016-04-04 17:24:16 +02:00 committed by Ben Nemec
parent 5d098fabd0
commit fcbcc1c4e3
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/source/advanced_deployment/node_placement.rst
View File

@ -31,6 +31,11 @@ If this approach is used, all nodes for a given role (e.g Controller, Compute
or each of the Storage roles) must be tagged in the same way, or the Nova
scheduler will be unable to match the capabilities correctly.
.. note:: Profile matching is redundant when precise node placement is used.
To avoid scheduling failures you should use the default "baremetal"
flavor for deployment in this case, not the flavors designed for
profile matching ("compute", "control", etc).
Create an environment file with Scheduler Hints
----------------------------------------------