File system mounting method, device and equipment

Abstract

The invention provides a file system mounting method, device and equipment, and the method can comprise the steps: responding to an updating operation executed on a mounting file list of a target container group, determining a mounting configuration file corresponding to the target container group, and enabling the mounting configuration file to comprise identifiers of a plurality of target mounting files; determining identifiers of a plurality of current mounted files corresponding to the target container group; according to the identifications of the multiple target mounted files and the identifications of the multiple current mounted files, in a file container corresponding to the target container group, the mounted files of the target container group are updated, and the files corresponding to the target container group and the files in the file container have a mapping relation. And the mounting efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of computers, and in particular, to a method, apparatus, and device for mounting a file system. Background Art

[0002] A container orchestration engine (Kubernetes) cluster may include multiple container groups (pods), and a container group may include multiple containers. When creating a container, a Persistent Volume Claim (PVC) and the corresponding Persistent Volume (PV) can be mounted for the container. The PV can be used to store data sets.

[0003] In the related art, when running an application in a pod, the data set in the PV can be accessed. The data set includes the data required to run the application. However, in the above manner, when it is necessary to replace the data set, the PVC needs to be updated, and then the pod needs to be restarted, and it is impossible to dynamically mount data for the running pod, resulting in low mounting efficiency. Summary of the Invention

[0004] Multiple aspects of this application provide a method, apparatus, and device for mounting a file system to improve the mounting efficiency.

[0005] In a first aspect, an embodiment of this application provides a method for mounting a file system, including:

[0006] In response to an update operation performed on a mounting file list of a target container group, determine a mounting configuration file corresponding to the target container group, where the mounting configuration file includes identifiers of multiple target mounting files;

[0007] Determine identifiers of multiple current mounting files corresponding to the target container group;

[0008] According to the identifiers of the multiple target mounting files and the identifiers of the multiple current mounting files, update the mounting files of the target container group in a file container corresponding to the target container group, where the file corresponding to the target container group has a mapping relationship with the files in the file container.

[0009] In a possible implementation manner, updating the mounting files of the target container group in the file container corresponding to the target container group according to the identifiers of the multiple target mounting files and the identifiers of the multiple current mounting files includes:

[0010] According to the identifiers of the multiple target mounting files and the identifiers of the multiple current mounting files, determine the identifier of the file to be mounted and / or the identifier of the file to be unmounted;

[0011] Update the mounted files of the target container group in the file container according to the identifier of the file to be mounted and / or the identifier of the file to be unmounted.

[0012] In a possible implementation, updating the mounted files of the target container group in the file container according to the identifier of the file to be mounted and / or the identifier of the file to be unmounted includes at least one of the following:

[0013] Create the file to be mounted in the file container according to the identifier of the file to be mounted;

[0014] Delete the file to be unmounted in the file container according to the identifier of the file to be unmounted.

[0015] In a possible implementation, in response to an update operation performed on the mounted file list of the target container group, determining the mounted configuration file corresponding to the target container group includes:

[0016] Monitor the mounted file list through a third-party component, where the mounted file list includes multiple file identifiers;

[0017] When it is monitored that the mounted file list is updated, determine whether there is an existing mounted configuration file corresponding to the target container group;

[0018] If there is no existing mounted configuration file corresponding to the target container group, generate the mounted configuration file according to the updated mounted file list;

[0019] If there is an existing mounted configuration file corresponding to the target container group, update the existing mounted configuration file according to the updated mounted file list to obtain the mounted configuration file, where the mounted configuration file includes the file identifiers in the updated mounted file list.

[0020] In a possible implementation, before determining the identifiers of the multiple currently mounted files corresponding to the target container group, it includes:

[0021] Monitor the mounted configuration file corresponding to the target container group;

[0022] It is monitored that the mounted configuration file corresponding to the target container group is generated, or it is monitored that the mounted configuration file corresponding to the target container group is updated.

[0023] In a possible implementation, the target container group and the file container are deployed on a server; the target container group corresponds to a first file, the file container includes a second file, and the server includes a third file; where

[0024] The second file includes at least one mounted file corresponding to the target container group;

[0025] There is a soft link relationship between the first file and the third file, and the second file is mounted in the third file. The soft link relationship is used for the target container group to access the at least one mounted file of the target container group through the first file, the third file, and the second file.

[0026] In a possible implementation manner, the target container group and the file container are deployed on a server; the target container group corresponds to a first file, the file container includes a second file and a fourth file, and the server includes a third file; wherein,

[0027] The fourth file includes at least one mounted file corresponding to the target container group;

[0028] The fourth file is mounted in the second file;

[0029] There is a binding relationship between the first file and the third file, and the second file is mounted in the third file. The binding relationship is used for the target container group to access the at least one mounted file of the target container group through the first file, the third file, the second file, and the fourth file.

[0030] In a possible implementation manner, the target container group and the file container are deployed on a server; the target container group corresponds to a first file, the file container includes a second file, and the server includes a third file; wherein,

[0031] The second file includes at least one mounted file corresponding to the target container group;

[0032] There is a recursive binding relationship between the first file and the third file, and the second file is mounted in the third file. The recursive binding relationship is used for the target container group to recursively access the at least one mounted file of the target container group through the first file, the third file, and the second file.

[0033] In a second aspect, an embodiment of the present application provides a file system mounting device, which includes: a response module, a determination module, and an update module, wherein,

[0034] The response module is configured to, in response to an update operation performed on the mounted file list of the target container group, determine a mounted configuration file corresponding to the target container group, and the mounted configuration file includes identifiers of a plurality of target mounted files;

[0035] The determining module is configured to determine the identifiers of multiple currently mounted files corresponding to the target container group;

[0036] The updating module is configured to update the mounted files of the target container group in the file container corresponding to the target container group according to the identifiers of the multiple target mounted files and the identifiers of the multiple currently mounted files, and there is a mapping relationship between the files corresponding to the target container group and the files in the file container.

[0037] In a possible implementation manner, the updating module is specifically configured to:

[0038] Determine the identifier of the file to be mounted and / or the identifier of the file to be unmounted according to the identifiers of the multiple target mounted files and the identifiers of the multiple currently mounted files;

[0039] Update the mounted files of the target container group in the file container according to the identifier of the file to be mounted and / or the identifier of the file to be unmounted.

[0040] In a possible implementation manner, the updating module is specifically configured to:

[0041] Create the file to be mounted in the file container according to the identifier of the file to be mounted;

[0042] Delete the file to be unmounted in the file container according to the identifier of the file to be unmounted.

[0043] In a possible implementation manner, the response module is specifically configured to:

[0044] Monitor the mounted file list through a third-party component, and the mounted file list includes multiple file identifiers;

[0045] When it is monitored that the mounted file list is updated, determine whether there is an existing mounted configuration file corresponding to the target container group;

[0046] If there is no existing mounted configuration file corresponding to the target container group, generate the mounted configuration file according to the updated mounted file list;

[0047] If there is an existing mounted configuration file corresponding to the target container group, update the existing mounted configuration file according to the updated mounted file list to obtain the mounted configuration file, and the mounted configuration file includes the file identifiers in the updated mounted file list.

[0048] In a possible implementation manner, the device includes a monitoring module, and the monitoring module is configured to:

[0049] Monitor the mounted configuration file corresponding to the target container group;

[0050] It is monitored that the mounting configuration file corresponding to the target container group is generated, or it is monitored that the mounting configuration file corresponding to the target container group is updated.

[0051] In a possible implementation manner, the target container group and the file container are deployed on a server; the target container group corresponds to a first file, the file container includes a second file, and the server includes a third file; wherein,

[0052] The second file includes at least one mounting file corresponding to the target container group;

[0053] There is a soft link relationship between the first file and the third file, the second file is mounted in the third file, and the soft link relationship is used for the target container group to access the at least one mounting file of the target container group through the first file, the third file, and the second file.

[0054] In a possible implementation manner, the target container group and the file container are deployed on a server; the target container group corresponds to a first file, the file container includes a second file and a fourth file, and the server includes a third file; wherein,

[0055] The fourth file includes at least one mounting file corresponding to the target container group;

[0056] The fourth file is mounted in the second file;

[0057] There is a binding relationship between the first file and the third file, the second file is mounted in the third file, and the binding relationship is used for the target container group to access the at least one mounting file of the target container group through the first file, the third file, the second file, and the fourth file.

[0058] In a possible implementation manner, the target container group and the file container are deployed on a server; the target container group corresponds to a first file, the file container includes a second file, and the server includes a third file; wherein,

[0059] The second file includes at least one mounting file corresponding to the target container group;

[0060] There is a recursive binding relationship between the first file and the third file, the second file is mounted in the third file, and the recursive binding relationship is used for the target container group to recursively access the at least one mounting file of the target container group through the first file, the third file, and the second file.

[0061] In a third aspect, an embodiment of the present application provides an electronic device, including: a memory and a processor;

[0062] The memory stores computer-executable instructions;

[0063] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the method according to any one of the first aspect.

[0064] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, they are used to implement the method according to any one of the first aspect.

[0065] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, and when the computer program is executed by a processor, it implements the method according to any one of the first aspect.

[0066] An embodiment of the present application provides a method, device and equipment for mounting a file system. The server can determine a mounting configuration file corresponding to a target container group in response to an update operation performed on a mounting file list of the target container group, and determine identifiers of a plurality of current mounting files corresponding to the target container group. Furthermore, according to the identifiers of a plurality of target mounting files in the mounting configuration file and the identifiers of the plurality of current mounting files, the mounting files of the target container group can be updated in a file container corresponding to the target container group, and there is a mapping relationship between the file corresponding to the target container group and the files in the file container. Since a plurality of mounting files of the target container group can be updated in the file container and then the plurality of mounting files are synchronously mounted to the target container group, updating a plurality of mounting files in the file container is to update a plurality of mounting files of the target container group, and the operation of the target container group does not need to be interrupted to mount files; and it supports dynamic mounting of a plurality of mounting files. Compared with the prior art where a PVC only supports mounting one mounting file, the mounting efficiency is improved. Description of the Drawings

[0067] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation to the present application. In the drawings:

[0068] Figure 1 It is a schematic diagram of a scenario provided by an exemplary embodiment of the present application;

[0069] Figure 2 It is a schematic flowchart of a method for mounting a file system provided by an exemplary embodiment of the present application;

[0070] Figure 3Schematic flowchart of another file mounting method provided by an exemplary embodiment of the present application;

[0071] Figure 4A Schematic diagram of a mounting method provided by an exemplary embodiment of the present application;

[0072] Figure 4B Schematic diagram of another mounting method provided by an exemplary embodiment of the present application;

[0073] Figure 4C Schematic diagram of yet another mounting method provided by an exemplary embodiment of the present application;

[0074] Figure 5 Schematic process diagram of a file system mounting method provided by an exemplary embodiment of the present application;

[0075] Figure 6 Schematic structural diagram of a file system mounting device provided by an exemplary embodiment of the present application;

[0076] Figure 7 Schematic structural diagram of another file system mounting device provided by an exemplary embodiment of the present application;

[0077] Figure 8 Schematic structural diagram of a server provided by an exemplary embodiment of the present application. Detailed implementation manners

[0078] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or fully authorized by all parties. Moreover, the collection, use, and processing of relevant data need to comply with relevant laws, regulations, and standards, and corresponding operation entrances are provided for the user to choose to authorize or reject.

[0079] To make the objectives, technical solutions, and advantages of the present application clearer, the technical solutions of the present application will be clearly and completely described below in conjunction with specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts shall fall within the protection scope of the present application.

[0080] Figure 1 Schematic diagram of a scenario provided by an exemplary embodiment of the present application. Please refer to Figure 1 , including a file container and a target container group. There is a mapping relationship between the files in the file container and the files corresponding to the target container group.

[0081] The file container includes the identifiers of multiple currently mounted files, namely the identifier Mount1 of the mounted file 1 and the identifier Mount2 of the mounted file 2. Since the files in the file container have a mapping relationship with the files corresponding to the target container group, at this time, the currently mounted files of the target container group are also the mounted file 1 and the mounted file 2. The target container group may include the identifiers of the multiple currently mounted files, that is, the identifier Mount1 of the mounted file 1 and the identifier Mount2 of the mounted file 2.

[0082] When it is necessary to update the mounted files of the target container group, the mounted files can be updated in the file container. Assume that in the file container, the mounted file 1 and the mounted file 2 included in the currently mounted files can be updated to the mounted file 2 and the mounted file 3. After the update, the file container may include the identifier Mount2 of the mounted file 2 and the identifier Mount3 of the mounted file 3.

[0083] After the update in the file container, the multiple mounted files in the file container can be mapped to the target container group to update the mounted files in the file container, that is, to update the mounted files of the target container group. For example, the mounted file 2 and the mounted file 3 in the file container can be mapped to the target container group so that the mounted files of the target container group include the mounted file 2 and the mounted file 3. The target container group may include the identifier Mount2 of the mounted file 2 and the identifier Mount3 of the mounted file 3.

[0084] In the related art, when running an application in a pod, the dataset in the PV can be accessed. The dataset includes the data required to run the application. However, in the above method, when it is necessary to replace the dataset, the PVC needs to be updated, and then the pod needs to be restarted, and it is impossible to dynamically mount data for the running pod, resulting in low mounting efficiency.

[0085] In the embodiment of the present application, the target container group has a corresponding file container. The mounted files of the target container group can be updated in the file container corresponding to the target container group according to the identifiers of multiple target mounted files and the identifiers of multiple currently mounted files. The file corresponding to the target container group has a mapping relationship with the files in the file container. Since the multiple mounted files of the target container group can be updated in the file container and then the multiple mounted files are synchronously mounted to the target container group, updating the multiple mounted files in the file container is to update the multiple mounted files of the target container group. It is not necessary to interrupt the operation of the target container group to mount files; and it supports dynamic mounting of multiple mounted files. Compared with the prior art where the PVC only supports mounting one mounted file, the mounting efficiency is improved.

[0086] Next, the technical solutions shown in this application will be described in detail through specific embodiments. It should be noted that the following several embodiments can exist independently or be combined with each other. For the same or similar content, it will not be repeated in different embodiments.

[0087] Figure 2 The flowchart of a file system mounting method provided for an exemplary embodiment of this application. Please refer to Figure 2 , the method may include:

[0088] S201. In response to an update operation performed on the mounting file list of the target container group, determine the mounting configuration file corresponding to the target container group.

[0089] The execution subject of the embodiments of this application can be a server or a file system mounting device provided in the server. The file system mounting device can be implemented by software or by a combination of software and hardware. The file system mounting device can be a processor in the server. For the sake of easy understanding, in the following, the execution subject is taken as an example of a server for description.

[0090] The mounting file list may include identifiers, data sources, and configuration parameters of multiple mounting files, etc. One mounting file includes one data source.

[0091] Optionally, the identifier of the mounting file can be represented by a directory. For example, if mounting file 1 is in directory Mount1, the identifier of mounting file 1 can be Mount1.

[0092] Optionally, the identifier of the mounting file can also be represented by the file name of the mounting file. For example, if the file name of mounting file 1 is file001, the identifier of mounting file 1 can be file001.

[0093] When the user needs to add or delete the mounting files of the target container group, the user can update the mounting file list, and the server can, in response to the update operation performed on the mounting file list, determine the mounting configuration file corresponding to the target container group.

[0094] The mounting configuration file includes identifiers of multiple target mounting files. Optionally, the mounting configuration file may also include data sources, mounting paths, and configuration parameters of multiple target mounting files, etc. The mounting configuration file can be a Fuse-configmap file.

[0095] For example, if the target container group is pod-1 and the list of mounted files includes the identifier of mounted file 1 and the identifier of mounted file 2, and if the user deletes the identifier of mounted file 1 from the list of mounted files and adds the identifier of mounted file 3, then in response to the update operation performed by the user on the list of mounted files, the mounted configuration file 1 corresponding to pod-1 can be determined. The mounted configuration file 1 can include the identifiers of 2 target mounted files, namely, the identifier Mount2 of mounted file 2 and the identifier Mount3 of mounted file 3.

[0096] S202. Determine the identifiers of multiple current mounted files corresponding to the target container group.

[0097] The target container group can be a container group for which the mounted files need to be updated.

[0098] The target container group can have a corresponding file container. The file container can be a container in a user space file system (Fuse) pod.

[0099] The identifiers of multiple current mounted files corresponding to the target container group are the same as the identifiers of multiple current mounted files in the file container.

[0100] Optionally, the identifiers of multiple current mounted files can be determined in the file container, that is, the identifiers of multiple current mounted files corresponding to the target container group are determined.

[0101] For example, the identifiers of multiple current mounted files can be determined in the file container, including the identifier Mount1 of mounted file 1 and the identifier Mount2 of mounted file 2.

[0102] S203. Update the mounted files of the target container group in the file container corresponding to the target container group according to the identifiers of multiple target mounted files and the identifiers of multiple current mounted files.

[0103] The file corresponding to the target container group has a mapping relationship with the file in the file container, that is, the mounted files in the target container group are the same as those in the file container.

[0104] In an optional embodiment, the mounted files of the target container group can be updated in the file container corresponding to the target container group according to the identifiers of multiple target mounted files and the identifiers of multiple current mounted files in the following manner: determine the identifier and / or the identifier of the file to be unmounted of the file to be mounted according to the identifiers of multiple target mounted files and the identifiers of multiple current mounted files; update the mounted files of the target container group in the file container according to the identifier and / or the identifier of the file to be unmounted of the file to be mounted.

[0105] Since the files corresponding to the target container group have a mapping relationship with the files in the file container, after determining the identifier of the file to be mounted and / or the identifier of the file to be unmounted, the mounted files can be updated in the file container according to the identifier of the file to be mounted and / or the identifier of the file to be unmounted, so as to update the mounted files of the target container group.

[0106] For example, if the identifiers of multiple target mounted files include the identifier Mount2 of mounted file 2 and the identifier Mount3 of mounted file 3, and the identifiers of multiple current mounted files include the identifier Mount1 of mounted file 1 and the identifier Mount2 of mounted file 2, then it can be determined that the identifier of the file to be mounted is Mount3 and the identifier of the file to be unmounted is Mount1. The server can perform an update in the file container according to the identifier Mount3 of the file to be mounted and the identifier Mount1 of the file to be unmounted, that is, unmount the mounted file 1 corresponding to Mount1 and mount the mounted file 3 corresponding to Mount3, so as to update the mounted files of the target container group.

[0107] In the embodiment of the present application, the server can determine the mounted configuration file corresponding to the target container group in response to an update operation performed on the mounted file list of the target container group, and determine the identifiers of multiple current mounted files corresponding to the target container group. Furthermore, according to the identifiers of multiple target mounted files in the mounted configuration file and the identifiers of multiple current mounted files, the mounted files of the target container group can be updated in the file container corresponding to the target container group, and the files corresponding to the target container group have a mapping relationship with the files in the file container. Since multiple mounted files of the target container group can be updated in the file container and then the multiple mounted files are synchronously mounted to the target container group, updating multiple mounted files in the file container is to update multiple mounted files of the target container group. Without interrupting the operation of the target container group, files can be mounted; and it supports dynamic mounting of multiple mounted files. Compared with the prior art where PVC only supports mounting one mounted file, the mounting efficiency is improved.

[0108] Next, based on Figure 2 the embodiment shown, in combination with Figure 3 , the above file system mounting method will be described in detail.

[0109] Figure 3 FIG. is a schematic flowchart of another file mounting method provided by an exemplary embodiment of the present application. Please refer to Figure 3 , the method may include:

[0110] S301. Listen to the mounted file list through a third-party component.

[0111] The mounted file list includes multiple file identifiers. The multiple file identifiers are the identifiers of multiple mounted files.

[0112] Optionally, the third-party component can be a Thin Runtime Controller.

[0113] Optionally, a third-party component can be provided in the server, and the mounted file list can be periodically monitored through the third-party component.

[0114] S302. When it is monitored that the mounted file list is updated, determine whether there is an existing mounted configuration file corresponding to the target container group.

[0115] When the mounting information in the mounted file list changes, it can be determined whether there is already an existing mounted configuration file corresponding to the target container group in the server. If not, step S303 can be executed; if so, step S304 can be executed. Among them, the mounting information refers to information such as the identifier of the mounted file, the data source, and the configuration parameters.

[0116] For example, if the target container group is pod-1, and it is monitored that in the mounted file list, the identifier Mount1 of the mounted file 1 is deleted and the identifier Mount3 of the mounted file 3 is added, it can be determined that the mounted file list is updated, and it can be determined whether there is a mounted configuration file 1 corresponding to pod-1 in the server. If not, step S303 can be executed; if so, step S304 can be executed.

[0117] S303. Generate a mounted configuration file according to the updated mounted file list.

[0118] Since there is no existing mounted configuration file corresponding to the target container group in the server, a mounted configuration file can be generated according to the updated mounted file list. The mounted configuration file can include the file identifiers in the updated mounted file list.

[0119] For example, if the updated mounted file list includes the identifier Mount2 of the mounted file 2 and the identifier Mount3 of the mounted file 3, a mounted configuration file 1 can be generated according to the updated mounted file list, and the mounted configuration file 1 can include the identifier Mount2 of the mounted file 2 and the identifier Mount3 of the mounted file 3.

[0120] S304. Update the existing mounted configuration file according to the updated mounted file list to obtain a mounted configuration file.

[0121] If there is an existing mounted configuration file corresponding to the target container group in the server, the existing mounted configuration file can be updated according to the updated mounted file list to obtain a mounted configuration file.

[0122] For example, if the updated list of mounted files includes the identifier Mount2 of mounted file 2 and the identifier Mount3 of mounted file 3, and the existing mounted configuration file includes the identifier Mount1 of mounted file 1 and the identifier Mount2 of mounted file 2, then the existing mounted configuration file can be updated according to the updated list of mounted files, that is, the identifier Mount1 of mounted file 1 is deleted from the existing mounted configuration file, and the identifier Mount3 of mounted file 3 is added, to obtain mounted configuration file 1, which may include the identifier Mount2 of mounted file 2 and the identifier Mount3 of mounted file 3.

[0123] S305. Monitor the mounted configuration file corresponding to the target container group.

[0124] Optionally, the mounted configuration file corresponding to the target container group can be monitored through a file container. For example, if the target container group 1 is pod-1 and the corresponding mounted configuration file is mounted configuration file 1, then the mounted configuration file 1 corresponding to pod-1 can be monitored through the file container.

[0125] S306. It is monitored that the mounted configuration file corresponding to the target container group is generated, or it is monitored that the mounted configuration file corresponding to the target container group is updated.

[0126] Optionally, the mounted configuration file includes a resource identity document (ID), and after the mounted configuration file is updated, the resource ID is also updated.

[0127] If the mounted configuration file corresponding to the target container group is just generated, then it can be monitored through the file container that the mounted configuration file corresponding to the target container group is generated; if it is monitored that the resource ID in the mounted configuration file is updated, then it can be determined that the mounted configuration file corresponding to the target container group is updated.

[0128] S307. Determine the identifiers of multiple current mounted files corresponding to the target container group.

[0129] Optionally, the identifiers of multiple current mounted files can be determined in the file container, that is, the identifiers of multiple current mounted files corresponding to the target container group are determined.

[0130] For example, if the target container group is pod-1, the identifiers of multiple current mounted files corresponding to pod-1 can be determined in the file container, assuming they include the identifier Mount1 of mounted file 1 and the identifier Mount2 of mounted file 2.

[0131] S308. Determine the identifier of the file to be mounted and / or the identifier of the file to be unmounted according to the identifiers of multiple target mounted files and the identifiers of multiple current mounted files.

[0132] The identifiers of multiple target mounted files can be determined in the mounting configuration file, and then, based on the identifiers of the multiple target mounted files and the identifiers of the multiple current mounted files, the identifier of the file to be mounted and / or the identifier of the file to be unmounted can be determined.

[0133] For example, if the identifiers of the multiple target mounted files include the identifier Mount2 of mounted file 2 and the identifier Mount3 of mounted file 3, and the identifiers of the multiple current mounted files include the identifier Mount1 of mounted file 1 and the identifier Mount2 of mounted file 2, then the identifier of the file to be mounted can be determined as Mount3, and the identifier of the file to be unmounted can be determined as Mount1.

[0134] S309. Update the mounted files of the target container group in the file container according to the identifier of the file to be mounted and / or the identifier of the file to be unmounted.

[0135] In an optional embodiment, the mounted files of the target container group can be updated in the file container according to the identifier of the file to be mounted and / or the identifier of the file to be unmounted in the following manner: create the file to be mounted in the file container according to the identifier of the file to be mounted; delete the file to be unmounted in the file container according to the identifier of the file to be unmounted.

[0136] For example, if the identifier of the file to be mounted is Mount3 and the identifier of the file to be unmounted is Mount1, then the file to be mounted can be created in the file container according to the identifier Mount3 of the file to be mounted, that is, the mounted file 3 corresponding to Mount3; the file to be unmounted can be deleted in the file container according to the identifier Mount1 of the file to be unmounted, that is, the mounted file 1 corresponding to Mount1, so as to update the mounted files of the target container group.

[0137] Both the target container group and the file container can be deployed on the server. The target container group corresponds to a first file, the first file is in the server, the file container includes a second file, and the server includes a third file.

[0138] The first file can be the file corresponding to the target container group. For example, the first file can be the / var / lib / kubelet / … / mount / file.

[0139] The second file can be the root file corresponding to the multiple mounted files. For example, the second file can be the Mount-Point file.

[0140] The third file can be the file on the server. For example, the third file can be the / runtime-mnt / … / thin-fuse file.

[0141] Optionally, after creating the files to be mounted and / or deleting the files to be unmounted in the file container, the mounted files in the file container can be synchronously mounted to the target container group to update the mounted files of the target container group in the file container.

[0142] Optionally, synchronously mounting the mounted files in the file container to the target container group can include the following three methods:

[0143] Method 1: Synchronously mount the mounted files of the target container group by means of a soft link according to the mounted files in the file container.

[0144] Figure 4A Schematic diagram of a mounting method provided for an exemplary embodiment of the present application. Please refer to Figure 4A , a file container and a target container group can be deployed in the server. The target container group can correspond to a first file, the first file is in the server, the file container includes a second file, and the server includes a third file.

[0145] The second file can be the root directory of at least one mounted file. The second file can include at least one mounted file corresponding to the target container group. For example, the second file can include two mounted files corresponding to the target container group, namely mounted file 2 and mounted file 3.

[0146] There is a soft link relationship between the first file and the third file, and the second file is mounted in the third file. The second file can be regarded as the root mount point and mounted in the third file. In the technical solution of the present application, by mounting the second file, at least one mounted file in the second file can be mounted. Compared with PVC which only supports one mount point, it can not only support multiple mount points, but also maintain the consistency of the PVC definition.

[0147] Optionally, through a Container Storage Interface (CSI) plugin, the third file can be linked to the first file by means of a soft link (symlink), so that there is a soft link relationship between the first file and the third file. The soft link relationship can be used for the target container group to access at least one mounted file of the target container group through the first file, the third file and the second file. There can be multiple mount file identifiers in the target container group.

[0148] For example, the target container group can access the first file / var / lib / kubelet / … / mount / , and based on the first file, access the third file / runtime-mnt / … / thin-fuse. Furthermore, based on the third file, it can access the second file Mount-Point, and then access the mount file 2 corresponding to Mount2 and the mount file 3 corresponding to Mount3 under the second file. In the target container group, there can be an identifier Mount2 corresponding to the mount file 2 and an identifier Mount3 corresponding to the mount file 3.

[0149] In Method 1, there is no need to introduce additional FUSE device overhead, and when deleting the target container group, only the soft link needs to be cancelled, which will not affect the mount files in the file container.

[0150] Method 2: Synchronously mount the mount files of the target container group by means of a bind mount based on the mount files in the file container.

[0151] Figure 4B Schematic diagram of another mounting method provided by an exemplary embodiment of the present application. Please refer to Figure 4B , a file container and a target container group can be deployed in the server. The target container group can correspond to a first file, the first file is in the server, the file container can include a second file and a fourth file, and the server can include a third file. Among them, the fourth file can be the / mnt file.

[0152] The fourth file can be the root directory of at least one mount file. The fourth file includes at least one mount file corresponding to the target container group. For example, the fourth file can include 2 mount files corresponding to the target container group, namely mount file 2 and mount file 3.

[0153] The fourth file can be mounted in the second file. The second file can be a view of the fourth file. There is a binding relationship between the first file and the third file, and the second file is mounted in the third file.

[0154] Optionally, through the CSI plugin, the third file can be bind-mounted to the first file, so that there is a binding relationship between the first file and the third file. The binding relationship can be used for the target container group to access at least one mount file of the target container group through the first file, the third file, the second file, and the fourth file.

[0155] For example, the target container group can access the first file / var / lib / kubelet / … / mount / , access the third file / runtime-mnt / … / thin-fuse based on the first file, then access the second file Mount-Point based on the third file, then access the fourth file / mnt based on the second file, and finally access the mount file 2 corresponding to Mount2 and the mount file 3 corresponding to Mount3 under the fourth file. In the target container group, there can be an identifier Mount2 corresponding to the mount file 2 and an identifier Mount3 corresponding to the mount file 3.

[0156] In Method 2, the second file can be kept as a Fuse file system, and the existing CSI mounting logic can be reused.

[0157] Method 3: Synchronously mount the mount files of the target container group in a bind mount manner according to the mount files in the file container.

[0158] Figure 4C It is a schematic diagram of another mounting method provided by the exemplary embodiment of the present application. Please refer to Figure 4C , a file container and a target container group can be deployed in the server. The target container group can correspond to a first file, the first file is in the server, the file container includes a second file, and the server includes a third file.

[0159] The second file includes at least one mount file corresponding to the target container group.

[0160] There is a recursive binding relationship between the first file and the third file, and the second file is mounted in the third file. The second file can be regarded as the root mount point and mounted in the third file. In the technical solution of the present application, by mounting the second file, it is possible to mount at least one mount file in the second file. Compared with PVC that only supports one mount point, it can not only support multiple mount points, but also maintain the consistency of the PVC definition.

[0161] Optionally, through the CSI plugin, the third file can be recursively bound (recursive bind Mount) to the first file, so that there is a recursive binding relationship between the first file and the third file. The recursive binding relationship can be used for the target container group to recursively access at least one mount file of the target container group through the first file, the third file, and the second file.

[0162] For example, the target container group can access the first file / var / lib / kubelet / … / mount / , and access the third file / runtime-mnt / … / thin-fuse based on the first file. Furthermore, it can access the second file Mount-Point based on the third file, and then access the mount file 2 corresponding to Mount2 and the mount file 3 corresponding to Mount3 under the second file. In the target container group, there can be an identifier Mount2 corresponding to the mount file 2 and an identifier Mount3 corresponding to the mount file 3.

[0163] In Method 3, there is no need to introduce an additional FUSE, and the performance is good.

[0164] Through the above three methods, the mount files in the file container and the mount files of the target container group can have a mapping relationship and be kept consistent.

[0165] In the technical solution of this application, by listening to the mount file list through a third-party component, changes in the mount files can be detected in a timely manner, and multiple mount files of the target container group can be updated quickly, ensuring timeliness; and it can be extended to different file systems; and without adding a new PVC object, it can support multiple mount files.

[0166] In the embodiment of this application, the server can listen to the mount file list through a third-party component. When it is detected that the mount file list is updated, it is judged whether there is an existing mount configuration file corresponding to the target container group. If not, a mount configuration file can be generated according to the updated mount file list; if so, the existing mount configuration file can be updated according to the updated mount file list to obtain the mount configuration file. The server can listen to the mount configuration file corresponding to the target container group. When it is detected that the mount configuration file corresponding to the target container group is generated, or when it is detected that the mount configuration file corresponding to the target container group is updated, the identifiers of multiple current mount files corresponding to the target container group can be determined. The server can determine the identifier of the file to be mounted and / or the identifier of the file to be unmounted according to the identifiers of multiple target mount files and the identifiers of multiple current mount files, and update the mount files of the target container group in the file container according to the identifier of the file to be mounted and / or the identifier of the file to be unmounted. Since multiple mount files of the target container group can be updated in the file container and then the multiple mount files are synchronously mounted to the target container group, updating multiple mount files in the file container is equivalent to updating multiple mount files of the target container group, and the operation of the target container group does not need to be interrupted to mount the files; and the second file can be regarded as the root directory of multiple mount files, and by mounting the second file, multiple mount files can be dynamically mounted. Compared with the prior art where PVC only supports mounting one mount file, the mounting efficiency is improved.

[0167] Next, based on any of the above embodiments, in combination with Figure 5 , the above file system mounting method will be described in detail.

[0168] Figure 5 It is a schematic process diagram of a file system mounting method provided by an exemplary embodiment of the present application. Please refer to Figure 5 , including steps ①②③④⑤.

[0169] In step ①, the mounted file list can be updated. The mounted file list before the update may include the identifier Mount1 of the mounted file 1, the identifier Mount2 of the mounted file 2, and the relevant mounting information of the mounted file 1 and the mounted file 2. The mounted file list after the update may include the identifier Mount2 of the mounted file 2, the identifier Mount3 of the mounted file 3, and the relevant mounting information of the mounted file 2 and the mounted file 3.

[0170] In step ②, the mounted file list can be monitored through a third-party component.

[0171] In step ③, when it is monitored that the mounted file list has been updated, it is judged whether there is an existing mounting configuration file corresponding to the target container group. If not, a mounting configuration file can be generated according to the updated mounted file list; if so, the existing mounting configuration file can be updated according to the updated mounted file list to obtain the mounting configuration file. For example, the mounting configuration file 1 may include the identifier Mount2 of the mounted file 2 and the identifier Mount3 of the mounted file 3.

[0172] In step ④, the mounting configuration file corresponding to the target container group can be monitored through a file container. When it is monitored that the mounting configuration file corresponding to the target container group is generated, or when it is monitored that the mounting configuration file corresponding to the target container group has been updated, a script can be executed to perform mounting / unmounting in the file container according to the mounting configuration file.

[0173] Specifically, the identifiers of multiple currently mounted files can be determined in the file container, including the identifier Mount1 of the mounted file 1 and the identifier Mount2 of the mounted file 2. The identifiers of multiple target mounted files can be determined in the mounting configuration file, including the identifier Mount2 of the mounted file 2 and the identifier Mount3 of the mounted file 3. Therefore, based on the identifiers of the 2 target mounted files and the identifiers of the 2 currently mounted files, the identifier of the file to be mounted can be determined as Mount3, and the identifier of the file to be unmounted can be determined as Mount1. Then, based on the identifier Mount3 of the file to be mounted, the file to be mounted can be created in the file container, that is, the mounted file 3 corresponding to Mount3. The file to be unmounted can be deleted in the file container based on the identifier Mount1 of the file to be unmounted, that is, the mounted file 1 corresponding to Mount1, so that the multiple mounted files in the file container are updated to the mounted file 2 and the mounted file 3.

[0174] The second file in the file container can be mounted in the third file in the server. The second file can include at least one mounted file corresponding to the target container group, regarded as the root directory of the at least one mounted file.

[0175] In step ⑤, through the CSI plugin, the third file can be mounted to the first file in any one of the soft link method, the bind mount method, or the recursive mount method, so that the target container group can access the mounted file 2 and the mounted file 3 through the third file and the second file. There is a mapping relationship between the files corresponding to the target container group and the files in the file container.

[0176] Optionally, the third file can also be unmounted from the first file in any one of the soft link method, the bind mount method, or the recursive mount method.

[0177] In an embodiment of the present application, the server can monitor the mounted file list through a third-party component. When it is detected that the mounted file list is updated, it is determined whether there is an existing mounted configuration file corresponding to the target container group. If not, a mounted configuration file can be generated according to the updated mounted file list; if so, the existing mounted configuration file can be updated according to the updated mounted file list to obtain the mounted configuration file. The server can monitor the mounted configuration file corresponding to the target container group. When it is detected that the mounted configuration file corresponding to the target container group is generated, or when it is detected that the mounted configuration file corresponding to the target container group is updated, the identifiers of multiple current mounted files corresponding to the target container group can be determined. The server can determine the identifier of the file to be mounted and / or the identifier of the file to be unmounted according to the identifiers of multiple target mounted files and the identifiers of multiple current mounted files, and update the mounted files of the target container group in the file container according to the identifier of the file to be mounted and / or the identifier of the file to be unmounted, and synchronously mount them to the target container group. Since multiple mounted files of the target container group can be updated in the file container and then synchronously mounted to the target container group, updating multiple mounted files in the file container is to update multiple mounted files of the target container group. Without interrupting the operation of the target container group, files can be mounted; and the second file can be regarded as the root directory of multiple mounted files, and by mounting the second file, multiple mounted files can be dynamically mounted, which improves the mounting efficiency compared with the prior art where PVC only supports mounting one mounted file.

[0178] Figure 6 The following is a schematic structural diagram of a file system mounting device provided by an exemplary embodiment of the present application. Please refer to Figure 6 , the file system mounting device 10 includes: a response module 11, a determination module 12, and an update module 13, where

[0179] The response module 11 is configured to determine the mounted configuration file corresponding to the target container group in response to an update operation performed on the mounted file list of the target container group, and the mounted configuration file includes identifiers of multiple target mounted files;

[0180] The determination module 12 is configured to determine the identifiers of multiple current mounted files corresponding to the target container group;

[0181] The update module 13 is configured to update the mounted files of the target container group in the file container corresponding to the target container group according to the identifiers of the multiple target mounted files and the identifiers of the multiple current mounted files, and the file corresponding to the target container group has a mapping relationship with the files in the file container.

[0182] The file system mounting device provided by the embodiments of the present application can execute the technical solutions shown in the above method embodiments. The implementation principles and beneficial effects are similar and will not be elaborated here.

[0183] In a possible implementation manner, the updating module 13 is specifically configured to:

[0184] Determine the identifier of the file to be mounted and / or the identifier of the file to be unmounted according to the identifiers of the multiple target mounted files and the identifiers of the multiple current mounted files;

[0185] Update the mounted files of the target container group in the file container according to the identifier of the file to be mounted and / or the identifier of the file to be unmounted.

[0186] In a possible implementation manner, the updating module 13 is specifically configured to:

[0187] Create the file to be mounted in the file container according to the identifier of the file to be mounted;

[0188] Delete the file to be unmounted in the file container according to the identifier of the file to be unmounted.

[0189] In a possible implementation manner, the response module 11 is specifically configured to:

[0190] Monitor the mounted file list through a third-party component, where the mounted file list includes multiple file identifiers;

[0191] When it is monitored that the mounted file list is updated, determine whether there is an existing mounted configuration file corresponding to the target container group;

[0192] If there is no existing mounted configuration file corresponding to the target container group, generate the mounted configuration file according to the updated mounted file list;

[0193] If there is an existing mounted configuration file corresponding to the target container group, update the existing mounted configuration file according to the updated mounted file list to obtain the mounted configuration file, where the mounted configuration file includes the file identifiers in the updated mounted file list.

[0194] The file system mounting device provided by the embodiments of the present application can execute the technical solutions shown in the above method embodiments. The implementation principles and beneficial effects are similar and will not be elaborated here.

[0195] Figure 7 It is a schematic structural diagram of another file system mounting device provided by an exemplary embodiment of the present application. Please refer to Figure 7 , in Figure 6Based on the illustrated embodiment, the file system mounting device 10 further includes: a monitoring module 14,

[0196] The monitoring module 14 is configured to:

[0197] Monitor the mounting configuration file corresponding to the target container group;

[0198] When it is monitored that the mounting configuration file corresponding to the target container group is generated, or when it is monitored that the mounting configuration file corresponding to the target container group is updated.

[0199] In a possible implementation manner, the target container group and the file container are deployed on a server; the target container group corresponds to a first file, the file container includes a second file, and the server includes a third file; wherein,

[0200] The second file includes at least one mounting file corresponding to the target container group;

[0201] There is a soft link relationship between the first file and the third file, the second file is mounted in the third file, and the soft link relationship is used for the target container group to access the at least one mounting file of the target container group through the first file, the third file, and the second file.

[0202] In a possible implementation manner, the target container group and the file container are deployed on a server; the target container group corresponds to a first file, the file container includes a second file and a fourth file, and the server includes a third file; wherein,

[0203] The fourth file includes at least one mounting file corresponding to the target container group;

[0204] The fourth file is mounted in the second file;

[0205] There is a binding relationship between the first file and the third file, the second file is mounted in the third file, and the binding relationship is used for the target container group to access the at least one mounting file of the target container group through the first file, the third file, the second file, and the fourth file.

[0206] In a possible implementation manner, the target container group and the file container are deployed on a server; the target container group corresponds to a first file, the file container includes a second file, and the server includes a third file; wherein,

[0207] The second file includes at least one mounting file corresponding to the target container group;

[0208] There is a recursive binding relationship between the first file and the third file, the second file is mounted in the third file, and the recursive binding relationship is used for the target container group to recursively access the at least one mounted file of the target container group through the first file, the third file, and the second file.

[0209] The file system mounting device provided by the embodiments of the present application can execute the technical solutions shown in the above method embodiments, and its implementation principle and beneficial effects are similar, which will not be elaborated here.

[0210] An exemplary embodiment of the present application provides a schematic structural diagram of a server. Please refer to Figure 8 , the server 20 may include a processor 21 and a memory 22. Exemplarily, the processor 21 and the memory 22 are interconnected with each other through a bus 23.

[0211] The memory 22 stores computer execution instructions;

[0212] The processor 21 executes the computer execution instructions stored in the memory 22, so that the processor 21 executes the method shown in the above method embodiments.

[0213] Figure 8 The server shown in

[0214] Correspondingly, an embodiment of the present application provides a computer-readable storage medium, in which computer execution instructions are stored, and when the computer execution instructions are executed by a processor, they are used to implement the method described in the above method embodiments.

[0215] Correspondingly, an embodiment of the present application may also provide a computer program product, including a computer program, which when executed by a processor, can implement the method shown in the above method embodiments.

[0216] Those skilled in the art should understand that the embodiments of the present invention can be provided as a method, a system, or a computer program product. Therefore, the present invention can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable program codes.

[0217] The present invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each flow and / or block in the flowchart illustrations and / or block diagrams, and combinations of flows and / or blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processors of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions executed by the processors of the computer or other programmable data processing device create means for implementing the functions specified in the flowchart Figure 1 one or more flows and / or blocks Figure 1 or means for implementing the functions specified in one or more boxes or blocks.

[0218] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable memory produce a manufacture including instruction means that implement the functions specified in the flowchart Figure 1 one or more flows and / or blocks Figure 1 or one or more boxes or blocks.

[0219] These computer program instructions may also be loaded onto a computer or other programmable data processing device, such that a series of operational steps are performed on the computer or other programmable device to produce a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in the flowchart Figure 1 one or more flows and / or blocks Figure 1 or one or more boxes or blocks.

[0220] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0221] The memory may include non-permanent memory in the form of computer-readable media, random access memory (RAM), and / or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). The memory is an example of computer-readable media.

[0222] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0223] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0224] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A file system mounting method, characterized in that, Including: In response to an update operation performed on the list of mounted files of a target container group, determining a mounted configuration file corresponding to the target container group, where the mounted configuration file includes identifiers of multiple target mounted files; Determining identifiers of multiple current mounted files corresponding to the target container group; According to the identifiers of the multiple target mounted files and the identifiers of the multiple current mounted files, updating the mounted files of the target container group in a file container corresponding to the target container group, where the file corresponding to the target container group has a mapping relationship with the files in the file container.

2. The method according to claim 1, characterized in that, According to the identifiers of the multiple target mounted files and the identifiers of the multiple current mounted files, updating the mounted files of the target container group in a file container corresponding to the target container group includes: Determining identifiers of files to be mounted and / or identifiers of files to be unmounted according to the identifiers of the multiple target mounted files and the identifiers of the multiple current mounted files; Updating the mounted files of the target container group in the file container according to the identifiers of the files to be mounted and / or the identifiers of the files to be unmounted.

3. The method according to claim 2, wherein Updating the mounted files of the target container group in the file container according to the identifiers of the files to be mounted and / or the identifiers of the files to be unmounted includes at least one of the following: Creating the file to be mounted in the file container according to the identifier of the file to be mounted; Deleting the file to be unmounted in the file container according to the identifier of the file to be unmounted.

4. The method according to any one of claims 1 to 3, characterized in that, In response to an update operation performed on the list of mounted files of a target container group, determining a mounted configuration file corresponding to the target container group includes: Listening to the list of mounted files through a third-party component, where the list of mounted files includes multiple file identifiers; When it is monitored that the list of mounted files is updated, determining whether there is an existing mounted configuration file corresponding to the target container group; If there is no existing mounted configuration file corresponding to the target container group, generating the mounted configuration file according to the updated list of mounted files; If there is an existing mounted configuration file corresponding to the target container group, updating the existing mounted configuration file according to the updated list of mounted files to obtain the mounted configuration file, where the mounted configuration file includes the file identifiers in the updated list of mounted files.

5. The method according to any one of claims 1-4, characterized in that, Before determining the identifiers of multiple current mounted files corresponding to the target container group, it includes: Listening to the mounted configuration file corresponding to the target container group; It is monitored that the mounted configuration file corresponding to the target container group is generated, or it is monitored that the mounted configuration file corresponding to the target container group is updated.

6. The method according to any one of claims 1-5, characterized in that, The target container group and the file container are deployed on a server; the target container group corresponds to a first file, the file container includes a second file, and the server includes a third file; where The second file includes at least one mounted file corresponding to the target container group; There is a soft link relationship between the first file and the third file, and the second file is mounted in the third file. The soft link relationship is used for the target container group to access at least one mounted file of the target container group through the first file, the third file, and the second file.

7. The method according to any one of claims 1-5, characterized in that, The target container group and the file container are deployed on a server; the target container group corresponds to a first file, the file container includes a second file and a fourth file, and the server includes a third file; wherein, The fourth file includes at least one mounted file corresponding to the target container group; The fourth file is mounted in the second file; There is a binding relationship between the first file and the third file, and the second file is mounted in the third file. The binding relationship is used for the target container group to access at least one mounted file of the target container group through the first file, the third file, the second file, and the fourth file.

8. The method according to any one of claims 1-5, characterized in that, The target container group and the file container are deployed on a server; the target container group corresponds to a first file, the file container includes a second file, and the server includes a third file; wherein, The second file includes at least one mounted file corresponding to the target container group; There is a recursive binding relationship between the first file and the third file, and the second file is mounted in the third file. The recursive binding relationship is used for the target container group to recursively access at least one mounted file of the target container group through the first file, the third file, and the second file.

9. A file system mounting device, characterized in that Including: A response module, a determination module, and an update module, wherein, The response module is configured to, in response to an update operation performed on the mounted file list of the target container group, determine the mounted configuration file corresponding to the target container group, and the mounted configuration file includes identifiers of multiple target mounted files; The determination module is configured to determine identifiers of multiple currently mounted files corresponding to the target container group; The update module is configured to update the mounted files of the target container group in the file container corresponding to the target container group according to the identifiers of the multiple target mounted files and the identifiers of the multiple currently mounted files. There is a mapping relationship between the file corresponding to the target container group and the files in the file container.

10. A server, characterized in that, Including: At least one processor; And A memory communicatively connected to the at least one processor; Wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to cause the server to execute the method according to any one of claims 1-8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, and when the processor executes the computer-executable instructions, the method according to any one of claims 1-8 is implemented.

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, the method according to any one of claims 1-8 is implemented.

Images