Updating a cloud service with farms grouped for a same update deployment stage

Patent metadata

Field	Value
Publication number	US-2024394035-A1
Application number	US-202318323959-A
Country	US
Kind code	A1
Filing date	May 25, 2023
Priority date	May 25, 2023
Publication date	Nov 28, 2024
Grant date	—

Abstract

An orchestrator for updating a cloud service includes: an orchestrator service host computer comprising a processor and memory; an orchestrator service for execution by the orchestrator service host computer for orchestrating updates to farms of the cloud service over a service bus; a stage management service for determining which farms should be in each stage of an update deployed by the orchestrator service; and a grouping table identifying farms that should be in a common stage of the update deployed by the orchestrator service. The stage management service places farms grouped in the grouping table in a common stage of the update deployment.

First claim

What is claimed is:

1 . An orchestrator for updating a cloud service comprising:
an orchestrator service host computer comprising a processor and memory; an orchestrator service for execution by the orchestrator service host computer for orchestrating updates to farms of the cloud service over a service bus; a stage management service for determining which farms should be in each stage of an update deployed by the orchestrator service; and a grouping table identifying farms that should be in a common stage of the update deployed by the orchestrator service, wherein the stage management service places farms grouped in the grouping table in a common stage of the update deployment.

2 . The orchestrator of claim 1 , further comprising a temperature monitoring service for determining a temperature of individual farms, wherein the stage management service determines which farms should be in each stage of update deployment based on farm temperature except as overridden by farm groupings in the table.

3 . The orchestrator of claim 2 , wherein the stage management service is to determine when a requested percentage of a userbase for a next update stage, based on farm temperature, would split a first group of farms grouped in the grouping table into different update stages and, in response, hold the first group of farms for update in a subsequent stage that will not split the first group.

4 . The orchestrator of claim 3 , wherein, when holding the first group of farms for the subsequent stage, the stage management service fills a current stage with other farms that are not grouped in groups large enough to be split due to the requested percentage of the userbase.

5 . The orchestrator of claim 1 , further comprising an Application Programming Interface (API) of the stage management service through which the orchestrator service requests an identification of farms for each stage of update deployment.

6 . The orchestrator of claim 5 , wherein farms are grouped in a hierarchy using labels and names, with a farm label comprising a plurality of farms with different farm names.

7 . The orchestrator of claim 6 , wherein the API of the stage management service comprises:
a first API for when farms for update in a common stage are grouped by farm label; and a second API for when farms for update in a common stage are grouped by farm name.

8 . The orchestrator of claim 6 , wherein the orchestrator service performs synchronization of updates to grouped farm names as part of a cross-regional controller network move.

9 . A method of deploying updates for a cloud service that is supported by a population of farms, the update being deployed in a series of stages that successively include a larger percentage of a userbase, the method comprising:
identifying a customer of the cloud service with tenants of the cloud service in different regions such that the tenants are at risk of being place in different stages of the update deployment resulting in a potential difference in cloud service version for different parts of the customer; for the identified customer, determining which farms of the cloud service should be in a single stage of the update deployment to avoid the potential difference in cloud service version for different parts of the customer; generating a grouping table identifying the farms that should be in the single stage of the update deployment; and overriding other considerations, based on the grouping table, to place the identified farm, as grouped in the grouping table, in a common stage of the update deployment.

10 . The method of claim 9 , further comprising:
with a temperature monitoring service, determining a temperature of individual farms; and determining which farms should be in each stage of update deployment based on farm temperature except as overridden by farm groupings in the table.

11 . The method of claim 10 , further comprising:
determining when a requested percentage of a userbase for a next update stage would, based on farm temperature, split a first group of farms grouped in the grouping table into different update stages and, in response, holding the first group of farms for update in a subsequent stage that will not split the first group.

12 . The method of claim 11 , further comprising, when holding the first group of farms for the subsequent stage, filling a current stage with other farms that are not grouped in groups large enough to be split due to the requested percentage of the userbase.

13 . The method of claim 9 , further comprising an Application Programming Interface (API) of a stage management service through which an orchestrator service requests an identification of farms for each stage of update deployment.

14 . The method of claim 13 , wherein farms are grouped in a hierarchy using labels and names, with a farm label comprising a plurality of farms with different farm names.

15 . The method of claim 14 , wherein the API of the stage management service comprises:
a first API for when farms for update in a common stage are grouped by farm label; and a second API for when farms for update in a common stage are grouped by farm name.

16 . The method of claim 14 , wherein synchronization of updates to grouped farm names is performed as part of a cross-regional controller network move.

17 . The method of claim 9 , wherein use of the grouping table is subject to an expiration data or user input to end synchronization of updates to grouped farms.

18 . The method of claim 9 , wherein grouping farms for a customer in the grouping table is provided based on customer type.

19 . A processing system comprising:
a processor; a network interface to a service bus in communication with a population of farms supporting a cloud service; a memory storing executable instructions which, when executed by the processor, cause the processor, alone or in combination with other processors, to implement a cloud service update orchestration service, the orchestration service comprising a database of payload stage sequence overrides for when farms are being allocated to a stage of an update deployment; and a management control plane service to update the overrides based on an update service client dynamic link library, the overrides protecting a group of farms from being allocated to different stages of the update deployment.

20 . The processing system of claim 19 , further comprising a temperature compute application to determine a temperature for farms in the population of farms and update the payload stage sequence overrides based on the determined temperatures.

Assignees

• Microsoft Technology Licensing Llc

Inventors

• Verma Nidhi
• Nigam Rahul
• Panda Biranchi Narayan

Classifications

• G06F2009/45575

  Starting, stopping, suspending or resuming virtual machine instances · CPC title

• G06F2009/4557

  Distribution of virtual machine instances; Migration and load balancing · CPC title

• G06F9/45558

  Hypervisor-specific management and integration aspects · CPC title

• G06F8/65 Primary

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