Microsoft Technology Licensing, LLC

Romit Chattopadhyay

Mariyan Dimitrov Fransazov

David Nissimoff

Peter Zabback

Peter Alfred Zabback

Solutions for balancing speed and risk by managing configuration changes include: receiving a second configuration item for displacement, in an exposure group, of a first configuration item; receiving an exposure state, wherein the exposure state indicates an exposure tree comprising a first configuration item branch and a second configuration item branch; determining, based at least on the exposure state: a first portion of the exposure group to continue with the first configuration item, and a second portion of the exposure group to receive the second configuration item; deploying the second configuration item to the second portion of the exposure group, in accordance with the exposure state; receiving, from the central orchestrator, an updated exposure state; and deploying the second configuration item in accordance with the updated exposure state. In some examples, the exposure tree is a hierarchical binary tree. An exemplary configuration item includes a software application version.

Configuration change control for computing environments

According to examples, a host device may be instructed to pre-spawn a number of first host processes and a number of second host processes, in which the number of first host processes and the number of second host processes are defined in a first scaling constraint and are each greater than or equal to one. The host device may pre-spawn the second host processes in one or more computing nodes through identification of a host process of the first host processes that is unbound from a client session, termination of the identified host process, and pre-spawning of a second host process that provides a second version of the service based on the termination. The host device may also decrease the number of first host processes and increase the number of second host processes in the one or more computing nodes as defined in a second scaling constraint.

Upgrade a version of a service

According to examples, a method for upgrading a version of a service across a plurality of computing nodes may include instructing a host device to pre-spawn a number of first host processes configured to provide a first version of the service in the computing nodes and to pre-spawn a number of second host processes configured to provide a second version of the service according to a first scaling constraint in the computing nodes. The method may also include, in response to receiving an indication that each of the second host processes is operating properly in the computing nodes, instructing the host device to decrease the number of first host processes and to increase the number of second host processes in the computing nodes as defined in a second scaling constraint.

According to examples, a method for upgrading a version of a service may include instructing a host device to pre-spawn a number of first host processes configured to provide a first version of the service in a computing node and to pre-spawn a number of second host processes configured to provide a second version of the service according to a first scaling constraint in the computing node. The method may also include, in response to receiving an indication that each of the second host processes is operating properly, instructing the host device to decrease the number of first host processes and to increase the number of second host processes as defined in a second scaling constraint.

According to examples, an apparatus may include a processor and a memory on which is stored machine readable instructions that are to cause the processor to receive, from a first node, a client request and a response corresponding to the processed client request, in which the first node is configured to generate the response by processing the client request on a service and processed client request is configured to change a state of the service. The instructions are also to cause the processor to receive, from the first node, a response corresponding to the received request, generate an entry including the received request and response, commit the generated entry into a journal, and send an acknowledgement of the received request and response to the first node after the generated entry is committed into the journal.

Growing community of inventors

Redmond, WA, United States of America

Romit Chattopadhyay