Microsoft Technology Licensing, LLC

Parveen Kumar Patel

Albert Gordon Greenberg

Deepak Bansal

David A Maltz

Sudipta Sengupta

Jonathan David Goldstein

Murari Sridharan

Lihua Yuan

Hasan Alkhatib

Narasimhan Agrahara Venkataramaiah

Srinath Setty

David Allen Dion

Jacob Rubin Lorch

Lidong Zhou

Vladimir Petter

Vyacheslav Kuznetsov

Jitendra Dattatraya Padhye

Karan Mehra

Navendu Jain

Yongguang Zhang

Balaji Satyanarayana Prabhakar

Xinyan Zan

Himanshu Raj

Brian Don Zill

Anil K Ruia

Yiqun Cai

Nisheeth Srivastava

Yunus Mohammed

Jun Wang

David Garfield Thaler, Iii

Yi Meng

Wei Zhao

Rebecca Isaacs

Murali Krishna Sangubhatla

Marios Zikos

Ashwin Narasimha Murthy

Parantap Lahiri

Charles Loboz

Changhoon Kim

Jinglei Ren

Yu-Shun Wang

Hemant Kumar

Volodymyr Ivanov

Matthew Kerner

Ankur Agiwal

Geoff Outhred

Randall Kern

Nelamangala Krishnaswamy Srinivas

Dave Maltz

Gareth Bradshaw

Cristian Costache

Naveen Reddy Karri

Sandeep Koushik Sheshadri

Kamel Sbaia

Narayanan Annamalai

HongYu Wu

Yagya Narayanan Sethuraman

Mohammedreza Alizadeh Attar

Jacek Nowak

Kevin O'Regan

Wok Suk Yoo

Varun Venkatesh

Randy Kern

Narasimhan A Venkataramaiah

A computing device requests access to an application object from a remote storage system in order to locally execute application functionality without hosting application resources. An accessed object is associated with an intent in the storage system and locked. Locking an object in combination with an intent prevents computing devices that are not performing the intent from accessing the object. An intent defines one or more operations to be performed with the requested object, which are serialized as intent steps and stored in the storage system. Upon executing an intent step, the computing device stores a log entry at the storage system signifying the step's completion. A locked object remains locked until the log entries indicate every intent step as complete. Different computing devices can unlock a locked object by executing any incomplete steps of an intent associated with the locked object.

Intents and locks with intent

Described is a server monitoring technology that is scalable to large numbers of servers, e.g., in a datacenter. Agents on servers run queries to monitor data sources for that server, such as performance counters and other events. The agents monitor their resource usage and those of monitored events to stay within an administrator-specified resource budget (policy), e.g., by modifying the running queries and/or monitoring parameters. A controller receives results of the monitoring, analyzes the results, and takes action as needed with respect to server operation and monitoring. The controller may dynamically update an agent's queries, monitoring parameters and/or monitored data post-processing operations. The controller may issue alerts and reports, including alerts indicative of inter-server problems between two or more servers.

Flexible and safe monitoring of computers

A storage account is replicated across multiple data centers so as to withstand an outage of the storage account. A front end and applications use data stored in the storage accounts to manage resources of a cloud computing system. A client includes an interface used by the front end to access the storage accounts, in addition to an interface that is used by the applications to access the storage accounts. Other features, which ensure that a read operation survives even if a head replica or a tail replica is down, include reading from a head replica instead of from a tail replica, a two phase prepare-commit operation to propagate changes from head to tail replicas, and provisioning a back end repair service if a failure occurs in the middle of the prepare-commit operation.

Replicating storage tables used to manage cloud-based resources to withstand storage account outage

A system that includes multiple hosts, each running a plurality of virtual machines. The system may be, for example, a cloud computing environment in which there are services and a service coordination system that communicates with the hosts and with the services. The services include a middleware management service that is configured to maintain per-tenant middleware policy for each of multiple tenants. The middleware management service causes the middleware policy to be applied to network traffic by directing network traffic to a middleware enforcement mechanism. This middleware policy is per-tenant in that it depends on an identity of a tenant.

Multi-tenant middleware cloud service technology

Various embodiments of methods and systems for network infrastructure configuration based on network device configuration templates are provided. A network device configuration template is received where the network device configuration template corresponds to network device configuration data based on template elements. Template elements include variable placeholders, versions, Stock Keeping Units (SKUs), firmware, and target devices identified in the network device configuration template. Values for the template elements are referenced from a dataset storage component. The network device configuration data are classified into different classification units. The network device configuration data are merged with the network device configuration template that programmatically defines configuration of network devices. A network device configuration instance is generated based on evaluating the template elements and replacing template elements with values from the dataset storage. The network device can be associated with a configuration scope, where the configuration scope indicates intended configuration features of the network devices.

Network device configuration framework

Routing messages between virtual networks using a mapping of virtual addresses from one virtual network to a virtual address of the other virtual network. Each virtual network has a valid set of virtual addresses, some of which being assigned to virtual nodes within the corresponding network. When a virtual network identifies a message to be sent, it identifies a destination for the message. Some destinations may be within the same virtual network and thus may be routed to virtual nodes within the virtual network. Other destinations may instead be mapped to a virtual address of another virtual network. In that case, routing information may also be obtained and the message may be dispatched to the virtual address of the other virtual network. This may be performed without the need for a gateway, which publishes a public address that is globally unique.

Routing messages between virtual networks

A multi-gateway virtual machine that operates multiple gateways. Each gateway acts as an interface between a virtual network and entities outside of the virtual network. Each virtual network has its own address space, which may be overlapping with the address space of other virtual networks, even if the gateways of those virtual networks are operating on the same virtual machine. Accordingly, the principles described herein relate to a virtual machine that can operate thereon multiple gateways, and thus to a multi-gateway virtual machine that services multiple virtual networks.

Multiple gateway operation on single operating system

Methods and apparatus are provided for controlling communication between a virtualized network and non-virtualized entities using a virtualization gateway. A packet is sent by a virtual machine in the virtualized network to a non-virtualized entity. The packet is routed by the host of the virtual machine to a provider address of the virtualization gateway. The gateway translates the provider address of the gateway to a destination address of the non-virtualized entity and sends the packet to the non-virtualized entity. The non-virtualized entity may be a physical resource, such as a physical server or a storage device. The physical resource may be dedicated to one customer or may be shared among customers.

Virtualization gateway between virtualized and non-virtualized networks

Redirecting message flows to bypass load balancers. A destination intermediary receives a source-side message that includes a virtual address of a load balancer as a destination, and that is augmented to include a network address of a destination machine as a destination. The destination intermediary determines that a source intermediary should address subsequent network messages that originate from a source machine and that are associated with the same multi-message flow to the destination machine while bypassing the load balancer. The destination intermediary modifies the source-side message so the destination for the source-side message addresses the destination machine, and passes the modified source-side message to the destination machine. The destination intermediary receives a response from the destination machine identifying the source machine as its destination, and modifies the response so a source address identifies the virtual address of the load balancer, and dispatches the modified response to the source machine.

Load balancer bypass

The obtaining of a lease on a resource in a circumstance in which multiple lease servers are capable of granting a lease to the resource. A computing entity attempts to obtain the lease on the resource by causing a lease request to be sent to each of at least most (and perhaps all) of the lease servers. In response, the computing entity receives one or more responses to the lease requests. If the computing entity receives grants of a lease from a majority of the lease servers that are capable of granting a lease to the resource, then it is determined that the computing entity acquired a lease on the resource. On the other hand, if the computing entity receives grants of a lease from less than a majority of the lease servers, it is determined that the computing entity failed to acquire the lease on the resource.

Acquiring resource lease using multiple lease servers

Growing community of inventors

Redmond, WA, United States of America

Parveen Kumar Patel