# US 2021/0240369 A1 · Virtual storage policies for virtual persistent volumes

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

- Number: US 2021/0240369 A1
- Document ID: US20210240369A1
- Status: Published application
- Kind: A1
- Application number: 16/779,139
- Filed: 2020-01-31
- Published: 2021-08-05
- Earliest claimed: 2020-01-31
- Assignees: Hewlett Packard Enterprise Development LP
- Applicants: Hewlett Packard Enterprise Development LP
- Inventors: Bradley Cain
- Web page: https://patentgrep.com/patent/US20210240369A1

## CPC

- G06F 3/0631: {by allocating resources to storage systems}
- G06F 3/0604: {Improving or facilitating administration, e.g. storage management}
- G06F 3/0605: {by facilitating the interaction with a user or administrator}
- G06F 3/0644: {Management of space entities, e.g. partitions, extents, pools}
- G06F 3/0664: {at device level, e.g. emulation of a storage device or system}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F 3/0679: {Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]}
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 9/44526: {Plug-ins; Add-ons}
- G06F 2009/45579: {I/O management, e.g. providing access to device drivers or storage}
- G06F 2009/45583: {Memory management, e.g. access or allocation}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Example implementations relate to virtual persistent volumes. In an example, a virtual persistent volume storage class is presented to a container orchestrator that includes parameters describing an associated virtual storage policy. In response to a provisioning request that identifies the virtual persistent volume storage class, a virtual persistent volume is created by determining a mapping of the parameters of the virtual persistent volume storage class to parameters of available storage classes so that the parameters of the virtual persistent volume storage class are fulfilled. At least one volume is provisioned to constitute the virtual persistent volume, according to the mapping.

## Claims

### Claim 1

A non-transitory machine readable medium storing instructions for a policy engine of a storage virtualization system that are executable by a processing resource, the non-transitory machine readable medium comprising:
instructions to present to a container orchestrator in a container environment a virtual persistent volume storage class that includes parameters describing an associated virtual storage policy;
instructions to receive a persistent volume provisioning request that identifies the virtual persistent volume storage class;
instructions to create a virtual persistent volume in response to the persistent volume provisioning request by:
determining a mapping of the parameters of the virtual persistent volume storage class to parameters of storage classes available in the container environment that fulfills the parameters of the virtual persistent volume storage class, and
provisioning at least one volume from storage types represented by the storage classes based on the mapping, the at least one volume to constitute the virtual persistent volume; and
instructions to generate a virtualization map entry that maps the virtual persistent volume to the at least one volume provisioned from the storage types which constitute the virtual persistent volume.

### Claim 2 (depends on 1)

The non-transitory machine readable medium of claim 1, further comprising instructions to translate the storage classes to respective storage profiles using a common schema,
wherein the virtual persistent volume storage class conforms to the common schema, and
wherein the determining the mapping is based on matching the parameters of the virtual persistent volume storage class to parameters of the storage profiles as a proxy for the storage classes.

### Claim 3 (depends on 2)

The non-transitory machine readable medium of claim 2, wherein the storage classes are non-standardized and at least some of the storage classes are associated with different storage vendors.

### Claim 4 (depends on 1)

The non-transitory machine readable medium of claim 1, further comprising instructions to discover available storage plug-ins on the container environment for use in the provisioning.

### Claim 5 (depends on 1)

The non-transitory machine readable medium of claim 1, further comprising: instructions to present to the container orchestrator a plurality of different virtual persistent volume storage classes having different parameter values associated with different virtual storage policies; and
instructions to store virtualization maps for virtual persistent volumes in response to persistent volume provisioning requests for different ones of the different virtual persistent volume storage classes.

### Claim 6 (depends on 1)

The non-transitory machine readable medium of claim 1, wherein the virtual persistent volume includes a single volume provisioned from a single storage type.

### Claim 7 (depends on 1)

The non-transitory machine readable medium of claim 1, wherein the virtual persistent volume includes multiple volumes provisioned from different storage types, and
wherein the instructions to create the virtual persistent volume include blending multiple volumes provisioned from different storage types in a hierarchical structure that relates data objects by content-based signatures to a root object.

### Claim 8 (depends on 1)

The non-transitory machine readable medium of claim 1, wherein the virtual persistent volume storage class includes a backup policy, and the mapping that fulfills the parameters of the virtual persistent volume storage class is associated with a backup storage class and a primary storage class, and
the instructions to create the virtual persistent volume includes:
provisioning, as one of the at least one volume, a backup volume associated with the backup storage class, and
provisioning, as another of the at least one volume, a primary storage volume associated with the primary storage class, using a provisioning request that identifies the backup volume as a replication target.

### Claim 9

A method comprising:
presenting to a container orchestrator, by a storage virtualization system in a container environment, a virtual persistent volume storage class that includes parameters describing an associated virtual storage policy;
receiving, by the storage virtualization system, a persistent volume provisioning request that identifies the virtual persistent volume storage class; and
creating, by the storage virtualization system, a virtual persistent volume in response to the persistent volume provisioning request by:
determining a mapping of the parameters of the virtual persistent volume storage class to parameters of storage classes available in the container environment that fulfills the parameters of the virtual persistent volume storage class, and
provisioning at least one volume from storage types represented by the storage classes based on the mapping, the at least one volume to constitute the virtual persistent volume; and
generating a virtualization map entry that maps the virtual persistent volume to the at least one volume provisioned from the storage types which constitute the virtual persistent volume.

### Claim 10 (depends on 9)

The method of claim 9, wherein at least some of the storage classes are associated with different storage vendors.

### Claim 11 (depends on 9)

The method of claim 9, further comprising:
maintaining, by the storage virtualization system, storage profiles that are translated via a common schema from respective ones of the storage classes,
wherein the virtual persistent volume storage class conforms to the common schema, and
wherein the determining the mapping is based on matching the parameters of the virtual persistent volume storage class to parameters of the storage profiles as a proxy for the storage classes.

### Claim 12 (depends on 9)

The method of claim 9, further comprising discovering available storage plug-ins on the container environment for use in the provisioning.

### Claim 13 (depends on 9)

The method of claim 9, further comprising:
presenting to a container orchestrator, by the storage virtualization system, a plurality of different virtual persistent volume storage classes having different parameter values associated with different virtual storage policies; and
storing, by the storage virtualization system, virtualization maps for virtual persistent volumes created by the storage virtualization system in response to persistent volume provisioning requests for different ones of the different virtual persistent volume storage classes.

### Claim 14 (depends on 9)

The method of claim 9, wherein the virtual persistent volume includes a single volume provisioned from a single storage type.

### Claim 15 (depends on 9)

The method of claim 9, wherein the virtual persistent volume includes multiple volumes provisioned from different storage types that are blended by a data path in a hierarchical structure that relates data objects by content-based signatures to a root object.

### Claim 16

A system comprising:
a processing resource; and
a non-transitory machine readable medium storing instructions that, when executed, cause the processing resource to:
present to a container orchestrator in a container environment a virtual persistent volume storage class that includes parameters describing an associated virtual storage policy,
receive a persistent volume provisioning request that identifies the virtual persistent volume storage class,
create a virtual persistent volume in response to the persistent volume provisioning request by:
determining a mapping of the parameters of the virtual persistent volume storage class to parameters of storage classes available in the container environment, so that the mapping fulfills the parameters of the virtual persistent volume storage class, wherein at least some of the storage classes are associated with different storage vendors, and
provisioning at least one volume from storage types represented by the storage classes based on the mapping, the at least one volume to constitute the virtual persistent volume; and
generate a virtualization map entry that maps the virtual persistent volume to the at least one volume provisioned from the storage types which constitute the virtual persistent volume.

### Claim 17 (depends on 16)

The system of claim 16, wherein the non-transitory machine readable medium stores instructions that, when executed, cause the processing resource to translate the storage classes to storage profiles via a common schema,
the virtual persistent volume storage class conforms to the common schema, and
the determining the mapping is based on matching the parameters of the virtual persistent volume storage class to parameters of the storage profiles as a proxy for the storage classes.

### Claim 18 (depends on 16)

The system of claim 16, wherein the virtual persistent volume includes multiple volumes provisioned from different storage types, and
the non-transitory machine readable medium stores instructions for a data path that, when executed, cause the processing resource to blend the multiple volumes in a hierarchical structure that relates data objects by content-based signatures to a root object.

### Claim 19 (depends on 16)

The system of claim 16, wherein the virtual persistent volume includes a single volume provisioned from a single storage type.
