Juniper Networks, Inc.

Microsoft Technology Licensing, LLC

Amazon Technologies, Inc.

Fungible, Inc.

Mirapoint, Inc.

Fujitsu Corporation

Hal Computer Systems, Inc.

Mirapoint Software, Inc.

Ankeena Networks, Inc.

Jaspal Kohli

Kumar Narayanan

Prabakar Sundarrajan

Junxiao He

Sunil Mukundan

Michael Nishimoto

Zubair Visharam

Pradeep S Sindhu

Nafea Bshara

Anthony Nicholas Liguori

Matthew Shawn Wilson

Raviprasad Venkatesha Murthy Mummidi

Vikram Venkataraghavan

Saar Gross

Philip A Thomas

Navaneeth Krishnan Ramaswamy

Mohammed Zubair Visharam

Daniel D McNeil

Joseph L DiMartino

Kiran Desai

Wolf-Dietrich Weber

Bertrand Serlet

Srihari Raju Vegesna

Shalesh Thusoo

Niteen Aravind Patkar

Karthik Narayanan

Chih-Wei David Chang

Farnad Sajjadian

Pratapa Reddy Vaka

Joel Frederick Boney

Xiaoqin Ma

Saravanan Purushothaman

Max He

Sunil Kumar Tekkatte Subramanya

Daniel James Nigel Picken

Arun Kumar Srinivasan

Junxiao (Max) He

Shivakumar Karathozuvu Narayanan

This disclosure describes a set of techniques that include establishing and managing quality of service standards across storage cluster resources in a data center. In one example, this disclosure describes a method that includes establishing a quality of service standard for a tenant sharing a storage resource with a plurality of tenants, wherein the storage resource is provided by the plurality of storage nodes in the storage cluster; allocating a volume of storage within the storage cluster, wherein allocating the volume of storage includes identifying a set of storage nodes to provide the storage resource for the volume of storage, and wherein the set of storage nodes are a subset of the plurality of storage nodes; and scheduling operations to be performed by the set of storage nodes for the volume of storage.

Predictable and adaptive quality of service for storage

This disclosure describes techniques for providing early acknowledgments to a source device performing a data write operation within a data center or across a geographically-distributed data center. In one example, this disclosure describes a method that includes receiving, by a gateway device and from a source device within a local data center, data to be stored at a remote destination device that is located within a remote data center; storing, by the gateway device, the data to high-speed memory included within the gateway device; transmitting, by the gateway device, the data over a connection to the remote data center; after transmitting the data and before the data is stored at the remote destination device, outputting, by the gateway device to the source device, a local acknowledgment, wherein the local acknowledgment indicates to the source device that the data can be assumed to have been stored at the remote destination device.

Early acknowledgment for write operations

Techniques are disclosed for providing scalable and concurrent file systems. A backend storage system comprising an interface and a processing unit may be configured to perform the techniques. The interface may present the file system storing objects representative of data. The processing unit may receive, from a frontend host system coupled to the backend storage system, a plurality of client operations to perform with respect to the objects identified by the client operations, and identify an object type associated with each of the identified objects. The processing unit may select, based on the object types, one or more backend operators that implement the plurality of client operations, and apply the backend operators to the identified objects.

Providing scalable and concurrent file systems

A peripheral device may implement storage virtualization for non-volatile storage devices connected to the peripheral device. A host system connected to the peripheral device may host one or multiple virtual machines. The peripheral device may implement different virtual interfaces for the virtual machines or the host system that present a storage partition at a non-volatile storage device to the virtual machine or host system for storage. Access requests from the virtual machines or host system are directed to the respective virtual interface at the peripheral device. The peripheral device may perform data encryption or decryption, or may perform throttling of access requests. The peripheral device may generate and send physical access requests to perform the access requests received via the virtual interfaces to the non-volatile storage devices. Completion of the access requests may be indicated to the virtual machines via the virtual interfaces.

Virtualizing non-volatile storage at a peripheral device

A key-value store supporting GET, PUT and DELETE operations, serializes multiple clients using two locks, and that supports asynchronous resizing. The locking scheme includes an operation of holding two locks, one for the key involved in the operation, one for the page currently searched or updated. The store can either be a single volume holding keys and data or can be organized as a directory volume referencing a number of data volumes organized by data-size ranges. The scheme also supports asynchronous resizing of the directory while continuing to perform operations.

Data processing unit with key value store

Suspend, restart and resume to update storage virtualization at a peripheral device

Techniques are described in which network devices, such as one or more data center access nodes, are configured to support durable block storage with inline erasure coding, i.e., erasure coding in real time as data is updated. A Durable Block Device (DBD) supports a block level API for one or more storage volumes that may be mapped to one or more applications executed by servers in communication with the data center access nodes. The disclosure describes the operation of the data plane of the DBD that is hosted on one or more access nodes, and its interactions with the management and control planes of the DBD that are hosted on one or more of the servers. The disclosure describes generation of a log structured volume in the DBD configured to gather multiple data blocks into larger chunks of data for inline erasure coding for storage across multiple storage devices.

Durable block storage in data center access nodes with inline erasure coding

A first device may receive a content request from a second device. The content request may include a dynamic network address and a request for a content file. The first device may determine that the dynamic network address is not included in a first index; determine one or more response values associated with the content file; determine that the one or more response values are included in a second index when the one or more response values match one or more response values included in the second index; generate an association between the dynamic network address and the second index to map the dynamic network address to the second index and to the content file based on determining that the one or more response values are included in the second index; and provide the content file to the second device.

Identifying content files in a cache using a response-based cache index

Peripheral device providing virtualized non-volatile storage

A first server may receive, from a client device, an indication of a request for a content file via a network address; identify that the network address is a dynamic network address; establish a communication session with a second; receive a portion of the content file from the second server; determine an index parameter based on receiving the portion of the content file; determine whether the content file is being stored by the first server based on a cache index and based on the index parameter or based on information associated with the request for the content file; receive a remaining portion of the content file based on determining that the content file is not being stored by the first server; and provide the content file to the client device.

Caching objects identified by dynamic resource identifiers

A publication exchange device may receive information that identifies a subscriber device, and may receive a set of subscription keys associated with subscribed-to network event information to be provided to the subscriber device. The publication exchange device may receive published network event information from one or more publisher devices, and may determine that the published network event information includes information that matches the set of subscription keys. The publication exchange device may identify the subscribed-to network event information, from the published network event information, using the set of subscription keys. The publication exchange device may provide the subscribed-to network event information to the subscriber device based on identifying the subscribed-to network event information.

Publish-subscribe based exchange for network services

A device receives, from a client device, a request for a resource, where the request provides an identifier of the client device. The device selects a target device for the resource, connects with the selected target device, and provides a proxy of the request to the selected target device, where the proxy of the request hides the identifier of the client device. The device receives the resource from the selected target device, where the resource provides an identifier of the target device. The device provides a proxy of the resource to the client device, where the proxy of the resource hides the identifier of the target device.

Routing proxy for resource requests and resources

A device receives, from a client device, a request for a resource, and accesses a table that includes one or more items of information. The device compares information provided in the request to the one or more items of information provided in the table, and terminates a connection for the request at the device when the information provided in the request matches at least one of the one or more items of information provided in the table. The device forwards the request to a network when the connection is not terminated at the device, and selects a target device for the resource when the connection is terminated at the device.

Terminating connections and selecting target source devices for resource requests

A device receives requests for content, determines requests for a same identifier from the requests for the content, and stores information associated with the determined requests in an object. The object includes a number of the determined requests, and a current time and a start time associated with the determined requests. The device also determines whether the number of the determined requests satisfies a first threshold, and determines whether a difference between the current time and the start time satisfies a second threshold. The device identifies a loop associated with another device when the number of the determined requests satisfies the first threshold and the difference satisfies the second threshold, and provides information associated with the identified loop.

Detection and prevention of a transaction loop in a cache server

Growing community of inventors

Sunnyvale, CA, United States of America

Jaspal Kohli