Difference between revisions of "Neutron/LBaaS/Glossary"
| Line 12: | Line 12: | ||
Object that represents an endpoint of load balancing device that has IP address.<br/> | Object that represents an endpoint of load balancing device that has IP address.<br/> | ||
In existing model it also has tcp port, protocol, session persistence setting. | In existing model it also has tcp port, protocol, session persistence setting. | ||
| + | Vip is plugged into a subnet, so as an object, it has subnet attribute. | ||
==== Pool ==== | ==== Pool ==== | ||
Object that represents a group of nodes. Pool defines subnet where nodes reside, balancing algorithm, nodes itself (indirectly)<br/> | Object that represents a group of nodes. Pool defines subnet where nodes reside, balancing algorithm, nodes itself (indirectly)<br/> | ||
| Line 17: | Line 18: | ||
==== Listener ==== | ==== Listener ==== | ||
==== Member ==== | ==== Member ==== | ||
| + | ==== Health Monitor ==== | ||
| + | ==== Loadbalancer ==== | ||
Revision as of 08:41, 24 March 2014
Root object
An object that represents a logical configuration.
It has certain features that are applied to it and spread to all it's depending objects such as:
* vendor or provider or flavor * admin state (Up or Down)
On implementation side there are some more attributes of that object
* insertion mode and insertion-specific parameters * backend binding information
Usually the workflow of creating operational configuration begins with creating the root object.
Vip
Object that represents an endpoint of load balancing device that has IP address.
In existing model it also has tcp port, protocol, session persistence setting.
Vip is plugged into a subnet, so as an object, it has subnet attribute.
Pool
Object that represents a group of nodes. Pool defines subnet where nodes reside, balancing algorithm, nodes itself (indirectly)
In existing LBaaS model Pool is the root object.
