Inter-tenant and intra-tenant flock management

Patent metadata

Field	Value
Publication number	US-2016350098-A1
Application number	US-201514849467-A
Country	US
Kind code	A1
Filing date	Sep 9, 2015
Priority date	May 29, 2015
Publication date	Dec 1, 2016
Grant date	—

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.

First claim

What is claimed is:

1 . A method comprising:
determining, by a network service, a target end state for a software product that is deployed by a set of one or more tenants; generating, by the network service for the set of one or more tenants, a cacheable object for updating the software product to the target end state; generating, by the network service for a particular tenant of 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; wherein the tenant-specific configuration data varies between at least two tenants of the set of one or more tenants; wherein the target-specific configuration data varies between at least two targets of the particular tenant; sending the cacheable object from the network service to each tenant of the set of one or more tenants; sending the tenant-specific configuration data and the target-specific configuration data from the network service to the particular tenant of the set of one or more tenants.

2 . The method of claim 1 , wherein the set of one or more tenants includes a plurality of tenants, the method further comprising generating, by the network service for each respective tenant of the plurality of tenants, different tenant-specific configuration data and target-specific configuration data.

3 . The method of claim 1 , wherein the particular tenant has a plurality of deployments of the software product, the method further comprising generating, by the network service for each deployment of the plurality of deployments, different target-specific configuration data.

4 . The method of claim 1 , wherein the cacheable object is a gold image, the method further comprising maintaining, by the network service, subscription data that identifies which tenants are subscribed to follow changes to the gold image; wherein the set of one or more tenants are subscribed to follow the gold image.

5 . The method of claim 4 , wherein generating, by the network service for the set of one or more tenants, a cacheable object for updating the software product to the target end state comprises applying a set of one or more patches to a previous version of the gold image.

6 . The method of claim 1 , wherein the set of one or more tenants includes a plurality of tenants; wherein the cacheable object is sent to the particular tenant at a different time than at least one other tenant in the set of one or more tenants based on priority information maintained by the network service for the plurality of tenants.

7 . The method of claim 1 , wherein the particular tenant is associated with a gateway for storing the cacheable object and a plurality of target deployments, the method further comprising monitoring, by the network service, which target deployments of the plurality of target deployments have been updated using the cacheable object.

8 . The method of claim 1 , wherein sending the cacheable object from the network service to each tenant of the set of one or more tenants comprises sending a notification to each tenant of the set of one or more tenants that the cacheable object is available for download; wherein each tenant of the set of one or more tenants downloads the cacheable object to a gateway.

9 . The method of claim 1 , further comprising determining whether the particular tenant has downloaded the cacheable object within a threshold period of time; wherein sending the cacheable object from the network service to the particular tenant is performed in response to determining that the particular tenant has not downloaded the cacheable object within the threshold period of time.

10 . The method of claim 1 , wherein the tenant-specific configuration data is generated based on settings associated with the software product that are custom to a particular tenant; wherein the target-specific configuration data is generated based on settings associated with the software product that are custom to a particular deployment of the software product.

11 . A method comprising:
receiving, by a network service from a set of one or more tenants, metadata that identifies a set of components for one or more deployments of a software product; generating, by the network service, tenant-anonymous data based on the set of components identified by the metadata for the one or more deployments of the software product; wherein the tenant-anonymous data does not reveal sensitive information for the set of one or more tenants and, when combined with tenant-specific data, forms a tenant-specific deployment of software running in a computing environment to serve a particular tenant; sending the tenant-anonymous data from the network service to a particular tenant that has a particular deployment of the software product.

12 . The method of claim 11 ,
wherein the set of components identified by the metadata includes a particular patch applied to at least one deployment of the one or more deployments of the software product; wherein the tenant-anonymous data includes a recommendation for applying the particular patch to the particular deployment of the software product.

13 . The method of claim 11 , further comprising:
receiving, by a network service from the particular tenant, metadata that identifies a particular set of components for the particular deployment of the software product; comparing the particular set of components with the set of components for the one or more deployments of the software product; wherein the tenant-anonymous data is further based on a result of said comparing the particular set of components with the set of components for the one or more deployments of the software product.

14 . The method of claim 11 , wherein the tenant-anonymous data identifies a set of one or more patches that have improved a performance of a at least one deployment of the one or more deployments.

15 . The method of claim 11 , wherein the particular tenant and the one or more tenants are subscribed to a gold image for a software product; wherein the particular deployment and the one or more deployments are updated in response to an update to the gold image.

16 . The method of claim 15 , wherein the tenant-anonymous data identifies a status associated with updating the one or more deployments of the software product to a most recent version of the particular gold image.

17 . The method of claim 11 , wherein at least one tenant of the one or more tenants is subscribed to a particular gold image; wherein the particular tenant is not currently subscribed to the particular gold image; wherein the tenant-anonymous data recommends that the particular tenant subscribe to the particular gold image.

18 . The method of claim 11 , wherein the tenant-anonymous data recommends that the particular tenant delay an update of a software product in response to determining that the update has negatively impacted performance for at least one deployment of the one or more deployments of the software product.

19 . The method of claim 11 , wherein the tenant-anonymous data identifies one or more rogue patches applied to at least one deployment of the one or more deployments of the software product.

20 . The method of claim 11 , further comprising generating, by the network service, an updated version of a gold image for the particular tenant based on the tenant-anonymous data.

2

Assignees

• Oracle Int Corp

Inventors

• Kuchibhotla Balasubrahmanyam
• Srinivasan Hariprasanna
• Paliwal Bharat
• Khanuja Kamaldeep

Classifications

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• G06F9/44505

  Configuring for program initiating, e.g. using registry, configuration files · CPC title

• G06F8/60

  Software deployment · CPC title

• H04L67/34

  involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title

• G06F8/65 Primary

  Updates (security arrangements therefor G06F21/57) · CPC title