Browse Prior Art Database

Method to implement public/private volumes distributed to hosts Disclosure Number: IPCOM000248680D
Publication Date: 2016-Dec-27
Document File: 5 page(s) / 114K

Publishing Venue

The Prior Art Database


The main point in this invention is to use volume mapping to implement cluster which could include a set of host. Cluster will provide a easy, efficient way to manage/maintance all the hosts to a storage, and to distribute volumes to hosts. Also using volume mapping to implement cluster offers the strongly extensible structure. It makes the regional management for hosts easier as never before.

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


Method to implement public/private volumes distributed to hosts

Problem statement and background We hope to find a way to solve the following two problems:

1.If one volume needs to be mapped to multiple hosts, clients have to do the same work for each host repeatedly. 2.Even though hosts can be combined together in some storage, these hosts have to share all volumes. But some of them often need their private volumes. 3.Hard to management and maintenance if there are lots of volumes and hosts.

Also, this method should be flexible and extensive enough to be applied to more complicated cases.

Core idea

A cluster owns an internal volume mapping which is used to save a copy of the relationships between shared volumes and their Logical Unit Numbers(The acronym, LUN will be used below). This internal volume mapping is transparent to the outside and can not be shared by any other clusters and hosts. All hosts under a cluster can keep their original volume mappings. All shared/private volumes are dynamically calculated by comparing the volume mappings of a cluster and its hosts.

Detailed Description:

Terms: 1.Cluster: a logical collection which includes a group of hosts. 2.Volume mapping: a collection which saves the relationships of volumes and LUNs

Principle: 1.Each cluster has an internal volume mapping. A copy is saved in the cluster for those volumes shared by all hosts under it. Hosts always keep their original volume mappings regardless they are under a cluster or not. 5.All volumes in the cluster, but not in the host must be added into host’s volume mapping automatically when a host is added into the cluster.

Algorithm: 1.All shared volumes must have the same LUNs in the cluster and its hosts. 2.Any actions, including adding/updating/deleting shared volumes, must update all hosts’ volume mappings, as well as the copy in their cluster. 3.Any actions to private volumes only needs to update the related host’s volume mapping. 4.When add a host into a cluster, LUNs must be same...