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.

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.

Abstract: Techniques are described for managing updates across one or more targets using standard software images. In one embodiment, a first version of a software application is deployed on a set of one or more targets. A software binary is then generated for an updated version of the software application. The software binary for the updated version of the software application is deployed to the set of one or more targets. While the software binary for the updated version of the software application is deployed, the previous version of the software application remains active on a particular target. The updated version of the software application is activated, using the software binary, on the particular target.

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.

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.

Abstract: Disclosed are a system, method, and computer program product for a unified system for implementing clones. The unified system includes the appropriate infrastructure to create, maintain, and administer clones and supporting data sources in the computing environment. In addition, a user interface is provided that is capable of visually displaying relationships and lineages of sources and clones in the system. The user interface provides functionality to select any given object, and to trace its parent-child relationships to highlight its related parent and/or child source/clone.

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.

Abstract: Techniques are described for inter-tenant and intra-tenant software management services in a cloud environment. In an embodiment, a network service determines a target end state for a software product that is deployed by a set of one or more tenants. The network service generates, for the set of one or more tenants, a cacheable object for updating the software product to the target end state. The network service generates, for a particular tenant in the set of one or more tenants, tenant-specific configuration data for applying configurations associated with the respective tenant and target-specific configuration data for applying configurations associated with a respective deployment of the software product. The network service sends the cacheable object to each tenant of the set of one or more tenants and the configuration data to the particular tenant.

Abstract: Techniques are described for managing a plurality of different versions of a software application for set of software deployments. In one embodiment, a reference for a set of one or more target software deployments is maintained on a computing device. The reference is associated with a plurality of versions of a software application. An updated version of the software application is received for the set of one or more target software deployments. In response, a particular version of the software application is replaced with the updated version of the software application. After replacing the particular version of the software application with the updated version of the software application, the reference is associated with the updated version of the software application and not the particular version of the software application.

Abstract: Techniques are described for generating configuration level signatures. In an embodiment, one or more computing devices are used to generate a first signature for a particular software deployment that is configured at a particular configuration level. The first signature is generated based on digest information that identifies a plurality of deployed source components for the particular software deployment. Mapping data is stored that maps the first signature to the digest information identifying the plurality of deployed source components for the particular software deployment. A second signature is generated based on information that defines target source components for a set of software deployments that includes the particular software deployment. The first signature is compared with the second signature to determine whether the deployed source components satisfy the target source components. An indication of whether the deployed source components satisfy the target source components is stored.

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.

Abstract: Techniques are described for managing drift within a standardized environment. According to one embodiment, an end state definition is stored that identifies a standard set of source components for a plurality of targets. A drift manager determines that at least one target of the plurality of targets has drifted from the standard set of source components identified by the end state definition. After determining that the at least one target of the plurality of targets has drifted from the standard set of source components identified by the end state definition, the drift manager reconciles the at least one target with the end state definition.

Abstract: Techniques are described for inter-tenant and intra-tenant software management services in a cloud environment. In an embodiment, a network service determines a target end state for a software product that is deployed by a set of one or more tenants. The network service generates, for the set of one or more tenants, a cacheable object for updating the software product to the target end state. The network service generates, for a particular tenant in the set of one or more tenants, tenant-specific configuration data for applying configurations associated with the respective tenant and target-specific configuration data for applying configurations associated with a respective deployment of the software product. The network service sends the cacheable object to each tenant of the set of one or more tenants and the configuration data to the particular tenant.

Abstract: Techniques are described for managing a plurality of different versions of a software application for set of software deployments. In one embodiment, a reference for a set of one or more target software deployments is maintained on a computing device. The reference is associated with a plurality of versions of a software application. An updated version of the software application is received for the set of one or more target software deployments. In response, a particular version of the software application is replaced with the updated version of the software application. After replacing the particular version of the software application with the updated version of the software application, the reference is associated with the updated version of the software application and not the particular version of the software application.

Abstract: Techniques are described for generating configuration level signatures. In an embodiment, one or more computing devices are used to generate a first signature for a particular software deployment that is configured at a particular configuration level. The first signature is generated based on digest information that identifies a plurality of deployed source components for the particular software deployment. Mapping data is stored that maps the first signature to the digest information identifying the plurality of deployed source components for the particular software deployment. A second signature is generated based on information that defines target source components for a set of software deployments that includes the particular software deployment. The first signature is compared with the second signature to determine whether the deployed source components satisfy the target source components. An indication of whether the deployed source components satisfy the target source components is stored.

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.

Abstract: Techniques are described for managing updates across one or more targets using standard software images. In one embodiment, a first version of a software application is deployed on a set of one or more targets. A software binary is then generated for an updated version of the software application. The software binary for the updated version of the software application is deployed to the set of one or more targets. While the software binary for the updated version of the software application is deployed, the previous version of the software application remains active on a particular target. The updated version of the software application is activated, using the software binary, on the particular target.

Abstract: Disclosed are a system, method, and computer program product for a unified system for implementing clones. The unified system includes the appropriate infrastructure to create, maintain, and administer clones and supporting data sources in the computing environment. In addition, a user interface is provided that is capable of visually displaying relationships and lineages of sources and clones in the system. The user interface provides functionality to select any given object, and to trace its parent-child relationships to highlight its related parent and/or child source/clone.

Abstract: Techniques are described for managing drift within a standardized environment. According to one embodiment, an end state definition is stored that identifies a standard set of source components for a plurality of targets. A drift manager determines that at least one target of the plurality of targets has drifted from the standard set of source components identified by the end state definition. After determining that the at least one target of the plurality of targets has drifted from the standard set of source components identified by the end state definition, the drift manager reconciles the at least one target with the end state definition.

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.