DNS-based in-packet service version tagging
地域：
NY
NY Armonk
摘要
Embodiments of the present communications systems and methods may provide the capability for fast and reliable transitioning between the different versions of the service of the multi-node service deployed in the utility computing system. For example, in an embodiment, a computer-implemented method for data traffic distribution may comprise allocating a plurality of data traffic service network addresses to a load balancer service, wherein each data traffic service network address is associated with a different version of the load balancer service, receiving a plurality of data traffic flows, and distributing each data traffic flow to a version of the load balancer service based on a data traffic service network address of each data traffic flow.
說明書
The present invention relates to techniques for data traffic distribution by allocating data traffic service network addresses to a load balancer service, wherein each data traffic service network address is associated with a different version of the load balancer service including, in a broader sense of version, changes such as configuration changes, node upgrades, and elastic changes to the service pool size of the service, etc.
In utility computing environments such as cloud computing environments, it is advantageous to ensure the services can elastically grow and shrink according to the load imposed by their clients. When the load goes up, the system should adapt by allocating more resources and increasing the service capacity so that clients do not experience disturbances due to the increased load. When the load goes down, the system should adapt by timely releasing the unneeded resources to reduce the overall operational costs and/or improve the overall resource utilization by assigning the resources elsewhere.
Service elasticity is typically implemented through a scalable pool of service nodes, wherein nodes are added and removed to align allocated capacity to the total demand. An additional entity, a load balancer, may be installed to receive client requests and to multiplex them among the nodes in the service pool.
權(quán)利要求
What is claimed is:1. A computer-implemented method for data traffic distribution comprising:allocating a plurality of publicly-accessible data traffic service network addresses to a load balancer service comprising a plurality of load balancing nodes, wherein each publicly-accessible data traffic service network address is associated with a different version of the load balancer service and with a plurality of back-end pool nodes, wherein each different version of the load balancer service comprises a change in a number of load balancing nodes, a change in a number of back-end pool nodes, or both; receiving a plurality of data traffic flows; distributing each data traffic flow to a version of the load balancer service based on a publicly-accessible data traffic service network address of each data traffic flow, wherein each version of the load balancer service distributes data traffic to the plurality of back-end pool nodes associated with each version of the load balancer service; and transitioning to a first version of the load balancer service by allocating a publicly-accessible data traffic service network address associated with the first version of the load balancer service, and when a second version of the load balancer service has no more old in-progress connections, de-allocating a publicly-accessible data traffic service network address associated with the second version of the load balancer service. 2. The method of claim 1 , further comprising:de-allocating a publicly-accessible data traffic service network address associated with a version of the load balancer service. 3. The method of claim 2 , wherein the allocated publicly-accessible data traffic service network addresses are registered in a Domain Name server. 4. The method of claim 1 , wherein a configuration of each version of the load balancer service includes a set of data traffic flow rules. 5. The method of claim 4 , wherein the data traffic flow rules are configured in a traffic distributor. 6. The method of claim 5 , wherein the traffic flow rules are OpenFlow rules. 7. A system for data traffic distribution, the system comprising:at least one Domain Name server storing an allocation of a plurality of publicly-accessible data traffic service network addresses to a load balancer service comprising a plurality of load balancing nodes, wherein each publicly-accessible data traffic service network address is associated with a different version of the load balancer service and with a plurality of back-end pool nodes, wherein each different version of the load balancer service comprises a change in a number of load balancing nodes, a change in a number of back-end pool nodes, or both; and at least one traffic distributor receiving a plurality of data traffic flows and distributing each data traffic flow to a version of the load balancer service based on a publicly-accessible data traffic service network address of each data traffic flow, wherein each version of the load balancer service distributes data traffic to the plurality of back-end pool nodes associated with each version of the load balancer service, wherein the system is further configured to transition a first version of the load balancer service by allocating a publicly-accessible data traffic service network address associated with the first version of the load balancer service and registering the allocated publicly-accessible data traffic service network address in the at least one Domain Name server, and when a second version of the load balancer service has no more old in-progress connections, de-allocating a publicly-accessible data traffic service network address associated with the second version of the load balancer service. 8. The system of claim 7 , further comprising:replacing in the at least one Domain Name server a publicly-accessible data traffic service network address associated with an old version of the load balancer service with a publicly-accessible data traffic service network address associated with a new version of the load balancer service. 9. The system of claim 7 , wherein a configuration of each version of the load balancer service comprises a set of data traffic flow rules in the at least one traffic distributor. 10. The system of claim 9 , wherein the traffic flow rules are OpenFlow rules. 11. A computer program product for data traffic distribution, the computer program product comprising a non-transitory computer readable storage having program instructions embodied therewith, the program instructions executable by a computer, to cause the computer to perform a method comprising:allocating a plurality of publicly-accessible data traffic service network addresses to a load balancer service comprising a plurality of load balancing nodes, wherein each publicly-accessible data traffic service network address is associated with a different version of the load balancer service and with a plurality of back-end pool nodes, wherein each different version of the load balancer service comprises a change in a number of load balancing nodes, a change in a number of back-end pool nodes, or both; receiving a plurality of data traffic flows; distributing each data traffic flow to a version of the load balancer service based on a publicly-accessible data traffic service network address of each data traffic flow, wherein each version of the load balancer service distributes data traffic to the plurality of back-end pool nodes associated with each version of the load balancer service; and transitioning to a first version of the load balancer service by allocating a publicly-accessible data traffic service network address associated with the first version of the load balancer service, and when a second version of the load balancer service has no more old in-progress connections, de-allocating a publicly-accessible data traffic service network address associated with the second version of the load balancer service. 12. The computer program product of claim 11 , further comprising program instructions for:de-allocating a publicly-accessible data traffic service network address associated with a version of the load balancer service. 13. The computer program product of claim 12 , wherein the allocated publicly-accessible data traffic service network addresses are registered in a Domain Name server. 14. The computer program product of claim 11 , wherein a configuration of each version of the load balancer service includes a set of data traffic flow rules. 15. The computer program product of claim 14 , wherein the data traffic flow rules are configured in a traffic distributor. 16. The method of claim 15 , wherein the traffic flow rules are OpenFlow rules.
意見反饋
使用該功能遇到問題