Method and apparatus for configuring a network file system

Abstract

The application discloses a method and device for configuring a network file system, and relates to the technical field of computers. The method comprises the following steps: configuring a plurality of network file systems for any storage class in a container deployment system; creating a persistent storage volume declaration pointing to the storage class; determining a target network file system from the plurality of network file systems based on a determination strategy of the network file system; and creating a container package in the container deployment system based on the persistent storage volume declaration and the target network file system, wherein the container package comprises at least one container. The method can realize that one storage class corresponds to a plurality of network file systems, improve the performance of the container deployment platform, and reduce the maintenance cost.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more particularly to methods and apparatus for configuring network file systems. Background Technology

[0002] Configuring a containerized storage backend enables effective management of storage devices or stored data. Typically, when configuring NFS (Network File System), only one NFS storage is configured per Storage class. When multiple NFS storages are needed, multiple Storage classes are required, which can lead to poor system performance and high system maintenance costs. Summary of the Invention

[0003] This disclosure provides a method, apparatus, electronic device, and computer-readable storage medium for configuring a network file system.

[0004] According to a first aspect of this disclosure, a method for configuring a network file system is provided, comprising: configuring multiple network file systems for any storage class in a containerized deployment system; creating a persistent storage volume declaration pointing to the storage class; determining a target network file system from the multiple network file systems based on a network file system determination strategy; and creating a container wrapper in the containerized deployment system based on the persistent storage volume declaration and the target network file system, wherein the container wrapper includes at least one container.

[0005] In some embodiments, after configuring multiple network file systems, the method for configuring network file systems further includes: determining the weight of each network file system in the multiple network file systems; and determining a target network file system from the multiple network file systems based on a network file system determination strategy, including: determining the target network file system from the multiple network file systems based on the weight of each network file system.

[0006] In some embodiments, the weights include probability weights. Determining a target network file system from multiple network file systems based on the weight of each network file system includes: using the probability weight of each network file system as the probability of selecting that network file system; and determining the target network file system based on the probability of selecting each network file system.

[0007] In some embodiments, determining a target network file system from multiple network file systems based on a network file system determination strategy includes: in response to detecting that a persistent storage volume declaration has been created, determining the target network file system from multiple network file systems based on a network file system determination strategy.

[0008] In some embodiments, a container wrapper is created in a containerized deployment system based on a persistent storage volume declaration and a target network file system, including: creating a persistent volume based on the target network file system, binding the persistent volume to the persistent storage volume declaration; and creating a container wrapper for binding the persistent storage volume declaration.

[0009] According to a second aspect of this disclosure, an apparatus for configuring a network file system is provided, comprising: a configuration unit configured to configure multiple network file systems for any storage class in a containerized deployment system; a creation unit configured to create a persistent storage volume declaration pointing to the storage class; a determination unit configured to determine a target network file system from the multiple network file systems based on a determination strategy for the network file system; and a deployment unit configured to create a container package in the containerized deployment system based on the persistent storage volume declaration and the target network file system, wherein the container package includes at least one container.

[0010] In some embodiments, the configuration unit further includes: a first determining module for determining the weight of each of the plurality of network file systems; and a determining unit including: a second determining module configured to determine a target network file system from the plurality of network file systems based on the weight of each network file system.

[0011] In some embodiments, the weights include probability weights, and the determining unit includes: a third determining module configured to use the probability weight of each network file system as the probability of selecting that network file system; and a fourth determining module configured to determine the target network file system based on the probability of selecting each network file system.

[0012] In some embodiments, the determining unit includes a fifth determining module configured to, in response to detecting that a persistent storage volume declaration has been created, determine a target network file system from a plurality of network file systems based on a network file system determination strategy.

[0013] In some embodiments, the deployment unit includes: a binding module configured to create a persistent volume based on a target network file, the persistent volume being bound to a persistent storage volume declaration; and a deployment module configured to create a container wrapper for binding the persistent storage volume declaration.

[0014] According to a third aspect of this disclosure, embodiments of this disclosure provide an electronic device including: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method for configuring a network file system as provided in the first aspect.

[0015] According to a fourth aspect of this disclosure, embodiments of this disclosure provide a computer-readable storage medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the method for configuring a network file system as provided in the first aspect.

[0016] The method and apparatus for configuring network file systems provided in this disclosure include: configuring multiple network file systems for any storage class in a containerized deployment system; creating a persistent storage volume declaration pointing to the storage class; determining a target network file system from multiple network file systems based on a network file system determination strategy; and creating a container encapsulation in the containerized deployment system based on the persistent storage volume declaration and the target network file system, wherein the container encapsulation includes at least one container, which can realize that one storage class corresponds to multiple network file systems, thereby improving the performance of the containerized deployment platform and reducing maintenance costs.

[0017] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0018] The accompanying drawings are provided for a better understanding of this solution and do not constitute a limitation of this application. Wherein:

[0019] Figure 1 This is an exemplary system architecture diagram in which embodiments of this application can be applied;

[0020] Figure 2 This is a flowchart of one embodiment of the method for configuring a network file system according to this application;

[0021] Figure 3 This is a flowchart of another embodiment of the method for configuring a network file system according to this application;

[0022] Figure 4 This is a schematic diagram of a containerized deployment system architecture in an application scenario of the method for configuring a network file system according to this application;

[0023] Figure 5 This is a schematic diagram of one embodiment of an apparatus for configuring a network file system according to the present application;

[0024] Figure 6 This is a block diagram of an electronic device used to implement the method for configuring a network file system according to the embodiments of this application. Detailed Implementation

[0025] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of this application, including various details to aid understanding. These should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this application. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0026] Figure 1 An exemplary system architecture 100 is shown, in which embodiments of the method or apparatus for configuring a network file system of this application may be applied.

[0027] like Figure 1 As shown, system architecture 100 may include terminal devices 101, 102, and 103, a network 104, and a server 105. Network 104 serves as the medium for providing communication links between terminal devices 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0028] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Terminal devices 101, 102, and 103 can be user terminal devices, on which various client applications can be installed, such as data maintenance applications, image applications, video applications, search applications, financial applications, etc.

[0029] Terminal devices 101, 102, and 103 can be various electronic devices with displays that support receiving messages from the server, including but not limited to smartphones, tablets, e-book readers, electronic players, laptops, and desktop computers.

[0030] Terminal devices 101, 102, and 103 can be either hardware or software. When terminal devices 101, 102, and 103 are hardware, they can be various electronic devices. When terminal devices 101, 102, and 103 are software, they can be installed in the electronic devices listed above. They can be implemented as multiple software programs or software modules (e.g., multiple software modules used to provide distributed services) or as a single software program or software module. No specific limitations are made here.

[0031] Server 105 can configure multiple network file systems for any storage class in the containerized deployment system, create persistent storage volume declarations pointing to the storage class, determine the target network file system from multiple network file systems based on the network file system determination strategy, and then create a container package in the containerized deployment system based on the persistent storage volume declaration and the target network file system, wherein the container package includes at least one container.

[0032] It should be noted that the method for configuring a network file system provided in the embodiments of this disclosure can be executed by the server 105, and correspondingly, the apparatus for configuring a network file system can be located in the server 105.

[0033] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0034] Continue to refer to Figure 2 The flowchart 200, illustrating an embodiment of a method for configuring a network file system according to the present disclosure, includes the following steps:

[0035] Step 201: Configure multiple network file systems for any storage class in the containerized deployment system.

[0036] In this embodiment, the execution body of the method for configuring the network file system (e.g.) Figure 1 The server shown can be configured with multiple Network File System (NFS) configurations for a storage class in a containerized deployment system, so that a storage class can mount multiple NFS configurations.

[0037] Step 202: Create a persistent storage volume declaration that points to the storage class.

[0038] In this embodiment, a persistent volume claim (PVC) pointing to the storage class can be created, which is used to represent the user's request for storage.

[0039] Step 203: Based on the determination strategy of the network file system, determine the target network file system from multiple network file systems.

[0040] In this embodiment, a target network file system can be determined from multiple network file systems corresponding to the storage class based on a network file system determination strategy. This strategy can be based on the load of each network file system, or on the read / write frequency or number of read / write operations of each network file system, to optimize the storage performance of the entire storage system.

[0041] Step 204: Based on the persistent storage volume declaration and the target network file system, create a container package in the containerized deployment system, wherein the container package includes at least one container.

[0042] In this embodiment, a container pod can be created in the containerized deployment system based on a persistent storage volume declaration and a target network file system. The container pod includes at least one container for deploying an application or program. The container pod can be the smallest execution unit in a Kubernetes (K8S, a system for managing containerized applications on multiple hosts in a cloud platform) cluster.

[0043] The method for configuring network file systems provided in this embodiment configures multiple network file systems for any storage class in a containerized deployment system, creates a persistent storage volume declaration pointing to the storage class, determines the target network file system from multiple network file systems based on the network file system determination strategy, and then creates a container encapsulation in the containerized deployment system based on the persistent storage volume declaration and the target network file system. The container encapsulation includes at least one container. Multiple network file systems can be configured for one storage class. After determining the target network file system based on the network file system determination strategy, the container encapsulation containing the container is created using the target network file system. This can realize multiple network file systems corresponding to one storage class, improve the performance of the containerized deployment platform and reduce maintenance costs.

[0044] Continue to refer to Figure 3 The following is a flow 300 illustrating another embodiment of a method for configuring a network file system according to the present disclosure, comprising the following steps:

[0045] Step 301: Configure multiple network file systems for any storage class in the containerized deployment system, and determine the weight of each network file system among the multiple network file systems.

[0046] In this embodiment, the execution body of the method for configuring the network file system (e.g.) Figure 1The server shown can be configured with multiple network file systems for a storage class in a containerized deployment system, so that a storage class can mount multiple network file systems, and a weight can be configured for each network file system. This weight is used to indicate the probability of using a particular network file system when the containerized deployment system selects a network file system to create a container package.

[0047] Step 302: Create a persistent storage volume declaration that points to the storage class.

[0048] Step 303: Based on the weight of each network file system, determine the target network file system from multiple network file systems.

[0049] In this embodiment, the target network file system can be determined from multiple network file systems based on the weight of each network file system. For example, different network file systems can be selected in turn as the target network file system each time the target network file system needs to be determined, according to the weight of each network file system.

[0050] Step 304: Based on the persistent storage volume declaration and the target network file system, create a container package in the containerized deployment system, wherein the container package includes at least one container.

[0051] In this embodiment, the descriptions of steps 302 and 304 are consistent with those of steps 202 and 204, and will not be repeated here.

[0052] The method for configuring a network file system provided in this embodiment is compared to... Figure 2 The described embodiment configures multiple network file systems for the storage class, as well as the weight of each network file system, and specifically defines the network file system determination strategy as determining the target network file system based on the weight of each network file system, which can improve the efficiency and convenience of determining the target network file system.

[0053] Optionally, the weights include probability weights. Based on the weights of each network file system, the target network file system is determined from multiple network file systems, including: using the probability weight of each network file system as the probability of selecting that network file system; and determining the target network file system based on the probability of selecting each network file system.

[0054] In this embodiment, the weights include probability weights, and the probability weight of each network file system can be used as the probability of selecting that network file system, so that the target network file system can be determined based on the probability weights each time the target network file system is determined.

[0055] In the above combination Figure 2 and Figure 3In some optional implementations of the described embodiments, determining a target network file system from multiple network file systems based on a network file system determination strategy includes: in response to detecting that a persistent storage volume declaration has been created, determining the target network file system from multiple network file systems based on a network file system determination strategy.

[0056] In this embodiment, if the creation of a persistent storage volume declaration is detected to be complete, the target network file system can be determined from multiple network file systems based on the network file system determination strategy.

[0057] In the above combination Figure 2 and Figure 3 In some optional implementations of the described embodiments, creating a container wrapper in a containerized deployment system based on a persistent storage volume declaration and a target network file system includes: creating a persistent volume based on the target network file system, binding the persistent volume to the persistent storage volume declaration; and creating a container wrapper for binding the persistent storage volume declaration.

[0058] In this embodiment, a persistent volume (PV) can be created based on the target network file, and the persistent volume can be bound to the aforementioned persistent storage volume declaration to create a container encapsulation using the persistent storage volume declaration, thereby completing the setup of containerized deployment.

[0059] In some application scenarios, methods for configuring network file systems include:

[0060] Step 401: Create a storage class, configure multiple NFS storages, and set their weights (e.g., ...). Figure 4 The Kubernetes cluster shown includes nfs1, nfs2, and nfs3.

[0061] Step 402: Multiple subsequently created PVCs (such as PVC1, PVC2, PVC3, and PVC4) can all specify the same storage class, such as... Figure 4 As shown.

[0062] Step 403: After the PVC is created, when the CSI (Container Storage Interface) detects that the PVC has been created, it randomly selects an NFS storage according to the NFS storage weight configured in the storage class and creates a storage PV, and then binds the PVC to the created PV.

[0063] Step 404: Create a pod (e.g., pod1, pod2, pod3, pod4) that is bound to each PVC.

[0064] Further reference Figure 5 As an implementation of the methods shown in the above figures, this disclosure provides an embodiment of an apparatus for configuring a network file system, which is similar to... Figure 2 and Figure 3 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.

[0065] like Figure 5 As shown, the apparatus for configuring a network file system in this embodiment includes: a configuration unit 501, a creation unit 502, a determination unit 503, and a deployment unit 504. The configuration unit is configured to configure multiple network file systems for any storage class in a containerized deployment system; the creation unit is configured to create a persistent storage volume declaration pointing to the storage class; the determination unit is configured to determine a target network file system from the multiple network file systems based on a network file system determination strategy; and the deployment unit is configured to create a container package in the containerized deployment system based on the persistent storage volume declaration and the target network file system, wherein the container package includes at least one container.

[0066] In some embodiments, the configuration unit further includes: a first determining module for determining the weight of each of the plurality of network file systems; and a determining unit including: a second determining module configured to determine a target network file system from the plurality of network file systems based on the weight of each network file system.

[0067] In some embodiments, the weights include probability weights, and the determining unit includes: a third determining module configured to use the probability weight of each network file system as the probability of selecting that network file system; and a fourth determining module configured to determine the target network file system based on the probability of selecting each network file system.

[0068] In some embodiments, the determining unit includes a fifth determining module configured to, in response to detecting that a persistent storage volume declaration has been created, determine a target network file system from a plurality of network file systems based on a network file system determination strategy.

[0069] In some embodiments, the deployment unit includes: a binding module configured to create a persistent volume based on a target network file, the persistent volume being bound to a persistent storage volume declaration; and a deployment module configured to create a container wrapper for binding the persistent storage volume declaration.

[0070] Each unit in the aforementioned device 500 and the reference Figure 2 , Figure 3The steps described in the method correspond to those steps. Therefore, the operations, features, and technical effects described above for the method of configuring a network file system also apply to device 500 and the units contained therein, and will not be repeated here.

[0071] According to embodiments of this application, this application also provides an electronic device and a readable storage medium.

[0072] like Figure 6 The diagram shown is a block diagram of an electronic device 600 for configuring a network file system according to an embodiment of this application. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present application described and / or claimed herein.

[0073] like Figure 6 As shown, the electronic device includes one or more processors 601, a memory 602, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The components are interconnected via different buses and can be mounted on a common motherboard or otherwise as required. The processors can process instructions executed within the electronic device, including instructions stored in or on memory to display graphical information of a GUI on an external input / output device (such as a display device coupled to the interface). In other embodiments, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple electronic devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system). Figure 6 Take the 601 processor as an example.

[0074] The memory 602 is the non-transitory computer-readable storage medium provided in this application. This memory stores instructions executable by at least one processor to cause the at least one processor to perform the method for configuring a network file system provided in this application. The non-transitory computer-readable storage medium of this application stores computer instructions for causing a computer to perform the method for configuring a network file system provided in this application.

[0075] Memory 602, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs, non-transitory computer-executable programs, and modules, such as the program instructions / modules corresponding to the method for configuring a network file system in the embodiments of this application (e.g., appendix). Figure 6 The acquisition unit 601, distribution unit 602, first determination unit 603, second determination unit 604, and third determination unit 605 are shown. The processor 601 executes various functional applications and data processing of the server by running non-transient software programs, instructions, and modules stored in the memory 602, that is, it implements the method for configuring the network file system in the above method embodiments.

[0076] Memory 602 may include a program storage area and a data storage area. The program storage area may store an operating system and applications required for at least one function; the data storage area may store data created based on the use of the electronic device for extracting video clips. Furthermore, memory 602 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory 602 may optionally include memory remotely located relative to processor 601, and this remote memory may be connected to the electronic device for extracting video clips via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0077] The electronic device for configuring a network file system may further include an input device 603, an output device 604, and a bus 605. The processor 601, memory 602, input device 603, and output device 604 may be connected via the bus 605 or other means. Figure 6 Taking the connection between China and Israel via bus 605 as an example.

[0078] Input device 603 can receive input digital or character information, as well as generate key signal inputs related to user settings and function control of the electronic device used to extract video clips, such as touch screens, keypads, mice, trackpads, touchpads, joysticks, one or more mouse buttons, trackballs, joysticks, etc. Output device 604 may include display devices, auxiliary lighting devices (e.g., LEDs), and haptic feedback devices (e.g., vibration motors). The display device may include, but is not limited to, liquid crystal displays (LCDs), light-emitting diode (LED) displays, and plasma displays. In some embodiments, the display device may be a touch screen.

[0079] Various implementations of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, application-specific integrated circuits (ASICs), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include: implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transferring data and instructions to the storage system, the at least one input device, and the at least one output device.

[0080] These computational programs (also referred to as programs, software, software applications, or code) include machine instructions for a programmable processor and can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. As used herein, the terms “machine-readable medium” and “computer-readable medium” refer to any computer program product, device, and / or apparatus (e.g., disk, optical disk, memory, programmable logic device (PLD)) used to provide machine instructions and / or data to a programmable processor, including machine-readable media that receive machine instructions as machine-readable signals. The term “machine-readable signal” refers to any signal used to provide machine instructions and / or data to a programmable processor.

[0081] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0082] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0083] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other.

[0084] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this application can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this application can be achieved, and this is not limited herein.

[0085] The specific embodiments described above do not constitute a limitation on the scope of protection of this application. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A method for configuring a network file system, comprising: Configure multiple network file systems for any storage class in a containerized deployment system; Determine the weight of each of the plurality of network file systems, wherein the weight is used to indicate the probability of using a certain network file system when selecting a network file system to create a container package in a containerized deployment system; Create a persistent storage volume declaration pointing to the storage class; Based on a determination strategy for network file systems, a target network file system is determined from the plurality of network file systems, wherein the determination strategy includes at least one of the following: determining the target network file system based on the load of each network file system; determining the target network file system based on the read / write frequency and / or read / write count of each network file system; and determining the target network file system from the plurality of network file systems based on the weight of each network file system. Based on the persistent storage volume declaration and the target network file system, a container package is created in the containerized deployment system, wherein the container package includes at least one container.

2. The method according to claim 1, wherein, The weights include probability weights, and determining the target network file system from the plurality of network file systems based on the weights of each network file system includes: The probability weight of each network file system is used as the probability of selecting that network file system; The target network file system is determined based on the probability of selecting each of the network file systems.

3. The method according to claim 1, wherein, The determination strategy based on the network file system determines the target network file system from the plurality of network file systems, including: In response to the detection that the persistent storage volume declaration has been created, the target network file system is determined from the plurality of network file systems based on the network file system determination strategy.

4. The method according to claim 1, wherein, The step of creating a container wrapper in the containerized deployment system based on the persistent storage volume declaration and the target network file system includes: A persistent volume is created based on the target network file, and the persistent volume is bound to the persistent storage volume declaration; Create a container wrapper for binding the persistent storage volume declaration.

5. An apparatus for configuring a network file system, comprising: The configuration unit is configured to configure multiple network file systems for any storage class in a containerized deployment system; The first determining module determines the weight of each of the plurality of network file systems, wherein the weight is used to indicate the probability of using a certain network file system when selecting a network file system to create a container package in a containerized deployment system. The creation unit is configured to create a persistent storage volume declaration pointing to the storage class; The determining unit is configured to determine a target network file system from the plurality of network file systems based on a determination strategy of the network file system, wherein the determination strategy includes at least one of the following: determining the target network file system based on the load of each network file system; determining the target network file system based on the read / write frequency and / or read / write count of each network file system; and determining the target network file system from the plurality of network file systems based on the weight of each network file system. The deployment unit is configured to create a container package in the containerized deployment system based on the persistent storage volume declaration and the target network file system, wherein the container package includes at least one container.

6. The apparatus according to claim 5, wherein, The weights include probability weights, and the determining unit includes: The third determining module is configured to use the probability weight of each network file system as the probability of selecting that network file system; The fourth determining module is configured to determine the target network file system based on the probability of selecting each of the network file systems.

7. The apparatus according to claim 5, wherein, The determining unit includes: The fifth determining module is configured to, in response to detecting that the persistent storage volume declaration has been created, determine the target network file system from the plurality of network file systems based on the network file system determination strategy.

8. The apparatus according to claim 5, wherein, The deployment unit includes: The binding module is configured to create a persistent volume based on the target network file, and the persistent volume is declared to be bound to the persistent storage volume; The deployment module is configured to create a container wrapper for binding the persistent storage volume declaration.

9. An electronic device, comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-4.

10. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-4.

Images