openstack/senlin
Code Issues Proposed changes

Merge "Revise affinity policy doc for developer"

Browse Source
This commit is contained in:
Jenkins 2016-07-31 04:32:26 +00:00 committed by Gerrit Code Review
commit dc957c3ad0
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/source/developer/policies/affinity_v1.rst
View File

@ -41,6 +41,9 @@ The policy is capable of handling the following actions:
resize a cluster. The policy will try to parse the raw inputs if no other resize a cluster. The policy will try to parse the raw inputs if no other
policies have done this. policies have done this.
- ``NODE_CREATE``: an action originated from a node creation RPC request.
The policy is capable of processing the node associated with this action.
The policy will be checked **BEFORE** any of the above mentioned actions is The policy will be checked **BEFORE** any of the above mentioned actions is
executed. When the action is ``CLUSTER_RESIZE``, the affinity policy will executed. When the action is ``CLUSTER_RESIZE``, the affinity policy will
check if it is about the creation of new nodes. If the resize request is about check if it is about the creation of new nodes. If the resize request is about
@ -51,7 +54,7 @@ policies, if any. If no such data exists, it then checks the user-provided
"``count``" input if there is one. The policy is also designed to parse a "``count``" input if there is one. The policy is also designed to parse a
cluster resize request and see if there are new nodes to be created. cluster resize request and see if there are new nodes to be created.
After validating the ``count`` value, the deletion policy proceeds to update After validating the ``count`` value, the affinity policy proceeds to update
the ``data`` property of the action with node placement data. For example: the ``data`` property of the action with node placement data. For example:
:: ::