CN111966471B - Access method, device, electronic equipment and computer storage medium - Google Patents
Access method, device, electronic equipment and computer storage medium Download PDFInfo
- Publication number
- CN111966471B CN111966471B CN202011127902.3A CN202011127902A CN111966471B CN 111966471 B CN111966471 B CN 111966471B CN 202011127902 A CN202011127902 A CN 202011127902A CN 111966471 B CN111966471 B CN 111966471B
- Authority
- CN
- China
- Prior art keywords
- file system
- network file
- pod
- service
- virtual machine
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Bioethics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Databases & Information Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses an access method, an access device, electronic equipment and a computer storage medium. The method comprises the following steps: under the condition that a service POD is connected with a network file system POD, acquiring network file system service from the network file system POD; and accessing a target file system corresponding to the target file system directory through the network file system service. The embodiment of the application can realize multi-node access to the back-end storage system, improve the availability of the system and shorten the recovery time of the system during crash.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to an access method, an access device, an electronic device, and a computer storage medium.
Background
An important technical implementation of cloud computing is virtualization, i.e., the virtualization of computing, storage, and network resources.
In a virtualization cluster, a virtual machine cluster, i.e., a virtual machine cluster, does not have a storage System, and a backend physical storage System needs to be mounted through a Network File System (NFS) service, so that data accessed during task running is stored in the backend physical System.
Generally, all tasks access the backend storage system through one NFS VM (Virtual Machine), the access efficiency is low, and when the NFS service crashes, the access of all tasks is affected.
Disclosure of Invention
In order to solve at least one problem in the prior art, embodiments of the present application provide an access method, an access device, an electronic device, and a computer storage medium.
In a first aspect, an embodiment of the present application provides an access method, including:
under the condition that a service POD is connected with a network file system POD, acquiring network file system service from the network file system POD;
and accessing the target file system corresponding to the target file system directory through the network file system service.
In one embodiment, the method further comprises:
responding to a task running instruction, and creating a service POD and a corresponding network file system POD on a target virtual machine;
establishing a network file system service in a network file system (POD);
mounting a target file system directory to a network file system service;
and connecting the service POD with the corresponding network file system POD.
In one embodiment, mounting a target file system directory to a network file system service includes:
creating a network file system persistent volume request of a network file system (POD);
mounting a network file system persistent volume request to a network file system service;
creating a network file system persistent volume of a network file system (POD);
mounting the network file system continuous volume to a network file system continuous volume request;
mounting a target file system directory to the network file system persistent volume;
connecting a service POD with a corresponding network file system POD, comprising: the network file system persistent volume is associated with a network file system service.
In one embodiment, one service POD is connected to multiple network file systems PODs;
acquiring a network file system service from a network file system (POD), comprising: respectively acquiring network file system services from a plurality of network file Systems (PODs);
accessing a target file system corresponding to a target file system directory through a network file system service, comprising: and accessing the target file system corresponding to the mounted target file system directory through the acquired network file system services.
In one embodiment, the method further comprises:
running a cluster virtual machine on a physical machine platform;
creating a service POD and a corresponding network file system POD on a target virtual machine, wherein the service POD comprises the following steps:
creating a service POD on the cluster virtual machine;
and creating a network file system POD on the cluster virtual machine.
In one embodiment, the method further comprises:
running a cluster virtual machine and a network file system virtual machine on a physical machine platform;
creating a service POD and a corresponding network file system POD on a target virtual machine comprises the following steps:
creating a service POD on the cluster virtual machine;
a network file system POD is created on a network file system virtual machine.
In one embodiment, the method further comprises:
detecting that the POD (file system) is abnormal;
and deleting the network file system POD, and returning to execute the step of creating the network file system POD on the target virtual machine.
In a second aspect, an embodiment of the present application provides an access apparatus, including:
a network file system service acquisition module: the network file system service acquisition module is used for acquiring the network file system service from a network file system (POD) under the condition that the service POD is connected with the POD;
a target file system access module: and the target file system is used for accessing the target file system corresponding to the target file system directory through the network file system service.
In one embodiment, the apparatus further comprises:
a POD creation module: the system comprises a task execution instruction module, a service POD and a corresponding network file system POD, wherein the task execution instruction module is used for responding to the task execution instruction and creating the service POD and the corresponding network file system POD on a target virtual machine;
a service creation module: for creating a network file system service in a network file system, POD;
a first mounting module: for mounting a target file system directory to a network file system service;
a connecting module: the system is used for connecting the service POD with the corresponding network file system POD.
In one embodiment, the apparatus further comprises:
a request creation unit: a network file system persistent volume request for creating a network file system, POD;
a first mounting unit: the device comprises a POD (disk driver) for mounting a network file system persistent volume request to the POD;
a persistent volume creation unit: a network file system persistent volume for creating a network file system POD;
a second mounting unit: a persistent volume request for mounting a network file system persistent volume to a network file system;
a third mounting unit: the target file system directory is mounted to the network file system persistent volume;
the connection module is further configured to: the network file system persistent volume is associated with a network file system service.
In one embodiment, one service POD is connected to multiple network file systems PODs;
the network file system service acquisition module is further configured to: respectively acquiring network file system services from a plurality of network file Systems (PODs);
the target file system access module is further to: and accessing the target file system corresponding to the mounted target file system directory through the acquired network file system services.
In one embodiment, the apparatus further comprises:
the cluster virtual machine operation module: the system comprises a physical machine platform, a cluster virtual machine and a virtual machine control module, wherein the physical machine platform is used for running the cluster virtual machine;
the POD creation module is further configured to:
creating a service POD on the cluster virtual machine;
and creating a network file system POD on the cluster virtual machine.
In one embodiment, the apparatus further comprises:
the virtual machine operation module: the system comprises a physical machine platform, a cluster virtual machine and a network file system virtual machine, wherein the physical machine platform is used for running the cluster virtual machine and the network file system virtual machine;
the POD creation module is further configured to:
creating a service POD on the cluster virtual machine;
a network file system POD is created on a network file system virtual machine.
In one embodiment, the apparatus further comprises:
an anomaly detection module: the device is used for detecting the existence of an anomaly of a network file system (POD);
a deletion module: the system is used for deleting the network file system POD and triggering the POD creating module.
In a third aspect, an embodiment of the present application further provides an electronic device, including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to cause the at least one processor to perform a method provided by any one of the embodiments of the present application.
In a fourth aspect, embodiments of the present application further provide a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform a method provided by any one of the embodiments of the present application.
One embodiment in the above application has the following advantages or benefits: in the embodiment of the application, under the condition that a service POD is connected with a network file system POD, network file system service is acquired from the network file system POD; and accessing the target file system corresponding to the target file system directory through the network file system service. Therefore, the service POD can have a corresponding relation with the network file system POD, when a plurality of PODs operate, the PODs can respectively acquire network file system services from the corresponding network file system PODs and access the backend storage, and multi-node access backend storage is realized. Meanwhile, the operation of other network file systems cannot be influenced by the POD crash of one network file system.
Other effects of the above-described alternative will be described below with reference to specific embodiments.
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 a schematic flow chart of an access method according to an embodiment of the present application;
FIG. 2 is a flow chart of an access method according to an embodiment of the present application;
FIG. 3 is a flow chart illustrating an access method according to an embodiment of the present application;
FIG. 4 is a flow chart illustrating an access method according to an embodiment of the present application;
fig. 5 is a schematic diagram of an application scenario of an access method according to an embodiment of the present application;
FIG. 6 is a schematic structural diagram of an access device according to an embodiment of the present application;
FIG. 7 is a schematic structural diagram of an access device according to an embodiment of the present application;
FIG. 8 is a schematic structural diagram of an access device according to an embodiment of the present application;
fig. 9 is a schematic diagram of an access device 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.
An embodiment of the present application first provides an access method, including the steps shown in fig. 1:
step S11: under the condition that a service POD is connected with a network file system POD, acquiring network file system service from the network file system POD;
step S12: and accessing the target file system corresponding to the target file system directory through the network file system service.
In embodiments of the present application, the POD may be referred to as a pea POD. The POD functions like a container, having the function of storing information. One or more PODs may be included in one container. The service POD and the Network File System (NFS) POD are used to mount a backend storage system address, so that the virtual machine cluster can access the backend storage system through the service POD and the network file system POD. Meanwhile, the service POD may have a corresponding relationship with the network file system POD. In the network file system POD, a network file system service may be mounted. When a network file system service in a network file system POD fails, other network file system PODs can still normally operate, so tasks corresponding to other network file system PODs can still access the back-end storage, and normal operation is not affected.
In the embodiment of the present application, a service POD is connected to a network file system POD. Alternatively, one service POD is connected to a plurality of network file systems PODs. Alternatively, a plurality of service PODs are connected to a plurality of network file system PODs.
In this embodiment of the present application, when a service POD is connected to a network file system POD, a node in a virtual computer (hereinafter referred to as a virtual machine) cluster issues an instruction, so that the service POD acquires a network file system service from the network file system POD. The virtual machine cluster may be a virtual machine cluster, such as a K8S cluster, running on a VMware (Borui) platform.
In the embodiment of the present application, both the service POD and the network file system POD may run on any one or more virtual machines of the virtual machine cluster.
In this embodiment of the present application, the target file system may be a file system in a VMDK (VMWare Virtual Machine Disk Format, Virtual hard Disk Format created by VMWare) Format.
In one embodiment, referring to FIG. 2, mounting a target file system directory to a network file system service includes:
step S21: responding to a task running instruction, and creating a service POD and a corresponding network file system POD on a target virtual machine;
step S22: establishing a network file system service in a network file system (POD);
step S23: mounting a target file system directory to a network file system service;
step S24: and connecting the service POD with the corresponding network file system POD.
In this embodiment of the present application, the target virtual machine may be any virtual machine in the virtual machine cluster. A virtual machine cluster may include a Master virtual machine (Master VM) and a Node virtual machine (Node VM). The service POD is created on the target virtual machine, and the service POD may be created on the primary virtual machine or the node virtual machine by issuing a service POD creation instruction by the primary virtual machine after issuing a task operation instruction when the user operates the task.
Since the NFS service is created in the NFS POD, in the case where the service POD and the NFS POD are connected, the service POD can acquire the NFS service from the NFS POD.
In one embodiment, referring to fig. 3, step S23 includes:
step S31: a network file system Persistent Volume request (PVC) to create a network file system POD;
step S32: mounting a network file system persistent volume request to a network file system service;
step S33: creating a network file system Persistent Volume (PV) of a network file system POD;
step S34: mounting the network file system continuous volume to a network file system continuous volume request;
step S35: mounting the target file system directory to the network file system persistent volume;
after step S35, in step S24, the service POD is connected to the corresponding network file system POD, including step S36: the network file system persistent volume is associated with a network file system service.
In the embodiment of the present application, a network file system POD may be used to replace a network file system virtual machine, so that a corresponding relationship exists between a service POD and the network file system POD, and thus, a plurality of service PODs may access corresponding network file system PODs in parallel.
In one embodiment, one service POD is connected to multiple network file systems PODs;
in step S11, acquiring a network file system service from a network file system POD, includes: respectively acquiring network file system services from a plurality of network file Systems (PODs);
in step S12, accessing the target file system corresponding to the target file system directory through the network file system service includes: and accessing the target file system corresponding to the mounted target file system directory through the acquired network file system services.
In other embodiments of the present application, one service POD may be connected to one network file system POD. When one NFS service crashes, the virtual machine can quickly recreate the NFS POD, and the time for creating the NFS POD is less than the time for restarting the virtual machine when the NFS VM crashes, so that high availability and automatic recovery of multiple nodes can be realized.
In one embodiment, before step S11, the access method further includes:
running a cluster virtual machine on a physical machine platform;
creating a service POD and a corresponding network file system POD on a target virtual machine, wherein the service POD comprises the following steps:
creating a service POD on the cluster virtual machine;
and creating a network file system POD on the cluster virtual machine.
In this embodiment, the physical machine platform may be a hardware basis on which a virtual machine cluster runs, and the virtual machine cluster may include a plurality of cluster virtual machines, including a primary virtual machine and a node virtual machine, for example. The logical volume of the backend storage can be converted into a network file system on the physical platform, so that the logical volume can be mounted in the NFS POD, and the business POD can access the backend storage system through the NFS service.
In some embodiments, before step S11, the access method further includes:
running a cluster virtual machine and a network file system virtual machine on a physical machine platform;
creating a service POD and a corresponding network file system POD on a target virtual machine comprises the following steps:
creating a service POD on the cluster virtual machine;
a network file system POD is created on a network file system virtual machine.
In this embodiment of the present application, a network file system virtual machine, that is, an NFS virtual machine, is a virtual machine that runs outside a virtual machine cluster, does not belong to the virtual machine cluster, but can perform transmission and reception of information with each virtual machine in the virtual machine cluster.
In one embodiment, after step S12, the access method further includes:
detecting that the POD (file system) is abnormal;
and deleting the network file system POD, and returning to execute the step of creating the network file system POD on the target virtual machine.
In the embodiment of the present application, the existence of the abnormality in the network file system POD may be an NFS service abnormality in the network file system POD, a network file system persistent volume request abnormality, or a network file system persistent volume abnormality.
In an example of the present application, referring to fig. 4 and 5, an access method implemented on the cloud system architecture shown in fig. 5 includes the following steps:
step S41: a storage Logical volume (LUN) 52 is partitioned in the storage cluster 51. For example, the storage cluster 51 may be a distributed storage cluster.
Step S42: the block device file corresponding to LUN52 is sent to VMware platform 54 through network switch 53.
Step S43: the block device File corresponding to LUN52 is converted into a File in VMDK format of VMFS (VMware Virtual Machine File System, high-performance cluster File System) File System on VMware platform 54. Thereby making the system of the block device corresponding to LUN52 the target file system in VMDK format. The conversion may specifically be performed by the data center of the VMware platform 54.
Step S44: the K8S (Kubernets) cluster 55 is launched and run on the VMware platform 54.
Step S45: and receiving a task operation instruction. The task execution instruction may be, for example, a video playing instruction, a software execution instruction, or the like.
Step S46: a service POD56 is created on the K8S (kubernets) cluster 55.
Step S47: a network file system POD57 is created on the K8S cluster 55.
Step S48: the service POD56 and the network file system POD57 are connected.
Step S49: acquiring the network file system service 58 from the network file system POD 57;
step S410: the target file system corresponding to the target file system directory is accessed through the network file system service 58. The target file system directory may be in a format such as "/… …/… …".
In this specific example of the present application, still referring to fig. 5, after creating the service POD56, the method further includes:
creating a service persistent volume request and mounting the service persistent volume request to the service POD 56;
creating a service continuous volume and mounting the service continuous volume to a service continuous volume request;
and mounting the target file system directory to the service persistent volume.
In another example of the present application, if other task execution requests are received, a new service POD is created on the K8S cluster 55. If the other tasks are associated with the currently running task, the new service POD is associated with the existing service POD, so that the two service PODs can mount the same PVC, PV and the target file system directory.
In the specific example of the present application, still referring to fig. 5, after creating the NFS POD57, the method further includes:
mount NFS service 58 to NFS POD 57;
creating a network file system persistent volume request; and mounts the network file system persistent volume request to NFS service 58;
creating a network file system continuous volume, and mounting the network file system continuous volume to a network file system continuous volume request;
mount the target file system directory to the network file system persistent volume request.
An embodiment of the present application further provides an access apparatus, as shown in fig. 6, including:
network file system service acquisition module 61: the network file system service acquisition module is used for acquiring the network file system service from a network file system (POD) under the condition that the service POD is connected with the POD;
target file system access module 62: and the target file system is used for accessing the target file system corresponding to the target file system directory through the network file system service.
In one embodiment, as shown in fig. 7, the apparatus further comprises:
the POD creation module 71: the system comprises a task execution instruction module, a service POD and a corresponding network file system POD, wherein the task execution instruction module is used for responding to the task execution instruction and creating the service POD and the corresponding network file system POD on a target virtual machine;
the service creation module 72: for creating a network file system service in a network file system, POD;
the first mounting module 73: for mounting a target file system directory to a network file system service;
the connection module 74: the system is used for connecting the service POD with the corresponding network file system POD.
In one embodiment, as shown in fig. 8, the apparatus further comprises:
the request creation unit 81: a network file system persistent volume request for creating a network file system, POD;
first mounting unit 82: the device comprises a POD (disk driver) for mounting a network file system persistent volume request to the POD;
the persistent volume creation unit 83: a network file system persistent volume for creating a network file system POD;
second mounting unit 84: a persistent volume request for mounting a network file system persistent volume to a network file system;
third mounting unit 85: the target file system directory is mounted to the network file system persistent volume;
the connection module 74 is also configured to: the network file system persistent volume is associated with a network file system service.
In one embodiment, one service POD is connected to multiple network file systems PODs;
the network file system service acquisition module is further configured to: respectively acquiring network file system services from a plurality of network file Systems (PODs);
the target file system access module is further to: and accessing the target file system corresponding to the mounted target file system directory through the acquired network file system services.
In one embodiment, the apparatus further comprises:
the cluster virtual machine operation module: the system comprises a physical machine platform, a cluster virtual machine and a virtual machine control module, wherein the physical machine platform is used for running the cluster virtual machine;
the POD creation module is further configured to: creating a service POD on the cluster virtual machine; and creating a network file system POD on the cluster virtual machine.
In one embodiment, the apparatus further comprises:
the virtual machine operation module: the system comprises a physical machine platform, a cluster virtual machine and a network file system virtual machine, wherein the physical machine platform is used for running the cluster virtual machine and the network file system virtual machine;
the POD creation module is further configured to: creating a service POD on the cluster virtual machine; a network file system POD is created on a network file system virtual machine.
In one embodiment, the apparatus further comprises:
an anomaly detection module: the device is used for detecting the existence of an anomaly of a network file system (POD);
a deletion module: the system is used for deleting the network file system POD and triggering the POD creating module.
The functions of each module in each apparatus in the embodiment of the present application may refer to corresponding descriptions in the above method, 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. 9, is a block diagram of an electronic device according to a method of an embodiment of the application. 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. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, 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. 9, the electronic apparatus includes: one or more processors 901, memory 902, 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 for a Graphical User Interface (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 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). Fig. 9 illustrates an example of a processor 901.
The memory 902 may include a program storage area and a data storage area, wherein the program storage 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, and the like. Further, the memory 902 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 902 may optionally include memory located remotely from the processor 901, which may be connected to the electronic device 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.
The electronic device implementing the method of the embodiment of the present application may further include: an input device 903 and an output device 904. The processor 901, the memory 902, the input device 903 and the output device 904 may be connected by a bus or other means, and fig. 9 illustrates the connection by a bus as an example.
The input device 903 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the electronic device, such as a touch screen, keypad, mouse, track pad, touch pad, pointer, one or more mouse buttons, track ball, joystick, or other input device. The output devices 904 may include a display device, auxiliary lighting devices (e.g., LEDs), tactile feedback devices (e.g., vibrating motors), and the like. 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 Integrated Circuits (ASICs), 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, and the present invention is not limited thereto as long as the desired results of the technical solutions disclosed in the present application can be achieved.
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 (16)
1. An access method, comprising:
under the condition that a service POD is connected with a network file system POD, acquiring network file system services from the network file system POD, wherein one or more service PODs are arranged, each service POD is connected with a plurality of network file system PODs, and the service PODs and the network file system PODs have corresponding relations; the service POD is created on the target virtual machine and is used for running the tasks of the system of the target virtual machine;
accessing a target file system corresponding to a target file system directory through the network file system service; the target file system directory is mounted in the network file system service, so that the target file system can be accessed by the service POD.
2. The method of claim 1, further comprising:
responding to a task running instruction, and creating a service POD and a corresponding network file system POD on a target virtual machine;
creating a network file system service in the network file system POD;
mounting a target file system directory to the network file system service;
and connecting the service POD with the corresponding network file system POD.
3. The method of claim 2, wherein mounting a target file system directory to the network file system service comprises:
creating a network file system persistent volume request of the network file system POD;
mounting the network file system persistent volume request to the network file system service;
creating a network file system persistent volume of the network file system POD;
mounting the network file system persistent volume to the network file system persistent volume request;
mounting the target file system directory to the network file system persistent volume;
connecting the service POD with the network file system POD, including: associating the network file system persistent volume with the network file system service.
4. The method of claim 2,
acquiring a network file system service from the network file system POD, comprising: respectively acquiring network file system services from a plurality of network file system PODs;
accessing a target file system corresponding to a target file system directory through the network file system service includes: and accessing the target file system corresponding to the mounted target file system directory through the acquired network file system services.
5. The method according to any one of claims 2 to 4, further comprising: running a cluster virtual machine on a physical machine platform;
creating a service POD and a corresponding network file system POD on a target virtual machine, wherein the service POD comprises the following steps: creating the service POD on the cluster virtual machine; creating the network file system POD on the cluster virtual machine.
6. The method according to any one of claims 2 to 4, further comprising: running a cluster virtual machine and a network file system virtual machine on a physical machine platform;
creating a service POD and a corresponding network file system POD on a target virtual machine comprises the following steps: creating the service POD on the cluster virtual machine; creating the network file system POD on the network file system virtual machine.
7. The method according to any one of claims 2 to 4, further comprising:
detecting that the network file system POD has abnormity;
and deleting the network file system POD, and returning to execute the step of creating the network file system POD on the target virtual machine.
8. An access device, comprising:
a network file system service acquisition module: the network file system service acquisition system is used for acquiring network file system services from network file system PODs (POD) under the condition that the service PODs are connected with the network file system PODs, wherein one or more service PODs are arranged, each service POD is connected with a plurality of network file system PODs, and the service PODs and the network file system PODs have corresponding relations; the service POD is created on the target virtual machine and is used for running the tasks of the system of the target virtual machine;
a target file system access module: the target file system is used for accessing the target file system corresponding to the target file system directory through the network file system service; the target file system directory is mounted in the network file system service, so that the target file system can be accessed by the service POD.
9. The apparatus of claim 8, further comprising:
a POD creation module: the system comprises a task execution instruction module, a service POD and a corresponding network file system POD, wherein the task execution instruction module is used for responding to the task execution instruction and creating the service POD and the corresponding network file system POD on a target virtual machine;
a service creation module: for creating a network file system service in the network file system POD;
a first mounting module: means for mounting a target file system directory to the network file system service;
a connecting module: the server is used for connecting the service POD with the corresponding network file system POD.
10. The apparatus of claim 9, wherein the first mounting module comprises:
a request creation unit: a network file system persistent volume request for creating the network file system POD;
a first mounting unit: for mounting the network file system persistent volume request to the network file system POD;
a persistent volume creation unit: a network file system persistent volume for creating the network file system POD;
a second mounting unit: means for mounting the network file system persistent volume to the network file system persistent volume request;
a third mounting unit: the target file system directory is mounted to the network file system persistent volume;
the connection module is further configured to: associating the network file system persistent volume with the network file system service.
11. The apparatus of claim 9,
the network file system service acquisition module is further configured to: respectively acquiring network file system services from a plurality of network file system PODs;
the target file system access module is further configured to: and accessing the target file system corresponding to the mounted target file system directory through the acquired network file system services.
12. The apparatus of any one of claims 9 to 11, further comprising:
the cluster virtual machine operation module: the system comprises a physical machine platform, a cluster virtual machine and a virtual machine control module, wherein the physical machine platform is used for running the cluster virtual machine;
the POD creation module is further configured to:
creating the service POD on the cluster virtual machine;
creating the network file system POD on the cluster virtual machine.
13. The apparatus of any one of claims 9 to 11, further comprising:
the virtual machine operation module: the system comprises a physical machine platform, a cluster virtual machine and a network file system virtual machine, wherein the physical machine platform is used for running the cluster virtual machine and the network file system virtual machine;
the POD creation module is further configured to:
creating the service POD on the cluster virtual machine;
creating the network file system POD on the network file system virtual machine.
14. The apparatus of any one of claims 9 to 11, further comprising:
an anomaly detection module: for detecting the presence of an anomaly in the network file system POD;
a deletion module: the system is used for deleting the network file system POD and triggering the POD creating module.
15. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
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-7.
16. 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-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011127902.3A CN111966471B (en) | 2020-10-21 | 2020-10-21 | Access method, device, electronic equipment and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011127902.3A CN111966471B (en) | 2020-10-21 | 2020-10-21 | Access method, device, electronic equipment and computer storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111966471A CN111966471A (en) | 2020-11-20 |
| CN111966471B true CN111966471B (en) | 2022-03-08 |
Family
ID=73387050
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011127902.3A Active CN111966471B (en) | 2020-10-21 | 2020-10-21 | Access method, device, electronic equipment and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111966471B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113051244B (en) * | 2021-03-22 | 2023-07-21 | 北京百度网讯科技有限公司 | Data access method and device, and data acquisition method and device |
| CN114640678A (en) * | 2022-03-14 | 2022-06-17 | 明阳产业技术研究院(沈阳)有限公司 | Pod management method, device and medium based on SR-IOV |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110096232A (en) * | 2019-04-25 | 2019-08-06 | 新华三云计算技术有限公司 | The processing method of disk lock, the creation method of storage unit and relevant apparatus |
| CN110221915A (en) * | 2019-05-21 | 2019-09-10 | 新华三大数据技术有限公司 | Node scheduling method and apparatus |
| CN110297935A (en) * | 2019-06-28 | 2019-10-01 | 京东数字科技控股有限公司 | Image search method, device, medium and electronic equipment |
| CN111475469A (en) * | 2020-03-19 | 2020-07-31 | 中山大学 | Virtual file system-based small file storage optimization system in KUBERNETES user mode application |
| CN111488322A (en) * | 2020-04-08 | 2020-08-04 | 网易（杭州）网络有限公司 | File system service method and device and server equipment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190377604A1 (en) * | 2018-06-11 | 2019-12-12 | Nuweba Labs Ltd. | Scalable function as a service platform |
-
2020
- 2020-10-21 CN CN202011127902.3A patent/CN111966471B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110096232A (en) * | 2019-04-25 | 2019-08-06 | 新华三云计算技术有限公司 | The processing method of disk lock, the creation method of storage unit and relevant apparatus |
| CN110221915A (en) * | 2019-05-21 | 2019-09-10 | 新华三大数据技术有限公司 | Node scheduling method and apparatus |
| CN110297935A (en) * | 2019-06-28 | 2019-10-01 | 京东数字科技控股有限公司 | Image search method, device, medium and electronic equipment |
| CN111475469A (en) * | 2020-03-19 | 2020-07-31 | 中山大学 | Virtual file system-based small file storage optimization system in KUBERNETES user mode application |
| CN111488322A (en) * | 2020-04-08 | 2020-08-04 | 网易（杭州）网络有限公司 | File system service method and device and server equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111966471A (en) | 2020-11-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102552419B1 (en) | Method, device, electronic equipment and readable storage medium for sharing gpu | |
| CN111258609A (en) | Upgrading method and device of Kubernetes cluster, electronic equipment and medium | |
| JP7167222B2 (en) | APPLET DATA ACQUISITION METHOD, APPARATUS, DEVICE, AND STORAGE MEDIUM | |
| CN111045985B (en) | File storage processing method, server, electronic device and storage medium | |
| CN110704162B (en) | Method, device and equipment for sharing container mirror image by physical machine and storage medium | |
| CN111966471B (en) | Access method, device, electronic equipment and computer storage medium | |
| KR20210036874A (en) | Method and apparatus for processing development machine operation task, device and storage medium | |
| CN111694857A (en) | Method and device for storing resource data, electronic equipment and computer readable medium | |
| CN111506401A (en) | Automatic driving simulation task scheduling method and device, electronic equipment and storage medium | |
| CN110765075A (en) | Storage method and equipment of automatic driving data | |
| CN111881387A (en) | Data processing method, device, equipment and medium for small program | |
| CN112565356A (en) | Data storage method and device and electronic equipment | |
| CN112540914A (en) | Execution method, execution device, server and storage medium for unit test | |
| CN112286851A (en) | Server mainboard, server, control method, electronic device and readable medium | |
| CN111770154A (en) | Service detection method, device, equipment and storage medium | |
| CN111740859A (en) | Test environment deployment method and device, electronic equipment and storage medium | |
| CN111339462A (en) | Component rendering method, device, server, terminal and medium | |
| CN111966877A (en) | Front-end service method, device, equipment and storage medium | |
| CN111782357A (en) | Label control method and device, electronic equipment and readable storage medium | |
| CN110536283B (en) | Terminal identifier acquisition method, device, electronic equipment and medium | |
| CN111767169A (en) | Data processing method and device, electronic equipment and storage medium | |
| US20210208976A1 (en) | Backup management | |
| CN111597192B (en) | Database switching control method and device and electronic equipment | |
| CN111639116A (en) | Data access connection session protection method and device | |
| CN113158098A (en) | Page generation method, device, equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |