Redistributing update resources during update campaigns
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.
1. A system for redistributing resources between sub-organizations during an update campaign, the system comprising:
at least one computing device; and
at least one application executable on the at least one computing device, wherein, when executed, the at least one application causes the at least one computing device to at least:
create an update campaign for updating a plurality of devices in a first organization;
initiate an execution of the update campaign;
identify additional devices to be included in the update campaign for a first organization;
determine that executing the update campaign in the additional devices exceeds resources allotted to the first organization;
identify a second organization that has a surplus of resources;
allocate at least a portion of the resources allotted to the second organization to the first organization; and
initiate the execution of the update campaign for the additional devices in the first organization.
2. The system of claim 1 , wherein the resources comprise at least one of: an amount of devices executing an active update, an amount of data to be downloaded during the updated campaign, or a time for completing the update campaign.
3. The system of claim 1 , wherein the first organization and the second organization are sub-organizations of an enterprise organization.
4. The system of claim 3 , wherein the enterprise organization is allotted a predefined number of resources, and the first organization and the second organization are allotted a subset of the predefined number of resources.
5. The system of claim 1 , wherein, when executed, the at least one application further causes the at least one computing device to at least receive one or more inputs from a user interacting with an administrative console, the one or more inputs defining the resources to be allotted to the first organization and the second organization.
6. The system of claim 1 , wherein the at least one computing device is in data communication with the plurality of devices over a network and, when executed, the at least one application further causes the at least one computing device to at least:
detect a computing capacity associated with at least one of: the at least one computing device or the network; and
generate a recommendation for throttle settings defining allotted resources for the first organization and the second organization based on the detected computing capacity.
7. The system of claim 1 , wherein:
the additional devices are registered with an enterprise organization following the execution of the updated campaign; and
when executed, the at least one application further causes the at least one computing device to at least evaluate the update campaign following a predefined period of time, the identification of the additional devices occurring during the evaluation of the update campaign.
8. A method for redistributing resources between sub-organizations during an update campaign, comprising:
creating, by at least one computing device, an update campaign for updating a plurality of devices in a first organization;
initiating, by the at least one computing device, an execution of update campaign;
identifying, by the at least one computing device, additional devices to be included in the update campaign for a first organization;
determining, by the at least one computing device, that executing the update campaign in the additional devices exceeds resources allotted to the first organization;
identifying, by the at least one computing device, a second organization that has a surplus of resources;
allocating, by the at least one computing device, at least a portion of the resources allotted to the second organization to the first organization; and
initiating, by the at least one computing device, the execution of the update campaign for the additional devices in the first organization.
9. The method of claim 8 , wherein the resources comprise at least one of: an amount of devices executing an active update, an amount of data to be downloaded during the updated campaign, or a time for completing the update campaign.
10. The method of claim 8 , wherein the first organization and the second organization are sub-organizations of an enterprise organization.
11. The method of claim 10 , wherein the enterprise organization is allotted a predefined number of resources, and the first organization and the second organization are allotted a subset of the predefined number of resources.
12. The method of claim 8 , further comprising receiving, by the at least one computing device, one or more inputs from a user interacting with an administrative console, the one or more inputs defining the resources to be allotted to the first organization and the second organization.
13. The method of claim 8 , wherein the at least one computing device is in data communication with the plurality of devices over a network and, further comprising:
detecting, by the at least one computing device, a computing capacity associated with at least one of: the at least one computing device or the network; and
generating, by the at least one computing device, a recommendation for throttle settings defining allotted resources for the first organization and the second organization based on the detected computing capacity.
14. The method of claim 8 , wherein the additional devices are registered with an enterprise organization following the execution of the updated campaign, and further comprising evaluating, by the at least one computing device, the update campaign following a predefined period of time, the identification of the additional devices occurring during the evaluation of the update campaign.
15. A non-transitory, computer-readable medium embodying a program for redistributing resources between sub-organizations during an update campaign, wherein when executed by a computing device, the program causes the computing device to at least:
create an update campaign for updating a plurality of devices in a first organization;
initiate an execution of update campaign;
identify additional devices to be included in the update campaign for a first organization;
determine that executing the update campaign in the additional devices exceeds resources allotted to the first organization;
identify a second organization that has a surplus of resources;
allocate at least a portion of the resources allotted to the second organization to the first organization; and
initiate the execution of the update campaign for the additional devices in the first organization.
16. The non-transitory, computer-readable medium of claim 15 , wherein the resources comprise at least one of: an amount of devices executing an active update, an amount of data to be downloaded during the updated campaign, or a time for completing the update campaign.
17. The non-transitory, computer-readable medium of claim 15 , wherein:
the first organization and the second organization are sub-organizations of an enterprise organization; and
the enterprise organization is allotted a predefined number of resources, and the first organization and the second organization are allotted a subset of the predefined number of resources.
18. The non-transitory, computer-readable medium of claim 15 , wherein, when executed, the program further causes the computing device to at least receive one or more inputs from a user interacting with an administrative console, the one or more inputs defining the resources to be allotted to the first organization and the second organization.
19. The non-transitory, computer-readable medium of claim 15 , wherein the computing device is in data communication with the plurality of devices over a network and, when executed, the program further causes the computing device to at least:
detect a computing capacity associated with at least one of: the at least one computing device or the network; and
generate a recommendation for throttle settings defining allotted resources for the first organization and the second organization based on the detected computing capacity.
20. The non-transitory, computer-readable medium of claim 15 , wherein:
the additional devices are registered with an enterprise organization following the execution of the updated campaign; and
wherein, when executed, the program further causes the computing device to at least evaluate the update campaign following a predefined period of time, the identification of the additional devices occurring during the evaluation of the update campaign.