Drift management of images

• US 10,073,693 B2
• Filed: 01/12/2017
• Issued: 09/11/2018
• Est. Priority Date: 09/26/2014
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Kuchibhotla, Balasubrahmanyam, Paliwal, Bharat, Srinivasan, Hariprasanna, Khanuja, Kamaldeep, Sanklecha, Shachi, Vaidhiyanathan, Ramalakshmi
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Berman, Stephen
• Application Number:
  US15/404,564
• Publication Number:
  US 20170123786A1
• Time in Patent Office: 607 Days
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/63 Image based installation; Cloning; Build to order
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Abstract

Techniques are described for standardizing configuration levels across a plurality of software deployments. In one embodiment, a standardization management system generates, based on a plurality of software deployments that have different source components, an end state definition that identifies a recommended standard set of source components for the plurality of software deployments. Based on the end state definition that identifies the recommended standard set of source components for the plurality of software deployments, the standardization management system generates an image that includes the standard set of source components for the plurality of software deployments. The image may be used to update software deployments that are part of the plurality of software deployments and do not include the standard set of source components.

Claims

1. A method comprising:

collecting, from a plurality of target deployments that follow changes to a software image, data that identifies a set of source components from which the plurality of target deployments are run;

comparing a set of signatures including a hash value generated from digest information that describes the set of source components, including at least a base version of a software system and a set of patch information applied to the base version of the software system, from which the plurality of target deployments are run, to at least one signature generated based on a recommended set of source components for a plurality of active versions of the software image, the plurality of active versions of the software image including at least a first version of the software image that reflects currently recommended source components and a second version of the software image that reflects previously recommended source components;

responsive at least to comparing the set of signatures generated from digest information that describes the set of source components, including the set of patch information, from which the plurality of target deployments are run, to the at least one signature generated based on the recommended set of source components from the plurality of active versions of the software image, presenting;

(a) a first subset of one or more target deployments of the plurality of target deployments that include at least one source component that is not a currently recommended source component or a previously recommended source component reflected in the plurality of active versions of the software image; and

(b) a second subset of one or more target deployments of the plurality of target deployments that are run from the currently recommended source components; and

reconciling at least one target deployment in the first subset of one or more target deployments with the second subset of one or more target deployments.

2. The method of claim 1, further comprising presenting, through a visualization:

(c) a third subset of one or more target deployments of the plurality of target deployments that are run from the previously recommended source components.

3. The method of claim 2, wherein the visualization comprises a pie chart that identifies how many target deployments are included in the first subset of one or more target deployments, the second subset of one or more target deployments, and the third subset of one or more target deployments and wherein, responsive to a user selecting a portion of the pie chart that corresponds to the first subset, a list of target deployments included in the first subset of one or more target deployments are displayed.

4. The method of claim 1, wherein the reconciling the at least one target deployment comprises:

receiving, through the a graphical user interface, a request to reconcile all of the target deployments in the first subset of one or more target deployments;

responsive to receiving the request through the graphical user interface, updating each target deployment in the first subset of one or more target deployments using the first version of the software image.

5. The method of claim 4, further comprising presenting, through the graphical user interface, an update status for each target deployment in the first subset of one or more target deployments responsive to the request.

6. The method of claim 1, further comprising generating a new version of the software image using at least one source component included in at least one target deployment in the first subset of one or more target deployments.

7. The method of claim 1, further comprising computing and presenting a compliance rate based on how many target deployments of the plurality of target deployments are in the first subset of one or more target deployments.

8. One or more non-transitory computer-readable media storing instructions which, when executed by one or more processors, causing operations comprising:

collecting, from a plurality of target deployments that follow changes to a software image, data that identifies a set of source components from which the plurality of target deployments are run;

comparing a set of signatures including a hash value generated from digest information that describes the set of source components, including at least a base version of a software system and a set of patch information applied to the base version of the software system, from which the plurality of target deployments are run, to at least one signature generated based on a recommended set of source components for a plurality of active versions of the software image, the plurality of active versions of the software image including at least a first version of the software image that reflects currently recommended source components and a second version of the software image that reflects previously recommended source components;

responsive at least to comparing the set of signatures generated from digest information that describes the set of source components, including the set of patch information, from which the plurality of target deployments are run, to the at least one signature generated based on the recommended set of source components from the plurality of active versions of the software image, presenting;

(a) a first subset of one or more target deployments of the plurality of target deployments that include at least one source component that is not a currently recommended source component or a previously recommended source component reflected in the plurality of active versions of the software image; and

(b) a second subset of one or more target deployments of the plurality of target deployments that are run from the currently recommended source components; and

reconciling at least one target deployment in the first subset of one or more target deployments with the second subset of one or more target deployments.

9. The one or more non-transitory computer-readable media of claim 8, wherein the instructions further cause operations comprising presenting, through a visualization:

(c) a third subset of one or more target deployments of the plurality of target deployments that are run from the previously recommended source components.

10. The one or more non-transitory computer-readable media of claim 9, wherein the visualization comprises a pie chart that identifies how many target deployments are included in the first subset of one or more target deployments, the second subset of one or more target deployments, and the third subset of one or more target deployments and wherein, responsive to a user selecting a portion of the pie chart that corresponds to the first subset, a list of target deployments included in the first subset of one or more target deployments are displayed.

11. The one or more non-transitory computer-readable media of claim 8, wherein the instructions for reconciling the at least one target deployment comprises instructions for:

receiving, through the a graphical user interface, a request to reconcile all of the target deployments in the first subset of one or more target deployments;

responsive to receiving the request through the graphical user interface, updating each target deployment in the first subset of one or more target deployments using the first version of the software image.

12. The one or more non-transitory computer-readable media of claim 11, the instructions further causing operations comprising presenting, through the graphical user interface, an update status for each target deployment in the first subset of one or more target deployments responsive to the request.

13. The one or more non-transitory computer-readable media of claim 8, the instructions further causing operations comprising generating a new version of the software image using at least one source component included in at least one target deployment in the first subset of one or more target deployments.

14. The one or more non-transitory computer-readable media of claim 8, the instructions further causing operations comprising computing and presenting a compliance rate based on how many target deployments of the plurality of target deployments are in the first subset of one or more target deployments.

15. A system comprising:

one or more hardware processors;

one or more non-transitory computer-readable media storing instructions which, when executed by the one or more hardware processors, cause operations comprising;

collecting, from a plurality of target deployments that follow changes to a software image, data that identifies a set of source components from which the plurality of target deployments are run;

comparing a set of signatures including a hash value generated from digest information that describes the set of source components, including at least a base version of a software system and a set of patch information applied to the base version of the software system, from which the plurality of target deployments are run, to at least one signature generated based on a recommended set of source components for a plurality of active versions of the software image, the plurality of active versions of the software image including at least a first version of the software image that reflects currently recommended source components and a second version of the software image that reflects previously recommended source components;

responsive at least to comparing the set of signatures generated from digest information that describes the set of source components, including the set of patch information, from which the plurality of target deployments are run, to the at least one signature generated based on the recommended set of source components from the plurality of active versions of the software image, presenting;

(a) a first subset of one or more target deployments of the plurality of target deployments that include at least one source component that is not a currently recommended source component or a previously recommended source component reflected in the plurality of active versions of the software image; and

(b) a second subset of one or more target deployments of the plurality of target deployments that are run from the currently recommended source components; and

reconciling at least one target deployment in the first subset of one or more target deployments with the second subset of one or more target deployments.

16. The system of claim 15, wherein the instructions further cause operations comprising presenting, through a visualization:

(c) a third subset of one or more target deployments of the plurality of target deployments that are run from the previously recommended source components.

17. The system of claim 16, wherein the visualization comprises a pie chart that identifies how many target deployments are included in the first subset of one or more target deployments, the second subset of one or more target deployments, and the third subset of one or more target deployments and wherein, responsive to a user selecting a portion of the pie chart that corresponds to the first subset, a list of target deployments included in the first subset of one or more target deployments are displayed.

18. The system of claim 15, wherein the instructions for reconciling the at least one target deployment comprises instructions for:

receiving, through the a graphical user interface, a request to reconcile all of the target deployments in the first subset of one or more target deployments;

responsive to receiving the request through the graphical user interface, updating each target deployment in the first subset of one or more target deployments using the first version of the software image.

19. The system of claim 18, the instructions further causing operations comprising presenting, through the graphical user interface, an update status for each target deployment in the first subset of one or more target deployments responsive to the request.

20. The system of claim 15, the instructions further causing operations comprising generating a new version of the software image using at least one source component included in at least one target deployment in the first subset of one or more target deployments.