canmove, Confirmed users
1,173
edits
Services/NodeAssignment: Difference between revisions
→DB Fields
(→Design) |
|||
| Line 70: | Line 70: | ||
<br>'''LDAP''' - The value to be written into the LDAP if this node is selected | <br>'''LDAP''' - The value to be written into the LDAP if this node is selected | ||
<br>'''Available''' - A count of remaining assignments available in this period. This value is not defined by nodeassigment and is simply set by the service at whatever period is desired. | <br>'''Available''' - A count of remaining assignments available in this period. This value is not defined by nodeassigment and is simply set by the service at whatever period is desired. | ||
<br>''' | <br>'''Current Load''' - Although it is not a direct reflection of users, it will be incremented by 1 for each user added. Services should set their weights according to how much impact they want each additional user to have to the algorithm | ||
<br>'''Capacity''' - The theoretical maximum weight to be associated with the node | <br>'''Capacity''' - The theoretical maximum weight to be associated with the node | ||
<br>'''Down''' - a binary value indicating whether a node is down. The node service makes this available via api, but it is expected that the service itself will be regularly checking the value. Users will not be assigned to a node that has been marked as down. | <br>'''Down''' - a binary value indicating whether a node is down. The node service makes this available via api, but it is expected that the service itself will be regularly checking the value. Users will not be assigned to a node that has been marked as down. | ||