Vmware, Inc.

Omnissa, LLC

Ilya Mayorski

Ivo Petkov

Sabo Rusev

Militsa Borisova

Dobromir Ivanov

Kristiyan Yankov

Ivan Nikolov Ivanov

Plamen Penev

Militsa Arnaudova

Disclosed are various embodiments for the controlling the amount of active updates that can occur during a given time on devices that are associated with tenants (e.g., organizations) and subtenants (e.g., sub-organizations) in a multi-tenant environment. In particular, each tenant and subtenant is assigned throttle corresponding to different update parameters (e.g., an amount of devices executing an active update, an amount of data to be downloaded during a campaign, a time for completing the update campaign, etc.). When an update campaign is established, the update campaign can define the different devices that are to be updated. In some situations, the number of active updates required may exceed the allotted resources for a given subtenant. When a subtenant requires additional resources than what is assigned to complete the update, the subtenant can borrow resources defined by the update parameters from a subtenant peer that has a surplus.

Redistributing update resources during update campaigns

Disclosed are various embodiments for separating creation of and executing of updated campaigns in multitenancy environments. For example, an organization can have a hierarchical structure such that a root organization includes multiple sub-organizations. A root organization administrator may create an update campaign for enforcing software policies on devices that are included in the sub-organizations. A sub-organization administrator can approve and define the execution schedule for when the devices included in the sub-organization can execute the update campaign.

Multitenancy hierarchical update campaigns

Examples of generating a result set from a data lake based upon a real-time data set are described. A data lake can be structured across multiple databases or tables that are not necessarily directly linked to one another. A conjunction schema can specify how data can be queried across the data lake. When an incoming real-time data set is obtained, a multi-query can be generated against the data lake by utilizing the conjunction schema.

Connecting real-time data sets to historical data

Disclosed are various embodiments for updating IoT endpoints. A software update package can be deployed to a IoT gateway. The software package can have lifecycle scripts and software executable for installation on IoT endpoints. The lifecycle scripts represent different lifecycle phases of the update process.

Deploying device campaign updates to IoT devices

Disclosed are various embodiments for collecting and presenting IoT metrics. A software update package can be deployed to an IoT gateway. A device template used to register an IoT endpoint with an IoT management service can also define metrics that can be collected regarding the performance of the IoT endpoints.

IoT endpoint metrics

Managing the creation and execution of update campaigns in an multitenancy hierarchy

Disclosed are various embodiments for automatically creating device campaigns. A computing device first determines that a second version of a software package assigned to an existing device campaign has been uploaded to a data store. The existing device campaign can include an existing compliance policy applicable to individual IoT endpoints assigned to the existing device campaign. The compliance policy may specify that a first version of the software package be installed on the individual IoT endpoints. In response, to the change, the computing device can create a new device campaign that includes a new compliance policy applicable to the individual IoT endpoints assigned to the new device campaign. The new compliance policy may specify that the second version of the software package be assigned to the individual IoT endpoints.

Automatic creation of device campaigns

Approaches for automatically creating device campaigns are disclosed herein. A computing device first determines that a second version of a software package assigned to an existing device campaign has been uploaded to a data store. The existing device campaign can include an existing compliance policy applicable to individual IoT endpoints assigned to the existing device campaign. The compliance policy may specify that a first version of the software package be installed on the individual IoT endpoints. In response, to the change, the computing device can create a new device campaign that includes a new compliance policy applicable to the individual IoT endpoints assigned to the new device campaign. The new compliance policy may specify that the second version of the software package be assigned to the individual IoT endpoints.

Growing community of inventors

Sofia, Bulgaria

Ilya Mayorski