# US 2017/0286080 A1 · Policy driven flight management

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0286080 A1
- Document ID: US20170286080A1
- Status: Published application
- Kind: A1
- Application number: 15/196,069
- Filed: 2016-06-29
- Published: 2017-10-05
- Earliest claimed: 2016-04-03
- Assignees: Microsoft Technology Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: Shobana Krishnamoorthy; llker Celikyilmaz; Randy David Thomson; Min Shao; Divyachapan S. Padur
- Web page: https://patentgrep.com/patent/US20170286080A1

## CPC

- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management
- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A hosted service may include multiple applications and have a large number of active features, each in varying stages of deployment, that are gradually rolled out in one or more deployment environments. The hosted service may include a flight state machine, which may provide policy based flight management for feature rollout. For example, in response to receipt of a flight request associated with a feature of the hosted service, the flight state machine may be configured to retrieve a policy associated with rollout of the feature, determine a flight state, and determine a deployment state of the feature. The flight state machine may then be configured to initiate or continue deployment of the feature in a current deployment environment or initiate deployment of the feature in a next environment based on the policy, the flight state, and the deployment state of the feature.

## Claims

### Claim 1

A method to provide policy driven flight management, the method comprising:
receiving a flight request associated with a feature of a hosted service; and
in response to receiving the flight request:
retrieving a policy associated with rollout of the feature from a policy store, wherein the rollout includes one or more deployment environments;
determining a flight state;
determining a deployment state of the feature; and
initiating or continuing deployment of the feature for a current deployment environment or initiating deployment of the feature in a next deployment environment based on the policy, the flight state, and the configuration deployment state of the feature.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
in response to creation of the feature, associating the feature with a flight.

### Claim 3 (depends on 2)

The method of claim 2, wherein the flight request includes to advance the flight, suspend the flight, resume the flight, deactivate the flight, or delete the flight.

### Claim 4 (depends on 2)

The method of claim 2, further comprising:
tracking a status of the flight.

### Claim 5 (depends on 4)

The method of claim 4, further comprising:
generating or updating a report to be provided to a developer of the feature based on the tracked status, wherein the report is a flight configuration file.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
validating the deployment of the feature in the current deployment environment prior to initiating deployment of the feature in the next deployment environment based on the policy, the flight state, and the configuration deployment state of the feature.

### Claim 7 (depends on 1)

The method of claim 1, wherein determining the flight state comprises:
determining whether the flight state is created, active, suspended, expired, or deleted.

### Claim 8 (depends on 1)

The method of claim 1, wherein determining the deployment state of the feature comprises:
determining whether the deployment state of the feature is not started, deploying, completed, or failed.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
providing options for a developer to add, modify, and delete one or more rules of the policy.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
employing local scope management.

### Claim 11

A computing device to provide policy driven flight management, the computing device comprising:
a memory configured to store instructions; and
one or more processors coupled to the memory, the one or more processors configured to execute a hosted service in conjunction with the instructions stored in the memory, wherein the hosted service comprises:
a flight state machine configured to:
receive a flight request associated with a feature of the hosted service; and
in response to receipt of the flight request:
retrieve a policy associated with rollout of the feature from a policy store, wherein the rollout includes one or more deployment environments;
determine a state of the flight;
determine a deployment state of the feature; and
initiate or continue deployment of the feature for a current deployment environment or initiate deployment of the feature in a next deployment environment based on the policy, the state of the flight, and the deployment state of the feature.

### Claim 12 (depends on 11)

The computing device of claim 11, wherein the policy comprises rules that define properties associated with the rollout.

### Claim 13 (depends on 12)

The computing device of claim 12, wherein the rules are applicable to the feature or are applicable to a group of features to which the feature is a member of.

### Claim 14 (depends on 12)

The computing device of claim 12, wherein the rules define the one or more deployment environments.

### Claim 15 (depends on 12)

The computing device of claim 12, wherein the rules define criteria for initiating the deployment of the feature in the next deployment environment

### Claim 16 (depends on 15)

The computing device of claim 15, wherein the criteria includes a validation time period for the deployment of the feature in the current deployment environment, a risk level of the deployment of the feature in the next deployment environment, and a speed of the deployment of the feature.

### Claim 17 (depends on 12)

The computing device of claim 12, wherein the rules define a relationship between the rollout of the feature and a rollout of another feature of the hosted service.

### Claim 18 (depends on 11)

The computing device of claim 11, wherein the flight state machine comprises one or more of a feature management component, flight management component, and a policy management component.

### Claim 19

A computer readable memory device with instructions stored thereon to provide policy driven flight management, the instructions comprising:
receiving a flight request associated with a feature of a hosted service; and
in response to receiving the flight request:
retrieving a policy associated with rollout of the feature from a policy store, wherein the rollout includes one or more deployment environments;
determining a flight state;
determining a deployment state of the feature; and
initiating or continuing deployment of the feature for a current deployment environment or initiating deployment of the feature in a next deployment environment based on the policy, the flight state, and the deployment state of the feature.

### Claim 20 (depends on 19)

The computer readable memory device of claim 19, the instructions further comprising:
retrieving policies associated with the rollout of the feature for each application within the hosted service from the policy store.
