# US 2014/0156817 A1 · Modular service level objective (slo) subsystem for a network storage system

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

- Number: US 2014/0156817 A1
- Document ID: US20140156817A1
- Status: Published application
- Kind: A1
- Application number: 14/173,530
- Filed: 2014-02-05
- Published: 2014-06-05
- Earliest claimed: 2011-02-23
- Assignees: NetApp, Inc.
- Applicants: NetApp, Inc.
- Inventors: David Slik
- Web page: https://patentgrep.com/patent/US20140156817A1

## CPC

- H04L 41/0813: characterised by the conditions triggering a change of settings
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- G06F 3/0604: {Improving or facilitating administration, e.g. storage management}
- G06F 3/0646: {Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems}
- G06F 3/0653: {Monitoring storage devices or systems}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A service level objective (SLO) subsystem that includes an SLO engine in a network storage system that allows new degrees of freedom to be added to the SLO subsystem, without requiring any modification of an associated SLO engine or the system's existing SLOs, and without requiring the SLO engine to have any a priori knowledge of the new degrees of freedom. In certain embodiments, the system has a modular design which includes the SLO engine and one or more SLO modules that interface with the SLO engine. Each SLO module corresponds to a different degree of freedom. Each SLO module evaluates SLO compliance and determines what specific action(s) within its corresponding degree of freedom should be taken to comply with an SLO.

## Claims

### Claim 1

A service level objective (SLO) engine, comprising:
an application program interface (API) configured to enable the SLO engine to communicate with multiple components, each of the components configured to evaluate a different one of multiple categories of configuration state of a data storage system in relation to any specified SLO and to produce a corresponding result; and
a compliance component configured to:
rank the results from the components; and
identify one or more operations to perform on the data storage system in one or more of the categories of configuration state to increase a measurement of a category of configuration state to which a specified SLO is satisfied, based on an individual ranked result of the ranked results.

### Claim 2 (depends on 1)

The SLO engine of claim 1, wherein the one or more operations to perform on the data storage system are specified by a proposed layout in the individual ranked result.

### Claim 3 (depends on 1)

The SLO engine of claim 1, wherein the API enables the SLO engine to communicate with an arbitrary number of the components, wherein at least some of the components are designed to evaluate a measurement of a different category of configuration state in relation to an arbitrary SLO.

### Claim 4 (depends on 3)

The SLO engine of claim 3, wherein the result produced by the components includes a proposed layout.

### Claim 5 (depends on 4)

The SLO engine of claim 4, wherein the result produced by the components includes an indication of a category of configuration state to which the proposed layout will satisfy the specified SLO.

### Claim 6 (depends on 5)

The SLO engine of claim 5, wherein the indication comprises an SLO value associated with the proposed layout.

### Claim 7 (depends on 4)

The SLO engine of claim 4, wherein the result produced by the components further includes a steady-state cost and a transition cost associated with the proposed layout.

### Claim 8 (depends on 1)

The SLO engine of claim 1, wherein the compliance component, causes a plurality of proposed layouts received from the components to be processed iteratively by the components to converge towards an optimal layout and ranking.

### Claim 9 (depends on 1)

The SLO engine of claim 1, wherein the interface is configured to provide to each of the components SLO data indicative of the specified SLO and a current layout of the data storage system.

### Claim 10 (depends on 1)

The SLO engine of claim 1, wherein at least one component of the multiple components is from a group comprising:
a data mirroring component configured to control data mirroring in relation to a specified SLO;
a data placement component configured to control data placement in relation to a specified SLO;
a namespace placement component configured to control data access in relation to a specified SLO;
a data replication component configured to control data replication in relation to a specified SLO;
a data caching component configured to control data caching in relation to a specified SLO;
a data transformation component configured to control data transformation, including encryption or compression or both, in relation to a specified SLO; or
a data dispersion component configured to control geographic dispersion of data in relation to a specified SLO.

### Claim 11

A processing system, comprising:
a processor;
a memory coupled to the processor;
an interface configured to communicate with an arbitrary number of external components, each of which is designed to evaluate a different category of configuration state in relation to any arbitrary SLO; and
an SLO engine operatively coupled to, but functionally distinct from, at least some of the external components, to provide to each of the coupled external components SLO data indicating a desired SLO for the data storage system and state data representing a current state of data stored in the data storage system, to receive from each of the coupled external components a separate output that includes a proposed layout and an SLO value associated with the proposed layout.

### Claim 12 (depends on 11)

The processing system of claim 11, wherein the SLO value received from each of the coupled external components represents a measurement of a category of configuration state to which the proposed layout will satisfy an SLO characteristic in a category of configuration state represented by the corresponding component.

### Claim 13 (depends on 12)

The processing system of claim 12, wherein the SLO engine is further configured to select, based on the output values, a proposed layout to apply to the data storage system to increase a measurement of the category of configuration state to which the desired SLO is satisfied.

### Claim 14 (depends on 11)

The processing system of claim 11, wherein at least one component of the external components is from a group comprising:
a data mirroring component configured to control data mirroring in relation to a specified SLO;
a namespace placement component configured to control data access in relation to a specified SLO;
a data placement component configured to control data placement in relation to a specified SLO;
a data replication component configured to control data replication in relation to a specified SLO;
a data caching component configured to control data caching in relation to a specified SLO;
a data transformation component configured to control data transformation, including compression or encryption or both, in relation to a specified SLO; or
a data dispersion component configured to control geographic dispersion of data in relation to a specified SLO.

### Claim 15 (depends on 11)

The processing system of claim 11, further comprising multiple internal components of the SLO engine, each representing a different category of configuration state of a data storage system.

### Claim 16

A method, comprising:
providing, to each of multiple functional modules, service level objective (SLO) data indicative of a specified SLO for a data storage system, at least some of the functional modules corresponding to a different one of multiple categories of configuration state, at least some of the functional modules configured to apply the SLO data to a function that represents a particular relationship between an SLO characteristic and the corresponding category of configuration state, wherein at least some of the functional modules are configured with the category of configuration state, but without the SLO, and are configured to evaluate a measurement of the category of configuration state in relation to any arbitrary SLO;
receiving from at least some of the functional modules an output set that includes a layout for the data storage system and an indication of a category of configuration state to which the layout will satisfy the specified SLO; and
selecting a layout to apply to the data storage system based on the output sets from multiple functional modules.

### Claim 17 (depends on 16)

The method of claim 16, wherein at least some of the functional modules are configured to apply the SLO data and state data indicative of a current state of the data storage system to the function that represents a particular relationship between an SLO characteristic and the corresponding category of configuration state.

### Claim 18 (depends on 16)

The method of claim 16, wherein the indication received from at least some of the functional modules represents a category of configuration state to which the corresponding layout will satisfy an SLO characteristic in a category of configuration state represented by the corresponding functional module.

### Claim 19 (depends on 18)

The method of claim 18, wherein selecting a layout to apply to the data storage system comprises:
ranking the layouts received from the plurality of functional modules; and
selecting one of the ranked layouts to apply to the data storage system.

### Claim 20 (depends on 18)

The method of claim 18, wherein the layouts received from multiple functional modules are iteratively processed multiple times by the plurality of functionality modules to converge towards an optimal layout and ranking.

### Claim 21 (depends on 16)

The method of claim 16, wherein at least one category of configuration state from the plurality of categories of configuration state is from a group comprising:
data mirroring;
data placement;
data access control;
data replication;
data caching;
data transformation; or
data geographic dispersion.
