Vmware, Inc.

Omnissa, LLC

Sabo Rusev

Ivo Petkov

Ilya Mayorski

Militsa Borisova

Dobromir Ivanov

Alexander Dimitrov

Kristiyan Georgiev

Dimitar Kirilov Kostov

Miroslav Mitevski

Ivan Nikolov Ivanov

Kristiyan Yankov

Plamen Penev

Nikola Atanasov

Stanislav Asenov Hadjiiski

Alexandar Savov

Sonya Ivanova Tsolova

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 automatic enrollment of Internet of Things (IoT) endpoints. An identity of an IoT endpoint is verified by an IoT gateway. The IoT gateway is configured to transmit, over a network, an enrollment request to an IoT management service. The enrollment of the IoT endpoint with the IoT management service is confirmed. A compliance policy for the IoT endpoint is retrieved from a command queue. The compliance policy is stored in the command queue until retrieved by the IoT gateway. The IoT gateway enforces the compliance policy on the IoT endpoint.

Policy-based auto-enrollment of devices in ota 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

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

Disclosed are various embodiments for automatic enrollment of Internet of Things (IoT) endpoints. An enrollment request is received from an internet of things (IoT) gateway, the enrollment request comprising an identifier for an IoT endpoint and at least one property of the IoT endpoint. In response to enrollment of the IoT endpoint, a campaign template is identified that matches the at least one property of the IoT endpoint. A campaign associated with the campaign template is then identified, the campaign comprising a collection of policies that are applicable to individual IoT endpoints assigned to the campaign. Subsequently, the IoT endpoint is assigned to the campaign.

Auto-enrollment of IoT endpoints

Disclosed are various embodiments for the automatic generation of configurations for Internet of Things (IoT) endpoints. At least one metric is collected for an Internet of Things (IoT) endpoint. Then, a function that generates configuration data for the IoT endpoint is invoked. In some instances, the at least one metric is supplied as an argument for the IoT endpoint. The configuration data is received as a result of the function. A device campaign is then created to apply the configuration data to the IoT endpoint. The IoT endpoint can then be assigned to the device campaign.

Automatic generation of configurations for IoT endpoints

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.

An example method of managing virtualized computing resources provided by a public cloud includes: grouping subscriptions in the public cloud into reservations, each of the reservations including constraints on virtualized computing resources provided by at least one of the subscriptions; allocating the reservations among a plurality of principals; receiving a request to provision a workload from a user associated with a first principal of the plurality of principals, wherein the workload includes metadata describing constraints of the workload; generating a deployment plan for the workload based on the metadata therein and at least one of the reservations allocated to the first principal, the deployment plan specifying a first subscription of the subscriptions; and transmitting a deployment.

Pooling public cloud resources from different subscriptions using reservations

An example method of extending a cloud manager configured to manage a public cloud includes: receiving a content package at the cloud manager, the content package including a component entity, the component entity including a resource type entity that represents a resource provided by the public cloud, a user interface (UI) form entity that defines a UI for configuring the resource, and a lifecycle operations logic that extends at least one phase of a workflow of the cloud manager; receiving a request from a user through the UI defined by the UI form entity to create the resource in the public cloud; executing the workflow of the cloud manager in response to the request; and executing the lifecycle operations logic during execution of the workflow.

Growing community of inventors

Sofia, Bulgaria

Sabo Rusev