Jamie Hannaford | 8cdaa80 | 2014-11-03 15:11:39 +0100 | [diff] [blame] | 1 | /* |
| 2 | Package nodes provides information and interaction with the Node API resource |
| 3 | for the Rackspace Cloud Load Balancer service. |
| 4 | |
| 5 | Nodes are responsible for servicing the requests received through the load |
| 6 | balancer's virtual IP. A node is usually a virtual machine. By default, the |
| 7 | load balancer employs a basic health check that ensures the node is listening |
| 8 | on its defined port. The node is checked at the time of addition and at regular |
| 9 | intervals as defined by the load balancer's health check configuration. If a |
| 10 | back-end node is not listening on its port, or does not meet the conditions of |
| 11 | the defined check, then connections will not be forwarded to the node, and its |
| 12 | status is changed to OFFLINE. Only nodes that are in an ONLINE status receive |
| 13 | and can service traffic from the load balancer. |
| 14 | |
| 15 | All nodes have an associated status that indicates whether the node is |
| 16 | ONLINE, OFFLINE, or DRAINING. Only nodes that are in ONLINE status can receive |
| 17 | and service traffic from the load balancer. The OFFLINE status represents a |
| 18 | node that cannot accept or service traffic. A node in DRAINING status |
| 19 | represents a node that stops the traffic manager from sending any additional |
| 20 | new connections to the node, but honors established sessions. If the traffic |
| 21 | manager receives a request and session persistence requires that the node is |
| 22 | used, the traffic manager uses it. The status is determined by the passive or |
| 23 | active health monitors. |
| 24 | |
| 25 | If the WEIGHTED_ROUND_ROBIN load balancer algorithm mode is selected, then the |
| 26 | caller should assign the relevant weights to the node as part of the weight |
| 27 | attribute of the node element. When the algorithm of the load balancer is |
| 28 | changed to WEIGHTED_ROUND_ROBIN and the nodes do not already have an assigned |
| 29 | weight, the service automatically sets the weight to 1 for all nodes. |
| 30 | |
| 31 | One or more secondary nodes can be added to a specified load balancer so that |
| 32 | if all the primary nodes fail, traffic can be redirected to secondary nodes. |
| 33 | The type attribute allows configuring the node as either PRIMARY or SECONDARY. |
| 34 | */ |
Jamie Hannaford | b6927c1 | 2014-11-03 10:31:26 +0100 | [diff] [blame] | 35 | package nodes |