# US 2016/0291892 A1 · Volume Admission Control for High-Performance Distributed Data Storage System

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2016/0291892 A1
- Document ID: US20160291892A1
- Status: Published application
- Kind: A1
- Application number: 14/673,723
- Filed: 2015-03-30
- Published: 2016-10-06
- Earliest claimed: 2015-03-30
- Assignees: Formation Data Systems, Inc.
- Applicants: Formation Data Systems, Inc.
- Inventors: Vinay Pundalika Rao; Mark S. Lewis; Anna Povzner
- Web page: https://patentgrep.com/patent/US20160291892A1

## CPC

- G06F 3/0629: {Configuration or reconfiguration of storage systems}
- G06F 3/0604: {Improving or facilitating administration, e.g. storage management}
- G06F 3/0607: {by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device}
- G06F 3/0613: {in relation to throughput}
- G06F 3/0631: {by allocating resources to storage systems}
- G06F 3/065: {Replication mechanisms}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 3/0683: {Plurality of storage devices}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

New storage volumes are registered to a data storage environment. Registering new storage volumes is controlled based on the performance requirements of the storage volumes compared to the capacity of the data storage environment.

## Claims

### Claim 1

A method of registering new storage volumes to a data storage environment comprising a plurality of storage nodes, the method comprising:
receiving a request to register a new storage volume to a subcluster of one or more storage nodes, wherein quality of service (QOS) parameters specify one or more I/O operations per second (IOPS) requirements for the new storage volume;
determining whether an IOPS capacity of the subcluster is sufficient to accommodate addition of the IOPS requirement for the new storage volume; and
if the IOPS capacity of the subcluster is sufficient, registering the new storage volume to the subcluster.

### Claim 2 (depends on 1)

The method of claim 1, wherein the QOS parameters for the new storage volume are specified in service level agreements for the storage volumes.

### Claim 3 (depends on 1)

The method of claim 1, wherein the QOS parameters for the new storage volume comprise I/O priority for the storage volume.

### Claim 4 (depends on 1)

The method of claim 1, wherein the QOS parameters for the new storage volume comprise a minimum IOPS requirement for the new storage volume.

### Claim 5 (depends on 1)

The method of claim 1, wherein the QOS parameters for the new storage volume comprise a maximum IOPS requirement for the new storage volume.

### Claim 6 (depends on 1)

The method of claim 1, wherein determining whether an IOPS capacity of the subcluster is sufficient comprises determining whether an IOPS capacity of the subcluster is sufficient to support minimum IOPS requirements for all existing storage volumes on the subcluster plus a minimum IOPS requirement for the new storage volume.

### Claim 7 (depends on 6)

The method of claim 6, wherein determining whether an IOPS capacity of the subcluster is sufficient further comprises adjusting the IOPS capacity of the subcluster by a loading factor.

### Claim 8 (depends on 7)

The method of claim 7, wherein some of the minimum IOPS requirements for storage volumes are soft requirements and the loading factor is greater than 1.

### Claim 9 (depends on 7)

The method of claim 7, wherein the loading factor is less than 1.

### Claim 10 (depends on 7)

The method of claim 7, wherein the loading factor is in a range from 0.5-0.75.

### Claim 11 (depends on 1)

The method of claim 1, wherein determining whether an IOPS capacity of the subcluster is sufficient comprises determining whether an IOPS capacity of the subcluster is sufficient to support maximum IOPS requirement for all existing storage volumes on the subcluster plus a maximum IOPS requirement for the new storage volume.

### Claim 12 (depends on 11)

The method of claim 11, wherein determining whether an IOPS capacity of the subcluster is sufficient further comprises adjusting the maximum IOPS requirement for storage volumes by a burst factor indicative of burstiness of I/O activity on the subcluster.

### Claim 13 (depends on 11)

The method of claim 11 wherein the burst factor is in a range from 0.3-0.4.

### Claim 14 (depends on 11)

The method of claim 11, wherein the burst factor is adapted over time based on actual burstiness of I/O activity on the subcluster.

### Claim 15 (depends on 1)

The method of claim 1, wherein determining whether an IOPS capacity of the subcluster is sufficient comprises adjusting the IOPS capacity of the subcluster by a replication factor indicative of a number of times storage volumes on the subcluster are replicated on the subcluster.

### Claim 16 (depends on 15)

The method of claim 15, wherein the replication factor is adapted over time based on actual replications on the subcluster.

### Claim 17 (depends on 1)

The method of claim 1, further comprising:
providing a notification if the IOPS capacity of the subcluster is not sufficient.

### Claim 18 (depends on 1)

The method of claim 1, further comprising:
if the IOPS capacity of the subcluster is not sufficient, then not registering the new storage volume to the subcluster.

### Claim 19 (depends on 1)

The method of claim 1, wherein the request to register a new storage volume is received over a network from an application module.

### Claim 20

A non-transitory computer-readable storage medium storing computer program modules for registering new storage volumes to a data storage environment comprising a plurality of storage nodes, the computer program modules executable to perform steps comprising:
receiving a request to register a new storage volume to a subcluster of one or more storage nodes, wherein quality of service (QOS) parameters specify one or more I/O operations per second (IOPS) requirements for the new storage volume;
determining whether an IOPS capacity of the subcluster is sufficient to accommodate addition of the IOPS requirement for the new storage volume; and
if the IOPS capacity of the subcluster is sufficient, registering the new storage volume to the subcluster.

### Claim 21

A data storage environment comprising:
a plurality of application nodes that send application read requests and application write requests for data;
a plurality of storage nodes in communication with the application nodes, the storage nodes for storing the data organized as storage volumes;
an orchestration manager module in communication with the application nodes and the storage nodes, the orchestration manager module configured for:
receiving a request from an application node to register a new storage volume to a subcluster of one or more of the storage nodes, wherein quality of service (QOS) parameters specify one or more I/O operations per second (IOPS) requirements for the new storage volume;
determining whether an IOPS capacity of the subcluster is sufficient to accommodate addition of the IOPS requirement for the new storage volume; and
if the IOPS capacity of the subcluster is sufficient, registering the new storage volume to the subcluster.
