Microsoft Technology Licensing, LLC

Alexander Evgenievich Nosov

Patrick R Kenny

Raymond W McCollum

Lev Novik

Tomas Talius

Travis Muhlestein

Sameer Arun Verkhedkar

Ahmed El-Shimi

Ashvinkumar J Sanghvi

Robin Dhananjay Dhamankar

Sandeep Lingam

Vishwajith Kumbalimutt

Howard M Hance

Stephen Wah Lee

Michael A Thatcher

Daniel L Lemmond

Satyanarayana Narlapuram

Steve Menzies

Nicholas Alexander Allen

Robert M Fries

John Anthony Taylor

Kartik Paramasivam

Brian Reistad

Igor Sedukhin

Johannes Helander

Daniel Eshner

Richard Shawn Bice

Tony Petrossian

Ramasubramaniam Poornalingam

Michael Oliver Neary

Steve Lee

Raul Guillermo Camacho

William Leo Oellermann, Jr

Yashesvi Sharma

Vishwa Kumbalimutt

A system and method include association of a first plurality of software licenses of a first type with a first subscription associated with a first plurality of cloud-based resources, determination of a first number of the first plurality of software licenses to activate based on the types of the first plurality of resources, activation of the first number of the first plurality of software licenses, monitoring of usage of the first plurality of resources, determination, based on the monitored usage, of a second one or more resources to associate with the first subscription, determination, in response to determining the second resources, of a second number of the first plurality of software licenses to activate based on the types of the second one or more resources, activation of the second number of the first plurality of software licenses, and association of the second resources with the first subscription.

Rights management of cloud resources

Application service configuration of a timeframe for performing dataloss failover (failover that does not attempt full data replication to the secondary data store) from a primary data store to the secondary data store. A data-tier service, such as perhaps a database as a service (or DBaaS), could receive that configuration from the application service and automatically perform the dataloss failover as configured by the application service. This relieves the application service from having to manage the failover workflow while still allowing the application service to appropriately balance the timing of dataloss failover, which will depend on a very application-specific optimal balance between the negative effects of operational latency versus dataloss.

Application service-level configuration of dataloss failover

A maximum lag between data stores can be specified that corresponds to a recovery point objective defined in a service level agreement. Lag can be monitored during a data replication between a primary data store and a secondary data store located in geographically different regions. Activity on the primary data store including incoming data transactions can be throttled as a function of the lag and the maximum lag.

Recovery point objective enforcement

Semi-automatic failover includes automatic failover by a service provider as well as self-serviced failover by a service consumer. A signal can be afforded by a service provider based on analysis of an incident that affects the service provider. Initiation of self-serviced failover by a service consumer can be predicated on the signal. In one instance, the signal provides information that aids a decision of whether or not to failover. In another instance, the signal can grant or deny permission to perform a self-serviced failover.

Semi-automatic failover

Service virtualization containers to aggregate service functionality from a plurality of services into an apparent service exhibiting the aggregated functionality. A plurality of service implementations is assigned to a service virtualization container. The container selects some of the service operations from the service implementations. One or more message characteristics are assigned to the service operations in one or more routing tables. A message is received at a service endpoint different from the service endpoints of any of the service implementations. A determination is made of one or more message characteristics. The one or more routing tables are consulted to select a determined service operation based on the message characteristics. The message is routed to the selected service implementation. Embodiments may also include functionality for aggregating metadata from service implementations and providing metadata based on the aggregated metadata to clients requesting metadata from a service virtualization container.

Service virtualization container

Embodiments described herein are based on the principle that shells execute commands as units of characters. Accordingly, embodiments herein provide for a sending side with enough intelligence to isolate each command, examine it, perform some levels of validation, and deliver a structured representation of the command to the remote processor before doing any network operations. More specifically, embodiments herein provided for a mechanism of identifying a command and encapsulating the command into a single message (e.g., a SOAP, HTTPS, or other type message), which is then sent to a remote shell for processing as an entire unit. Accordingly, embodiments herein treat the command as a single unit, rather than as a character-oriented transmission.

Shell input/output segregation

A virtual environment can be configured to coordinate life cycles of virtual machines and application programs executing therein. In one implementation, the virtual environment includes an application layer and a virtual machine layer. The application layer communicates with the virtual machine layer to coordinate and directs virtual machine creation and deletion in a coordinated fashion with application programs. For example, the application layer receives a request to initiate an application program. The application layer determines from associated application properties the type and/or number of virtual machines to be created. The application layer then directs creation of the appropriate virtual machines (through the virtual machine layer), and further directs installation of the requested application programs therein. When detecting removal of the application program from the created virtual machines, the application layer can automatically direct removal or decommissioning of the corresponding virtual machine.

Synchronizing virtual machine and application life cycles

Embodiments described herein are based on the principle that shells execute commands as units of characters. Accordingly, embodiments herein provide also provide for some special cases of asynchronous control signals that change the shell operation flow. For example, signal messages may be used to terminate, pause, resume, or otherwise modify the execution of a command. In other words, if a user wishes to change the execution state of a command, a client can create a signal message and send such message to the shell processor, which can take the appropriate action as desired. Note that by modeling the control or signal commands as discrete messages (as well as other embodiments modeled and described herein), such commands are not mistakenly executed on a command as is the case for current protocols that use a character-by-character transmission.

Shell operation flow change

Embodiments described herein are based on the principle that shells execute commands as units of characters sent within a message. Accordingly, embodiments herein provide for establishing a remote processing session for commands by using a binding mechanism that binds a series of commands to a remote shell using a message rather than a binary stream of data. More specifically, embodiments herein provided for a mechanism of encapsulating both a command and a binding mechanism (e.g., a shell identifier and/or shell token) into a single message. Accordingly, the binding mechanism can be used throughout the lifetime of the session and allows for modeling the shell processor session (its lifetime) as a series of commands, rather than as a series of characters. In addition, note that because the binding mechanism for the shell sessions is sent within messages, the problems associated with binary or character-by-character establishment of current shell sessions are overcome.

Shell sessions

Transferring command-lines as a message

A template creator creates a template class that stores at least one template parameter. The template creator also specifies at least one additional object to be created when an instance of the template class is created. A template user initiates the creation of a new instance of the template class. If an error occurs during the creation of the new instance of the template class, the template user receives a report identifying the error.

Method and apparatus for creating templates

Subscription-based notification using event channels that each correspond to a particular scope. Each channel manages notifications through the use of a schema definition. The event subscriptions identify the position and attributes that any desired event notification would take in the schema definition. The channel then receives event notifications in the form of XML fragments. The channel then determines the position that the XML fragment would take as defined by the schema definition. The channel determines whether the position and attributes of the event notification matches the position and attributes of the event subscription. If a match is found, then the event notification is copied and forwarded to the recipient designated in the corresponding subscription.

Flexible subscription-based event notification

Growing community of inventors

Bellevue, WA, United States of America

Alexander Evgenievich Nosov