# US 10,122,793 B2 · On-demand workload management in cloud bursting > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,122,793 B2 - Document ID: US10122793B2 - Status: Granted - Kind: B2 - Application number: 14/923,539 - Filed: 2015-10-27 - Published: 2017-04-27 - Granted: 2018-11-06 - Earliest claimed: 2015-10-27 - Assignees: International Business Machines Corporation - Applicants: International Business Machines Corporation - Inventors: Kai Liu; Kewei Sun; Di Xu; Xiao Zhong - Web page: https://patentgrep.com/patent/US10122793B2 ## CPC - H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] - H04L 67/1029: using data related to the state of servers by a load balancer - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A system, computer program product, and method is described to manage cloud bursting from a private cloud to a public cloud. The method starts with executing one or more software components of at least one application receiving transaction requests on at least one processing node accessing at least one database server. The one processing node is managed by at least one controller in a first deployment model of a computing infrastructure. The controller, the processing nodes and the database servers each include instrumentation for tracking of performance metrics thereof. A map is created of transaction requests received by the controller to data resources in the database by analyzing the set of common structures. The map is used to identify which of the software components and corresponding data resources in the database to move a processing node in a second deployment model of a computing infrastructure. ## Claims ### Claim 1 A computer-based method for on-demand workload management between a first deployment model of a computing infrastructure and a second deployment model of a computing infrastructure, the method comprising: executing one or more software components of at least one application receiving transaction requests on a first processing node accessing at least one file server with persistent data in at least one database, the first processing node is managed by at least one controller in a first deployment model of a computing infrastructure; performing enhanced transaction tracing analytics through use of instrumentation of the processing node and the file server for tracking which files in which table in which database in the first processing node in the file server are being requested; parsing the transaction requests tracked by the instrumentation into a set of common structures for analysis; creating a transaction-data map of transaction requests received by the controller to data resources in the file server by analyzing the set of common structures, the transaction-data map including a timestap, a method name, a table name in the at least one database, an inbound/outbound type with a source identifier; and using the transaction-data map with information from a load balancer and predefined weights assigned to the one or more software components to identify which of the the one or more software components and corresponding data resources in the file server to move over to a second processing node in a second deployment model of a computing infrastructure. ### Claim 2 (depends on 1) The computer-based method of claim 1, wherein the transaction requests are tracked using tokens and the file server is at least one database server, each of the tokens include a user identifier of a user, a thread identifier for a thread handling each of the transaction requests, a timestamp of each of the transaction requests, and name of at least one database table in the database server. ### Claim 3 (depends on 1) The computer-based method of claim 1, where in the first deployment model of a computing infrastructure is a private cloud. ### Claim 4 (depends on 3) The computer-based method of claim 3, where in the second deployment model of a computing infrastructure is a public cloud. ### Claim 5 (depends on 1) The computer-based method of claim 1, wherein the creating the transaction-data map includes creating the transaction-data map with a frequency of the inbound/outbound type with a souce identifier during a time period, and a response time to fulfill the the inbound/outbound type with a souce identifier of transaction. ### Claim 6 (depends on 5) The computer-based method of claim 5, wherein the creating the transaction-data map further includes creating the transaction-data map a settable weighting factor associated with each of the inbound/outbound type with a souce identifier for each of the transaction requests. ### Claim 7 (depends on 6) The computer-based method of claim 6, wherein using the transaction-data map includes identifying software components with lower frequency of the inbound/outbound type with a source identifier of each of the transaction requests during the time period. ### Claim 8 (depends on 1) The computer-based method of claim 1, further comprising: updating a load balancer configuration to redirect new transaction requests to the second processing node in the second deployment model of the computing infrastructure. ### Claim 9 A system for managing allocation of software components between a first deployment model of a computing infrastructure and a second deployment model of a computing infrastructure, the system comprising: a memory; a processor communicatively coupled to the memory, where the processor is configured to perform executing one or more software components of at least one application receiving transaction requests on a first processing node accessing at least one file server with persistent data in at least one database, the first processing node is managed by at least one controller in a first deployment model of a computing infrastructure; performing enhanced transaction tracing analytics through use of instrumentation of the processing node and the file server for tracking which files in which table in which database in the first processing node in the file server are being requested; parsing the transaction requests tracked by the instrumentation into a set of common structures for analysis; creating a transaction-data map of transaction requests received by the controller to data resources in the file server by analyzing the set of common structures, the transaction-data map including a timestap, a method name, a table name in the at least one database, an inbound/outbound type with a source identifier; and using the transaction-data map with information from a load balancer and predefined weights assigned to the one or more software components to identify which of the the one or more software components and corresponding data resources in the file server to move over to a second processing node in a second deployment model of a computing infrastructure. ### Claim 10 (depends on 9) The system of claim 9, wherein the transaction requests are tracked using tokens and the file server is at least one database server, each of the tokens include a user identifier of a user, a thread identifier for a thread handling each of the transaction requests, a timestamp of each of the transaction requests, and name of at least one database table in the database server. ### Claim 11 (depends on 9) The system of claim 9, where in the first deployment model of a computing infrastructure is a private cloud. ### Claim 12 (depends on 11) The system of claim 11, where in the second deployment model of a computing infrastructure is a public cloud. ### Claim 13 (depends on 9) The system of claim 9, the creating the transaction-data map includes creating the transaction-data map with a frequency of the inbound/outbound type with a souce identifier during a time period, and a response time to fulfill the the inbound/outbound type with a souce identifier of transaction. ### Claim 14 (depends on 13) The system of claim 13, wherein the creating the transaction-data map further includes creating the transaction-data map a settable weighting factor associated with each of the inbound/outbound type with a souce identifier for each of the transaction requests. ### Claim 15 (depends on 14) The system of claim 14, wherein using the transaction-data map includes identifying software components with lower frequency of the inbound/outbound type with a source identifier of transaction request during the time period. ### Claim 16 (depends on 9) The system of claim 9, further comprising: a load balancer being updated with a configuration to redirect new transaction requests to the second processing node in the second deployment model of the computing infrastructure. ### Claim 17 A non-transitory computer program product for managing allocation of software components between a first deployment model of a computing infrastructure and a second deployment model of a computing infrastructure, the computer program product comprising a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code configured to perform: executing one or more software components of at least one application receiving transaction requests on a first processing node accessing at least one file server with persistent data in at least one database, the first processing node is managed by at least one controller in a first deployment model of a computing infrastructure; performing enhanced transaction tracing analytics through use of instrumentation of the processing node and the file server for tracking which files in which table in which database in the first processing node in the file server are being requested; parsing the transaction requests tracked by the instrumentation into a set of common structures for analysis; creating a transaction-data map of transaction requests received by the controller to data resources in the file server by analyzing the set of common structures, the transaction-data map including a timestap, a method name, a table name in the at least one database, an inbound/outbound type with a source identifier; and using the transaction-data map with information from a load balancer and predefined weights assigned to the one or more software components to identify which of the the one or more software components and corresponding data resources in the file server to move over to a second processing node in a second deployment model of a computing infrastructure. ### Claim 18 (depends on 17) The computer program product of claim 17, wherein the transaction requests are tracked using tokens and the file server is at least one database server, each of the tokens include a user identifier of a user, a thread identifier for a thread handling each of the transaction requests, a timestamp of each of the transaction requests, and name of at least one database table in the database server. ### Claim 19 (depends on 17) The computer program product of claim 17, where in the first deployment model of a computing infrastructure is a private cloud. ### Claim 20 (depends on 19) The computer program product of claim 19, where in the second deployment model of a computing infrastructure is a public cloud.