INTER-TENANT AND INTRA-TENANT FLOCK MANAGEMENT
First Claim
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.
1 Assignment
0 Petitions
Accused Products
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.
24 Citations
40 Claims
-
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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
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. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18, 19, 20)
-
-
21. One or more non-transitory computer-readable media storing instruction which, when executed by one or more processors, cause operations 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. - View Dependent Claims (22, 23, 24, 25, 26, 27, 28, 29, 30)
-
-
31. One or more non-transitory computer-readable media storing instruction which, when executed by one or more processors, cause operations 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. - View Dependent Claims (32, 33, 34, 35, 36, 37, 38, 39, 40)
-
Specification