Systems and methods for performing storage location virtualization

• US 10,216,455 B1
• Filed: 02/14/2017
• Issued: 02/26/2019
• Est. Priority Date: 02/14/2017
• Status: Active Grant

• Current Assignee: Veritas Technologies, LLC (Whitehouse Group Ltd.)
• Original Assignee: Veritas Technologies, LLC (Whitehouse Group Ltd.)
• Inventors: Schroeder, Ryan, Searls, Kirk, Christensen, Aaron
• Primary Examiner(s): Bertram, Ryan
• Assistant Examiner(s): Ta, Trang K
• Application Number:
  US15/432,614
• Time in Patent Office: 742 Days
• Field of Search: None
• CPC Class Codes: G06F 16/183 Provision of network file services by network file servers, e.g. by using NFS, CIFS network file access protocols H04L67/1097
• CPC Class Codes: G06F 3/0605 by facilitating the interaction with a user or administrator
• CPC Class Codes: G06F 3/0608 Saving storage space on storage systems
• 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/0673 Single storage device

Abstract

The disclosed computer-implemented method for performing storage location virtualization may include (i) identifying a volume storage location for an operating-system-level virtualization container that isolates an instance of user space, the volume storage location providing a working space for data accessed during the existence of the operating-system-level virtualization container, (ii) mapping, through an automated driver that performs location virtualization, the volume storage location to multiple distinct source locations outside of the operating-system-level virtualization container, rather than a single source location, and (iii) propagating, through the automated driver, changes to the data within the working space of the volume storage location during the existence of the operating-system-level virtualization container to the respective multiple distinct source locations outside of the operating-system-level virtualization container to preserve the changes. Various other methods, systems, and computer-readable media are also disclosed.

Claims

1. A computer-implemented method for performing storage location virtualization, at least a portion of the method being performed by a computing device comprising at least one processor, the method comprising:

identifying a volume storage location for an operating-system-level virtualization container that isolates an instance of user space, the volume storage location providing a working space for data accessed during the existence of the operating-system-level virtualization container;

mapping, through an automated driver that performs location virtualization, the volume storage location to multiple distinct source locations outside of the operating-system-level virtualization container, rather than a single source location, such that contents from the multiple distinct source locations appear within the volume storage location as a combined single location for the contents; and

propagating, through the automated driver, changes to the data within the working space of the volume storage location during the existence of the operating-system-level virtualization container to the respective multiple distinct source locations outside of the operating-system-level virtualization container to preserve the changes,

wherein identifying the volume storage location enables usage of the volume storage location to be repeatable such that a user can provide access to the volume storage location from within a different operating-system-level virtualization container without the user repeatedly identifying the multiple distinct source locations.

2. The computer-implemented method of claim 1, wherein:

the operating-system-level virtualization container operates in a cluster environment; and

the automated driver provides access to the volume storage location to multiple operating-system-level virtualization containers on distinct nodes across the cluster environment.

3. The computer-implemented method of claim 2, wherein the automated driver further virtualizes the volume storage location within the cluster environment such that the volume storage location is available to each node of the cluster environment regardless of which node issues an access request to the volume storage location.

4. The computer-implemented method of claim 1, wherein identifying the volume storage location comprises:

receiving a name for the volume storage location; and

saving the name for the volume storage location to enable repeated reference to the volume storage location.

5. The computer-implemented method of claim 1, wherein:

a file within one of the multiple distinct source locations is categorized as sensitive; and

the automated driver blocks access, from the operating-system-level virtualization container, to the file.

6. The computer-implemented method of claim 1, wherein mapping, through the automated driver that performs location virtualization, the volume storage location to multiple distinct source locations outside of the operating-system-level virtualization container comprises initially receiving a selection from a user of the multiple distinct source locations as sources for the volume storage location.

7. The computer-implemented method of claim 1, wherein:

one of the multiple distinct source locations outside of the operating-system-level virtualization container comprises a mountable network file system; and

the automated driver is configured to mount the mountable network file system to propagate at least one of the changes to the data within the working space of the volume storage location during the existence of the operating-system-level virtualization container to the mountable network file system.

8. The computer-implemented method of claim 1, wherein:

one of the multiple distinct source locations outside of the operating-system-level virtualization container comprises a scalable redundant storage system instance; and

the automated driver is configured to access the scalable redundant storage system instance through a corresponding application programming interface.

9. The computer-implemented method of claim 1, wherein instead of repeating a process of manually selecting the multiple distinct source locations, the user is enabled to reference an identifier that was previously assigned to the volume storage location.

10. The computer-implemented method of claim 1, wherein the automated driver operates at a kernel level of a corresponding operating system.

11. A system for performing storage location virtualization, the system comprising:

an identification module, stored in memory, that identifies a volume storage location for an operating-system-level virtualization container that isolates an instance of user space, the volume storage location providing a working space for data accessed during the existence of the operating-system-level virtualization container;

a mapping module, stored in memory, that maps, through an automated driver that performs location virtualization, the volume storage location to multiple distinct source locations outside of the operating-system-level virtualization container, rather than a single source location, such that contents from the multiple distinct source locations appear within the volume storage location as a combined single location for the contents;

a propagation module, stored in memory, that propagates, through the automated driver, changes to the data within the working space of the volume storage location during the existence of the operating-system-level virtualization container to the respective multiple distinct source locations outside of the operating-system-level virtualization container to preserve the changes; and

at least one physical processor configured to execute the identification module, the mapping module, and the propagation module,

wherein the identification module identifying the volume storage location enables usage of the volume storage location to be repeatable such that a user can provide access to the volume storage location from within a different operating-system-level virtualization container without the user repeatedly identifying the multiple distinct source locations.

12. The system of claim 11, wherein:

the operating-system-level virtualization container operates in a cluster environment; and

the automated driver provides access to the volume storage location to multiple operating-system-level virtualization containers on distinct nodes across the cluster environment.

13. The system of claim 12, wherein the automated driver further virtualizes the volume storage location within the cluster environment such that the volume storage location is available to each node of the cluster environment regardless of which node issues an access request to the volume storage location.

14. The system of claim 11, wherein the identification module identifies the volume storage location at least in part through:

receiving a name for the volume storage location; and

saving the name for the volume storage location to enable repeated reference to the volume storage location.

15. The system of claim 11, wherein:

a file within one of the multiple distinct source locations is categorized as sensitive; and

the automated driver blocks access, from the operating-system-level virtualization container, to the file.

16. The system of claim 11, wherein the mapping module maps, through the automated driver that performs location virtualization, the volume storage location to multiple distinct source locations outside of the operating-system-level virtualization container at least in part through initially receiving a selection from a user of the multiple distinct source locations as sources for the volume storage location.

17. The system of claim 11, wherein:

one of the multiple distinct source locations outside of the operating-system-level virtualization container comprises a mountable network file system; and

the automated driver is configured to mount the mountable network file system to propagate at least one of the changes to the data within the working space of the volume storage location during the existence of the operating-system-level virtualization container to the mountable network file system.

18. The system of claim 11, wherein:

one of the multiple distinct source locations outside of the operating-system-level virtualization container comprises a scalable redundant storage system instance; and

the automated driver is configured to access the scalable redundant storage system instance through a corresponding application programming interface.

19. The system of claim 11, wherein instead of repeating a process of manually selecting the multiple distinct source locations, the user is enabled to reference an identifier that was previously assigned to the volume storage location.

20. A non-transitory computer-readable medium comprising one or more computer-readable instructions that, when executed by at least one processor of a computing device, cause the computing device to:

identify a volume storage location for an operating-system-level virtualization container that isolates an instance of user space, the volume storage location providing a working space for data accessed during the existence of the operating-system-level virtualization container;

map, through an automated driver that performs location virtualization, the volume storage location to multiple distinct source locations outside of the operating-system-level virtualization container, rather than a single source location, such that contents from the multiple distinct source locations appear within the volume storage location as a combined single location for the contents; and

propagate, through the automated driver, changes to the data within the working space of the volume storage location during the existence of the operating-system-level virtualization container to the respective multiple distinct source locations outside of the operating-system-level virtualization container to preserve the changes,

wherein identifying the volume storage location enables usage of the volume storage location to be repeatable such that a user can provide access to the volume storage location from within a different operating-system-level virtualization container without the user repeatedly identifying the multiple distinct source locations.