Microsoft Technology Licensing, LLC

Microsoft Corporation

Jitendra Dattatraya Padhye

Paramvir Bahl

Brian Don Zill

Ranveer Chandra

Alastair Wolman

Sharad Agarwal

Lenin Ravindranath Sivalingam

Shachar Raindel

Atul Adya

Venkata N Padmanabhan

Ratul Mahajan

Hongqiang Liu

Yibo Zhu

Daniel Max Firestone

Ryan Andrew Beckett

Richard Powell Draves, Jr

Karthick Jayaraman

Neha Milind Raje

Christopher Scott Johnston

Steven Jeffrey Benaloh

Ramachandran Ramjee

Kamal Jain

Anirudh Badam

Lili Qiu

Jacob Rubin Lorch

Lidong Zhou

George Varghese

Shahin Shayandeh

Daehyeok Kim

Behnaz Arzani

Wei Bai

Avi William Levy

Mahmoud S El Haddad

Alireza Khosgoftar Monafared

Xinchen Guo

Ian Obermiller

Jie Jerry Liu

Suman Kumar Nath

Kun Tan

Nikolaj Skallerud Bjorner

Srikanth Kandula

Lihua Yuan

Bernard D Aboba

Rachee Singh

Carlos Garcia Jurado Suarez

Miguel Oom Temudo De Castro

Richard Lloyd Hughes

Siddhartha Sen

Khoa Anh To

Gopala Srihari Narlanka

Yan Yu

Nuno Claudino Pereira Lopes

Hang Kwong Lee

Maik Riechert

Andrey Aleksandrovic Rybalchenko

Aniruddha Parkhi

Pradeep Kyasanur

Rohan Gandhi

Sarah Elisabeth McClure

Nuno Cerqueira Afonso

Philip Andrew Chou

Albert Gordon Greenberg

Thomas Moscibroda

Parveen Kumar Patel

David A Maltz

Bozidar Radunovic

Murari Sridharan

Yunnan Wu

Balaji Satyanarayana Prabhakar

Ronnie Chaiken

Carlo Aldo Curino

Vishnu Navda

Sandeep P Karanth

Youngki Lee

Mohamed Jawad Khaki

Rohan Narayana Murty

Sirius Kuttiyan

Christopher Charles John Butcher

Wenbiao Xing

Wei Wan

Li Chen

Patrick D Verkaik

Paramivir Bahl

Manpreet Singh

Bozidar Raduvic

Ashish Vulimiri

Christopher M Moore

Christopher Riederer

Mohammedreza Alizadeh Attar

Sarah Elisabeth Mcclure

Brian D Zill

A network verification system uses general-purpose programming language to create network verification tests. A test orchestrator builds a model of the network only using data from the network verification test. An optimization testing manager creates symbolic packets for verification tests using assertions based on a packet library embedded into the testing manager and the general-purpose programming language.

Network verification systems and methods

Techniques of packet level redundancy in distributed computing systems are disclosed herein. In one example, upon receiving an original packet to be transmitted from a source host to an application executing at a destination host, the source host generates a duplicated packet based on the received original packet. The source host can then encapsulate the original and duplicated packets with first and second outer headers having first and second header values, respectively, and transmitting the original and the duplicated packets from the source host to the destination host via a first network path and a second network path in the computer network, respectively. Then, the transmitted original and duplicated packets can be de-duplicated at the destination host before providing the de-duplicated original and duplicated packets to the application executing at the destination host.

Packet level redundancy in distributed computing systems

Techniques are disclosed for identifying faulty links in a virtualized computing environment. Network path latency information is received for one or more network paths in the networked computing environment. Based on the network path latency information, a probable presence of a faulty component is determined. In response to the determination, physical links for a network path associated with the probable faulty component are identified. Information indicative of likely sources of the probable faulty component is received from multiple hosts of the networked computing environment. Based on the identified physical links and information, a faulty component is determined.

Link fault isolation using latencies

Ghost routing is a network verification technique that uses a portion of a production network itself to verify the impact of potential network changes. Ghost routing logically partitions the production network into a main network and a ghost network. The main network handles live traffic while the ghost network handles traffic generated for diagnostic purposes. The ghost network may have a network topology identical to the production network and may use the same hardware and software as the production network. An operator may implement a network configuration change on the ghost network and then use verification tools to verify that the network configuration change on the ghost network does not result in bugs. Verifying on the ghost network may not affect the main network. If the network operator verifies the network configuration change on the ghost network, the network operator may implement the network configuration change on the main network.

Ghost routing

Distributed computing systems, devices, and associated methods of virtual RDMA switching are disclosed herein. In one embodiment, a method includes intercepting a command from an application in a container to establish an RDMA connection with a remote container on a virtual network. In response to the intercepted command, an RDMA endpoint at a physical NIC of a server is created. The method can also include intercepting another command to pair with a remote RDMA endpoint corresponding to the remote container. The intercepted another command contains data representing a routable network address of the remote RDMA endpoint in the RDMA computer network. Then, the RDMA endpoint created at the physical NIC of the server can be paired with the remote RDMA endpoint using the routable network address of the remote RDMA endpoint.

Virtual RDMA switching for containerized

Techniques for employing a decentralized sleep management service are described herein. In some instances, each computing device of a group of computing devices periodically shares information about itself with each other computing device of the group. With this information, each computing device within the group that is awake and capable of managing other devices selects a subset of devices to probe. The devices then probe this subset to determine whether the probed devices are asleep. In response to identifying a sleeping device, the probing device takes over management of the sleeping device. Managing the sleeping device involves informing other devices of the group that the sleeping device is being managed, in addition to monitoring requests for services on the sleeping device. In response to receiving a valid request for a service hosted by the sleeping device, the managing device awakens the sleeping device and ceases managing the now-woken device.

Decentralized sleep management

Various technologies described herein pertain to controlling geo-scale analytics with bandwidth and regulatory constraints. An analytical query (e.g., a recurrent analytical query, a non-recurrent analytical query, etc.) to be executed over distributed data in data partitions stored in a plurality of data centers can be received. Moreover, a query execution plan for the analytical query can be generated, where the query execution plan includes tasks. Further, replication strategies for the data partitions can be determined. A replication strategy for a particular data partition can specify one or more data centers to which the particular data partition is to be replicated if the particular data partition is to be replicated. The tasks of the query execution plan for the analytical query can further be scheduled to the data centers based on the replication strategies for the data partitions. The analytical query can be part of a workload of analytical queries.

Geo-scale analytics with bandwidth and regulatory constraints

Virtual RDMA switching for containerized applications

Techniques for facilitating load balancing in distributed computing systems are disclosed herein. In one embodiment, a method includes receiving, at a destination server, a request packet from a load balancer via the computer network requesting a remote direct memory access ('RDMA') connection between an originating server and one or more other servers selectable by the load balancer. The method can also include configuring, at the destination server, a rule for processing additional packets transmittable to the originating server via the RDMA connection based on the received reply packet. The rule is configured to encapsulate an outgoing packet transmittable to the originating server with an outer header having a destination field containing a network address of the originating server and a source field containing another network address of the destination server.

Load balancing in distributed computing systems

Distributed storage systems, devices, and associated methods of data replication are disclosed herein. In one embodiment, a server in a distributed storage system is configured to write, with an RDMA enabled NIC, a block of data from a memory of the server to a memory at another server via an RDMA network. Upon completion of writing the block of data to the another server, the server can also send metadata representing a memory location and a data size of the written block of data in the memory of the another server via the RDMA network. The sent metadata is to be written into a memory location containing data representing a memory descriptor that is a part of a data structure representing a pre-posted work request configured to write a copy of the block of data from the another server to an additional server via the RDMA network.

Group-based data replication in multi-tenant storage systems

Growing community of inventors

Redmond, WA, United States of America

Jitendra Dattatraya Padhye