Configuring object storage system for input/output operations

• US 8,595,460 B2
• Filed: 08/26/2011
• Issued: 11/26/2013
• Est. Priority Date: 08/26/2011
• Status: Active Grant

• Current Assignee: Vmware LLC (Broadcom, Inc.)
• Original Assignee: VMware, Inc. (Broadcom, Inc.)
• Inventors: Bhat, Rajesh, Acharya, Sanjay, Vaghani, Satyam B., Shih, Chiao-Chuan
• Primary Examiner(s): NGUYEN, HIEP T
• Application Number:
  US13/219,368
• Publication Number:
  US 20130054888A1
• Time in Patent Office: 823 Days
• Field of Search: None
• US Class Current: 711/170
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/0631 by allocating resources to storage systems
• CPC Class Codes: G06F 3/0661 Format or protocol conversion arrangements
• CPC Class Codes: G06F 3/0665 at area level, e.g. provisioning of virtual or logical volumes
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 3/0689 Disk arrays, e.g. RAID, JBOD
• CPC Class Codes: G06F 9/00 Arrangements for program control, e.g. control units program control for peripheral devices G06F13/10
• CPC Class Codes: H04L 61/103 across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
• CPC Class Codes: 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]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The storage system exports logical storage volumes that are provisioned as storage objects. These storage objects are accessed on demand by connected computer systems using standard protocols, such as SCSI and NFS, through logical endpoints for the protocol traffic that are configured in the storage system. When an input-output command (IO) is received at the storage system, an identifier is retrieved from the IO and translated into a logical storage volume identifier, and the IO is executed on storage locations referenced by a logical storage volume corresponding to the logical storage volume identifier.

Claims

1. A method for preparing a storage system to execute input-output commands (IOs), the method comprising:

receiving a request to prepare a logical storage volume;

selecting a protocol endpoint configured in the storage system through which IOs for the logical storage volume are to be received; and

generating an identifier to be included in IOs for the logical storage volume and returning the identifier to a computer system that issued the request.

2. The method of claim 1, further comprising:

determining one or more protocol endpoints configured in the storage system that are connected over a protocol path to the computer system,

wherein the protocol endpoint is selected from the one or more protocol endpoints.

3. The method of claim 2, wherein the one or more protocol endpoints are LUNs.

4. The method of claim 2, wherein the one or more protocol endpoints are mount points of a network-attached storage system.

5. The method of claim 2, wherein the request is received at the storage system over a non-protocol path and the identifier is returned over the non-protocol path.

6. The method of claim 1, further comprising:

maintaining a data structure that provides a mapping of identifiers included in IOs to logical storage volume identifiers,

wherein the request includes a logical storage volume identifier, and an entry is added to the data structure that identifies the selected protocol endpoint and associates the generated identifier with the logical storage volume identifier.

7. The method of claim 6, wherein the data structure maintains a reference count for each entry, the reference count being incremented each time a request is made to prepare the logical storage volume and a protocol endpoint that is selected to receive IOs for the logical volume is the same protocol endpoint that is identified in the entry.

8. The method of claim 7, wherein the reference count is decremented each time a request is made to decouple the logical storage volume from the protocol endpoint that was selected to receive IOs for the logical volume.

9. The method of claim 1, further comprising:

selecting a new protocol endpoint configured in the storage system through which IOs for the logical storage volume are to be received and coupling the logical storage volume to the new protocol endpoint; and

generating a new identifier to be included in IOs for the logical storage volume and returning the new identifier to a computer system that issued the request.

10. The method of claim 9, further comprising:

decoupling the logical storage volume from the old protocol endpoint so that new IOs for the logical storage volume are received through the new protocol endpoint.

11. A method for preparing a storage system to execute input-output commands (IOs) issued by a virtual machine running on a host computer, the method comprising:

receiving a request to prepare a metadata logical storage volume for the virtual machine;

selecting a protocol endpoint configured in the storage system through which IOs for the metadata logical storage volume are to be received;

receiving read IOs through the protocol endpoint and returning read data, the read data including identifiers for data logical storage volumes;

receiving a request to prepare the data logical storage volumes for the virtual machine; and

for each data logical storage volume, selecting a protocol endpoint configured in the storage system through which IOs for the logical storage volume are to be received.

12. The method of claim 11, wherein the metadata logical storage volume includes configuration and log files for the VM, a swap file for the VM, and disk descriptor files, one for each of virtual disks of the virtual machine.