Services/NodeAssignment: Difference between revisions

Services/NodeAssignment (view source)

221 bytes removed , 3 May 2011

canmove, Confirmed users

1,173

edits

@@ Line 70: / Line 70: @@
 <br>'''Node''' - The specific node in the cluster that a user is assigned to
 <br>'''LDAP''' - The value to be written into the LDAP if this node is selected
-<br>'''Max per period''' - The maximum number of users that should be assigned to this node. Once current-per-period is equal to max, no users will be assigned to the node. Period is undefined by the service and is simply set by the frequency with which the current-in-period value is zeroed.
+<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>'''Current in period''' - A count of users who have been assigned to this node since the value was last reset.
 <br>'''Weight''' - 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