CN115269497A

CN115269497A - Method and apparatus for configuring network file system

Info

Publication number: CN115269497A
Application number: CN202210854907.9A
Authority: CN
Inventors: 李祥哲; 徐春明; 张云飞; 赵建星; 樊建刚
Original assignee: Jingdong Technology Information Technology Co Ltd
Current assignee: Jingdong Technology Information Technology Co Ltd
Priority date: 2022-07-19
Filing date: 2022-07-19
Publication date: 2022-11-01

Abstract

The application discloses a method and a 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 the containerized deployment system; creating a persistent storage volume declaration that points to a 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 containerized deployment system based on the persistent storage volume declaration and the target network file system, wherein the container package comprises at least one container. By adopting the method, one storage class can correspond to a plurality of network file systems, the performance of the containerized deployment platform is improved, and the maintenance cost is reduced.

Description

Method and apparatus for configuring network file system

Technical Field

The present disclosure relates to the field of computer technology, and in particular, to a method and apparatus for configuring a network file system.

Background

Configuring the storage backend for containerized deployment may enable efficient management of storage devices or storage data. Generally, when an NFS (Network File System) is configured, only one NFS storage is configured for one storage class, and when multiple NFS storages are needed, multiple storage classes are needed, which may cause problems of poor System performance and high System maintenance cost.

Disclosure of Invention

The present disclosure provides a method, apparatus, electronic device, and computer-readable storage medium for configuring a network file system.

According to a first aspect of the present disclosure, there is provided a method for configuring a network file system, comprising: configuring a plurality of network file systems for any storage class in the containerized deployment system; creating a persistent storage volume declaration that points to a 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 containerization deployment system based on the persistent storage volume declaration and the target network file system, wherein the container package comprises at least one container.

In some embodiments, after configuring the plurality of network file systems, the method for configuring a network file system further comprises: determining a weight for each of a plurality of network file systems; determining a target network file system from the plurality of network file systems based on a determination policy of the network file system, comprising: and determining a target network file system from the plurality of network file systems based on the weight of each network file system.

In some embodiments, the weights include probabilistic weights, and determining the target network file system from the plurality of network file systems based on the weight of each network file system includes: taking the probability weight of each network file system as the probability of selecting the network file system; and determining a target network file system based on the probability of selecting each network file system.

In some embodiments, determining a target network file system from a plurality of network file systems based on a determined policy of the network file system comprises: in response to detecting that the persistent storage volume declaration creation is complete, a target network file system is determined from the plurality of network file systems based on a determination policy of the network file system.

In some embodiments, creating a container package 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, the persistent volume being declaratively bound to a persistent storage volume; a container package is created for binding the persisted storage volume claims.

According to a second aspect of the present disclosure, there is provided an apparatus for configuring a network file system, comprising: a configuration unit configured to configure a plurality of network file systems for any storage class in the containerized deployment system; a creating unit configured to create a persistent storage volume declaration that points to a storage class; a determining unit configured to determine a target network file system from the plurality of network file systems based on a determination policy of the network file system; the deployment unit is configured to create a container package in the containerization deployment system based on the persistent storage volume declaration and the target network file system, wherein the container package comprises at least one container.

In some embodiments, the configuration unit further comprises: a first determining module that determines a weight for each of a plurality of network file systems; a determination unit comprising: a second determination 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.

In some embodiments, the weight comprises a probability weight, and the determining unit comprises: a third determination module configured to take the probability weight of each network file system as the probability of selecting the network file system; a fourth determination module configured to determine a target network file system based on the probability of selecting each network file system.

In some embodiments, the determining unit comprises: a fifth determination module configured to determine a target network file system from the plurality of network file systems based on a determination policy of the network file system in response to detecting that the persistent storage volume declaration creation is complete.

In some embodiments, a deployment unit comprises: a binding module configured to create a persistent volume based on a target network file, the persistent volume being declaratively bound to a persistent storage volume; a deployment module configured to create a container package for binding the persisted storage volume claims.

According to a third aspect of the present disclosure, an embodiment of the present disclosure provides an electronic device, including: one or more processors: a storage device for storing one or more programs which, when executed by one or more processors, cause the one or more processors to implement a method for configuring a network file system as provided in the first aspect.

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

The method and the device for configuring the network file system provided by the disclosure comprise the following steps: configuring a plurality of network file systems for any storage class in the containerized deployment system; creating a persistent storage volume declaration that points to a 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; based on the persistent storage volume statement and the target network file system, a container package in the containerized deployment system is created, wherein the container package comprises at least one container, so that one storage class can correspond to a plurality of network file systems, the performance of the containerized deployment platform is improved, and the maintenance cost is reduced.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

The drawings are included to provide a better understanding of the present solution and are not intended to limit the present application. Wherein:

FIG. 1 is an exemplary system architecture diagram to which embodiments of the present application may be applied;

FIG. 2 is a flow diagram of one embodiment of a method for configuring a network file system according to the present application;

FIG. 3 is a flow diagram of another embodiment of a method for configuring a network file system according to the present application;

FIG. 4 is a schematic diagram of a containerized deployment system architecture in one application scenario of a method for configuring a network file system according to the present application;

FIG. 5 is a block diagram illustrating one embodiment of an apparatus for configuring a network file system according to the present application;

FIG. 6 is a block diagram of an electronic device for implementing a method for configuring a network file system according to an embodiment of the present application.

Detailed Description

The following description of the exemplary embodiments of the present application, taken in conjunction with the accompanying drawings, includes various details of the embodiments of the application for the understanding of the same, which are to be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

Fig. 1 illustrates an exemplary system architecture 100 to which embodiments of the present method for configuring a network file system or an apparatus for configuring a network file system may be applied.

As shown in fig. 1, the system architecture 100 may include

terminal devices

101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the

terminal devices

101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The user may use the

terminal devices

101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The

terminal devices

101, 102, 103 may be user terminal devices on which various client applications may be installed, such as data maintenance type applications, image type applications, video type applications, search type applications, financial type applications, and the like.

The

terminal devices

101, 102, 103 may be various electronic devices having a display screen and supporting receiving server messages, including but not limited to smartphones, tablets, e-book readers, electronic players, laptop portable computers, desktop computers, and the like.

The

terminal devices

101, 102, 103 may be hardware or software. When the

terminal devices

101, 102, and 103 are hardware, various electronic devices may be used, and when the

terminal devices

101, 102, and 103 are software, the electronic devices may be installed in the above-listed electronic devices. It may be implemented as multiple pieces of software or software modules (e.g., multiple software modules used to provide distributed services), or as a single piece of software or software module. And is not particularly limited herein.

Server 105 may configure a plurality of network file systems for any storage class in the containerized deployment system, create a persistent storage volume declaration that points to the storage class, determine a target network file system from the plurality of network file systems based on a determination policy of the network file systems, and then create a container package in the containerized deployment system based on the persistent storage volume declaration and the target network file, the container package including at least one container.

It should be noted that the method for configuring the network file system provided by the embodiment of the present disclosure may be executed by the server 105, and accordingly, the apparatus for configuring the network file system may be disposed in the server 105.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

With continued reference to FIG. 2, a flow 200 of one embodiment of a method for configuring a network file system according to the present disclosure is shown, comprising the steps of:

step 201, configuring a plurality of network file systems for any storage class in the containerized deployment system.

In this embodiment, an execution main body (for example, a server shown in fig. 1) of the method for configuring a Network File System may configure a plurality of Network File Systems (NFS) for a storage class (Storageclass) in a containerized deployment System, so that one storage class mounts the plurality of Network File systems.

At step 202, a persistent storage volume declaration is created that points to a storage class.

In this embodiment, a Persistent Volume Claim (PVC) may be created that points to the storage class and is used to characterize a user's request for storage.

Step 203, determining a target network file system from the plurality of network file systems based on the determination policy of the network file system.

In this embodiment, the target network file system may be determined from a plurality of network file systems corresponding to the storage class based on a determination policy of the network file system. The determination strategy of the network file system may be to determine a target network file system based on the load of each network file system, or may also determine the target network file system based on the read-write frequency or the read-write frequency of each network file system, so as to optimize the storage performance of the entire storage system.

Step 204, creating 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 comprises at least one container.

In this embodiment, a container package (Pod) in the containerization deployment system may be created based on the persistent storage volume declaration and the target network file system, where the container package includes at least one container for deploying an application or program, and the container package may be a smallest execution unit in a kubernets (K8S, a cluster for managing containerization of applications on multiple hosts in a cloud platform).

The method for configuring a network file system provided in this embodiment configures a plurality of network file systems for any storage class in a containerized deployment system, creates a persistent storage volume declaration pointing to the storage class, determines a target network file system from the plurality of network file systems based on a determination policy of the network file system, then creates a container package in the containerized deployment system based on the persistent storage volume declaration and the target network file system, where the container package includes at least one container, and can configure a plurality of network file systems for one storage class, and after determining the target network file system based on the determination policy of the network file system, creates a container package including a container using the target network file system, so that one storage class can correspond to the plurality of network file systems, thereby improving performance of the containerized deployment platform and reducing maintenance cost.

With continued reference to FIG. 3, a flow 300 of another embodiment of a method for configuring a network file system according to the present disclosure is shown, comprising the steps of:

step 301, configuring a plurality of network file systems for any storage class in the containerized deployment system, and determining a weight of each network file system in the plurality of network file systems.

In this embodiment, an executing entity (for example, a server shown in fig. 1) of the method for configuring a network file system may configure multiple network file systems for a storage class in a containerized deployment system, so that one storage class mounts multiple network file systems, and configures a weight for each network file system, where the weight is used to indicate a probability that a certain network file system is used when the containerized deployment system selects a network file system to create a container package.

Step 302, create a persistent storage volume declaration that points to a storage class.

Step 303, determining a target network file system from the plurality of network file systems based on the weight of each network file system.

In this embodiment, the target network file system may be determined from the multiple network file systems based on the weight of each network file system, for example, different network file systems may be selected as the target network file system in turn according to the order of the weights from large to small when the target network file system needs to be determined each time.

Step 304, creating a container package in the containerization deployment system based on the persistent storage volume declaration and the target network file system, wherein the container package comprises at least one container.

In this embodiment, the description of step 302 and step 304 is the same as the description of step 202 and step 204, and is not repeated here.

Compared with the embodiment described in fig. 2, the method for configuring the network file systems according to this embodiment configures a plurality of network file systems for the storage class and also configures the weight of each network file system, and specifically defines the determination policy of the network file system as determining the target network file system based on the weight of each network file system, so that the efficiency and convenience for determining the target network file system can be improved.

Optionally, the determining the target network file system from the multiple network file systems based on the weight of each network file system includes: taking the probability weight of each network file system as the probability of selecting the network file system; and determining a target network file system based on the probability of selecting each network file system.

In this embodiment, the weight includes a probability weight, and the probability weight of each network file system may be used as the probability of selecting the network file system, so that each time the target network file system is determined, the target network file system is determined based on the probability weight.

In some alternative implementations of the embodiments described above in conjunction with fig. 2 and 3, determining the target network file system from the plurality of network file systems based on the determination policy of the network file system includes: in response to detecting that the persistent storage volume declaration creation is complete, a target network file system is determined from the plurality of network file systems based on a determination policy of the network file system.

In this embodiment, if it is detected that the persistent storage volume declaration is completely created, a target network file system may be determined from the plurality of network file systems based on a determination policy of the network file system.

In some alternative implementations of the embodiments described above in connection with fig. 2 and 3, creating a container package in a containerized deployment system based on the persistent storage volume claims and the target network file system includes: creating a persistent volume based on the target network file, the persistent volume being declaratively bound to a persistent storage volume; a container package is created for binding the persisted storage volume claims.

In this embodiment, a Persistent Volume (PV) may be created based on a target network file, the Persistent Volume is used to bind the Persistent storage Volume statement, and a container package using the Persistent storage Volume statement is created, so that the construction of the containerization deployment is completed.

In some application scenarios, a method for configuring a network file system includes:

step 401, create storageclass, configure multiple nfs stores and set weights (nfs 1, nfs2, nfs3 in the K8S cluster shown in fig. 4).

At step 402, subsequently created pvcs (e.g., pvc1, pvc2, pvc3, and pvc 4) may each specify the storageclass, as shown in FIG. 4.

Step 403, after creating pvc, when csi (Container Storage interface) detects that pvc is created, randomly selecting an nfs Storage according to nfs Storage weight configured in the storageclass and creating Storage pv, and binding pvc with the created pv.

At step 404, a pod (e.g., pod1, pod2, pod3, pod 4) bound to each pvc is created.

With further reference to fig. 5, as an implementation of the methods shown in the above-mentioned figures, the present disclosure provides an embodiment of an apparatus for configuring a network file system, which corresponds to the method embodiments shown in fig. 2 and fig. 3, and which is particularly applicable to various electronic devices.

As shown in fig. 5, the apparatus for configuring a network file system according to this embodiment includes: an apparatus for configuring a network file system is provided, comprising: configuration unit 501, creation unit 502, determination unit 503, deployment unit 504. A configuration unit configured to configure a plurality of network file systems for any storage class in the containerized deployment system; a creating unit configured to create a persistent storage volume declaration that points to a storage class; a determining unit configured to determine a target network file system from the plurality of network file systems based on a determination policy of the 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 comprises at least one container.

In some embodiments, the determining unit comprises: a fifth determination module configured to determine a target network file system from the plurality of network file systems based on the determination policy of the network file system in response to detecting that the persistent storage volume declaration creation is complete.

In some embodiments, a deployment unit comprises: a binding module configured to create a persistent volume based on a target network file, the persistent volume being declaratively bound to a persistent storage volume; a deployment module configured to create a container package for binding the persistent storage volume declaration.

The units in the apparatus 500 described above correspond to the steps in the method described with reference to fig. 2 and 3. Thus, the operations, features and technical effects that can be achieved by the above-described method for configuring a network file system are also applicable to the apparatus 500 and the units included therein, and are not described herein again.

According to an embodiment of the present application, an electronic device and a readable storage medium are also provided.

As shown in fig. 6, a block diagram of an electronic device 600 for configuring a network file system according to an embodiment of the present application is shown. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic devices may also represent various forms of mobile devices, such as personal digital processors, cellular telephones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the present application that are described and/or claimed herein.

As shown in fig. 6, the electronic apparatus includes: one or more processors 601, memory 602, and interfaces for connecting the various components, including a high-speed interface and a low-speed interface. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions for execution within the electronic device, including instructions stored in or on the memory to display graphical information of a GUI on an external input/output apparatus (such as a display device coupled to the interface). In other embodiments, multiple processors and/or multiple buses may be used, along with multiple memories and multiple memories, as desired. Also, multiple electronic devices may be connected, with each device providing portions of the necessary operations (e.g., as a server array, a group of blade servers, or a multi-processor system). One processor 601 is illustrated in fig. 6.

The memory 602 is a non-transitory computer readable storage medium as provided herein. Wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform the method for configuring a network file system provided herein. The non-transitory computer readable storage medium of the present application stores computer instructions for causing a computer to perform the method for configuring a network file system provided by the present application.

The memory 602, which is a non-transitory computer readable storage medium, may be used to store non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules corresponding to the method for configuring a network file system in the embodiments of the present application (for example, the obtaining unit 601, the distributing unit 602, the first determining unit 603, the second determining unit 604, and the third determining unit 605 shown in fig. 6). The processor 601 executes various functional applications of the server and data processing by executing non-transitory software programs, instructions and modules stored in the memory 602, that is, implements the method for configuring the network file system in the above-described method embodiment.

The memory 602 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of the electronic device for extracting the video clip, and the like. Further, the memory 602 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 602 optionally includes memory remotely located from the processor 601, and these remote memories may be connected over a network to an electronic device for retrieving video clips. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The electronic device of the method for configuring a network file system may further include: an input device 603, an output device 604, and a bus 605. The processor 601, the memory 602, the input device 603, and the output device 604 may be connected by a bus 605 or other means, and are exemplified by the bus 605 in fig. 6.

The input device 603 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the electronic apparatus for extracting the video clip, such as an input device of a touch screen, a keypad, a mouse, a track pad, a touch pad, a pointing stick, one or more mouse buttons, a track ball, a joystick, or the like. The output devices 604 may include a display device, auxiliary lighting devices (e.g., LEDs), and tactile feedback devices (e.g., vibrating motors), among others. The display device may include, but is not limited to, a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display, and a plasma display. In some implementations, the display device can be a touch screen.

Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, application specific ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

These computer programs (also known as programs, software applications, or code) include machine instructions for a programmable processor, and may 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, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a 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 may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present application may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present application can be achieved, and the present invention is not limited herein.

The above-described embodiments should not be construed as limiting the scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for configuring a network file system, comprising:

configuring a plurality of network file systems for any storage class in the containerized deployment system;

creating a persistent storage volume declaration that points to the storage class;

determining a target network file system from the plurality of network file systems based on a determination policy of the network file system;

creating a container package in the containerization deployment system based on the persistent storage volume declaration and the target network file system, wherein the container package comprises at least one container.

2. The method of claim 1, wherein after configuring the plurality of network file systems, the method further comprises:

determining a weight for each of the plurality of network file systems;

the determining a target network file system from the plurality of network file systems based on the determination policy of the network file system comprises:

and determining the target network file system from the plurality of network file systems based on the weight of each network file system.

3. The method of claim 2, wherein the weights comprise probabilistic weights, the determining the target network file system from the plurality of network file systems based on the weight of each network file system comprising:

taking the probability weight of each network file system as the probability of selecting the network file system;

and determining the target network file system based on the probability of selecting each network file system.

4. The method of claim 1, wherein the determining a target network file system from the plurality of network file systems based on the determined policy of the network file system comprises:

in response to detecting that the persistent storage volume claims creation is complete, determining the target network file system from the plurality of network file systems based on a determination policy of the network file system.

5. The method of claim 1, wherein the creating a container package in the containerization deployment system based on the persistent storage volume declaration and the target network file system comprises:

creating a persistent volume based on the target network file, the persistent volume being declaratively bound to the persistent storage volume;

creating a container package for binding the persistent storage volume declaration.

6. An apparatus for configuring a network file system, comprising:

a configuration unit configured to configure a plurality of network file systems for any storage class in the containerized deployment system;

a creating unit configured to create a persistent storage volume declaration that points to the storage class;

a determining unit configured to determine a target network file system from the plurality of network file systems based on a determination policy of the network file system;

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.

7. The apparatus of claim 6, wherein the configuration unit further comprises:

a first determining module that determines a weight for each of the plurality of network file systems;

the determination unit includes:

a second determination module configured to determine the target network file system from the plurality of network file systems based on the weight of each network file system.

8. The apparatus of claim 7, wherein the weight comprises a probabilistic weight, the determining unit comprising:

a third determining module configured to take the probability weight of each network file system as the probability of selecting the network file system;

a fourth determination module configured to determine the target network file system based on the probability of selecting the each network file system.

9. The apparatus of claim 6, wherein the determining unit comprises:

a fifth determination module configured to determine the target network file system from the plurality of network file systems based on a determination policy of the network file system in response to detecting that the persistent storage volume declaration creation is complete.

10. The apparatus of claim 6, wherein the deployment unit comprises:

a binding module configured to create a persistent volume based on the target network file, the persistent volume being declaratively bound to the persistent storage volume;

a deployment module configured to create a container package for binding the persistent storage volume declaration.

11. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein, the first and the second end of the pipe are connected with each other,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-5.

12. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-5.