Browse Prior Art Database

Per node Quality of Service for Group of Volumes

IP.com Disclosure Number: IPCOM000248443D
Publication Date: 2016-Nov-30
Document File: 3 page(s) / 60K

Publishing Venue

The IP.com Prior Art Database

Related People

Akanksha Panse: INVENTOR [+7]

Abstract

A solution to provide QoS (Quality of Service) across a set of volumes in shared storage subsystem is proposed. The solution provides improved QoS for a group of volumes, by introducing a concept of volume group, which is a logical grouping of volumes, and also providing a way to set per node different Service Level Agreement (SLA) parameters for the configured volume groups.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 3

Per node Quality of Service for Group of Volumes

Akanksha Panse Apurv Barve Nachiket Karmalkar

Siddhi Chandan Mugdha Srineet Hari Vemuri

Priti Dhole

Abstract

A solution to provide QoS (Quality of Service) across a set of volumes in shared storage subsystem is proposed. The solution provides improved QoS for a group of volumes, by introducing a concept of volume group, which is a logical grouping of volumes, and also providing a way to set per node different Service Level Agreement (SLA) parameters for the configured volume groups.

Problem Statement

An administrator may configure multiple volumes with different I/O patterns or different storage/performance characteristics under an application and he/she may want some SLA for all these volumes together.

For example, given an Oracle database application having multiple data volumes and log volumes, all data volumes may need same SLA together and all log volumes may need some other combined SLA.

In case of applications running on multiple nodes, for the associated volume group configured, the administrator may need different SLAs on different nodes as per the application needs and the node functionality.

For example, in case of ETL (Extract- Transform-Load) workloads deployed on multiple nodes performing any of the Extract / Transform / Load activities, application may need different SLAs (such as MAXIOPS limits, latency limits) for volume group on different nodes, as per their functionality.

1

© 2016 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.


Page 02 of 3

Publication Description

We propose a solution to provide QoS across a set of volumes by introducing the concept of a volume group, which is a logical grouping of volumes.

In order to configure QoS settings for an application, we first create a volume group comprising the volumes used by that application and then set an SLA(s) on the group. The limit is applicable collectively over all volumes within a group.

Whenever a new volume gets added to the volume group, the group's SLA values becomes collectively applicable considering the newly added volume. Similarly, when the volume is removed from the group, the same SLA values will be collectively applicable to the remaining volumes in the group.

For each application volume group, we maintain a shared structure per node, which consists of volume group SLA related information such as volume group name, SLA v...