Microsoft Technology Licensing, LLC

Amazon Technologies, Inc.

Narayanan Lakshmanan

Bruce Gordon Payette

Kenneth M Hansen

Hemant Mahawar

Jeffrey P Snover

Mark Gray

Rahim Maknojia

Lee Holmes

Xiaoyong Zhou

Nitin Gupta

Miriam Rosenberg

Constantin Sorin Oprea

Christine Moeller

Soniya Parmar

Somak Chattopadhyay

Gautham Atluri

Jianhua Guo

Xuejian Pan

Adila Sadovic

Sharath Gopalappa

Sreeram Krishna Sama

Pavan Kumar Adepu

Systems and techniques are disclosed for generating a session identifier to be used when implementing changes in a complex system that facilitates identification and retrieval of data indicating the scope and impact of the changes. An execution identifier for a set of operations and a service identifier for a service performing the operations may be used as a basis for the session identifier. The session identifier may be provided to computing resources on which operations are performed and logged by the computing resources along with the results of the operations. This activity data associated with the particular set of operations can be retrieved using the session identifier to determine the scope and impact of the operations on the system.

Closed loop change management for cloud-based systems

Technologies are provided for non-monotonic eventual convergence for desired state configuration ('DSC'). In some situations DSC cannot move toward a desired state without first moving further from that state. For example, a file that needs to be replaced with a newer version but that is currently executing (desired state of 'operating') cannot be replaced without first being stopped. But stopping moves in the wrong direction relative to the desired state, which is to have the service operating. This moving away so as to be able to move forward is a problem for conventional DSC systems that results in failures. The solution to this problem is non-monotonic eventual convergence (&#x201c;NMEC&#x201d;) which enables a DSC system to configure a target system for a desired state by moving further away from a desired state if that is needed to eventually reach the desired state.

Non-monotonic eventual convergence for desired state configuration

Systems and methods for desired state configuration (DSC) are disclosed. DSC provides the ability to perform declarative configuration natively within a shell language and to use early-bound schematized data constructs embedded in a late-bound shell language. This allows declarative programming elements to be incorporated into imperative languages, such as scripts for configuration management. Script may combine the power of an imperative shell language with the ease of use of a declarative language and may use both imperative and declarative syntax in the same language.

Declarative configuration elements

Technologies are provided for non-monotonic eventual convergence for desired state configuration. One class of problem in DSC is that, in some situations, DSC cannot move forward toward a desired state without first moving further from the desired state. For example, an executable file providing a service that needs to be replaced with a newer version, but that is currently executing (i.e., in the desired state of 'operating'), cannot be replaced with the newer version without first being stopped. But stopping the service moves in the wrong direction relative to the desired state, which is to have the service operating. This moving away from the desired state so as to be able to move closer to the desired state is a problem for conventional DSC systems that results in failures. The solution to this problem is herein referred to as 'non-monotonic eventual convergence' or &#x201c;NMEC&#x201d;. Such NMEC enables a DSC system to configure a target system for a desired state by moving further away from that state if such is needed to eventually reach the desired state.

Systems and methods for configuring applications and resources on distributed nodes or machines are disclosed. A node exposes a synchronization resource that corresponds to a desired state on a remote resource. The node evaluates a state of the remote resource. A test function may be defined to check whether the remote resource is in the desired state. A set function may also be defined to set a state of the synchronization resource when the remote resource is in the desired state. The node configures the synchronization resource when the remote resource is in the desired state. The synchronization resource may be configured, for example, using a resource provider. The node may evaluate the states of a plurality remote resources. The synchronization resource may be configured when one or more of the remote resources are in the desired state or when all of the remote resources are in the desired state.

Distributed state model for system configuration synchronization

A workflow scripting system is described herein that combines the features of workflows and scripts by automatically translating between the two models. Using the system, a script author can create workflows on the fly using familiar scripting language, and a workflow author can use scripting steps to perform actions. Workflows run in this manner can be setup to execute in their own process to improve robustness or efficiency. Operations in an enterprise environment frequently take a long time and are subject to interruptions. By adding reliability concepts of workflows to a shell environment, users of the system can write scripts to address common needs of large-scale computing environments. Thus, the workflow scripting system blends the available resources provided by workflow and scripting environments to provide a host of powerful, advanced capabilities to IT personnel.

Automatic transcoding and semantic adaptation between scripting and workflow systems

Growing community of inventors

Bothell, WA, United States of America

Narayanan Lakshmanan