WO2022174553A1 - 文件处理方法、装置、电子设备和存储介质 - Google Patents

文件处理方法、装置、电子设备和存储介质 Download PDF

Info

Publication number
WO2022174553A1
WO2022174553A1 PCT/CN2021/108012 CN2021108012W WO2022174553A1 WO 2022174553 A1 WO2022174553 A1 WO 2022174553A1 CN 2021108012 W CN2021108012 W CN 2021108012W WO 2022174553 A1 WO2022174553 A1 WO 2022174553A1
Authority
WO
WIPO (PCT)
Prior art keywords
container
file
target node
scheduling group
operation request
Prior art date
Application number
PCT/CN2021/108012
Other languages
English (en)
French (fr)
Inventor
苗永昌
Original Assignee
北京百度网讯科技有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 北京百度网讯科技有限公司 filed Critical 北京百度网讯科技有限公司
Priority to EP21844172.3A priority Critical patent/EP4075269A4/en
Priority to KR1020227004988A priority patent/KR20220026603A/ko
Priority to JP2022513682A priority patent/JP2023518136A/ja
Priority to US17/641,370 priority patent/US20240054107A1/en
Publication of WO2022174553A1 publication Critical patent/WO2022174553A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/18—File system types
    • G06F16/188—Virtual file systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/13—File access structures, e.g. distributed indices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/18—File system types
    • G06F16/182—Distributed file systems
    • 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
    • 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

Definitions

  • the present disclosure relates to the field of computer technologies, and in particular, to the field of cloud computing.
  • container cluster management systems such as Kubernetes
  • Kubernetes for the creation and deployment of containers have also been widely used.
  • users In actual deployment and operation, users often need to view the internal files of the system and copy the internal files of the system to the outside for backup and analysis.
  • Commonly viewed and backed up file types include run logs, run data, and more.
  • the present disclosure provides a file processing method, apparatus, electronic device and storage medium.
  • a file processing method comprising:
  • a file processing apparatus comprising:
  • the container determination module is used to determine the container corresponding to the container scheduling group information in the target node based on the container scheduling group information corresponding to the file operation request received by the target node;
  • the path determination module is used to determine the file path of the container by using the node directory of the target node;
  • the file operation module is used to operate the file under the file path according to the file operation request.
  • an electronic device comprising:
  • the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method in any of the embodiments of the present disclosure.
  • a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the method in any of the embodiments of the present disclosure.
  • a computer program product comprising a computer program that, when executed by a processor, implements the method in any of the embodiments of the present disclosure.
  • the embodiment of the present disclosure provides a file processing method when a target node receives a file operation request, locates a specific container based on the container scheduling group information, and uses the node directory to determine the file path of the container, so that the files in the container cluster management system can be processed. operation, eliminating the use of proprietary commands, reducing operation and maintenance requirements and having better compatibility.
  • FIG. 1 is a schematic diagram of a file processing method provided by an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of a file processing method provided by another embodiment of the present disclosure.
  • FIG. 3 is a schematic diagram of a file processing apparatus provided by an embodiment of the present disclosure.
  • FIG. 4 is a schematic diagram of a file processing apparatus provided by another embodiment of the present disclosure.
  • FIG. 5 is a block diagram of an electronic device used to implement the file method of an embodiment of the present disclosure.
  • FIG. 1 shows a schematic diagram of a file operation method provided by an embodiment of the present disclosure. As shown in Figure 1, the method may include:
  • Step S110 based on the container scheduling group information corresponding to the file operation request received by the target node, determine the container corresponding to the container scheduling group information in the target node;
  • Step S120 using the node directory of the target node to determine the file path of the container
  • Step S130 according to the file operation request, operate the file under the file path.
  • the target node may be a node (Node) in the container cluster management system.
  • Container cluster management systems such as Kubernetes, are container orchestration tools that support automated deployment and management of containerized applications. Compared with virtual machines, containers can be deployed quickly, and containers are decoupled from underlying facilities and machine file systems, so they can be migrated between different clouds and different versions of operating systems.
  • a node is a hardware unit or a single machine in the container cluster management system, and is the host of the container.
  • Container scheduling group, or Pod is the smallest unit for container cluster management system to create, schedule, and manage containers. It is a collection of multiple containers. It provides a higher level of abstraction than containers, making deployment and management more flexible. For example, Kubernetes does not schedule containers directly, but encapsulates containers into Pods. Containers in the same Pod will share the same namespace and local network, and containers can easily communicate within the same pod.
  • the above steps S11 to S13 in the embodiment of the present disclosure may be performed by the target node, and specifically, may be performed by a file management agent module (Agent) in the target node.
  • a file management agent module can be set in each node of Kubernetes, and the requesting device that initiates the file operation request can send the file operation request to the distribution service module, and the distribution service module determines the target node and sends the file operation request. to the target node.
  • the container scheduling group information corresponding to the file operation request may be included in the file operation request, or obtained by querying the metadata information set of Kubernetes according to the relevant information in the file operation request.
  • the file for the requested operation of the file operation request may include operation logs, operation data, and the like.
  • the container scheduling group information corresponding to the request can be mapped to a specific container (Container) in the node.
  • the container here may refer to a container that runs according to the standard of the container runtime in the node after being created, where the container runtime is a software tool for executing the container and managing the container image on the node.
  • Docker may be used when the container is running, and correspondingly, a specific container in a node may also be referred to as a Docker Container or a Docker container.
  • the file path to be operated can be found by using the node directory of the target node.
  • the node directory may refer to a directory for reflecting the file system of the entire container, or a collection of paths.
  • operations can be performed on the files in the file path, such as viewing or copying, according to the file operation request.
  • a file processing method is provided when a target node receives a file operation request, locates a specific container based on the container scheduling group information, and uses the node directory to determine the file path of the container. file operation, eliminating the use of proprietary file operation commands such as the tar command, reducing operation and maintenance requirements and having better compatibility.
  • the file management agent module as the module for the Pod file in the dedicated management node, the compatibility can be further improved, and the permission scheme of the video memory in different user systems and the file management scheme of the bastion machine can be connected.
  • the above method may further include:
  • the container scheduling group created by the container cluster management system corresponds to the target node, create a container on the target node, and obtain the file view of the container and the data volume mount directory of the container scheduling group;
  • the above steps may be performed by the target node, and specifically, may be performed by a container runtime such as Docker in the target node.
  • a container runtime such as Docker in the target node.
  • containers run on nodes.
  • Docker is used as the underlying container runtime
  • Kubernetes can create a Pod container on the node corresponding to the Pod every time it creates a Pod, and the container will eventually run according to Docker's standards.
  • the underlying container runtime determines a file view for the container.
  • a container can be provided with a complete file view in a joint mount manner.
  • the joint mounted file view will be mounted on the node directory of the target node, so that the node directory of the target node can reflect the file system of the container.
  • the container when the container is running, it will mount some data volumes (Volumes) required by the container scheduling group. For example, use the Mount command to mount the data volumes required by the Pod to obtain the data volume mount directory.
  • the data volume mount directory also exists in the node directory.
  • the node directory can reflect the file systems of all containers in the node, and can The complete information required to operate the file is determined through the node directory, which is beneficial to realize the convenient operation of the file in the node.
  • step S120 using the node directory of the target node to determine the file path of the container, including:
  • the corresponding file view and data volume mounting directory can be found in the node directory according to the determined container. For example, in the node directory, find the file path of the joint mount and the file path mounted by the Mount command through the Docker Container. Therefore, the corresponding file view and data volume mount directory are used to accurately locate the file, and operate the file on the node to meet the user's needs.
  • step S110 based on the container scheduling group information corresponding to the file operation request received by the target node, determine the container corresponding to the container scheduling group information in the target node, including:
  • a container corresponding to the container scheduling group information is determined.
  • the file management agent module is also used to realize the container logical name conversion between the container scheduling group and the container management tool, for example, the logical name conversion from the container of the Kubernetes Pod to the Docker container, so as to obtain the name information of the Docker container, This enables the node to map the Pod information to the specific Docker container in the node.
  • the file under the file path is operated, including:
  • the local file service is, for example, Fileserver.
  • Fileserver you can directly manipulate the directory files mounted by the node federation according to the file path.
  • the operation type specified by the file operation request can include read, copy, delete, etc.
  • the file is directly operated through a local file service such as Fileserver, which has better transmission performance.
  • the above method may further include:
  • the distribution service module queries the container scheduling group information corresponding to the metadata information in the file operation request in the metadata information collection of the container cluster management system, and locates the target according to the container scheduling group information node, which sends the file operation request to the target node.
  • FIG. 2 shows a schematic diagram of operating on a pod file when the underlying container runtime of Kubernetes is docker according to the above embodiment.
  • Kubernetes 200 includes a plurality of nodes 220.
  • the requesting device sends a file operation request for a certain pod file to the distribution service module (Dispenser) 210 .
  • the distribution service module 210 receives the file operation request, locates the node 220 where the pod is located, and establishes a connection with the file management agent module 221 in the node 220 .
  • the file management agent module 221 After the file management agent module 221 establishes a connection with the distribution service module 210 and receives the file operation request for the pod file, it corresponds the pod information corresponding to the file operation request to the specific Docker container 222 of the node. Using the node directory 223, the jointly mounted file path and the Mount file path are found through the Docker container 222. Based on these file paths, file requests are processed through Fileserver. Fileserver directly manipulates the directory files mounted by the node federation.
  • the target node where the relevant container scheduling group is located can be located. Therefore, the file path can be directly determined in the target node where the container scheduling group is located. , which is more efficient than using proprietary commands to enter each node.
  • the embodiments of the present disclosure provide a file processing method when a target node receives a file operation request, which can be applied to a cloud-native microservice application platform, such as a Stack platform. Locate a specific container based on the container scheduling group information, and use the node directory to determine the file path of the container, so that the files in the container cluster management system can be operated, eliminating the use of proprietary commands, reducing operation and maintenance requirements and having more good compatibility.
  • a cloud-native microservice application platform such as a Stack platform.
  • FIG. 3 shows a schematic diagram of a file processing apparatus provided by an embodiment of the present disclosure.
  • the device includes:
  • the container determination module 310 is configured to determine the container corresponding to the container scheduling group information in the target node based on the container scheduling group information corresponding to the file operation request received by the target node;
  • the path determination module 320 is used for determining the file path of the container by using the node directory of the target node;
  • the file operation module 330 is configured to operate the file under the file path according to the file operation request.
  • the file processing apparatus may further include:
  • the container creation module 410 is configured to create a container on the target node when the container scheduling group created by the container cluster management system corresponds to the target node, and obtain the file view of the container and the data volume mount directory of the container scheduling group;
  • the directory mounting module 420 is configured to mount the file view of the container and the data volume mounting directory of the container scheduling group in the node directory of the target node.
  • the path determination module 320 is used to:
  • the container determination module 310 includes:
  • the conversion unit 311 is configured to perform logical name conversion from the container scheduling group to the container management tool based on the container scheduling group information corresponding to the file operation request received by the target node, to obtain container name information;
  • the determining unit 312 is configured to determine the container corresponding to the container scheduling group information based on the container name information.
  • the file manipulation module 330 is used to:
  • the file processing apparatus may further include:
  • the distribution service module 430 is configured to, in the case of receiving the file operation request, query the container scheduling group information corresponding to the metadata information in the file operation request in the metadata information set of the container cluster management system, and according to the container scheduling group The information is located to the target node, and the file operation request is sent to the target node.
  • the file processing apparatus provided by the embodiment of the present disclosure can implement the file processing method provided by the embodiment of the present disclosure, and has corresponding beneficial effects.
  • the present disclosure also provides an electronic device, a readable storage medium, and a computer program product.
  • FIG. 5 shows a schematic block diagram of an example electronic device 500 that may be used to implement embodiments of the present disclosure.
  • Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers.
  • Electronic devices may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smart phones, wearable devices, and other similar computing devices.
  • the components shown herein, their connections and relationships, and their functions are by way of example only, and are not intended to limit implementations of the disclosure described and/or claimed herein.
  • the electronic device 500 includes a computing unit 501 that can be executed according to a computer program stored in a read only memory (ROM) 502 or a computer program loaded from a storage unit 508 into a random access memory (RAM) 503 Various appropriate actions and handling. In the RAM 503, various programs and data required for the operation of the electronic device 500 can also be stored.
  • the computing unit 501, the ROM 502, and the RAM 503 are connected to each other through a bus 504.
  • An input output (I/O) interface 505 is also connected to bus 504 .
  • Various components in the electronic device 500 are connected to the I/O interface 505, including: an input unit 506, such as a keyboard, a mouse, etc.; an output unit 507, such as various types of displays, speakers, etc.; a storage unit 508, such as a magnetic disk, an optical disk etc.; and a communication unit 509, such as a network card, modem, wireless communication transceiver, and the like.
  • the communication unit 509 allows the electronic device 500 to exchange information/data with other devices through a computer network such as the Internet and/or various telecommunication networks.
  • Computing unit 501 may be various general-purpose and/or special-purpose processing components with processing and computing capabilities. Some examples of computing units 501 include, but are not limited to, central processing units (CPUs), graphics processing units (GPUs), various specialized artificial intelligence (AI) computing chips, various computing units that run machine learning model algorithms, digital signal processing processor (DSP), and any suitable processor, controller, microcontroller, etc.
  • the computing unit 501 executes the various methods and processes described above, such as a file processing method.
  • the file processing method may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 508 .
  • part or all of the computer program may be loaded and/or installed on electronic device 500 via ROM 502 and/or communication unit 509 .
  • the computer program When the computer program is loaded into RAM 503 and executed by computing unit 501, one or more steps of the file processing method described above may be performed.
  • the computing unit 501 may be configured to perform the file processing method by any other suitable means (eg, by means of firmware).
  • Various implementations of the systems and techniques described herein above may be implemented in digital electronic circuitry, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips system (SOC), load programmable logic device (CPLD), computer hardware, firmware, software, and/or combinations thereof.
  • FPGAs field programmable gate arrays
  • ASICs application specific integrated circuits
  • ASSPs application specific standard products
  • SOC systems on chips system
  • CPLD load programmable logic device
  • computer hardware firmware, software, and/or combinations thereof.
  • These various embodiments may include being implemented in one or more computer programs executable and/or interpretable on a programmable system including at least one programmable processor that
  • the processor which may be a special purpose or general-purpose programmable processor, may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device an output device.
  • Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, performs the functions/functions specified in the flowcharts and/or block diagrams. Action is implemented.
  • the program code may execute entirely on the machine, partly on the machine, partly on the machine and partly on a remote machine as a stand-alone software package or entirely on the remote machine or server.
  • a machine-readable medium may be a tangible medium that may contain or store a program for use by or in connection with the instruction execution system, apparatus or device.
  • the machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium.
  • Machine-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or devices, or any suitable combination of the foregoing.
  • machine-readable storage media would include one or more wire-based electrical connections, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), fiber optics, compact disk read only memory (CD-ROM), optical storage, magnetic storage, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read only memory
  • EPROM or flash memory erasable programmable read only memory
  • CD-ROM compact disk read only memory
  • magnetic storage or any suitable combination of the foregoing.
  • the systems and techniques described herein may be implemented on a computer having a display device (eg, a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user ); and a keyboard and pointing device (eg, a mouse or trackball) through which a user can provide input to the computer.
  • a display device eg, a CRT (cathode ray tube) or LCD (liquid crystal display) monitor
  • a keyboard and pointing device eg, a mouse or trackball
  • Other kinds of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (eg, visual feedback, auditory feedback, or tactile feedback); and can be in any form (including acoustic input, voice input, or tactile input to receive input from the user.
  • the systems and techniques described herein may be implemented on a computing system that includes back-end components (eg, as a data server), or a computing system that includes middleware components (eg, an application server), or a computing system that includes front-end components (eg, a user computer having a graphical user interface or web browser through which a user may interact with implementations of the systems and techniques described herein), or including such backend components, middleware components, Or any combination of front-end components in a computing system.
  • the components of the system may be interconnected by any form or medium of digital data communication (eg, a communication network). Examples of communication networks include: Local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.
  • a computer system can include clients and servers.
  • Clients and servers are generally remote from each other and usually 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Software Systems (AREA)
  • Human Computer Interaction (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

一种文件处理方法、装置、电子设备和存储介质，涉及云计算领域。具体实现方案为：基于目标节点接收到的文件操作请求所对应的容器调度组信息，确定目标节点中与容器调度组信息对应的容器（S110）；利用目标节点的节点目录，确定容器的文件路径（S120）；根据文件操作请求，对文件路径下的文件进行操作（S130）。根据上述技术方案，可以降低容器集群管理系统的运维要求并具有更好的兼容性。

Description

文件处理方法、装置、电子设备和存储介质
本申请要求于2021年2月20日提交的申请号为202110194453.2、发明名称为“文件处理方法、装置、电子设备和存储介质”的中国专利申请的优先权，该在先申请的内容通过引用结合在本申请中。
技术领域
本公开涉及计算机技术领域，尤其涉及云计算领域。
背景技术
随着云计算中容器技术的日益普及，用于执行容器的创建与部署的容器集群管理系统，例如Kubernetes，也得到了广泛的应用。在实际的部署运维中，用户常常有查看系统内部文件和复制系统内部文件到外部以备份和分析的需求。常见的查看和备份的文件类型包括运行日志、运行数据等。
发明内容
本公开提供了一种文件处理方法、装置、电子设备和存储介质。
根据本公开的一方面，提供了一种文件处理方法，包括：
基于目标节点接收到的文件操作请求所对应的容器调度组信息，确定目标节点中与容器调度组信息对应的容器；
利用目标节点的节点目录，确定容器的文件路径；
根据文件操作请求，对文件路径下的文件进行操作。
根据本公开的另一方面，提供了一种文件处理装置，包括：
容器确定模块，用于基于目标节点接收到的文件操作请求所对应的容器调度组信息，确定目标节点中与容器调度组信息对应的容器；
路径确定模块，用于利用目标节点的节点目录，确定容器的文件路径；
文件操作模块，用于根据文件操作请求，对文件路径下的文件进行操作。
根据本公开的另一方面，提供了一种电子设备，包括：
至少一个处理器；以及
与该至少一个处理器通信连接的存储器；其中，
该存储器存储有可被该至少一个处理器执行的指令，该指令被该至少一个处理器执行，以使该至少一个处理器能够执行本公开任一实施例中的方法。
根据本公开的另一方面，提供了一种存储有计算机指令的非瞬时计算机可读存储介质，该计算机指令用于使计算机执行本公开任一实施例中的方法。
根据本公开的另一方面，提供了一种计算机程序产品，包括计算机程序，该计算机程序被处理器执行时实现本公开任一实施例中的方法。
本公开实施例提供了目标节点接收到文件操作请求时的文件处理方法，基于容器调度组信息定位到具体的容器，利用节点目录确定容器的文件路径，从而能够对容器集群管理系统中的文件进行操作，免去了对专有命令的使用，降低运维要求并具有更好的兼容性。
应当理解，本部分所描述的内容并非旨在标识本公开的实施例的关键或重要特征，也不用于限制本公开的范围。本公开的其它特征将通过以下的说明书而变得容易理解。
附图说明
附图用于更好地理解本方案，不构成对本公开的限定。其中：
图1是本公开一个实施例提供的文件处理方法的示意图；
图2是本公开另一个实施例提供的文件处理方法的示意图；
图3是本公开一个实施例提供的文件处理装置的示意图；
图4是本公开另一个实施例提供的文件处理装置的示意图；
图5是用来实现本公开实施例的文件方法的电子设备的框图。
具体实施方式
以下结合附图对本公开的示范性实施例做出说明，其中包括本公开实施例的各种细节以助于理解，应当将它们认为仅仅是示范性的。因此，本领域普通技术人员应当认识到，可以对这里描述的实施例做出各种改变和修改，而不会背离本公开的范围和精神。同样，为了清楚和简明，以下的描述中省略了对公知功能和结构的描述。
图1示出了本公开一个实施例提供的文件操作方法的示意图。如图1所示，该方法可以包括：
步骤S110，基于目标节点接收到的文件操作请求所对应的容器调度组信息，确定目标节点中与容器调度组信息对应的容器；
步骤S120，利用目标节点的节点目录，确定容器的文件路径；
步骤S130，根据文件操作请求，对文件路径下的文件进行操作。
示例性地，目标节点可以是容器集群管理系统中的节点(Node)。容器集群管理系统，例如Kubernetes，是容器的编排工具，支持自动化部署和管理容器化应用。相对于虚拟机，容器能快速部署，且容器与底层设施、机器文件系统解耦，因此它能在不同云、不同版本操作系统间进行迁移。节点是容器集群管理系统中的硬件单元或者说单个机器，是容器的宿主机。容器调度组，或者称为Pod，是容器集群管理系统进行创建、调度和管理容器的最小单位，是多个容器的集合，提供了比容器更高层次的抽象，使得部署和管理更加灵活。举例而言，Kubernetes不直接调度容器，而是将 容器封装到Pod中，相同Pod中的容器将共享相同的名称空间和本地网络，且容器间可以很容易地在相同的pod中进行通信。
本公开实施例的上述步骤S11至S13，可以由目标节点执行，具体而言，可以由目标节点中的文件管理代理模块(Agent)执行。示例性地，可以在Kubernetes的每个节点中均设置文件管理代理模块，发起文件操作请求的请求设备可以将文件操作请求发送至分发服务模块，由分发服务模块确定目标节点，将文件操作请求发送至目标节点。示例性地，文件操作请求所对应的容器调度组信息，可以包含在文件操作请求中，也可以根据文件操作请求中的相关信息，通过查询Kubernetes的元数据信息集合得到。文件操作请求所请求操作的文件可以包括运行日志、运行数据等。
根据上述步骤S11，文件管理代理模块在接收到文件操作请求例如文件查看、复制请求等的情况下，可以将该请求对应的容器调度组信息，对应到本节点中具体的容器(Container)上。这里的容器可以指创建后按照节点中容器运行时的标准运行的容器，其中，容器运行时为用于执行容器并在节点上管理容器镜像的软件工具。在本公开的一些实施例中，容器运行时可以使用Docker，相应地，节点中具体的容器也可以称为Docker Container、Docker容器。
在确定具体的容器后，可以利用目标节点的节点目录找到待操作的文件路径。这里，节点目录可指用于反映整个容器的文件系统的目录，或者说路径集合。在确定文件路径后，可以根据文件操作请求，对文件路径下的文件进行操作，例如查看或者复制。
本公开实施例中，提供了目标节点接收到文件操作请求时的文件处理方法，基于容器调度组信息定位到具体的容器，利用节点目录确定容器的文件路径，从而能够对容器集群管理系统中的文件进行操作，免去了对专有的文件操作命令例如tar命令的使用，降低运维要求并具有更好的兼容性。并且，通过设置文件管理代理模块作为专用的管理节点中Pod文件的模块，可进一步提高兼容性，可以对接不同用户系统中显存的权限方案以及堡垒机文件管理方案。
在一种示例性的实施方式中，上述方法还可以包括：
在容器集群管理系统创建的容器调度组对应于目标节点的情况下，在目标节点上创建容器，并获取容器的文件视图以及容器调度组的数据卷挂载目录；
将容器的文件视图以及容器调度组的数据卷挂载目录挂载在目标节点的节点目录中。
上述步骤可以由目标节点执行，具体而言，可以由目标节点中的容器运行时例如Docker执行。例如，在Kubernetes中，容器运行在节点上。当底层的容器运行时采用Docker时，Kubernetes每次创建Pod后，均可以在Pod对应的节点上创建Pod的容器，该容器最终按照Docker的标准运行。
根据上述实施方式，在创建容器时，底层的容器运行时例如Docker为容器确定文件视图。示例性地，可以以联合挂载的方式为容器提供一个完整的文件视图。这个联合挂载后的文件视图，会挂载到目标节点的节点目录上，使得目标节点的节点目录可以反映容器的文件系统。
并且，容器运行时会挂载容器调度组需要的一些数据卷(Volume)，例如使用Mount命令挂载Pod所需的数据卷，得到数据卷挂载目录。该数据卷挂载目录同样存在节点目录中。
根据上述实施方式，在创建容器时，将容器的文件视图以及容器调度组的数据卷挂载目录挂载在目标节点的节点目录中，因此，节点目录可以反映节点中所有容器的文件系统，能够通过节点目录确定操作文件所需的完整信息，有利于实现在节点中便捷地操作文件。
示例性地，上述步骤S120中，利用目标节点的节点目录，确定容器的文件路径，包括：
根据容器，在目标节点的节点目录中查找对应的文件视图和数据卷挂载目录。
由于节点目录中挂载了各容器的文件视图和容器调度组的数据卷挂载目录，因此，根据确定的容器，可以在节点目录中查找到对应的文件视图和数据卷挂载目录。例如，在节点目录中，通过Docker Container找到联合挂载的文件路径以及Mount命令挂载的文件路径。从而利用对应的文件视图和数据卷挂载目录，准确定位文件，在节点操作文件，满足用户需求。
在一种示例性的实施方式中，上述步骤S110，基于目标节点接收到的文件操作请求所对应的容器调度组信息，确定目标节点中与容器调度组信息对应的容器，包括：
基于目标节点接收到的文件操作请求所对应的容器调度组信息，进行容器调度组到容器管理工具之间的容器逻辑名称转换，得到容器名称信息；
基于容器名称信息，确定与容器调度组信息对应的容器。
根据上述实施方式，文件管理代理模块还用于实现容器调度组到容器管理工具之间的容器逻辑名称转换，例如，Kubernetes Pod的容器到Docker容器的逻辑名称转换，以得到Docker容器的名称信息，使得节点可以将Pod信息，对应到节点中具体的Docker容器上。
在一种示例性的实施方式中，上述步骤S130中，根据文件操作请求，对文件路径下的文件进行操作，包括：
利用本地文件服务，对文件路径下的文件执行与文件操作请求指定的操作类型对应的操作。
其中，本地文件服务，例如是Fileserver。使用Fileserver可以根据文件路径直接操作节点联合挂载的目录文件。文件操作请求指定的操作类型可以包括读取、复制、删除等。
在上述实施方式中，直接通过本地文件服务如Fileserver操作文件，具 备更好的传输性能。
在一种示例性的实施方式中，上述方法还可以包括：
分发服务模块在接收到文件操作请求的情况下，在容器集群管理系统的元数据信息集合中查询与文件操作请求中的元数据信息对应的容器调度组信息，并根据容器调度组信息定位到目标节点，将文件操作请求发送至目标节点。
图2示出了根据上述实施方式，Kubernetes的底层容器运行时为docker时，对pod文件进行操作的示意图。如图2所示，Kubernetes 200包括多个节点220。请求设备向分发服务模块(Dispenser)210发送针对某个pod文件的文件操作请求。分发服务模块210接收文件操作请求，并定位到pod所在的节点220，与该节点220中的文件管理代理模块221建立连接。文件管理代理模块221与分发服务模块210建立连接并收到针对pod文件的文件操作请求后，将文件操作请求对应的pod信息，对应到本节点具体的Docker容器222上。利用节点目录223，通过Docker容器222找到联合挂载的文件路径以及Mount的文件路径。再基于这些文件路径，通过Fileserver处理对文件的请求。Fileserver直接操作节点联合挂载的目录文件。
通过设置分发服务模块，利用分发服务模块查询容器集群管理系统的元数据信息集合，可以定位到相关的容器调度组所在的目标节点，因此，能够直接在容器调度组所在的目标节点中确定文件路径，相比使用专有命令进入各节点，具有更高的效率。
本公开实施例提供了目标节点接收到文件操作请求时的文件处理方法，可以应用于云原生微服务应用平台，例如Stack平台。基于容器调度组信息定位到具体的容器，利用节点目录确定容器的文件路径，从而能够对容器集群管理系统中的文件进行操作，免去了对专有命令的使用，降低运维要求并具有更好的兼容性。
作为上述各方法的实现，本公开实施例还提供一种文件处理装置。图3示出了本公开实施例提供的文件处理装置的示意图。如图3所示，该装置包括：
容器确定模块310，用于基于目标节点接收到的文件操作请求所对应的容器调度组信息，确定目标节点中与容器调度组信息对应的容器；
路径确定模块320，用于利用目标节点的节点目录，确定容器的文件路径；
文件操作模块330，用于根据文件操作请求，对文件路径下的文件进行操作。
示例性地，如图4所示，文件处理装置还可以包括：
容器创建模块410，用于在容器集群管理系统创建的容器调度组对应于目标节点的情况下，在目标节点上创建容器，并获取容器的文件视图以及容器调度组的数据卷挂载目录；
目录挂载模块420，用于将容器的文件视图以及容器调度组的数据卷挂载目录挂载在目标节点的节点目录中。
示例性地，路径确定模块320用于：
根据容器，在目标节点的节点目录中查找对应的文件视图和数据卷挂载目录。
示例性地，如图4所示，容器确定模块310，包括：
转换单元311，用于基于目标节点接收到的文件操作请求所对应的容器调度组信息进行容器调度组到容器管理工具的逻辑名称转换，得到容器名称信息；
确定单元312，用于基于容器名称信息，确定与容器调度组信息对应的容器。
示例性地，文件操作模块330用于：
利用本地文件服务，对文件路径下的文件执行与文件操作请求指定的操作类型对应的操作。
示例性地，如图4所示，文件处理装置还可以包括：
分发服务模块430，用于在接收到文件操作请求的情况下，在容器集群管理系统的元数据信息集合中查询与文件操作请求中的元数据信息对应的容器调度组信息，并根据容器调度组信息定位到目标节点，将文件操作请求发送至目标节点。
本公开实施例提供的文件处理装置，能够实现本公开实施例提供的文件处理方法，具备相应的有益效果。
根据本公开的实施例，本公开还提供了一种电子设备、一种可读存储介质和一种计算机程序产品。
图5示出了可以用来实施本公开的实施例的示例电子设备500的示意性框图。电子设备旨在表示各种形式的数字计算机，诸如，膝上型计算机、台式计算机、工作台、个人数字助理、服务器、刀片式服务器、大型计算机、和其它适合的计算机。电子设备还可以表示各种形式的移动装置，诸如，个人数字处理、蜂窝电话、智能电话、可穿戴设备和其它类似的计算装置。本文所示的部件、它们的连接和关系、以及它们的功能仅仅作为示例，并且不意在限制本文中描述的和/或要求的本公开的实现。
如图5所示，电子设备500包括计算单元501，其可以根据存储在只读存储器(ROM)502中的计算机程序或者从存储单元508加载到随机访问存储器(RAM)503中的计算机程序来执行各种适当的动作和处理。在RAM 503中，还可存储电子设备500操作所需的各种程序和数据。计算单元501、ROM 502以及RAM 503通过总线504彼此相连。输入输出(I/O)接口505也连接至总线504。
电子设备500中的多个部件连接至I/O接口505，包括：输入单元506，例如键盘、鼠标等；输出单元507，例如各种类型的显示器、扬声器等； 存储单元508，例如磁盘、光盘等；以及通信单元509，例如网卡、调制解调器、无线通信收发机等。通信单元509允许电子设备500通过诸如因特网的计算机网络和/或各种电信网络与其他设备交换信息/数据。
计算单元501可以是各种具有处理和计算能力的通用和/或专用处理组件。计算单元501的一些示例包括但不限于中央处理单元(CPU)、图形处理单元(GPU)、各种专用的人工智能(AI)计算芯片、各种运行机器学习模型算法的计算单元、数字信号处理器(DSP)、以及任何适当的处理器、控制器、微控制器等。计算单元501执行上文所描述的各个方法和处理，例如文件处理方法。例如，在一些实施例中，文件处理方法可被实现为计算机软件程序，其被有形地包含于机器可读介质，例如存储单元508。在一些实施例中，计算机程序的部分或者全部可以经由ROM 502和/或通信单元509而被载入和/或安装到电子设备500上。当计算机程序加载到RAM503并由计算单元501执行时，可以执行上文描述的文件处理方法的一个或多个步骤。备选地，在其他实施例中，计算单元501可以通过其他任何适当的方式(例如，借助于固件)而被配置为执行文件处理方法。
本文中以上描述的系统和技术的各种实施方式可以在数字电子电路系统、集成电路系统、场可编程门阵列(FPGA)、专用集成电路(ASIC)、专用标准产品(ASSP)、芯片上系统的系统(SOC)、负载可编程逻辑设备(CPLD)、计算机硬件、固件、软件、和/或它们的组合中实现。这些各种实施方式可以包括：实施在一个或者多个计算机程序中，该一个或者多个计算机程序可在包括至少一个可编程处理器的可编程系统上执行和/或解释，该可编程处理器可以是专用或者通用可编程处理器，可以从存储系统、至少一个输入装置、和至少一个输出装置接收数据和指令，并且将数据和指令传输至该存储系统、该至少一个输入装置、和该至少一个输出装置。
用于实施本公开的方法的程序代码可以采用一个或多个编程语言的任何组合来编写。这些程序代码可以提供给通用计算机、专用计算机或其他可编程数据处理装置的处理器或控制器，使得程序代码当由处理器或控制器执行时使流程图和/或框图中所规定的功能/操作被实施。程序代码可以完全在机器上执行、部分地在机器上执行，作为独立软件包部分地在机器上执行且部分地在远程机器上执行或完全在远程机器或服务器上执行。
在本公开的上下文中，机器可读介质可以是有形的介质，其可以包含或存储以供指令执行系统、装置或设备使用或与指令执行系统、装置或设备结合地使用的程序。机器可读介质可以是机器可读信号介质或机器可读储存介质。机器可读介质可以包括但不限于电子的、磁性的、光学的、电磁的、红外的、或半导体系统、装置或设备，或者上述内容的任何合适组合。机器可读存储介质的更具体示例会包括基于一个或多个线的电气连接、便携式计算机盘、硬盘、随机存取存储器(RAM)、只读存储器(ROM)、可擦除可编程只读存储器(EPROM或快闪存储器)、光纤、便捷式紧凑盘 只读存储器(CD-ROM)、光学储存设备、磁储存设备、或上述内容的任何合适组合。
为了提供与用户的交互，可以在计算机上实施此处描述的系统和技术，该计算机具有：用于向用户显示信息的显示装置(例如，CRT(阴极射线管)或者LCD(液晶显示器)监视器)；以及键盘和指向装置(例如，鼠标或者轨迹球)，用户可以通过该键盘和该指向装置来将输入提供给计算机。其它种类的装置还可以用于提供与用户的交互；例如，提供给用户的反馈可以是任何形式的传感反馈(例如，视觉反馈、听觉反馈、或者触觉反馈)；并且可以用任何形式(包括声输入、语音输入、或者触觉输入来接收来自用户的输入。
可以将此处描述的系统和技术实施在包括后台部件的计算系统(例如，作为数据服务器)、或者包括中间件部件的计算系统(例如，应用服务器)、或者包括前端部件的计算系统(例如，具有图形用户界面或者网络浏览器的用户计算机，用户可以通过该图形用户界面或者该网络浏览器来与此处描述的系统和技术的实施方式交互)、或者包括这种后台部件、中间件部件、或者前端部件的任何组合的计算系统中。可以通过任何形式或者介质的数字数据通信(例如，通信网络)来将系统的部件相互连接。通信网络的示例包括：局域网(LAN)、广域网(WAN)和互联网。
计算机系统可以包括客户端和服务器。客户端和服务器一般远离彼此并且通常通过通信网络进行交互。通过在相应的计算机上运行并且彼此具有客户端-服务器关系的计算机程序来产生客户端和服务器的关系。
应该理解，可以使用上面所示的各种形式的流程，重新排序、增加或删除步骤。例如，本公开中记载的各步骤可以并行地执行也可以顺序地执行也可以不同的次序执行，只要能够实现本公开公开的技术方案所期望的结果，本文在此不进行限制。
上述具体实施方式，并不构成对本公开保护范围的限制。本领域技术人员应该明白的是，根据设计要求和其他因素，可以进行各种修改、组合、子组合和替代。任何在本公开的精神和原则之内所作的修改、等同替换和改进等，均应包含在本公开保护范围之内。

Claims (15)

  1. 一种文件处理方法，包括：
    基于目标节点接收到的文件操作请求所对应的容器调度组信息，确定所述目标节点中与所述容器调度组信息对应的容器；
    利用所述目标节点的节点目录，确定所述容器的文件路径；
    根据所述文件操作请求，对所述文件路径下的文件进行操作。
  2. 根据权利要求1所述的方法，还包括：
    在容器集群管理系统创建的容器调度组对应于所述目标节点的情况下，在所述目标节点上创建容器，并获取所述容器的文件视图以及所述容器调度组的数据卷挂载目录；
    将所述容器的文件视图以及所述容器调度组的数据卷挂载目录挂载在所述目标节点的节点目录中。
  3. 根据权利要求2所述的方法，其中，所述利用所述目标节点的节点目录，确定所述容器的文件路径，包括：
    根据所述容器，在所述目标节点的节点目录中查找对应的文件视图和数据卷挂载目录。
  4. 根据权利要求1-3中任一项所述的方法，其中，所述基于目标节点接收到的文件操作请求所对应的容器调度组信息，确定所述目标节点中与所述容器调度组信息对应的容器，包括：
    基于目标节点接收到的文件操作请求所对应的容器调度组信息，进行容器调度组到容器管理工具之间的容器逻辑名称转换，得到容器名称信息；
    基于所述容器名称信息，确定与所述容器调度组信息对应的容器。
  5. 根据权利要求1-3中任一项所述的方法，其中，所述根据所述文件操作请求，对所述文件路径下的文件进行操作，包括：
    利用本地文件服务，对所述文件路径下的文件执行与所述文件操作请求指定的操作类型对应的操作。
  6. 根据权利要求1-3中任一项所述的方法，还包括：
    分发服务模块在接收到文件操作请求的情况下，在容器集群管理系统的元数据信息集合中查询与所述文件操作请求中的元数据信息对应的容器调度组信息，并根据所述容器调度组信息定位到所述目标节点，将所述文件操作请求发送至所述目标节点。
  7. 一种文件处理装置，包括：
    容器确定模块，用于基于目标节点接收到的文件操作请求所对应的容器调度组信息，确定所述目标节点中与所述容器调度组信息对应的容器；
    路径确定模块，用于利用所述目标节点的节点目录，确定所述容器的文件路径；
    文件操作模块，用于根据所述文件操作请求，对所述文件路径下的文件进行操作。
  8. 根据权利要求7所述的装置，还包括：
    容器创建模块，用于在容器集群管理系统创建的容器调度组对应于所述目标节点的情况下，在所述目标节点上创建容器，并获取所述容器的文件视图以及所述容器调度组的数据卷挂载目录；
    目录挂载模块，用于将所述容器的文件视图以及所述容器调度组的数据卷挂载目录挂载在所述目标节点的节点目录中。
  9. 根据权利要求8所述的装置，其中，所述路径确定模块用于：
    根据所述容器，在所述目标节点的节点目录中查找对应的文件视图和数据卷挂载目录。
  10. 根据权利要求7-9中任一项所述的装置，其中，所述容器确定模块，包括：
    转换单元，用于基于目标节点接收到的文件操作请求所对应的容器调度组信息进行容器调度组到容器管理工具的逻辑名称转换，得到容器名称信息；
    确定单元，用于基于所述容器名称信息，确定与所述容器调度组信息对应的容器。
  11. 根据权利要求7-9中任一项所述的装置，其中，所述文件操作模块用于：
    利用本地文件服务，对所述文件路径下的文件执行与所述文件操作请求指定的操作类型对应的操作。
  12. 根据权利要求7-9中任一项所述的装置，还包括：
    分发服务模块，用于在接收到文件操作请求的情况下，在容器集群管理系统的元数据信息集合中查询与所述文件操作请求中的元数据信息对应的容器调度组信息，并根据所述容器调度组信息定位到所述目标节点，将所述文件操作请求发送至所述目标节点。
  13. 一种电子设备，其特征在于，包括：
    至少一个处理器；以及
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行权利要求1-6中任一项所述的方法。
  14. 一种存储有计算机指令的非瞬时计算机可读存储介质，其特征在于，所述计算机指令用于使计算机执行权利要求1-6中任一项所述的方法。
  15. 一种计算机程序产品，包括计算机程序，该计算机程序在被处理器执行时实现根据权利要求1-6中任一项所述的方法。
PCT/CN2021/108012 2021-02-20 2021-07-23 文件处理方法、装置、电子设备和存储介质 WO2022174553A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP21844172.3A EP4075269A4 (en) 2021-07-23 File processing method and apparatus, electronic device, and storage medium
KR1020227004988A KR20220026603A (ko) 2021-02-20 2021-07-23 파일 처리 방법, 장치, 전자 기기 및 저장 매체
JP2022513682A JP2023518136A (ja) 2021-02-20 2021-07-23 ファイル処理方法、装置、電子デバイス、記憶媒体、及びプログラム
US17/641,370 US20240054107A1 (en) 2021-02-20 2021-07-23 File processing method, electronic device, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110194453.2A CN112905537B (zh) 2021-02-20 2021-02-20 文件处理方法、装置、电子设备和存储介质
CN202110194453.2 2021-02-20

Publications (1)

Publication Number Publication Date
WO2022174553A1 true WO2022174553A1 (zh) 2022-08-25

Family

ID=76124181

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/108012 WO2022174553A1 (zh) 2021-02-20 2021-07-23 文件处理方法、装置、电子设备和存储介质

Country Status (2)

Country Link
CN (1) CN112905537B (zh)
WO (1) WO2022174553A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112905537B (zh) * 2021-02-20 2022-09-02 北京百度网讯科技有限公司 文件处理方法、装置、电子设备和存储介质
CN114064594B (zh) * 2021-11-22 2023-09-22 马上消费金融股份有限公司 数据处理方法和装置
CN115333836B (zh) * 2022-08-12 2023-05-30 北京百度网讯科技有限公司 验证文件的处理方法、装置、电子设备及可读存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109491859A (zh) * 2018-10-16 2019-03-19 华南理工大学 针对Kubernetes集群中容器日志的收集方法
CN110704376A (zh) * 2019-09-04 2020-01-17 广东浪潮大数据研究有限公司 日志文件保存方法及装置
US20200057618A1 (en) * 2018-08-14 2020-02-20 Hyperblox Inc. Software Acceleration Platform for Supporting Decomposed, On-Demand Network Services
CN111046011A (zh) * 2019-11-27 2020-04-21 中科曙光国际信息产业有限公司 日志收集方法、系统、节点、电子设备及可读存储介质
CN111352691A (zh) * 2018-12-21 2020-06-30 北京神州泰岳软件股份有限公司 一种日志采集方法和系统
CN112905537A (zh) * 2021-02-20 2021-06-04 北京百度网讯科技有限公司 文件处理方法、装置、电子设备和存储介质

Family Cites Families (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7739318B2 (en) * 2005-06-20 2010-06-15 Netapp, Inc. System and method for maintaining mappings from data containers to their parent directories
US7707193B2 (en) * 2005-09-22 2010-04-27 Netapp, Inc. System and method for verifying and restoring the consistency of inode to pathname mappings in a filesystem
CN106383852B (zh) * 2016-08-30 2019-11-05 中国民生银行股份有限公司 基于Docker容器的日志获取方法和装置
CN106789303B (zh) * 2016-12-29 2020-04-03 北京奇艺世纪科技有限公司 一种容器日志采集方法及装置
CN107169016B (zh) * 2017-03-31 2020-01-10 北京奇艺世纪科技有限公司 一种应用程序日志采集方法及装置
US10678935B2 (en) * 2017-04-11 2020-06-09 Nicira, Inc. Identifying container file events for providing container security
CN108845917A (zh) * 2018-04-09 2018-11-20 东峡大通（北京）管理咨询有限公司 容器内文件日志挂载模块、系统和方法
CN108681434A (zh) * 2018-05-24 2018-10-19 中科边缘智慧信息科技（苏州）有限公司 一种容器持久存储挂载方法
US20200125533A1 (en) * 2018-10-22 2020-04-23 Outcold Solutions LLC System and method for locating a file created by a process running in a linux container
CN111367615B (zh) * 2018-12-26 2023-08-18 卓望数码技术（深圳）有限公司 方便容器实例调度的方法、装置、设备及存储介质
CN109818934B (zh) * 2018-12-29 2021-10-22 达闼机器人有限公司 一种自动化日志处理的方法、装置及计算设备
CN110012087B (zh) * 2019-03-28 2022-02-01 中国工商银行股份有限公司 数据处理系统及数据处理方法
CN109977093A (zh) * 2019-04-04 2019-07-05 中科创达(重庆)汽车科技有限公司 基于lxc的多虚拟系统查看容器日志的方法及装置
CN110659246B (zh) * 2019-09-26 2022-05-03 北京百度网讯科技有限公司 基于容器的文件挂载方法、装置及电子设备
CN110688201B (zh) * 2019-09-29 2022-06-28 重庆小雨点小额贷款有限公司 一种日志管理方法及相关设备
CN110888852A (zh) * 2019-11-11 2020-03-17 北京宝兰德软件股份有限公司 一种挂载宿主机目录到容器环境中的方法及装置
CN110955578A (zh) * 2019-11-26 2020-04-03 深圳市信联征信有限公司 基于宿主机的日志收集方法、装置、计算机设备及存储介质
CN111274091B (zh) * 2020-01-17 2024-01-09 北京达佳互联信息技术有限公司 日志的处理方法、装置、计算机设备和存储介质
CN111309546A (zh) * 2020-01-19 2020-06-19 苏州浪潮智能科技有限公司 一种集群容器内文本日志的采集方法、系统及存储介质
CN111488320A (zh) * 2020-04-17 2020-08-04 上海思询信息科技有限公司 一种清理Kubernetes中业务应用程序日志的方法
CN111782339B (zh) * 2020-06-28 2024-04-12 京东科技控股股份有限公司 一种容器创建方法、装置、电子设备及存储介质
CN111913665B (zh) * 2020-07-30 2023-11-24 北京星辰天合科技股份有限公司 存储卷的挂载方法及装置、电子设备
CN111966305B (zh) * 2020-10-22 2021-02-09 腾讯科技（深圳）有限公司 持久卷分配方法、装置、计算机设备和存储介质
CN112379828B (zh) * 2020-10-27 2024-03-19 华云数据控股集团有限公司 基于动态文件系统的容器创建方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200057618A1 (en) * 2018-08-14 2020-02-20 Hyperblox Inc. Software Acceleration Platform for Supporting Decomposed, On-Demand Network Services
CN109491859A (zh) * 2018-10-16 2019-03-19 华南理工大学 针对Kubernetes集群中容器日志的收集方法
CN111352691A (zh) * 2018-12-21 2020-06-30 北京神州泰岳软件股份有限公司 一种日志采集方法和系统
CN110704376A (zh) * 2019-09-04 2020-01-17 广东浪潮大数据研究有限公司 日志文件保存方法及装置
CN111046011A (zh) * 2019-11-27 2020-04-21 中科曙光国际信息产业有限公司 日志收集方法、系统、节点、电子设备及可读存储介质
CN112905537A (zh) * 2021-02-20 2021-06-04 北京百度网讯科技有限公司 文件处理方法、装置、电子设备和存储介质

Also Published As

Publication number Publication date
CN112905537A (zh) 2021-06-04
CN112905537B (zh) 2022-09-02

Similar Documents

Publication Publication Date Title
WO2022174553A1 (zh) 文件处理方法、装置、电子设备和存储介质
US8170981B1 (en) Computer method and system for combining OLTP database and OLAP database environments
CN110100228A (zh) 利用云对象存储的文件系统层次结构的高效增量备份和恢复
US20120047107A1 (en) System and method for implementing on demand cloud database
JP2006012155A (ja) ユーザ定義型の指定されたメンバを遅延フェッチするシステムおよび方法
US11334526B2 (en) Handling previews of remotely stored content objects
US11216421B2 (en) Extensible streams for operations on external systems
US20070174360A1 (en) Storage system embedding database
WO2023093245A1 (zh) 基于分布式文件系统的元数据查询方法、设备和存储介质
WO2015094195A1 (en) Transaction query engine
US11983184B2 (en) Multi-tenant, metadata-driven recommendation system
JP2024521730A (ja) Ｓｑｌクエリを加速するための決定的分散キャッシュのための技術
US20170228383A1 (en) Active archive bridge
US11461274B2 (en) Processing streams on external data sources
EP4075269A1 (en) File processing method and apparatus, electronic device, and storage medium
US20240054107A1 (en) File processing method, electronic device, and storage medium
US20220075830A1 (en) Resumable ordered recursive traversal of an unordered directory tree
US11178216B2 (en) Generating client applications from service model descriptions
US9471587B2 (en) Remote enumeration of a directory
CN107423375B (zh) 应用程序搜索方法和装置
US11030241B2 (en) Query usage based organization for very large databases
US20240028593A1 (en) In-memory graph query engine with persisted storage
US11914610B1 (en) Multi-way data store conversion
US20240202075A1 (en) Dynamic slicing of filesystem data with application awareness
US11379147B2 (en) Method, device, and computer program product for managing storage system

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2021844172

Country of ref document: EP

Effective date: 20220126

ENP Entry into the national phase

Ref document number: 20227004988

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2022513682

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 17641370

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE