Version management of images

• US 9,921,820 B2
• Filed: 01/23/2015
• Issued: 03/20/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, Kaler, Akanksha Sheoran
• Primary Examiner(s): Bullock, Jr., Lewis A
• Assistant Examiner(s): HEBERT, THEODORE E
• Application Number:
  US14/603,532
• Publication Number:
  US 20160092209A1
• Time in Patent Office: 1,152 Days
• Field of Search: 717170
• 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 software configuration levels across targets. In one embodiment, a subscription is maintained that identifies a group of targets that subscribe to a particular image, where the particular image represents a standard to follow for targets that belong to the group of targets. The particular image may further include a first image version having a first set of source components. In response to receiving an update to the particular image, a second image version is generated for the particular image, where the second image version includes a second set of source components that are different than the first set of source components. Two or more targets in the group of targets that subscribe to the particular image may be updated based on the second image version.

Claims

1. A method comprising:

identifying a set of target software deployments that share at least one common primary attribute that defines a base version of a software resource;

comparing configuration level signatures for target software deployments in the set of target software deployments to determine which target software deployments share a common configuration level signature;

wherein the configuration level signature is generated, at least in part, from a set of one or more secondary attributes that are variable between different software deployments of the base version of the software resource and that identify one or more of;

a location where the target software deployments are installed, or a set of one or more patches applied to the target software deployments;

arranging the set of target software deployments into a plurality of groups based on which target software deployments share a common configuration level signature;

responsive at least to arranging the set of target software deployments into a plurality of groups based on which target software deployments share a common configuration level signature, generating subscription data that subscribes different respective groups of target software deployments of the plurality of groups to different respective images of a set of images;

wherein each respective image in the set of images represents a recommended software binary to follow for the respective group of target software deployments that are subscribed to the respective image;

wherein a particular image, in the set of images and to which a particular group of target software deployments in the set of target software deployments is subscribed, includes a first image version that is generated from a first set of source components;

generating a second image version for the particular image from a second set of source components that are different than the first set of source components;

updating two or more target software deployments in the particular group of target software deployments that subscribe to the particular image based on the second image version for the particular image; and

maintaining the first image version of the particular image in an active state until each target software deployment in the particular group of target software deployments that is subscribed to the particular image has been updated to a more current version of the particular image.

2. The method of claim 1, wherein generating the second image version for the particular image comprises applying one or more patches to the recommended software binary.

3. The method of claim 2, wherein the one or more patches are identified based on at least one of a recommendation from a service provider, drift information of patches from the group of target software deployments that subscribe to the particular image, or custom patches requested from a user.

4. The method of claim 1, wherein the second image version is released in a restricted state;

wherein the two or more target software deployments include target software deployments in the particular group of target software deployments that are part of a test set but do not include target software deployments within the particular group of target software deployments that do not belong to the test set.

5. The method of claim 1, further comprising promoting the second image version from one of a draft state or a restricted state to an active current state, wherein an image version in the active current state represents a most current image version for the particular image;

wherein promoting the second image version to the active current state causes a state of the first image version to change from the active current state to an active state.

6. The method of claim 1, further comprising receiving a second update to the particular image;

in response to receiving the second update to the particular image, generating a third image version for the particular image;

wherein the first image version remains active after the third image version is generated until all target software deployments in the particular group of target software deployments have been updated to one of the third image version or the second image version of the particular image.

7. The method of claim 1, wherein the subscription data further identifies a second group of target software deployments that subscribe to a second image;

wherein the second image represents a second recommended software binary to follow for target software deployments that belong to the second group of target software deployments;

wherein the second group of target software deployments follow changes to the second image but not the first image;

wherein the particular group of target software deployments follow changes to the first image but not the second image.

8. The method of claim 1, further comprising detecting that at least one target software deployment in the particular group of target software deployments has drifted from all active versions of the particular image;

and in response to detecting that the at least one target software deployment in the particular group of software deployments has drifted from all active versions of the particular image, reconciling a configuration of the at least one target software deployment with other target software deployments in the particular group of software deployments.

9. The method of claim 1, further comprising adding a new target software deployment to the particular group of target software deployments;

in response to adding the new target software deployment, updating a set of source components of the new target software deployment based on the second image version of the particular image.

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

identifying a set of target software deployments that share at least one common primary attribute that defines a base version of a software resource;

comparing configuration level signatures for target software deployments in the set of target software deployments to determine which target software deployments share a common configuration level signature;

wherein the configuration level signature is generated, at least in part, from a set of one or more secondary attributes that are variable between different software deployments of the base version of the software resource and that identify one or more of;

a location where the target software deployments are installed, or a set of one or more patches applied to the target software deployments;

arranging the set of target software deployments into a plurality of groups based on which target software deployments share a common configuration level signature;

responsive at least to arranging the set of target software deployments into a plurality of groups based on which target software deployments share a common configuration level signature, generating subscription data that subscribes different respective groups of target software deployments of the plurality of groups to different respective images of a set of images;

wherein each respective image in the set of images represents a recommended software binary to follow for the respective group of target software deployments that are subscribed to the respective image;

wherein a particular image, in the set of images and to which a particular group of target software deployments in the set of target software deployments is subscribed, includes a first image version that is generated from a first set of source components;

generating a second image version for the particular image from a second set of source components that are different than the first set of source components;

updating two or more target software deployments in the particular group of target software deployments that subscribe to the particular image based on the second image version for the particular image; and

maintaining the first image version of the particular image in an active state until each target software deployment in the particular group of target software deployments that is subscribed to the particular image has been updated to a more current version of the particular image.

11. The one or more non-transitory computer-readable media of claim 10, wherein instructions for generating the second image version for the particular image comprise instructions for applying one or more patches to the recommended software binary.

12. The one or more non-transitory computer-readable media of claim 11, wherein the one or more patches are identified based on at least one of a recommendation from a service provider, drift information of patches from the group of target software deployments that subscribe to the particular image, or custom patches requested from a user.

13. The one or more non-transitory computer-readable media of claim 10, wherein the second image version is released in a restricted state;

wherein the two or more target software deployments include target software deployments in the group of target software deployments that are part of a test set but do not include target software deployments within the group of target software deployments that do not belong to the test set.

14. The one or more non-transitory computer-readable media of claim 10, the instructions further causing operations comprising:

promoting the second image version from one of a draft state or a restricted state to an active current state, wherein an image version in the active current state represents a most current image version for the particular image;

wherein promoting the second image version to the active current state causes a state of the first image version to change from the active current state to an active state.

15. The one or more non-transitory computer-readable media of claim 10, the instructions further causing operations comprising receiving a second update to the particular image;

in response to receiving the second update to the particular image, generating a third image version for the particular image;

wherein the first image version remains active after the third image version is generated until all target software deployments in the particular group of target software deployments have been updated to one of the third image version or the second image version of the particular image.

16. The one or more non-transitory computer-readable media of claim 10, wherein the subscription data further identifies a second group of target software deployments that subscribe to a second image;

wherein the second image represents a second recommended software binary to follow for target software deployments that belong to the second group of target software deployments;

wherein the second group of target software deployments follow changes to the second image but not the first image;

wherein the particular group of target software deployments follow changes to the first image but not the second image.

17. The one or more non-transitory computer-readable media of claim 10, the instructions further causing operations comprising detecting that at least one target software deployment in the particular group of target software deployments has drifted from all active versions of the particular image;

and in response to detecting that the at least one target software deployment in the particular group of software deployments has drifted from all active versions of the particular image, reconciling a configuration of the at least one target software deployment with other target software deployments in the particular group of software deployments.

18. The one or more non-transitory computer-readable media of claim 10, the instructions further causing operations comprising adding a new target software deployment to the particular group of target software deployments;

in response to adding the new target software deployment, updating a set of source components of the new target software deployment based on the second image version of the particular image.

19. A method comprising:

maintaining subscription data that subscribes two or more groups of target software deployments to different respective images in a set of images;

wherein each respective image in the set of images represents a recommended software binary to follow for a subscribed group of target software deployments, in the two or more groups of targets software deployments;

receiving a request to initialize a new target software deployment;

in response to the request, automatically selecting a group of target software deployments, from the two or more groups of target software deployments based on a set of primary attributes that identify a base version of a software resource and one or more secondary attributes of the new target software deployment that are variable between different deployments of the base version of the software resource and that identify one or more of;

a location where the group of target software deployments are installed, or a set of one or more patches applied to the group of target software deployments;

performing a comparison of a first configuration level signature of the new target with at least a second configuration level signature associated with at least one active version of a particular image, in the set of images, to which the selected group is subscribed; and

based on the comparison initializing the new target software deployment using the active version of the particular image such that the first configuration level signature for the new target is updated to match the second configuration level signature of the active version of the particular image.

20. The method of claim 19,

wherein the one or more secondary attributes include at least one of a line of business associated with the new target software deployment, a location where the new software deployment is installed, or a patch applied to the new target software deployment.

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

maintaining subscription data that subscribes two or more groups of target software deployments to different respective images in a set of images;

wherein each respective image in the set of images represents a recommended software binary to follow for a subscribed group of target software deployments, in the two or more groups of targets software deployments;

receiving a request to initialize a new target software deployment;

in response to the request, automatically selecting a group of target software deployments, from the two or more groups of target software deployments based on a set of primary attributes that identify a base version of a software resource and one or more secondary attributes of the new target software deployment that are variable between different deployments of the base version of the software resource and that identify one or more of;

a location where the group of target software deployments are installed, or a set of one or more patches applied to the group of target software deployments;

performing a comparison of a first configuration level signature of the new target with at least a second configuration level signature associated with at least one active version of a particular image, in the set of images, to which the selected group is subscribed; and

based on the comparison initializing the new target software deployment using the active version of the particular image such that the first configuration level signature for the new target is updated to match the second configuration level signature of the active version of the particular image.

22. The one or more non-transitory computer-readable media of claim 21, wherein the one or more secondary attributes include at least one of a line of business associated with the new target software deployment, a location where the new software deployment is installed, or a patch applied to the new target software deployment.