File access method and device

Abstract

The invention provides a file access method and device.The method comprises the steps that when a cloud application running in a container accesses files under a cloud application directory in the container, if a virtual file system in a host receives a first file access request, whether a first directory in the host has a first identifier or not is judged; if the first directory has the first identifier, judging whether the first directory has a second identifier; if the first directory has the second identifier, the virtual file system sends the second file access request to the first file system for processing; or if the first directory does not have the second identifier, the virtual file system notifies the second file system to mount the remote directory to the first directory through the first file system, and sends the second file access request to the first file system for processing after mounting is completed, at least one of the two problems of low file access response speed and large storage space occupation in the existing scheme can be solved.

Description

Technical Field

[0001] The present invention relates to the field of cloud applications, and in particular to a file access method and device. Background Art

[0002] In cloud application scenarios (such as cloud gaming), application installation packages and hot update resources need to be shared across multiple instances (usually using a containerized solution that runs multiple containers on a host). There are generally two sharing methods: 1. Pre-installed solution: Application files are pre-copied from the storage server to the host, and applications in the container directly access the application files on the host. Because the application files are pre-copied to the host, all file access requests from applications in the container occur locally, resulting in a fast file access response. However, because the needs of cloud application users are generally unpredictable, when cloud application users want to use different applications, they need to constantly change the application files copied to the host, which is relatively complex to implement. Furthermore, given the limited storage space on the host, copying too many application files to the host is not recommended.

[0003] 2. Installation-free solution: Map application files on the storage server to the container through a network file system such as NFS or CIFS. Access requests from applications in the container to the application files are then converted to access requests to the application files on the storage server through network protocols. Because application files are not stored on the host, the host requires less storage space. However, since file access requests involve the network, file access response speeds are slow. Furthermore, because a single storage server needs to serve multiple instances, a large number of instances will make the storage server a performance bottleneck. Furthermore, because application files are mounted directly in the container, multiple containers on the same host cannot share the network file system cache.

[0004] In view of this, how to optimize the existing solutions to solve at least one of the two problems of slow file access response speed and large storage space occupation in the existing solutions has become a technical problem that needs to be solved urgently. Summary of the Invention

[0005] Therefore, embodiments of the present application provide a file access method and device.

[0006] In a first aspect, an embodiment of the present application provides a file access method, comprising: When a cloud application running in a container accesses files under a cloud application directory in the container, if the virtual file system in the host receives a first file access request from the container, it determines whether the first directory in the host has a first identifier, wherein the first file access request carries an access path, the access path is the path under the second directory in the host, the first directory is the second directory and any directory in the upper directory of the second directory, the second directory is mapped to the third directory in the container through a bind mount mechanism, the fourth directory and the fifth directory are associated directories of the file system in the container, the third directory is the fourth directory or the lower directory of the fourth directory or the upper directory of the fourth directory, the cloud application directory is the fifth directory or the lower directory of the fifth directory or the upper directory of the fifth directory, the first identifier is used to identify that the remote directory needs to be mounted to the corresponding directory through the first file system, and the first file system is a network file system; If the first directory has the first identifier, determining whether the first directory has the second identifier, wherein the second identifier is used to identify that the remote directory has been mounted to the corresponding directory through the first file system; If the first directory has the second identifier, the virtual file system sends the second file access request to the first file system for processing, and returns the processing result to the cloud application; or If the first directory does not have the second identifier, the virtual file system notifies the second file system to mount the remote directory to the first directory through the first file system. After the mounting is completed, the second file access request is sent to the first file system for processing, and the processing result is returned to the cloud application, where the second file system is the file system in the host.

[0007] In a second aspect, an embodiment of the present application further provides a file access device, comprising: The first judgment unit is used to determine whether the first directory in the host has a first identifier when the cloud application running in the container accesses a file under the cloud application directory in the container, if the virtual file system in the host receives a first file access request from the container, wherein the first file access request carries an access path, the access path is the path under the second directory in the host, the first directory is the second directory and any directory in the upper directory of the second directory, the second directory is mapped to the third directory in the container through a bind mount mechanism, the fourth directory and the fifth directory are associated directories of the file system in the container, the third directory is the fourth directory or the lower directory of the fourth directory or the upper directory of the fourth directory, the cloud application directory is the fifth directory or the lower directory of the fifth directory or the upper directory of the fifth directory, the first identifier is used to identify that the remote directory needs to be mounted to the corresponding directory through the first file system, and the first file system is a network file system; a second determining unit configured to determine, if the first directory has the first identifier, whether the first directory has a second identifier, wherein the second identifier is used to identify that the remote directory has been mounted to the corresponding directory through the first file system; a forwarding unit, configured to, if the first directory has the second identifier, cause the virtual file system to send the second file access request to the first file system for processing, and return the processing result to the cloud application; or If the first directory does not have the second identifier, the virtual file system notifies the second file system to mount the remote directory to the first directory through the first file system. After the mounting is completed, the second file access request is sent to the first file system for processing, and the processing result is returned to the cloud application, where the second file system is the file system in the host.

[0008] In summary, the file access method and device provided by the embodiments of the present application combine the bind mount for the second directory in the host with the network mount for the remote directory. The cloud application running in the container accesses the files under the cloud application directory in the container, and when the virtual file system in the host receives the first file access request from the container, it determines whether the first directory has the first identifier. When the first directory has the first identifier, the remote directory is accessed through the first file system mounted on the network. In this way, the application files in the remote directory do not need to be stored in the host, and the access requirements of different cloud applications can be met by setting multiple first directories with the first identifier. Compared with the existing pre-installed solution, It can reduce storage space usage and avoid the implementation complexity caused by the need to copy different files to the host when running different cloud applications in containers. The same cloud application in different containers on the same host can access the remote directory through the same first directory, so that these cloud applications can share the same virtual file system cache. Compared with the existing installation-free solution, it can reduce the overall memory consumption of the host, reduce network requests, improve file access speed, and then save bandwidth and improve the startup and running speed of cloud applications. In addition, in this solution, cloud applications do not need to know the processing logic of the host's virtual file system, which makes it easy to expand / adjust the processing logic and achieve decoupling. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 A flowchart of an embodiment of a file access method provided in an embodiment of the present application; Figure 2 A structural diagram of an embodiment of a file access device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0010] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the drawings in the present application only serve the purpose of illustration and description and are not used to limit the scope of protection of the present application. In addition, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate the operations implemented according to some embodiments of the present application. It should be understood that the operations of the flowcharts can be implemented out of sequence, and steps without logical context can be reversed or implemented simultaneously. In addition, those skilled in the art, under the guidance of the contents of this application, can add one or more other operations to the flowchart, or remove one or more operations from the flowchart.

[0011] In addition, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application generally described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work are within the scope of protection of the present application.

[0012] It should be noted that the term "comprising" will be used in the embodiments of the present application to indicate the existence of the features declared thereafter, but does not exclude the addition of other features.

[0013] Reference Figure 1 As shown, an embodiment of the present application provides a flowchart of a file access method, the method comprising: S10. When a cloud application running in a container accesses a file under a cloud application directory in the container, if the virtual file system in the host receives a first file access request from the container, it determines whether the first directory in the host has a first identifier, wherein the first file access request carries an access path, the access path is the path under the second directory in the host, the first directory is the second directory and any directory in the upper directory of the second directory, the second directory is mapped to the third directory in the container through a bind mount mechanism, the fourth directory and the fifth directory are associated directories of the file system in the container, the third directory is the fourth directory or a lower directory of the fourth directory or an upper directory of the fourth directory, the cloud application directory is the fifth directory or a lower directory of the fifth directory or an upper directory of the fifth directory, the first identifier is used to identify that the remote directory needs to be mounted to the corresponding directory through the first file system, and the first file system is a network file system; In this embodiment, it should be noted that the fourth and fifth directories are associated directories of the file system in the container, meaning that the fourth directory can be indirectly accessed by accessing the fifth directory, or, under certain restrictions, the fourth directory can be indirectly accessed by accessing the fifth directory. The remote directory to be shared over the network can be determined based on certain factors (such as cloud application popularity and package size). (For a particular cloud application, the remote directory stores all or part of the cloud application's files.) A first directory corresponding to the remote directory is pre-assigned with a first identifier, but the first directory is not assigned a second identifier. In this manner, step S13 is subsequently performed, where the remote directory is mounted only when the cloud application actually needs to access it. This achieves on-demand mounting, eliminating the need for a constant connection to the storage server and saving network resources between the host and the storage server. The remote directory refers to a directory on the storage server. Furthermore, it should be noted that for cloud application directories / files that require local access, they can be copied from the storage server to the host, and the corresponding first directory is assigned without the first identifier. This allows the cloud application in the container to directly access the first directory locally when it actually accesses it. In other words, this solution can integrate pre-installed solutions and free-installation solutions. Cloud applications in containers do not need to pay attention to the file access logic in the host, thus achieving solution decoupling.

[0014] The following example illustrates this. Example 1: Assume the container's file system is an OverlayFS file system, and OverlayFS file system 1 exists in the container. OverlayFS file system 1 does not have an upper layer. Cloud application A is running in the container. The directory containing cloud application A's installation package, APK, is the merge layer directory (i.e., the fifth directory) of OverlayFS file system 1. A directory in the container, distinct from the fifth directory, is the lower layer directory (i.e., the fourth directory) of OverlayFS file system 1. The fourth directory is identical to the third directory. When cloud application A accesses a file under the APK directory, the OverlayFS file system converts the file access request into an access request for the corresponding file in the lower layer directory and forwards the request to the virtual file system (VFS) in the host. After receiving the file access request, the VFS file system converts the request into an access request for the corresponding file in the second directory and determines whether a directory with a first identifier exists in the second directory and its upper-layer directories. If so (i.e., the first directory has the first identifier), step S11 and either step S12 or S13 are executed. If it does not exist (that is, the first directory does not have the first identifier), the VFS file system processes the access request for the corresponding file in the second directory and returns the processing result to cloud application A through OverlayFS file system 1. In addition, it should be noted that Example 1 uses the APK directory of cloud application A as an example. Since the APK directory is read-only, the upper layer of OverlayFS file system 1 does not exist in this example. However, if the data directory and sdcard directory of cloud application A are used as an example, and the OverlayFS file system is still used, then since the data directory and sdcard directory are readable and writable, the upper layer of the OverlayFS file system needs to be retained.

[0015] Example 2: Assume that the host's VFS file system is used in the container, cloud application B is running in the container, the fourth directory in the container is mapped to the fifth directory in the container through bind mounting, the third directory in the container is the same as the fourth directory in the container, and the APK directory of the installation package of cloud application B in the container is the same as the fifth directory. When cloud application B accesses a file under the APK directory, the VFS file system converts the file access request into an access request for the corresponding file under the third directory and an access request for the corresponding file under the second directory, and determines whether there is a directory with the first identifier in the second directory and its upper directory. The subsequent processing logic is the same as in Example 1 and will not be repeated here.

[0016] S11. If the first directory has a first identifier, determine whether the first directory has a second identifier, where the second identifier is used to identify that the remote directory has been mounted to the corresponding directory through the first file system; S12. If the first directory has the second identifier, the virtual file system sends the second file access request to the first file system for processing, and returns the processing result to the cloud application; or S13. If the first directory does not have the second identifier, the virtual file system notifies the second file system to mount the remote directory to the first directory through the first file system. After the mounting is completed, the second file access request is sent to the first file system for processing, and the processing result is returned to the cloud application, where the second file system is the file system in the host.

[0017] In this embodiment, it should be noted that the virtual file system manages the mounting of the remote directory through the second file system. Specifically, when the cloud application needs to actually access the remote directory, it is necessary to ensure that the remote directory has been mounted to the first directory through the first file system. If the remote directory has not been mounted to the first directory through the first file system at this time, it is necessary to notify the second file system to mount it. In addition, if the first directory has not been accessed for a long time, the second file system can unmount the corresponding mount point (that is, cancel the mounting of the remote directory between the first file system and the first directory). Finally, the virtual file system sends the second file access request to the first file system for processing, which enables the cloud application to access the remote directory. The first file access request and the second file access request are different. The second file access request is an access request to the corresponding file / folder under the second directory.

[0018] The file access method provided by the embodiment of the present application combines the bind mount for the second directory in the host with the network mount for the remote directory. The cloud application running in the container accesses the files under the cloud application directory in the container, and when the virtual file system in the host receives the first file access request from the container, it determines whether the first directory has the first identifier. When the first directory has the first identifier, the remote directory is accessed through the first file system mounted on the network. In this way, the application files in the remote directory do not need to be stored in the host, and the access requirements of different cloud applications can be met by setting multiple first directories with the first identifier. Compared with the existing pre-installation solution, it can reduce It takes up less storage space and avoids the implementation complexity caused by the need to copy different files to the host when running different cloud applications in the container. In addition, the same cloud application in different containers on the same host can access the remote directory through the same first directory, so that these cloud applications can share the same virtual file system cache. Compared with the existing installation-free solution, it can reduce the overall memory consumption of the host, reduce network requests, improve file access speed, and then save bandwidth and improve the startup and running speed of cloud applications. In addition, in this solution, cloud applications do not need to know the processing logic of the host's virtual file system, which makes it easy to expand / adjust the processing logic and achieve decoupling.

[0019] Based on the above method embodiment, the method may further include: If the first directory does not have the first identifier, the virtual file system processes the file access request and returns the processing result to the cloud application.

[0020] Based on the above method embodiment, the method may further include: Deleting the configuration item corresponding to the first directory in the configuration file of the user-mode program of the second file system, notifying the user-mode program of the second file system to load the configuration file, and deleting the first directory; or Notify the user mode program of the second file system to delete the configuration item corresponding to the first directory in the mount point list, and delete the first directory.

[0021] In this embodiment, it should be noted that when deleting a first directory, it is necessary to determine whether the first directory is associated with a mount point. If so, it is necessary to first cancel the mount relationship corresponding to the mount point (i.e., the mount relationship between the remote directory and the first directory via the first file system) before deleting the first directory. When canceling the mount relationship corresponding to the mount point, the existing user-mode program of the second file system can be used for processing, or a new user-mode program can be rebuilt to replace the existing user-mode program of the second file system and then processed by the new user-mode program. Specifically, processing using the existing user-mode program of the second file system may include: deleting the configuration item corresponding to the first directory in the configuration file of the user-mode program of the second file system, notifying the user-mode program of the second file system to load the configuration file, so that the user-mode program of the second file system compares the newly loaded configuration file with the previously loaded configuration file and uninstalls the mount points corresponding to the configuration items that existed in the previously loaded configuration file but not in the newly loaded configuration file. Processing by a new user-mode program may include: notifying the new user-mode program to delete the configuration item corresponding to the first directory in the mount point list, so that the new user-mode program uninstalls the mount point corresponding to the configuration item to be deleted. In addition, if the first directory is not associated with a mount point, you can directly delete the first directory.

[0022] Based on the aforementioned method embodiment, the second file system may include an autofs file system.

[0023] Based on the aforementioned method embodiment, the file system in the container may include an OverlayFS file system or a virtual file system.

[0024] In this embodiment, it should be noted that the file system in the container may include not only the OverlayFS file system and the virtual file system, but also the AUFS file system.

[0025] Reference Figure 2 FIG. 1 is a schematic diagram of a file access device according to an embodiment of the present invention, wherein the device includes: The first judgment unit 20 is used to determine whether the first directory in the host has a first identifier when the cloud application running in the container accesses a file under the cloud application directory in the container, if the virtual file system in the host receives a first file access request from the container, wherein the first file access request carries an access path, the access path is the path under the second directory in the host, the first directory is the second directory and any directory in the upper directory of the second directory, the second directory is mapped to the third directory in the container through a bind mount mechanism, the fourth directory and the fifth directory are associated directories of the file system in the container, the third directory is the fourth directory or a lower directory of the fourth directory or an upper directory of the fourth directory, the cloud application directory is the fifth directory or a lower directory of the fifth directory or an upper directory of the fifth directory, the first identifier is used to identify that the remote directory needs to be mounted to the corresponding directory through the first file system, and the first file system is a network file system; The second determining unit 21 is configured to determine whether the first directory has a second identifier if the first directory has the first identifier, wherein the second identifier is used to identify that the remote directory has been mounted to the corresponding directory through the first file system; The forwarding unit 22 is configured to send the second file access request to the first file system for processing if the first directory has the second identifier, and return the processing result to the cloud application; or If the first directory does not have the second identifier, the virtual file system notifies the second file system to mount the remote directory to the first directory through the first file system. After the mounting is completed, the second file access request is sent to the first file system for processing, and the processing result is returned to the cloud application, where the second file system is the file system in the host.

[0026] The file access device provided by the embodiment of the present application combines the bind mount for the second directory in the host with the network mount for the remote directory. The cloud application running in the container accesses the files under the cloud application directory in the container, and when the virtual file system in the host receives the first file access request from the container, it determines whether the first directory has the first identifier. When the first directory has the first identifier, the remote directory is accessed through the first file system mounted on the network. In this way, the application files in the remote directory do not need to be stored in the host, and the access requirements of different cloud applications can be met by setting multiple first directories with the first identifier. Compared with the existing pre-installation solution, it can reduce It takes up less storage space and avoids the implementation complexity caused by the need to copy different files to the host when running different cloud applications in the container. In addition, the same cloud application in different containers on the same host can access the remote directory through the same first directory, so that these cloud applications can share the same virtual file system cache. Compared with the existing installation-free solution, it can reduce the overall memory consumption of the host, reduce network requests, improve file access speed, and then save bandwidth and improve the startup and running speed of cloud applications. In addition, in this solution, cloud applications do not need to know the processing logic of the host's virtual file system, which makes it easy to expand / adjust the processing logic and achieve decoupling.

[0027] Based on the aforementioned device embodiment, the forwarding unit may also be configured to: If the first directory does not have the first identifier, the virtual file system processes the file access request and returns the processing result to the cloud application.

[0028] Based on the above device embodiment, the device may further include: a deleting unit, configured to delete the configuration item corresponding to the first directory in the configuration file of the user-mode program of the second file system, notify the user-mode program of the second file system to load the configuration file, and delete the first directory; or Notify the user mode program of the second file system to delete the configuration item corresponding to the first directory in the mount point list, and delete the first directory.

[0029] Based on the aforementioned device embodiment, the second file system may include an autofs file system.

[0030] Based on the aforementioned device embodiment, the file system in the container may include an OverlayFS file system or a virtual file system.

[0031] The file access device provided in the embodiment of the present application has an implementation process consistent with the file access method provided in the embodiment of the present application, and the effect that can be achieved is also the same as the file access method provided in the embodiment of the present application, which will not be repeated here.

[0032] The above are only specific embodiments of the present application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A file access method, characterized in that: include: When a cloud application running in a container accesses files under a cloud application directory in the container, if the virtual file system in the host receives a first file access request from the container, it determines whether the first directory in the host has a first identifier, wherein the first file access request carries an access path, the access path is the path under the second directory in the host, the first directory is the second directory and any directory in the upper directory of the second directory, the second directory is mapped to the third directory in the container through a bind mount mechanism, the fourth directory and the fifth directory are associated directories of the file system in the container, the third directory is the fourth directory or the lower directory of the fourth directory or the upper directory of the fourth directory, the cloud application directory is the fifth directory or the lower directory of the fifth directory or the upper directory of the fifth directory, the first identifier is used to identify that the remote directory needs to be mounted to the corresponding directory through the first file system, and the first file system is a network file system; If the first directory has the first identifier, determining whether the first directory has the second identifier, wherein the second identifier is used to identify that the remote directory has been mounted to the corresponding directory through the first file system; If the first directory has the second identifier, the virtual file system sends the second file access request to the first file system for processing, and returns the processing result to the cloud application; or If the first directory does not have the second identifier, the virtual file system notifies the second file system to mount the remote directory to the first directory through the first file system. After the mounting is completed, the second file access request is sent to the first file system for processing, and the processing result is returned to the cloud application, where the second file system is the file system in the host.

2. The method according to claim 1, wherein Also includes: If the first directory does not have the first identifier, the virtual file system processes the file access request and returns the processing result to the cloud application.

3. The method according to claim 1, wherein Also includes: Deleting the configuration item corresponding to the first directory in the configuration file of the user-mode program of the second file system, notifying the user-mode program of the second file system to load the configuration file, and deleting the first directory; or Notify the user mode program of the second file system to delete the configuration item corresponding to the first directory in the mount point list, and delete the first directory.

4. The method according to claim 1, wherein The second file system includes an autofs file system.

5. The method according to claim 1, wherein The file system in the container includes the OverlayFS file system or virtual file system.

6. A file access device, characterized in that: include: The first judgment unit is used to determine whether the first directory in the host has a first identifier when the cloud application running in the container accesses a file under the cloud application directory in the container, if the virtual file system in the host receives a first file access request from the container, wherein the first file access request carries an access path, the access path is the path under the second directory in the host, the first directory is the second directory and any directory in the upper directory of the second directory, the second directory is mapped to the third directory in the container through a bind mount mechanism, the fourth directory and the fifth directory are associated directories of the file system in the container, the third directory is the fourth directory or the lower directory of the fourth directory or the upper directory of the fourth directory, the cloud application directory is the fifth directory or the lower directory of the fifth directory or the upper directory of the fifth directory, the first identifier is used to identify that the remote directory needs to be mounted to the corresponding directory through the first file system, and the first file system is a network file system; a second determining unit configured to determine, if the first directory has the first identifier, whether the first directory has a second identifier, wherein the second identifier is used to identify that the remote directory has been mounted to the corresponding directory through the first file system; a forwarding unit, configured to, if the first directory has the second identifier, cause the virtual file system to send the second file access request to the first file system for processing, and return the processing result to the cloud application; or If the first directory does not have the second identifier, the virtual file system notifies the second file system to mount the remote directory to the first directory through the first file system. After the mounting is completed, the second file access request is sent to the first file system for processing, and the processing result is returned to the cloud application, where the second file system is the file system in the host.

7. The device according to claim 6, characterized in that The forwarding unit is further configured to: If the first directory does not have the first identifier, the virtual file system processes the file access request and returns the processing result to the cloud application.

8. The device according to claim 6, wherein Also includes: a deleting unit, configured to delete a configuration item corresponding to the first directory in a configuration file of a user-mode program of the second file system, notify the user-mode program of the second file system to load the configuration file, and delete the first directory; or Notify the user mode program of the second file system to delete the configuration item corresponding to the first directory in the mount point list, and delete the first directory.

9. The device according to claim 6, wherein The second file system includes an autofs file system.

10. The device according to claim 6, wherein The file system in the container includes the OverlayFS file system or virtual file system.

Images