MANAGE CONFLICTS IN A SOFTWARE AND HARDWARE INFRASTRUCTURE
A method of operating a computing infrastructure is provided. The computing infrastructure includes computing resources, a central repository connected to the computing resources, and a change request tool connected to the central repository. The method includes: receiving, by the central repository, a later change request for at least one of the computing resources; determining, by the central repository, which of the computing resources would be affected by the later change request; determining, by the central repository, that the later change request conflicts with an earlier change request; and invalidating the later change request.
1 . A method of operating a computing infrastructure comprising a plurality of computing resources, a central repository connected to the plurality of computing resources, and a change request tool connected to the central repository, the method comprising:
receiving, by the central repository, a later change request for at least one of the plurality of computing resources;
determining, by the central repository, which of the plurality of computing resources would be affected by the later change request;
determining, by the central repository, that the later change request conflicts with an earlier change request; and
invalidating the later change request.
2 . The method of claim 1 , further comprising:
receiving, by the central repository, a subsequent change request for at least one of the plurality of computing resources;
determining, by the central repository, which of the plurality of computing resources would be affected by the subsequent change request;
determining, by the central repository, that the subsequent change request is not in conflict with the earlier change request; and
locking the affected ones of the plurality of computing resources that would be affected by the subsequent change request.
3 . The method of claim 2 , further comprising:
determining, by the central repository, at least one owner of the plurality of computing resources that would be affected by the subsequent change request; and
notifying, by the central repository, the at least one owner of the subsequent change request.
4 . The method of claim 3 , further comprising:
receiving, by the central repository, approval of the subsequent change request from the at least one owner; and
notifying, by the central repository, at least one change implementor of the subsequent change request.
5 . The method of claim 1 , wherein the later change request is invalidated because at least one of the plurality of computing resources that would be affected by the later change request is locked by the central repository.
6 . The method of claim 1 , wherein:
the earlier change request includes a first timeslot during which the earlier change request is to be implemented;
the later change request includes a second timeslot during which the later change request is to be implemented; and
the second timeslot overlaps the first timeslot.
7 . The method of claim 1 , further comprising:
notifying, by the central repository, a change requester that submitted the later change request of the invalidation of the later change request.
8 . A change management system comprising:
a plurality of computing resources;
a central repository connected to the plurality of computing resources, the central repository including, for each of the computing resources, identification information, ownership information, and relationship information with respect to at least another one of the plurality of computing resources; and
a change request tool connected to the central repository for requesting a change to at least one of the plurality of computing resources.
9 . The change management system of claim 8 , further comprising:
an approval tool connected to the central repository for approving the requested change.
10 . The change management system of claim 8 , further comprising:
an implementation tool connected to the central repository for implementing the requested change.
11 . The change management system of claim 8 , wherein the central repository further comprises:
lock information for each of the computing resources, the lock information representing timeslots in which each of the computing resources is unavailable for the change.
12 . The change management system of claim 8 , wherein the central repository further comprises:
a database that includes the identification information, ownership information, and relationship information; and
a resource/asset management system configured to be used to maintain, monitor, add to, and/or subtract from the database.
13 . The change management system of claim 8 , wherein the central repository further comprises:
an information technology applications/software management system for monitoring at least some of the plurality of computing resources on an operating system level.
14 . The change management system of claim 8 , wherein the central repository further comprises:
an application release management system for monitoring at least some of the plurality of computing resources on the application level.
15 . A computer program product for memory management, the computer program product comprising a computer readable storage medium, the computer readable storage medium having program instructions embodied therewith, the programs instructions configured, when executed by at least one computer, to cause the at least one computer to perform a method comprising:
receiving, by a central repository of a computing infrastructure, a later change request, from a change request tool, for at least one of a plurality of computing resources of the computing infrastructure that is connected to the central repository;
determining, by the central repository, which of the plurality of computing resources would be affected by the later change request;
determining, by the central repository, that the later change request conflicts with an earlier change request; and
invalidating the later change request.
16 . The computer program product of claim 15 , further comprising:
receiving, by the central repository, a subsequent change request for at least one of the plurality of computing resources;
determining, by the central repository, which of the plurality of computing resources would be affected by the subsequent change request;
determining, by the central repository, that the subsequent change request is not in conflict with the earlier change request; and
locking the affected ones of the plurality of computing resources that would be affected by the subsequent change request.
17 . The computer program product of claim 16 , further comprising:
determining, by the central repository, at least one owner of the plurality of computing resources that would be affected by the subsequent change request; and
notifying, by the central repository, the at least one owner of the subsequent change request.
18 . The computer program product of claim 17 , further comprising:
receiving, by the central repository, approval of the subsequent change request from the at least one owner; and
notifying, by the central repository, at least one change implementor of the subsequent change request.
19 . The computer program product of claim 15 , wherein:
the earlier change request includes a first timeslot during which the earlier change request is to be implemented;
the later change request includes a second timeslot during which the later change request is to be implemented; and
the second timeslot overlaps the first timeslot.
20 . The computer program product of claim 15 , further comprising:
notifying, by the central repository, a change requester that submitted the later change request of the invalidation of the later change request.