US20200127897A1 - Automated nondisruptive merge of management systems - Google Patents
Automated nondisruptive merge of management systems Download PDFInfo
- Publication number
- US20200127897A1 US20200127897A1 US16/166,508 US201816166508A US2020127897A1 US 20200127897 A1 US20200127897 A1 US 20200127897A1 US 201816166508 A US201816166508 A US 201816166508A US 2020127897 A1 US2020127897 A1 US 2020127897A1
- Authority
- US
- United States
- Prior art keywords
- management system
- new
- server
- request server
- computer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 claims abstract description 50
- 238000004891 communication Methods 0.000 claims description 41
- 230000004044 response Effects 0.000 claims description 24
- 238000004590 computer program Methods 0.000 claims description 16
- 238000007726 management method Methods 0.000 description 262
- 238000010586 diagram Methods 0.000 description 22
- 230000006870 function Effects 0.000 description 10
- 238000012545 processing Methods 0.000 description 9
- 230000008569 process Effects 0.000 description 8
- 230000008901 benefit Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 4
- 239000000203 mixture Substances 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 2
- 239000000872 buffer Substances 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 230000001902 propagating effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000013519 translation Methods 0.000 description 2
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 229910052802 copper Inorganic materials 0.000 description 1
- 239000010949 copper Substances 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000001627 detrimental effect Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 230000008521 reorganization Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06312—Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
- H04L41/0856—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information by backing up or archiving configuration information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0876—Aspects of the degree of configuration automation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
- H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
Definitions
- the present invention relates to management systems and, more specifically, to an automated nondisruptive merge of management systems.
- a management system is a type of computer system, which may be distributed, used to manage the resources of an organization, perform services, and generally perform various other tasks needed by the organization.
- a management system may be distributed, used to manage the resources of an organization, perform services, and generally perform various other tasks needed by the organization.
- multiple organizations might exist, and each might have its own management system. Thus, not only are there multiple management systems across enterprises, but there are often multiple management systems within an enterprise.
- Merging management systems may also be desirable when merging enterprises or when revamping how computing resources are obtained, allocated, or accounted.
- Embodiments of the present invention are directed to a computer-implemented method for updating a management system.
- a non-limiting example of the computer-implemented method includes generating a new management application based on a first management application, where the first management application operates a first management system.
- a first set of resources of the first management system are assigned to the new management application, where the first set of resources support a first request server and a first worker server.
- a new worker server of the new management system is started, where the new worker server utilizes the first set of resources of the first management system.
- the first request server is instructed to send a first set of future requests of the first request server to the new worker server.
- the first request server is further instructed to redirect a remainder of the future requests of the first request server to a new request server of the new management application.
- the new management application operates a new management system based on the first management system.
- Embodiments of the present invention are directed to a system for updating a management system.
- a non-limiting example of the system includes a memory having computer-readable instructions and one or more processors for executing the computer-readable instructions.
- the computer-readable instructions include generating a new management application based on a first management application, where the first management application operates a first management system. Further according to the computer-readable instructions, a first set of resources of the first management system are assigned to the new management application, where the first set of resources support a first request server and a first worker server.
- a new worker server of the new management system is started, where the new worker server utilizes the first set of resources of the first management system.
- the first request server is instructed to send a first set of future requests of the first request server to the new worker server.
- the first request server is further instructed to redirect a remainder of the future requests of the first request server to a new request server of the new management application.
- the new management application operates a new management system based on the first management system.
- Embodiments of the invention are directed to a computer-program product for updating a management system, the computer-program product including a computer-readable storage medium having program instructions embodied therewith.
- the program instructions are executable by a processor to cause the processor to perform a method.
- a non-limiting example of the method includes generating a new management application based on a first management application, where the first management application operates a first management system. Further according to the method, a first set of resources of the first management system are assigned to the new management application, where the first set of resources support a first request server and a first worker server. A new worker server of the new management system is started, where the new worker server utilizes the first set of resources of the first management system.
- the first request server is instructed to send a first set of future requests of the first request server to the new worker server.
- the first request server is further instructed to redirect a remainder of the future requests of the first request server to a new request server of the new management application.
- the new management application operates a new management system based on the first management system.
- FIG. 1 is a diagram of a merger system according to some embodiments of the invention.
- FIG. 2 is a diagram of a management system according to some embodiments of the invention.
- FIG. 3 is a flow diagram of a method of creating a new management system, according to some embodiments of the invention.
- FIG. 4 is a flow diagram of a method of merging two or more management systems, according to some embodiments of the invention.
- FIG. 5 is a block diagram of a computer system for implementing some or all aspects of the merger system, according to some embodiments of this invention.
- compositions comprising, “comprising,” “includes,” “including,” “has,” “having,” “contains” or “containing,” or any other variation thereof, are intended to cover a non-exclusive inclusion.
- a composition, a mixture, process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but can include other elements not expressly listed or inherent to such composition, mixture, process, method, article, or apparatus.
- exemplary is used herein to mean “serving as an example, instance or illustration.” Any embodiment or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs.
- the terms “at least one” and “one or more” may be understood to include any integer number greater than or equal to one, i.e., one, two, three, four, etc.
- the terms “a plurality” may be understood to include any integer number greater than or equal to two, i.e., two, three, four, five, etc.
- connection may include both an indirect “connection” and a direct “connection.”
- a conventional management system views itself as the only management system that exists and is thus not optimized for the merger.
- merger generally requires manual intervention, which is slow and error-prone.
- manual merger requires the management systems involved to go offline until the merger is complete, which can be detrimental to normal operations.
- One way to address mergers is to splice code into a running management application of a management system. In practical terms, this means the management application must be architected specifically to enable splicing, which increases the cost of service. Further, if a splice must occur at an unexpected location within the code, then once again, manual intervention is required, and the management systems involved go offline.
- each management system includes a management application and a set of resources, as well as a request server, a worker server, and a response server operated through the management application.
- a new management application may be created based on first and second management applications belonging to first and second management systems, respectively, to be merged.
- the new management application may be given access to the resources of the first and second management applications, and the request servers, worker servers, and response servers of the new management application may gradually take over operations of the first and second management applications, as will be described herein.
- the above-described aspects of the invention address the shortcomings of the prior art by defining an improved mechanism of merging two or more management systems that utilize a new format of a management system.
- the merger process is automated, and services do not need to go offline while management systems are being merged.
- the code in management applications does not need to be architected to enable splicing, and human error is reduced or eliminated.
- FIG. 1 is a diagram of a merger system 100 according to some embodiments of the invention.
- the merger system 100 applies to two or more management systems 150 , each of which may be a computer system 105 , which may be physical, virtual, distributed, or a combination thereof.
- the management systems 150 may be administered through an administration system 101 , which may be in communication with the merger system 100 .
- the merger system 100 may be integrated into the administration system 101 , such that the administration system 101 may be configured to merge management systems 150 through use of the merger system 100 as described herein.
- the administration system 101 may manage a set of computer systems 105 , and the management systems 150 may utilize resources of such computer systems 105 .
- Each management system 150 may be associated with a configuration file 155 .
- the management systems 150 and the respective configuration files 155 will be described in more detail below.
- the merger system 100 may take as input a respective configuration file 155 of each management system 150 to be merged, as well as a prospective configuration file 155 of a new management system 150 to result from the merger.
- the merger system 100 may include a combination unit 110 and a migrator 120 .
- the combination unit 110 may determine how to combine the respective configuration files 155 of the existing management systems 150 to result in the prospective configuration file 155 , and the combination unit 110 may thus identify and remove any redundancies across the existing management systems 150 .
- the migrator 120 may migrate resources managed by the existing management system 150 to the final management system 150 , such as by updating permissions of the resources.
- Each of the combination unit 110 and the migrator 120 may include hardware, software, or a combination of both. For instance, each of these components may be a software module or a specialized hardware device.
- the combination unit 110 and the migrator 120 are illustrated and described herein as being distinct, it will be understood that this distinction is for illustrative purposes only, and these components may be integrated together or further divided.
- FIG. 2 is a diagram of a management system 150 according to some embodiments of the invention. More specifically, each management system 150 may include, or be otherwise associated with, a configuration file 155 . Each management system 150 may also include a management application 220 , also referred to as an instance of a management application or a management application instance, and set of resources. The set of resources may include one or more of the following: a set of included resources 230 , a set of managed resources 240 , and a set of potential resources 250 .
- the configuration file 155 of a management system 150 describes aspects of the management system 150 , such as the included resources 230 , the managed resources 240 , the potential resources 250 , and the communication layer 290 .
- the management application 220 has exclusive write access to its respective configuration file 155 , included resources 230 , managed resources 240 , and potential resources, as well as read access to the configuration files 155 of other management systems 150 .
- the management application 220 may enable an administrator of the management system 150 to access and utilize the associated resources of the management system 150 , including the installation and use of user applications.
- the included resources 230 may include one or more central processing units (CPUs), servers, disk spaces, network resources, or other resources useable to perform tasks of the management system 150 .
- a management system 150 may run at least one request server 260 , at least one worker server 270 , and at least one response server 280 , and the management system 150 may have at least one communication layer 290 . These components may run over the included resources 230 .
- Each of the request server 260 , the worker server 270 , and the response server 280 may include hardware, software, or a combination of both.
- the management application 220 may include code that instructs operations of these components.
- the request server 260 , the worker server 270 , and the response server 280 may be implemented as software, and the management application 220 may incorporate code for their implementation.
- the request server 260 which may be a web server, may receive requests from outside of the management system 150 .
- the request server 260 may perform preprocessing as needed and may then route each request to the worker server 270 .
- the worker server 270 may perform work to respond to each request, and the response server 280 may issue responses to locations outside of the management system 150 .
- Each such server may utilize included resources 230 of the management system 150 .
- the request server 260 , the worker server 270 , and the response server 280 may, but need not, utilize distinct resources from one another. For example, and not by way of limitation, these servers may utilize some of the same hardware or software.
- the managed resources 240 may include one or more CPUs, servers, disk spaces, network resources, or other resources managed by the management system 150 .
- the potential resources 250 may include one or more CPUs, servers, disk spaces, network resources, or other resources.
- the potential resources 250 are resources specified in the configuration file 155 as having the potential to be used by the management system 150 .
- an included resource 230 may be a part of the management system 150
- a managed resource 240 may be managed by the management system 150
- a potential resource 250 need not be in use at the time of creation, or instantiation, of the management system 150 .
- the communication layer 290 may define protocols for communications with and among the request server 260 , the worker server 270 , and the response server 280 .
- the communication layer 290 may define interactions between each pair of these servers, interactions between these servers and other resources, and interactions between these servers and the world outside the management system 150 .
- the communication layer 290 may be viewed as an interface or combination of interfaces.
- a management system 150 additionally includes a backup communication layer 295 , which has the same capabilities as the primary communication layer 290 , used as described below.
- the management application 220 may manage the various aspects of the management system 150 .
- the owner runs the administration system 101 , and each tenant runs an associated management system 150 .
- the form of management systems 150 described herein enables a multi-tenant environment by allowing a respective management application 220 to manage respective aspects of a corresponding management system 150 .
- each management system 150 may, but need not, share one or more computer systems 105 , such that each management system 150 has a dedicated set of resources, which may be physical or virtual.
- each management application 220 and corresponding management system 150 functions independently, even if sharing a computer system 105 with other management systems 150 and management applications 220 .
- multi-tenant environments are accomplished by running one instance of a management application 220 , with each tenant represented by a single user or set of users within that single application.
- This arrangement presents a variety of weaknesses. For instance, conventionally, all the tenants are managed by the same management code in that single management application 220 , so if a change to the management code is necessary for one tenant, all other tenants are forced to accept the change. Also conventionally, there is at least one administrator that can access the data of every tenant, and thus there exists a security risk that must be zealously guarded. Further, because resources are being shared, one user's use of computing capacity affects the capacity available to others.
- Each management application 220 may run its own code, thereby allowing each management application 220 to be independently updated.
- no administrator of a management system 150 is required to have access to all management applications 220 or all management systems 150 . Rather, each management instance can be assigned its own set of computing resources, specifically, for instance, the included resources 230 , the managed resources 240 , and the potential resources.
- FIG. 3 is a flow diagram of a method 300 of creating a new management system 150 according to some embodiments of the invention.
- the new management system 150 may run on one or more computer systems 105 along with one or more other management systems 150 .
- a new configuration file 155 describing the new management system 150 may be established before the new management system 150 can be instantiated.
- the new configuration file 155 may be established manually or automatically by a service provider who desires to establish a new tenancy with a new customer, where the new configuration file 155 is designed to suit the new customer's needs, and where the new customer will utilize the new management system 150 .
- this method 300 of creating a new management system 150 assumes that the new configuration file 155 exists.
- this method 300 of creating a management system 150 may be performed at the administration system 101 .
- instantiation of the new management system 150 may be initiated.
- this initiation may be in the form of an instruction received from an administrator of the administration system 101 .
- the administration system 101 may interrogate the new configuration file 155 and may compare the new configuration file 155 to existing configuration files 155 of existing management systems 150 .
- a conflict is deemed to exist when the new configuration file 155 specifies a resource, which may be an included resource 230 , a managed resource, or a potential resource 250 , that is unavailable due to existing configuration files 155 .
- a conflict may be deemed to exist when the new configuration file 155 specifies a resource, which may be an included resource 230 , a managed resource, or a potential resource 250 , that is unavailable due to existing configuration files 155 .
- an overlap of resources may be deemed a conflict.
- certain resources may be shared across management systems 150 through virtualization. However, in that case, certain capacities of such a shared resource may be dedicated to respective management systems 150 .
- a configuration file 155 specifies a capacity of a resource, where that capacity is unavailable, then a conflict is deemed to occur.
- instantiation may fail at block 320 .
- the administration system 101 may issue a notification of failure to the administrator.
- the resource assignments in the new configuration file 155 are made. In other words, for instance, permissions of the various included resources 230 , managed resources 240 , and potential resources 250 specified in the new configuration file 155 may be updated to provide read and write permission to a new management application 220 . Additionally, access to the new management application 220 may be assigned to a new administrator of the new management system 150 . At block 335 , other management systems 150 may be provided read access to the new configuration file 155 , and the new management application 220 may be provided read access to the configuration files 155 of other management systems 150 . At block 340 , the new management application 220 may be started, thereby starting the new management system 150 .
- authorized users of the new management system 150 may thus use the new management application 220 as if it is the only management application 220 on the administration system 101 .
- the management application 220 may extend, reduce, or modify resources in the new management system 150 , as long as the management application 220 remains within the bounds of the new configuration file 155 , thus maintaining the lack of conflict with other management systems 150 .
- the management application 220 is unable to access included resources 230 , managed resources 240 , and potential resources 250 of other management systems 150 , and analogously other management applications 220 are unable to access included resources 230 , managed resources 240 , and potential resources of the new management system 150 .
- resources can be nondisruptively migrated between management systems 150 , thereby enabling management systems 150 to be updated or merged through the process of such migration.
- a new management application 220 may be established as a copy of the original management application 220 .
- the new management application 220 does not control the various resources of the original management application 220 .
- changes are made to update code of the new management application 220 , thereby making the new management application 220 an updated version of the original management application 220 .
- the resources of the management system 150 may be migrated to the control of the new management application 220 .
- the new management application 220 may then become the primary management application 220 for the management system 150 .
- all application code can be updated or otherwise serviced nondisruptively, and no code has to be architected to facilitate splicing.
- This process of upgrading a management system 150 may be extended to merge management systems 150 , such that a resulting new management system 150 is effectively an updated version of two or more management systems 150 combined together. The details of such of merger are discussed below.
- FIG. 4 is a flow diagram of a method 400 of merging two or more management systems 150 , according to some embodiments of the invention.
- this method 400 may be performed at the merger system 100 .
- the management systems 150 described above provide advantages over conventional management systems 150 . One of such advantages is the ability to be automatically merged, as discussed herein. Although only two management systems 150 are discussed below, one of skill in the art will understand how to extend this method 400 to merge two or more management systems 150 . Further, in this example, each management system 150 includes at least one request server 260 , at least one worker server 270 , and at least one response server 280 .
- this method 400 is extensible to management systems 150 that do not have these servers.
- this disclosure refers to various management systems 150 each having a single request server 260 , a single worker server 270 , and a single response server 280 , it will be understood by one skilled in the art that each management system 150 may have one or more multiple servers of each of these types.
- an instruction may be received to merge a first management system 150 and a second management system 150 .
- the first management system 150 is associated with a first configuration file 155 and a first management application 220 , and includes a first request server 260 , a first worker server 270 , and a first response server 280 .
- the second management system 150 is associated with a second configuration file 155 and a second management application 220 , and includes a second request server 260 , a second worker server 270 , and a second response server 280 .
- the instruction to merge may include a prospective configuration file 155 .
- the prospective configuration file 155 may specify the desired configuration, such as included resources 230 , managed resources 240 , and potential resources 250 , of a new management system 150 to result from the merger.
- a respective backup communication layer 295 may be created based on the respective primary communication layer 290 .
- a management system 150 may already have a backup communication layer 295 in addition to the primary communication layer 290 . In that case, no new backup communication layer 295 need be made for that management system 150 .
- each management system 150 to be merged may include both a primary communication layer 290 and a backup communication layer 295 , where the respective primary communication layer 290 is active for each of the management systems 150 to be merged.
- a new management application 220 may be generated, where the new management application 220 is a combination of both the first and second management applications 220 .
- the new management system 150 may include a copy of the code of the first management application 220 , a copy of the code of the second management application 220 , and code to enable either copy to be executed on command.
- the new management application 220 may be given access to the resources of both the first management system 150 and the second management system 150 .
- the permissions of the included resources 230 , the managed resources 240 , and the potential resources 250 of each of the first management system 150 and the second management system 150 may be updated to allow read and write access to the new management application 220 .
- the request servers 260 , the worker servers 270 , and the response servers 280 of each of the first and second management systems 150 may now be readable and writable by the new management application 220 .
- the respective management applications 220 of the first and second management systems 150 are still controlling resources of the first and second management systems 150 , although the new management application 220 now has access to these resources as well.
- the new management application 220 may be dormant, with its versions of the request servers 260 , the worker servers 270 , and the response servers 280 not having started.
- the backup communication layers 295 of the first and second management systems 150 may be assigned to the new management system 150 and may become active for the new management system 150 .
- the new management system 150 may be able to utilize the backup communication layers 295 of the first and second management systems 150 to enable communications needed for operations of the request servers 260 , the worker servers 270 , and the response servers 280 of the new management system 150 .
- the backup communication layers 295 of the first and second management systems 150 may, therefore, become primary communication layers 290 for the new management system 150 .
- the new management application 220 may start, with the exception of its request servers 260 .
- the new worker servers 270 and the new response servers 280 may start in the new management application 220 .
- code within the new management application 220 that provides instructions to the worker servers 270 and the response servers 280 may be executed.
- the worker servers 270 and the response servers 280 may utilize the same resources as the respective worker servers 270 and response servers 280 of the first and second management systems 150 .
- the respective request servers 260 of the first management application 220 and the second management application 220 may be directed to forward requests through their respective backup communication layers 295 . Because the backup communication layers 295 are now assigned to the new management system 150 , this may effectively cause the request servers 260 of the first and second management systems 150 to forward their requests to the new worker servers 270 and new response servers 280 of the new management system 150 . Thus, according to some embodiments of the invention, all management functions except for receipt of requests are now being executed by the new management system 150 .
- the new request servers 260 are started in the new management application 220 .
- the first request server 260 and the second request server 260 of the first and second management applications 220 are instructed to redirect future requests to the new request servers 260 , such as by giving their respective listening sockets or other client interfaces to the new request servers 260 , for example. As such, no more requests are received at the first and second request servers 260 , but instead, requests are received at the new request servers 260 .
- the first and second management applications 220 may now be turned off, or they may continue to run in a dormant state while no longer handling requests or work.
- redundancies across the resources of the first and second management systems 150 may be recognized and removed. For instance, a redundancy may be recognized through comparison of the first and second configuration files 155 to the prospective configuration file 155 . In other words, more generally, when the first and second configuration files 155 are summed and the prospective configuration file 155 is subtracted from the resulting sum, then the difference is a set of redundant resources. This summing and subtracting may be performed for each category of resource to identify the redundancies within each category. Additionally, in some embodiments of the invention, the merger system 100 may be aware that only a fixed number of certain resources are needed.
- the merger system 100 may identify additional request servers 260 to be redundant. In that case, for instance, the merger system 100 may combine the code for the two or more request servers 260 into a single request server 260 , or may alert an administrator to do so.
- the new management system 150 includes the new management application 220 , which is based on the management applications 220 of the merged management systems 150 , as well as the included resources 230 , managed resources 240 , and potential resources 250 of the merged management applications 220 , potentially without redundancies.
- FIG. 5 is a block diagram of a computer system 105 for implementing some or all aspects of the merger system 100 , according to some embodiments of this invention.
- the merger systems 100 and methods described herein may be implemented in hardware, software (e.g., firmware), or a combination thereof.
- the methods described may be implemented, at least in part, in hardware and may be part of the microprocessor of a special or general-purpose computer system 105 , such as a personal computer, workstation, minicomputer, or mainframe computer.
- each management system 150 may utilize resources of one or more computer systems 105 and may thereby run across one or multiple such computer systems 105 .
- each of the combination unit 110 and the migrator 120 of the merger system 100 may be implemented as one or more computer systems 105 or portions thereof.
- the computer system 105 includes a processor 505 , memory 510 coupled to a memory controller 515 , and one or more input devices 545 and/or output devices 540 , such as peripherals, that are communicatively coupled via a local I/O controller 535 .
- These devices 540 and 545 may include, for example, a printer, a scanner, a microphone, and the like.
- Input devices such as a conventional keyboard 550 and mouse 555 may be coupled to the I/O controller 535 .
- the I/O controller 535 may be, for example, one or more buses or other wired or wireless connections, as are known in the art.
- the I/O controller 535 may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers, to enable communications.
- the I/O devices 540 , 545 may further include devices that communicate both inputs and outputs, for instance disk and tape storage, a network interface card (MC) or modulator/demodulator (for accessing other files, devices, systems, or a network), a radio frequency (RF) or other transceiver, a telephonic interface, a bridge, a router, and the like.
- MC network interface card
- modulator/demodulator for accessing other files, devices, systems, or a network
- RF radio frequency
- the processor 505 is a hardware device for executing hardware instructions or software, particularly those stored in memory 510 .
- the processor 505 may be a custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the computer system 105 , a semiconductor-based microprocessor (in the form of a microchip or chip set), a macroprocessor, or other device for executing instructions.
- the processor 505 includes a cache 570 , which may include, but is not limited to, an instruction cache to speed up executable instruction fetch, a data cache to speed up data fetch and store, and a translation lookaside buffer (TLB) used to speed up virtual-to-physical address translation for both executable instructions and data.
- the cache 570 may be organized as a hierarchy of more cache levels (L1, L2, etc.).
- the memory 510 may include one or combinations of volatile memory elements (e.g., random access memory, RAM, such as DRAM, SRAM, SDRAM, etc.) and nonvolatile memory elements (e.g., ROM, erasable programmable read only memory (EPROM), electronically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), tape, compact disc read only memory (CD-ROM), disk, diskette, cartridge, cassette or the like, etc.).
- volatile memory elements e.g., random access memory, RAM, such as DRAM, SRAM, SDRAM, etc.
- nonvolatile memory elements e.g., ROM, erasable programmable read only memory (EPROM), electronically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), tape, compact disc read only memory (CD-ROM), disk, diskette, cartridge, cassette or the like, etc.
- ROM erasable programmable read only memory
- EEPROM electronically
- the instructions in memory 510 may include one or more separate programs, each of which comprises an ordered listing of executable instructions for implementing logical functions.
- the instructions in the memory 510 include a suitable operating system (OS) 511 .
- the operating system 511 essentially may control the execution of other computer programs and provides scheduling, input-output control, file and data management, memory management, and communication control and related services.
- Additional data including, for example, instructions for the processor 505 or other retrievable information, may be stored in storage 520 , which may be a storage device such as a hard disk drive or solid-state drive.
- the stored instructions in memory 510 or in storage 520 may include those enabling the processor to execute one or more aspects of the merger systems 100 and methods of this disclosure.
- the computer system 105 may further include a display controller 525 coupled to a display 530 .
- the computer system 105 may further include a network interface 560 for coupling to a network 565 .
- the network 565 may be an IP-based network for communication between the computer system 105 and an external server, client and the like via a broadband connection.
- the network 565 transmits and receives data between the computer system 105 and external systems.
- the network 565 may be a managed Internet Protocol (IP) network administered by a service provider.
- IP Internet Protocol
- the network 565 may be implemented in a wireless fashion, e.g., using wireless protocols and technologies, such as WiFi, WiMax, etc.
- the network 565 may also be a packet-switched network such as a local area network, wide area network, metropolitan area network, the Internet, or other similar type of network environment.
- the network 565 may be a fixed wireless network, a wireless local area network (LAN), a wireless wide area network (WAN) a personal area network (PAN), a virtual private network (VPN), intranet or other suitable network system and may include equipment for receiving and transmitting signals.
- LAN wireless local area network
- WAN wireless wide area network
- PAN personal area network
- VPN virtual private network
- Merger systems 100 and methods according to this disclosure may be embodied, in whole or in part, in computer program products or in computer systems 105 , such as that illustrated in FIG. 5 .
- the present invention may be a system, a method, and/or a computer program product at any possible technical detail level of integration
- the computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention
- the computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device.
- the computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing.
- a non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing.
- RAM random access memory
- ROM read-only memory
- EPROM or Flash memory erasable programmable read-only memory
- SRAM static random access memory
- CD-ROM compact disc read-only memory
- DVD digital versatile disk
- memory stick a floppy disk
- a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon
- a computer readable storage medium is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
- Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network.
- the network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers.
- a network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
- Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages.
- the computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
- the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
- electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instruction by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
- These computer readable program instructions may be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
- These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
- the computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
- each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s).
- the functions noted in the blocks may occur out of the order noted in the Figures.
- two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Human Resources & Organizations (AREA)
- Software Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Game Theory and Decision Science (AREA)
- General Business, Economics & Management (AREA)
- Educational Administration (AREA)
- Development Economics (AREA)
- Automation & Control Theory (AREA)
- Hardware Redundancy (AREA)
Abstract
Description
- The present invention relates to management systems and, more specifically, to an automated nondisruptive merge of management systems.
- A management system is a type of computer system, which may be distributed, used to manage the resources of an organization, perform services, and generally perform various other tasks needed by the organization. Within an enterprise, multiple organizations might exist, and each might have its own management system. Thus, not only are there multiple management systems across enterprises, but there are often multiple management systems within an enterprise.
- In some cases, it becomes necessary to merge management systems. This may be desirable, for example, in the case of a reorganization, such as the merging of two departments, each with its own respective management system. Merging management systems may also be desirable when merging enterprises or when revamping how computing resources are obtained, allocated, or accounted.
- Embodiments of the present invention are directed to a computer-implemented method for updating a management system. A non-limiting example of the computer-implemented method includes generating a new management application based on a first management application, where the first management application operates a first management system. A first set of resources of the first management system are assigned to the new management application, where the first set of resources support a first request server and a first worker server. A new worker server of the new management system is started, where the new worker server utilizes the first set of resources of the first management system. The first request server is instructed to send a first set of future requests of the first request server to the new worker server. The first request server is further instructed to redirect a remainder of the future requests of the first request server to a new request server of the new management application. The new management application operates a new management system based on the first management system.
- Embodiments of the present invention are directed to a system for updating a management system. A non-limiting example of the system includes a memory having computer-readable instructions and one or more processors for executing the computer-readable instructions. The computer-readable instructions include generating a new management application based on a first management application, where the first management application operates a first management system. Further according to the computer-readable instructions, a first set of resources of the first management system are assigned to the new management application, where the first set of resources support a first request server and a first worker server. A new worker server of the new management system is started, where the new worker server utilizes the first set of resources of the first management system. The first request server is instructed to send a first set of future requests of the first request server to the new worker server. The first request server is further instructed to redirect a remainder of the future requests of the first request server to a new request server of the new management application. The new management application operates a new management system based on the first management system.
- Embodiments of the invention are directed to a computer-program product for updating a management system, the computer-program product including a computer-readable storage medium having program instructions embodied therewith. The program instructions are executable by a processor to cause the processor to perform a method. A non-limiting example of the method includes generating a new management application based on a first management application, where the first management application operates a first management system. Further according to the method, a first set of resources of the first management system are assigned to the new management application, where the first set of resources support a first request server and a first worker server. A new worker server of the new management system is started, where the new worker server utilizes the first set of resources of the first management system. The first request server is instructed to send a first set of future requests of the first request server to the new worker server. The first request server is further instructed to redirect a remainder of the future requests of the first request server to a new request server of the new management application. The new management application operates a new management system based on the first management system.
- Additional technical features and benefits are realized through the techniques of the present invention. Embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed subject matter. For a better understanding, refer to the detailed description and to the drawings.
- The specifics of the exclusive rights described herein are particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other features and advantages of the embodiments of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:
-
FIG. 1 is a diagram of a merger system according to some embodiments of the invention; -
FIG. 2 is a diagram of a management system according to some embodiments of the invention; -
FIG. 3 is a flow diagram of a method of creating a new management system, according to some embodiments of the invention; -
FIG. 4 is a flow diagram of a method of merging two or more management systems, according to some embodiments of the invention; and -
FIG. 5 is a block diagram of a computer system for implementing some or all aspects of the merger system, according to some embodiments of this invention. - The diagrams depicted herein are illustrative. There can be many variations to a diagram or the operations described therein without departing from the spirit of the invention. For instance, the actions can be performed in a differing order or actions can be added, deleted or modified. Also, the term “coupled” and variations thereof describes having a communications path between two elements and does not imply a direct connection between the elements with no intervening elements/connections between them. All of these variations are considered a part of the specification.
- In the accompanying figures and following detailed description of the disclosed embodiments, the various elements illustrated in the figures are provided with two- or three-digit reference numbers. With minor exceptions, the leftmost digit(s) of each reference number correspond to the figure in which its element is first illustrated.
- Various embodiments of the invention are described herein with reference to the related drawings. Alternative embodiments of the invention can be devised without departing from the scope of this invention. Various connections and positional relationships (e.g., over, below, adjacent, etc.) are set forth between elements in the following description and in the drawings. These connections and/or positional relationships, unless specified otherwise, can be direct or indirect, and the present invention is not intended to be limiting in this respect. Accordingly, a coupling of entities can refer to either a direct or an indirect coupling, and a positional relationship between entities can be a direct or indirect positional relationship. Moreover, the various tasks and process steps described herein can be incorporated into a more comprehensive procedure or process having additional steps or functionality not described in detail herein.
- The following definitions and abbreviations are to be used for the interpretation of the claims and the specification. As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having,” “contains” or “containing,” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a composition, a mixture, process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but can include other elements not expressly listed or inherent to such composition, mixture, process, method, article, or apparatus.
- Additionally, the term “exemplary” is used herein to mean “serving as an example, instance or illustration.” Any embodiment or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs. The terms “at least one” and “one or more” may be understood to include any integer number greater than or equal to one, i.e., one, two, three, four, etc. The terms “a plurality” may be understood to include any integer number greater than or equal to two, i.e., two, three, four, five, etc. The term “connection” may include both an indirect “connection” and a direct “connection.”
- The terms “about,” “substantially,” “approximately,” and variations thereof, are intended to include the degree of error associated with measurement of the particular quantity based upon the equipment available at the time of filing the application. For example, “about” can include a range of ±8% or 5%, or 2% of a given value.
- For the sake of brevity, conventional techniques related to making and using aspects of the invention may or may not be described in detail herein. In particular, various aspects of computing systems and specific computer programs to implement the various technical features described herein are well known. Accordingly, in the interest of brevity, many conventional implementation details are only mentioned briefly herein or are omitted entirely without providing the well-known system and/or process details.
- Turning now to an overview of technologies that are more specifically relevant to aspects of the invention, with conventional management systems, there is no automated way to merge management systems. A conventional management system views itself as the only management system that exists and is thus not optimized for the merger. As a result, merger generally requires manual intervention, which is slow and error-prone. Further, manual merger requires the management systems involved to go offline until the merger is complete, which can be detrimental to normal operations. One way to address mergers is to splice code into a running management application of a management system. In practical terms, this means the management application must be architected specifically to enable splicing, which increases the cost of service. Further, if a splice must occur at an unexpected location within the code, then once again, manual intervention is required, and the management systems involved go offline.
- Turning now to an overview of the aspects of the invention, one or more embodiments of the invention address the above-described shortcomings of the prior art by providing a new architecture for management systems and for merging such management systems in a way that is effectively instantaneous. More specifically, according to some embodiments of the invention, each management system includes a management application and a set of resources, as well as a request server, a worker server, and a response server operated through the management application. A new management application may be created based on first and second management applications belonging to first and second management systems, respectively, to be merged. The new management application may be given access to the resources of the first and second management applications, and the request servers, worker servers, and response servers of the new management application may gradually take over operations of the first and second management applications, as will be described herein.
- The above-described aspects of the invention address the shortcomings of the prior art by defining an improved mechanism of merging two or more management systems that utilize a new format of a management system. According to some embodiments of the invention, the merger process is automated, and services do not need to go offline while management systems are being merged. Further, the code in management applications does not need to be architected to enable splicing, and human error is reduced or eliminated.
- Turning now to a more detailed description of aspects of the present invention,
FIG. 1 is a diagram of amerger system 100 according to some embodiments of the invention. As shown inFIG. 1 , themerger system 100 applies to two ormore management systems 150, each of which may be acomputer system 105, which may be physical, virtual, distributed, or a combination thereof. Themanagement systems 150 may be administered through anadministration system 101, which may be in communication with themerger system 100. For example, and not by way of limitation, themerger system 100 may be integrated into theadministration system 101, such that theadministration system 101 may be configured to mergemanagement systems 150 through use of themerger system 100 as described herein. Theadministration system 101 may manage a set ofcomputer systems 105, and themanagement systems 150 may utilize resources ofsuch computer systems 105. - Each
management system 150 may be associated with aconfiguration file 155. Themanagement systems 150 and therespective configuration files 155 will be described in more detail below. Themerger system 100 may take as input arespective configuration file 155 of eachmanagement system 150 to be merged, as well as aprospective configuration file 155 of anew management system 150 to result from the merger. - The
merger system 100 may include acombination unit 110 and amigrator 120. Generally, thecombination unit 110 may determine how to combine therespective configuration files 155 of the existingmanagement systems 150 to result in theprospective configuration file 155, and thecombination unit 110 may thus identify and remove any redundancies across the existingmanagement systems 150. Generally, themigrator 120 may migrate resources managed by the existingmanagement system 150 to thefinal management system 150, such as by updating permissions of the resources. Each of thecombination unit 110 and themigrator 120 may include hardware, software, or a combination of both. For instance, each of these components may be a software module or a specialized hardware device. Additionally, while thecombination unit 110 and themigrator 120 are illustrated and described herein as being distinct, it will be understood that this distinction is for illustrative purposes only, and these components may be integrated together or further divided. -
FIG. 2 is a diagram of amanagement system 150 according to some embodiments of the invention. More specifically, eachmanagement system 150 may include, or be otherwise associated with, aconfiguration file 155. Eachmanagement system 150 may also include amanagement application 220, also referred to as an instance of a management application or a management application instance, and set of resources. The set of resources may include one or more of the following: a set of includedresources 230, a set of managedresources 240, and a set ofpotential resources 250. - In some embodiments of the invention, the
configuration file 155 of amanagement system 150 describes aspects of themanagement system 150, such as the includedresources 230, the managedresources 240, thepotential resources 250, and thecommunication layer 290. In some embodiments of the invention, themanagement application 220 has exclusive write access to itsrespective configuration file 155, includedresources 230, managedresources 240, and potential resources, as well as read access to the configuration files 155 ofother management systems 150. Generally, themanagement application 220 may enable an administrator of themanagement system 150 to access and utilize the associated resources of themanagement system 150, including the installation and use of user applications. - The included
resources 230 may include one or more central processing units (CPUs), servers, disk spaces, network resources, or other resources useable to perform tasks of themanagement system 150. In some embodiments of the invention, amanagement system 150 may run at least onerequest server 260, at least oneworker server 270, and at least oneresponse server 280, and themanagement system 150 may have at least onecommunication layer 290. These components may run over the includedresources 230. Each of therequest server 260, theworker server 270, and theresponse server 280 may include hardware, software, or a combination of both. Themanagement application 220 may include code that instructs operations of these components. For example, and not by way of limitation, therequest server 260, theworker server 270, and theresponse server 280 may be implemented as software, and themanagement application 220 may incorporate code for their implementation. Generally, therequest server 260, which may be a web server, may receive requests from outside of themanagement system 150. Therequest server 260 may perform preprocessing as needed and may then route each request to theworker server 270. Theworker server 270 may perform work to respond to each request, and theresponse server 280 may issue responses to locations outside of themanagement system 150. Each such server may utilize includedresources 230 of themanagement system 150. It will be understood that therequest server 260, theworker server 270, and theresponse server 280 may, but need not, utilize distinct resources from one another. For example, and not by way of limitation, these servers may utilize some of the same hardware or software. - The managed
resources 240 may include one or more CPUs, servers, disk spaces, network resources, or other resources managed by themanagement system 150. Analogously, thepotential resources 250 may include one or more CPUs, servers, disk spaces, network resources, or other resources. Thepotential resources 250 are resources specified in theconfiguration file 155 as having the potential to be used by themanagement system 150. Generally, an includedresource 230 may be a part of themanagement system 150, a managedresource 240 may be managed by themanagement system 150, and apotential resource 250 need not be in use at the time of creation, or instantiation, of themanagement system 150. - The
communication layer 290, also referred to as the primary communication layer, may define protocols for communications with and among therequest server 260, theworker server 270, and theresponse server 280. In other words, thecommunication layer 290 may define interactions between each pair of these servers, interactions between these servers and other resources, and interactions between these servers and the world outside themanagement system 150. Thecommunication layer 290 may be viewed as an interface or combination of interfaces. In some embodiments of the invention, amanagement system 150 additionally includes abackup communication layer 295, which has the same capabilities as theprimary communication layer 290, used as described below. - The
management application 220 may manage the various aspects of themanagement system 150. On relatively large enterprise systems, it is common for multiple tenants to share resources while ideally allowing no tenant to interfere or have knowledge of any other tenant. For instance, if the tenants are renting portions of resources from an owner, then it is critical that the owner ensure that each tenant, and confidential data of that tenant, is being kept separate from other tenants. In this example, the owner runs theadministration system 101, and each tenant runs an associatedmanagement system 150. The form ofmanagement systems 150 described herein enables a multi-tenant environment by allowing arespective management application 220 to manage respective aspects of acorresponding management system 150. As such,various management systems 150 may, but need not, share one ormore computer systems 105, such that eachmanagement system 150 has a dedicated set of resources, which may be physical or virtual. According to some embodiments of the invention, eachmanagement application 220 andcorresponding management system 150 functions independently, even if sharing acomputer system 105 withother management systems 150 andmanagement applications 220. - Conventionally, multi-tenant environments are accomplished by running one instance of a
management application 220, with each tenant represented by a single user or set of users within that single application. This arrangement presents a variety of weaknesses. For instance, conventionally, all the tenants are managed by the same management code in thatsingle management application 220, so if a change to the management code is necessary for one tenant, all other tenants are forced to accept the change. Also conventionally, there is at least one administrator that can access the data of every tenant, and thus there exists a security risk that must be zealously guarded. Further, because resources are being shared, one user's use of computing capacity affects the capacity available to others. - With multiple
distinct management applications 220, according to some embodiments of the invention, the above weaknesses and others are mitigated. Eachmanagement application 220 may run its own code, thereby allowing eachmanagement application 220 to be independently updated. In some embodiments of the invention, no administrator of amanagement system 150 is required to have access to allmanagement applications 220 or allmanagement systems 150. Rather, each management instance can be assigned its own set of computing resources, specifically, for instance, the includedresources 230, the managedresources 240, and the potential resources. -
FIG. 3 is a flow diagram of amethod 300 of creating anew management system 150 according to some embodiments of the invention. As discussed above, thenew management system 150 may run on one ormore computer systems 105 along with one or moreother management systems 150. According to some embodiments of the invention, before thenew management system 150 can be instantiated, anew configuration file 155 describing thenew management system 150 may be established. For example, and not by way of limitation, thenew configuration file 155 may be established manually or automatically by a service provider who desires to establish a new tenancy with a new customer, where thenew configuration file 155 is designed to suit the new customer's needs, and where the new customer will utilize thenew management system 150. Thus, thismethod 300 of creating anew management system 150 assumes that thenew configuration file 155 exists. In some embodiments of the invention, thismethod 300 of creating amanagement system 150 may be performed at theadministration system 101. - As shown in
FIG. 3 , atblock 305, instantiation of thenew management system 150 may be initiated. For example, and not by way of limitation, this initiation may be in the form of an instruction received from an administrator of theadministration system 101. Atblock 310, theadministration system 101 may interrogate thenew configuration file 155 and may compare thenew configuration file 155 to existingconfiguration files 155 of existingmanagement systems 150. - At
decision block 315, it may be determined whether a conflict exists between thenew configuration file 155 and the existing configuration files 155. In some embodiments of the invention, a conflict is deemed to exist when thenew configuration file 155 specifies a resource, which may be an includedresource 230, a managed resource, or apotential resource 250, that is unavailable due to existing configuration files 155. In other words, an overlap of resources may be deemed a conflict. It will be understood that, in some cases, certain resources may be shared acrossmanagement systems 150 through virtualization. However, in that case, certain capacities of such a shared resource may be dedicated torespective management systems 150. When aconfiguration file 155 specifies a capacity of a resource, where that capacity is unavailable, then a conflict is deemed to occur. - If there is a conflict, then instantiation may fail at
block 320. In that case, theadministration system 101 may issue a notification of failure to the administrator. - If no conflict is found, however, then instantiation begins at
block 325. Atblock 330, the resource assignments in thenew configuration file 155 are made. In other words, for instance, permissions of the various includedresources 230, managedresources 240, andpotential resources 250 specified in thenew configuration file 155 may be updated to provide read and write permission to anew management application 220. Additionally, access to thenew management application 220 may be assigned to a new administrator of thenew management system 150. Atblock 335,other management systems 150 may be provided read access to thenew configuration file 155, and thenew management application 220 may be provided read access to the configuration files 155 ofother management systems 150. Atblock 340, thenew management application 220 may be started, thereby starting thenew management system 150. - As such, authorized users of the
new management system 150 may thus use thenew management application 220 as if it is theonly management application 220 on theadministration system 101. Themanagement application 220 may extend, reduce, or modify resources in thenew management system 150, as long as themanagement application 220 remains within the bounds of thenew configuration file 155, thus maintaining the lack of conflict withother management systems 150. However, according to some embodiments of the invention, themanagement application 220 is unable to access includedresources 230, managedresources 240, andpotential resources 250 ofother management systems 150, and analogouslyother management applications 220 are unable to access includedresources 230, managedresources 240, and potential resources of thenew management system 150. - According to some embodiments of the invention, resources can be nondisruptively migrated between
management systems 150, thereby enablingmanagement systems 150 to be updated or merged through the process of such migration. To this end, generally, for aparticular management system 150, anew management application 220 may be established as a copy of theoriginal management application 220. Initially, thenew management application 220 does not control the various resources of theoriginal management application 220. As needed, changes are made to update code of thenew management application 220, thereby making thenew management application 220 an updated version of theoriginal management application 220. Then the resources of themanagement system 150 may be migrated to the control of thenew management application 220. Thenew management application 220 may then become theprimary management application 220 for themanagement system 150. According to some embodiments of the invention, with this approach, all application code can be updated or otherwise serviced nondisruptively, and no code has to be architected to facilitate splicing. This process of upgrading amanagement system 150 may be extended to mergemanagement systems 150, such that a resultingnew management system 150 is effectively an updated version of two ormore management systems 150 combined together. The details of such of merger are discussed below. -
FIG. 4 is a flow diagram of amethod 400 of merging two ormore management systems 150, according to some embodiments of the invention. In some embodiments of the invention, thismethod 400 may be performed at themerger system 100. According to some embodiments of the invention, themanagement systems 150 described above provide advantages overconventional management systems 150. One of such advantages is the ability to be automatically merged, as discussed herein. Although only twomanagement systems 150 are discussed below, one of skill in the art will understand how to extend thismethod 400 to merge two ormore management systems 150. Further, in this example, eachmanagement system 150 includes at least onerequest server 260, at least oneworker server 270, and at least oneresponse server 280. However, it will be understood that thismethod 400 is extensible tomanagement systems 150 that do not have these servers. Further, although this disclosure refers tovarious management systems 150 each having asingle request server 260, asingle worker server 270, and asingle response server 280, it will be understood by one skilled in the art that eachmanagement system 150 may have one or more multiple servers of each of these types. - As shown in
FIG. 4 , atblock 405, an instruction may be received to merge afirst management system 150 and asecond management system 150. Thefirst management system 150 is associated with afirst configuration file 155 and afirst management application 220, and includes afirst request server 260, afirst worker server 270, and afirst response server 280. Analogously, thesecond management system 150 is associated with asecond configuration file 155 and asecond management application 220, and includes asecond request server 260, asecond worker server 270, and asecond response server 280. Additionally, the instruction to merge may include aprospective configuration file 155. Theprospective configuration file 155 may specify the desired configuration, such as includedresources 230, managedresources 240, andpotential resources 250, of anew management system 150 to result from the merger. - At
block 410, for eachmanagement system 150 to be merged, a respectivebackup communication layer 295 may be created based on the respectiveprimary communication layer 290. In some cases, amanagement system 150 may already have abackup communication layer 295 in addition to theprimary communication layer 290. In that case, no newbackup communication layer 295 need be made for thatmanagement system 150. At this point, eachmanagement system 150 to be merged may include both aprimary communication layer 290 and abackup communication layer 295, where the respectiveprimary communication layer 290 is active for each of themanagement systems 150 to be merged. - At
block 415, anew management application 220 may be generated, where thenew management application 220 is a combination of both the first andsecond management applications 220. For example, and not by way of limitation, thenew management system 150 may include a copy of the code of thefirst management application 220, a copy of the code of thesecond management application 220, and code to enable either copy to be executed on command. - At
block 420, thenew management application 220 may be given access to the resources of both thefirst management system 150 and thesecond management system 150. In other words, for instance, the permissions of the includedresources 230, the managedresources 240, and thepotential resources 250 of each of thefirst management system 150 and thesecond management system 150 may be updated to allow read and write access to thenew management application 220. As a result, therequest servers 260, theworker servers 270, and theresponse servers 280 of each of the first andsecond management systems 150 may now be readable and writable by thenew management application 220. - According to some embodiments of the invention, at this point, the
respective management applications 220 of the first andsecond management systems 150 are still controlling resources of the first andsecond management systems 150, although thenew management application 220 now has access to these resources as well. In other words, thenew management application 220 may be dormant, with its versions of therequest servers 260, theworker servers 270, and theresponse servers 280 not having started. - At
block 425, the backup communication layers 295 of the first andsecond management systems 150 may be assigned to thenew management system 150 and may become active for thenew management system 150. In other words, thenew management system 150 may be able to utilize the backup communication layers 295 of the first andsecond management systems 150 to enable communications needed for operations of therequest servers 260, theworker servers 270, and theresponse servers 280 of thenew management system 150. The backup communication layers 295 of the first andsecond management systems 150 may, therefore, become primary communication layers 290 for thenew management system 150. - At
block 430, thenew management application 220 may start, with the exception of itsrequest servers 260. For instance, thenew worker servers 270 and thenew response servers 280 may start in thenew management application 220. More specifically, code within thenew management application 220 that provides instructions to theworker servers 270 and theresponse servers 280 may be executed. Theworker servers 270 and theresponse servers 280 may utilize the same resources as therespective worker servers 270 andresponse servers 280 of the first andsecond management systems 150. - At
block 435, therespective request servers 260 of thefirst management application 220 and thesecond management application 220 may be directed to forward requests through their respective backup communication layers 295. Because the backup communication layers 295 are now assigned to thenew management system 150, this may effectively cause therequest servers 260 of the first andsecond management systems 150 to forward their requests to thenew worker servers 270 andnew response servers 280 of thenew management system 150. Thus, according to some embodiments of the invention, all management functions except for receipt of requests are now being executed by thenew management system 150. - At
block 440, thenew request servers 260 are started in thenew management application 220. Atblock 445, thefirst request server 260 and thesecond request server 260 of the first andsecond management applications 220 are instructed to redirect future requests to thenew request servers 260, such as by giving their respective listening sockets or other client interfaces to thenew request servers 260, for example. As such, no more requests are received at the first andsecond request servers 260, but instead, requests are received at thenew request servers 260. Atblock 450, the first andsecond management applications 220 may now be turned off, or they may continue to run in a dormant state while no longer handling requests or work. - At
block 455, redundancies across the resources of the first andsecond management systems 150 may be recognized and removed. For instance, a redundancy may be recognized through comparison of the first and second configuration files 155 to theprospective configuration file 155. In other words, more generally, when the first and second configuration files 155 are summed and theprospective configuration file 155 is subtracted from the resulting sum, then the difference is a set of redundant resources. This summing and subtracting may be performed for each category of resource to identify the redundancies within each category. Additionally, in some embodiments of the invention, themerger system 100 may be aware that only a fixed number of certain resources are needed. For instance, if it is determined that only asingle request server 260 is needed, thus consolidating an interface for external entities interacting with thenew management system 150, then themerger system 100 may identifyadditional request servers 260 to be redundant. In that case, for instance, themerger system 100 may combine the code for the two ormore request servers 260 into asingle request server 260, or may alert an administrator to do so. - As a result, the two or
more management systems 150 have now been merged into a single,new management system 150 without disruption. In some embodiments of the invention, thenew management system 150 includes thenew management application 220, which is based on themanagement applications 220 of themerged management systems 150, as well as the includedresources 230, managedresources 240, andpotential resources 250 of themerged management applications 220, potentially without redundancies. -
FIG. 5 is a block diagram of acomputer system 105 for implementing some or all aspects of themerger system 100, according to some embodiments of this invention. Themerger systems 100 and methods described herein may be implemented in hardware, software (e.g., firmware), or a combination thereof. In some embodiments, the methods described may be implemented, at least in part, in hardware and may be part of the microprocessor of a special or general-purpose computer system 105, such as a personal computer, workstation, minicomputer, or mainframe computer. For instance, as shown inFIG. 1 , eachmanagement system 150 may utilize resources of one ormore computer systems 105 and may thereby run across one or multiplesuch computer systems 105. Additionally, each of thecombination unit 110 and themigrator 120 of themerger system 100 may be implemented as one ormore computer systems 105 or portions thereof. - In some embodiments of the invention, as shown in
FIG. 5 , thecomputer system 105 includes aprocessor 505,memory 510 coupled to amemory controller 515, and one ormore input devices 545 and/oroutput devices 540, such as peripherals, that are communicatively coupled via a local I/O controller 535. Thesedevices conventional keyboard 550 andmouse 555 may be coupled to the I/O controller 535. The I/O controller 535 may be, for example, one or more buses or other wired or wireless connections, as are known in the art. The I/O controller 535 may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers, to enable communications. - The I/
O devices - The
processor 505 is a hardware device for executing hardware instructions or software, particularly those stored inmemory 510. Theprocessor 505 may be a custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with thecomputer system 105, a semiconductor-based microprocessor (in the form of a microchip or chip set), a macroprocessor, or other device for executing instructions. Theprocessor 505 includes acache 570, which may include, but is not limited to, an instruction cache to speed up executable instruction fetch, a data cache to speed up data fetch and store, and a translation lookaside buffer (TLB) used to speed up virtual-to-physical address translation for both executable instructions and data. Thecache 570 may be organized as a hierarchy of more cache levels (L1, L2, etc.). - The
memory 510 may include one or combinations of volatile memory elements (e.g., random access memory, RAM, such as DRAM, SRAM, SDRAM, etc.) and nonvolatile memory elements (e.g., ROM, erasable programmable read only memory (EPROM), electronically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), tape, compact disc read only memory (CD-ROM), disk, diskette, cartridge, cassette or the like, etc.). Moreover, thememory 510 may incorporate electronic, magnetic, optical, or other types of storage media. Note that thememory 510 may have a distributed architecture, where various components are situated remote from one another but may be accessed by theprocessor 505. - The instructions in
memory 510 may include one or more separate programs, each of which comprises an ordered listing of executable instructions for implementing logical functions. In the example ofFIG. 5 , the instructions in thememory 510 include a suitable operating system (OS) 511. Theoperating system 511 essentially may control the execution of other computer programs and provides scheduling, input-output control, file and data management, memory management, and communication control and related services. - Additional data, including, for example, instructions for the
processor 505 or other retrievable information, may be stored instorage 520, which may be a storage device such as a hard disk drive or solid-state drive. The stored instructions inmemory 510 or instorage 520 may include those enabling the processor to execute one or more aspects of themerger systems 100 and methods of this disclosure. - The
computer system 105 may further include adisplay controller 525 coupled to adisplay 530. In some embodiments, thecomputer system 105 may further include anetwork interface 560 for coupling to anetwork 565. Thenetwork 565 may be an IP-based network for communication between thecomputer system 105 and an external server, client and the like via a broadband connection. Thenetwork 565 transmits and receives data between thecomputer system 105 and external systems. In some embodiments, thenetwork 565 may be a managed Internet Protocol (IP) network administered by a service provider. Thenetwork 565 may be implemented in a wireless fashion, e.g., using wireless protocols and technologies, such as WiFi, WiMax, etc. Thenetwork 565 may also be a packet-switched network such as a local area network, wide area network, metropolitan area network, the Internet, or other similar type of network environment. Thenetwork 565 may be a fixed wireless network, a wireless local area network (LAN), a wireless wide area network (WAN) a personal area network (PAN), a virtual private network (VPN), intranet or other suitable network system and may include equipment for receiving and transmitting signals. -
Merger systems 100 and methods according to this disclosure may be embodied, in whole or in part, in computer program products or incomputer systems 105, such as that illustrated inFIG. 5 . - The present invention may be a system, a method, and/or a computer program product at any possible technical detail level of integration. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
- The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
- Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
- Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instruction by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
- Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
- These computer readable program instructions may be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
- The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
- The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special-purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special-purpose hardware and computer instructions.
- The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments described herein.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/166,508 US10652093B1 (en) | 2018-10-22 | 2018-10-22 | Automated nondisruptive merge of management systems |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/166,508 US10652093B1 (en) | 2018-10-22 | 2018-10-22 | Automated nondisruptive merge of management systems |
Publications (2)
Publication Number | Publication Date |
---|---|
US20200127897A1 true US20200127897A1 (en) | 2020-04-23 |
US10652093B1 US10652093B1 (en) | 2020-05-12 |
Family
ID=70279015
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/166,508 Expired - Fee Related US10652093B1 (en) | 2018-10-22 | 2018-10-22 | Automated nondisruptive merge of management systems |
Country Status (1)
Country | Link |
---|---|
US (1) | US10652093B1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220058543A1 (en) | 2020-08-18 | 2022-02-24 | Edera L3C | Change Management System and Method |
US11539810B1 (en) * | 2022-05-16 | 2022-12-27 | International Business Machines Corporation | Data stream management |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7007036B2 (en) * | 2002-03-28 | 2006-02-28 | Lsi Logic Corporation | Method and apparatus for embedding configuration data |
EP1611532A4 (en) * | 2003-03-19 | 2008-10-22 | Unisys Corp | Server consolidation data model |
US8209680B1 (en) * | 2003-04-11 | 2012-06-26 | Vmware, Inc. | System and method for disk imaging on diverse computers |
US7412709B2 (en) * | 2003-11-07 | 2008-08-12 | International Business Machines Corporation | Method and apparatus for managing multiple data processing systems using existing heterogeneous systems management software |
US8023434B2 (en) | 2007-09-18 | 2011-09-20 | International Business Machines Corporation | Arrangements for auto-merging and auto-partitioning processing components |
US8909767B2 (en) | 2010-10-13 | 2014-12-09 | Rackware, Inc. | Cloud federation in a cloud computing environment |
US8775593B2 (en) | 2011-06-29 | 2014-07-08 | International Business Machines Corporation | Managing organizational computing resources in accordance with computing environment entitlement contracts |
US8904131B2 (en) * | 2012-08-22 | 2014-12-02 | International Business Machines Corporation | Automated migration to a new copy services target storage system to manage multiple relationships simultaneously while maintaining disaster recovery consistency |
US9280385B2 (en) | 2013-12-19 | 2016-03-08 | International Business Machines Corporation | Optimally provisioning and merging shared resources to maximize resource availability |
US20150372935A1 (en) * | 2014-06-24 | 2015-12-24 | Telefonaktiebolaget L M Ericsson (Publ) | System and method for migration of active resources |
-
2018
- 2018-10-22 US US16/166,508 patent/US10652093B1/en not_active Expired - Fee Related
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220058543A1 (en) | 2020-08-18 | 2022-02-24 | Edera L3C | Change Management System and Method |
US11900295B2 (en) | 2020-08-18 | 2024-02-13 | Edera L3C | System and method for third-party submissions of observations concerning journey reactions |
US11922353B2 (en) | 2020-08-18 | 2024-03-05 | Edera L3C | Change management system and method |
US11539810B1 (en) * | 2022-05-16 | 2022-12-27 | International Business Machines Corporation | Data stream management |
Also Published As
Publication number | Publication date |
---|---|
US10652093B1 (en) | 2020-05-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN108475251B (en) | Virtual network, hot swapping, hot scaling and disaster recovery for containers | |
US9760395B2 (en) | Monitoring hypervisor and provisioned instances of hosted virtual machines using monitoring templates | |
US11252050B2 (en) | Scalable, standardized I.T. deployment platform | |
US8898402B1 (en) | Assigning storage resources in a virtualization environment | |
CN114514507B (en) | System and method for supporting quota policy language in cloud infrastructure environment | |
US9589105B2 (en) | Securing protected health information based on software designation | |
US10891238B1 (en) | Dynamically joining and splitting dynamic address translation (DAT) tables based on operational context | |
CN117370280A (en) | Authority management method of cloud service and cloud data storage system thereof | |
US10652093B1 (en) | Automated nondisruptive merge of management systems | |
US11838296B1 (en) | Providing secure software project development environments | |
CA3132760A1 (en) | Inject interrupts and exceptions into secure virtual machine | |
AU2020234887B2 (en) | Dispatch of a secure virtual machine | |
WO2018011914A1 (en) | Data archive system and data archive method | |
Dufrasne et al. | IBM System Storage DS8000 Copy Services Scope Management and Resource Groups | |
US12013974B2 (en) | Provisioning a computing subsystem with disaggregated computing hardware resources selected in compliance with a physical location requirement of a workload | |
US20220269571A1 (en) | Virtual machine configuration update technique in a disaster recovery environment | |
US10073978B2 (en) | Efficient modification and creation of authorization settings for user accounts | |
US11868448B1 (en) | Shared dedicated host resource groups in a provider network | |
US12020040B2 (en) | Desired state management of software-defined data centers with a plurality of desired state configurations | |
US11356438B2 (en) | Access management system with a secret isolation manager | |
US20210232387A1 (en) | Linking copied code | |
US20210287043A1 (en) | Cognitive process data and decision tracking to facilitate artificial intelligence operations compliance | |
Bögelsack et al. | SAP S/4HANA on Microsoft Azure–Concepts and Architecture | |
Ward | SQL Server 2022 on Azure Virtual Machines | |
Syrewicze et al. | Migrating Virtual Machines Between Hosts |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SHULTZ, STEVEN;WIGGINS, PAUL S.;BRAZIE, CHARLES J.;AND OTHERS;SIGNING DATES FROM 20181011 TO 20181015;REEL/FRAME:047264/0633 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
ZAAA | Notice of allowance and fees due |
Free format text: ORIGINAL CODE: NOA |
|
ZAAB | Notice of allowance mailed |
Free format text: ORIGINAL CODE: MN/=. |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |