CN113535321A - Virtualized container management method, system and storage medium - Google Patents
Virtualized container management method, system and storage medium Download PDFInfo
- Publication number
- CN113535321A CN113535321A CN202010294730.2A CN202010294730A CN113535321A CN 113535321 A CN113535321 A CN 113535321A CN 202010294730 A CN202010294730 A CN 202010294730A CN 113535321 A CN113535321 A CN 113535321A
- Authority
- CN
- China
- Prior art keywords
- container
- storage layer
- operation request
- stack
- container storage
- 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.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 43
- 238000000034 method Methods 0.000 claims description 19
- 238000013507 mapping Methods 0.000 claims description 10
- 230000004069 differentiation Effects 0.000 claims description 6
- 230000009471 action Effects 0.000 claims description 4
- 238000004590 computer program Methods 0.000 claims description 4
- 238000005516 engineering process Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 7
- 230000008859 change Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 238000002955 isolation Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 230000004927 fusion Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 238000004140 cleaning Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000011176 pooling Methods 0.000 description 1
- 238000007781 pre-processing Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
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
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
-
- 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/45562—Creating, deleting, cloning virtual machine instances
-
- 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/4557—Distribution of virtual machine instances; Migration and load balancing
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a virtualized container management method, a system and a storage medium, wherein the virtualized container management method comprises the following steps: the container client sends a container operation request to the container service; the container service preprocesses the container operation request, schedules the container operation request and distributes the preprocessed container operation request to a container engine; the container engine establishes a container execution unit according to the received preprocessed container operation request; the container execution unit executes corresponding container operation on the container storage layer stack, a current container storage layer in the container storage layer stack is established based on a previous container storage layer stack, and the stack bottom layer of the container storage layer stack is a mirror image base layer.
Description
Technical Field
The present application relates to a virtualization network technology, and for example, to a virtualized container management method, system, and storage medium.
Background
Virtualization technology is an important technology of cloud computing, and is mainly used for pooling of physical resources, including servers, networks, and storage, so as to be flexibly allocated to users. The virtualization container technology is a lightweight virtualization technology, and can run applications and dependent items thereof in a resource isolation process. The virtualization container technology enables developers to package their applications and dependency packages into a lightweight, portable virtual container, which is then distributed to relevant servers for deployment.
A layered storage mode is adopted in the container, but a plurality of containers are mutually isolated, each container is based on the same mirror image base layer, storage layers of different containers are mutually isolated, and data has no dependency relationship. Therefore, the storage layer change of any container cannot be recovered through the storage layers of other containers, the storage layer isolation among the containers causes that a plurality of containers occupy excessive storage space, storage layer multiplexing and storage layer data backtracking cannot be performed among the containers, and linkage operation, deployment and recovery cannot be performed on the containers.
Disclosure of Invention
The application provides a virtualized container management method, a virtualized container management system and a virtualized container management storage medium, which are used for realizing data fusion of container storage layers with different spatial dimensions and expanding the operation freedom degree and the deployment freedom degree of a virtualized container.
In a first aspect, an embodiment of the present application provides a virtualized container management method, including: the container client sends a container operation request to the container service; the container service preprocesses the container operation request, schedules the container operation request and distributes the preprocessed container operation request to a container engine; the container engine establishes a container execution unit according to the received preprocessed container operation request; the container execution unit executes corresponding container operation on the container storage layer stack, a current container storage layer in the container storage layer stack is established based on a previous container storage layer stack, and the stack bottom layer of the container storage layer stack is a mirror image base layer.
In a second aspect, an embodiment of the present application provides a virtualized container management system, including: the system comprises a container client, a container service, a container engine, a container execution unit, a container storage and a container driver; the container client is configured to send a container operation request to the container service; the container service is configured to preprocess the container operation request, schedule the container operation request, and distribute the preprocessed container operation request to the container engine; the container engine is configured to create a container execution unit according to the received preprocessed container operation request; the container execution unit is configured to execute corresponding container operation on the container storage layer stack, a current container storage layer in the container storage layer stack is established based on a previous container storage layer stack, and a stack bottom layer of the container storage layer stack is a mirror image base layer; the container storage is arranged to store the stack layers of the container storage tiers in a stack with a mirror image base layer as a bottom layer of the stack; the container driver is configured to perform a corresponding container operation on the container storage layer stack according to a driving of the container execution unit.
In a third aspect, an embodiment of the present application provides a computer-readable storage medium, and when executed by a processor, the program implements the virtualized container management method of the first aspect.
Drawings
FIG. 1 is a block diagram illustrating a virtualized container management system according to an embodiment;
fig. 2 is a schematic structural diagram of a container storage layer stack in the virtualized container management system according to an embodiment of the present disclosure;
FIG. 3 is a flowchart of a virtualized container management method according to an embodiment;
fig. 4 is a block diagram of a container task system of a virtualized container management method according to an embodiment.
Detailed Description
Hereinafter, embodiments of the present application will be described in detail with reference to the accompanying drawings.
The virtualized container technology involves images, containers, and repositories. The mirror belongs to a static storage entity of a virtualized container, the container is an entity when the mirror runs, the container can be created, started, suspended, stopped, deleted and the like, and the warehouse is used for storing and distributing the mirror in a centralized mode. The essence of a container is a process, which is distinct from a process that is executed directly at the host, the container process running in a separate namespace that belongs to itself. In the virtualization container technology, images are stored in a layered mode. As an entity in mirror operation, the container is also stored in a layered manner. Each container runs on a mirror-based layer, on top of which a storage layer for the current container is created. The life cycle of the container storage layer is the same as that of the container, and when the container is lost, the container storage layer is also lost. Thus, any information stored in the storage layer of the container is lost as the container is deleted.
The embodiment of the application provides a virtualized container management method and a virtualized container management system, so as to solve the above problems.
Fig. 1 is a schematic structural diagram of a virtualized container management system according to an embodiment, and as shown in fig. 1, the virtualized container management system according to this embodiment includes:
a container client (client)11, a container service (server)12, a container engine (engine)13, a container execution unit (job)14, a container store (graph)15, and a container driver (driver) 16.
The container client 11 is arranged to send a container operation request to the container service 12; the container service 12 is configured to preprocess the container operation request, schedule the container operation request, and distribute the preprocessed container operation request to the container engine 13; the container engine 13 is arranged to create a container execution unit 14 according to the received preprocessed container operation request; the container execution unit 14 is configured to perform a corresponding container operation on a container storage tier stack, where a current container storage tier in the container storage tier stack is created based on a previous container storage tier stack, and a stack bottom layer of the container storage tier stack is a mirror image base layer; the container store 15 is arranged to store a stack of container stores in a stack of container stores with a mirror image base layer as a bottom layer of the stack; the container driver 16 is arranged to perform a corresponding container operation on the container store level stack in accordance with the driving of the container execution unit 14.
As can be seen from the virtualized container management system shown in fig. 1, there may be a plurality of container clients 11, and the container clients 11 are provided in terminals that need to use the virtualized container service. The container service 12 establishes communication with each container client 11, and a user can issue a container operation request to the container service 12 through the container client 11 in the local terminal. After receiving the container operation request, the container service 12 schedules the container engine 13, the container engine 13 establishes the container execution unit 14 corresponding to each container operation request, and the container execution unit 14 drives each container storage layer to execute the container operation through the container driver 16. Wherein the manipulated container storage levels are stored in a container storage level stack in the container store 15. The container service 12, the container engine 13, and the container driver 16 are logical function modules provided in the virtualized container management server. The container service 12 functions to establish communication with each container client 11 provided in the terminal, and to preprocess and schedule a container operation request issued by each container client 11. The function of the container engine 13 is to create container operation requests scheduled by the container service 12 as container execution units 14. The container execution unit 14 is a thread of a process space, and the container driver 16 is configured to drive each container storage layer to perform a container operation according to the container execution unit 14.
In the related art, a virtualized container is composed of a mirror image, a container and a warehouse, wherein the container corresponds to the mirror image, when the container runs, the mirror image is used as a base layer, a storage layer of a current container is created on the base layer, but the life cycles of the container storage layer and the container are the same, and when the container dies, the container storage layer dies. The layered storage mode is adopted in the container, but a plurality of containers are mutually isolated, each container is based on the same mirror image base layer, the storage layers of different containers are mutually isolated, and data has no dependency relationship. Therefore, the storage layer change of any container cannot be recovered through the storage layers of other containers, the storage layer isolation among the containers causes that a plurality of containers occupy excessive storage space, storage layer multiplexing and storage layer data backtracking cannot be performed among the containers, and linkage operation, deployment and recovery cannot be performed on the containers.
In the embodiment of the application, in order to solve the problems in the related art, a virtual container storage mode in a virtualized container technology is changed, layered storage is adopted among containers, a plurality of containers are based on a mirror image base layer, and on the base layer, container storage layers of all the containers are iterated in a layered mode. Specifically, a container storage layer stack is stored in the container storage 15, a stack bottom layer of the container storage layer stack is a mirror image base layer, only one mirror image base layer is provided, each container storage layer is stacked on the mirror image base layer in a layered manner, and a current container storage layer corresponding to a current container is created based on a previous container storage layer stack when being created, so that each container storage layer in the container storage layer stack has a dependency relationship with other container storage layers, data loss caused by the fact that the corresponding container storage layer is also died due to the died container is avoided, and data backtracking of the container storage layers can be performed through the dependency relationship between the containers. Fig. 2 is a schematic structural diagram of a container storage tier stack in the virtualized container management system according to an embodiment of the present application. As shown in fig. 2, the bottom layer of the stack of container storage layers is a mirror image base layer 21, and the container storage layers 22 of the first layer may be one or more based on the mirror image base layer 21. On the basis of the container storage layers 22 of the first layer, a second layer of container storage layers 23 may be created on the basis that each container storage layer 22 may be stacked, the second layer of container storage layers 23 being one or more. By analogy, each container storage tier in the stack of container storage tiers may be created based on a previous container storage tier stack, and each container storage tier may serve as a basis for other container storage tiers. The stack of container storage levels forms a "chain" structure when there is only one container storage level per container storage level in the stack of container storage levels, and forms a "multi-chain" structure when there are more than one container storage levels per container storage level in the stack of container storage levels. In the virtualized container management system provided in this embodiment, because the container storage layer is redesigned, the container node is changed from an "island" structure to a "chain" or "multi-chain" structure, and the virtualized container is divided and managed from the time and space dimensions, so that the operation management and control and data multiplexing of the virtualized container are greatly improved, and the switching of the virtualized container from a point operation state to a plane or even a three-dimensional operation state is realized. In addition, in the embodiment of the present application, any node in the container storage tier stack (i.e. any container storage tier) may derive a sub-stack layer to form a multi-stack branch structure of the virtualized container, so as to expand the virtualized container management from isolated container storage tier node management to multi-dimensional, multi-level container storage tier node management.
Fig. 3 is a flowchart of a virtualized container management method according to an embodiment, and as shown in fig. 3, the method according to this embodiment includes the following steps.
In step S3010, the container client sends a container operation request to the container service.
The virtualized container management method provided in this embodiment is used for performing virtualized container management based on the virtualized container management system shown in fig. 2. First, the container client 11 transmits a container operation request to the container service 12 according to an instruction of a user. The container operation request includes any request for operating on the virtualized container, for example, the container operation request includes at least one of the following requests: create container storage tier requests, stack container storage tier requests, merge container storage tier requests, remove container storage tier requests, cache container storage tier requests, derivative container storage tier branch requests, switch container storage tier requests across branches, merge container storage tier requests across branches, compare inter-branch container storage tier requests, delete container storage tier branch requests.
Step S3020, the container service preprocesses the container operation request, schedules the container operation request, and distributes the preprocessed container operation request to the container engine.
Since the container storage layer stack in the virtualized container management system shown in fig. 1 adopts a stack structure, there is only one mirror base layer in the container storage layer stack, each container storage layer in the container storage layer stack is associated with another container storage layer, and the container storage layer stack is built by stacking on the basis of the mirror base layer, the container client does not determine the position of the container storage layer to be operated in the container storage layer stack. Therefore, in order to enable the container engine 13 to correctly determine the container storage layer of the required operation in the container storage layer stack according to the container operation request, relevant information corresponding to the container storage layer of the required operation is included in the container operation request.
Therefore, after receiving the container operation request, the container service 12 needs to preprocess the container operation request, so as to determine the container operation stack layer corresponding to the container operation request, so as to accurately distribute the container operation stack layer to different container storage layers, and ensure the accuracy of stacking and data change among the container storage layers. The container service 12 then schedules the container operation request, distributing the preprocessed container operation request to the container engine 13. The container service 12 preprocesses the container operation request, and aims to determine a container storage layer of an operation required by the container operation request, including resolving image information corresponding to the container operation request, a mapping relationship between an image and the container storage layer, and the like.
In one embodiment, the container service 12 preprocesses container operation requests, including: the container service 12 determines the dependency of the container storage tier corresponding to the container operation request with other container storage tiers in the container storage tier stack.
The container service 12 preprocesses the container operation request and may include at least one of: the method comprises the steps of obtaining mirror image information (Meta info), obtaining container storage layer information (Meta info), establishing a mirror image and container mapping relation, establishing a container and container storage layer mapping relation, establishing a container storage layer and container operation command mapping relation, combining container operation commands related to the same container and the same storage layer, and establishing a container storage layer data cache. For example, the container operation request is a request for creating a container storage layer, the request for creating the container storage layer includes mirror image information corresponding to a container storage layer to be created, then the container information is acquired, a mirror image and container mapping relationship is established, a container storage layer data cache is created, and the like, then the container service 12 may distribute the preprocessed container operation request to the container engine 13, where the preprocessed container operation request indicates the mirror image and container mapping relationship, and then the container engine 13 may create a corresponding container storage layer in the container storage layer stack according to the mapping relationship, the mirror image information, and the container information.
In step S3030, the container engine creates a container execution unit according to the received preprocessed container operation request.
The container engine 13 is a core of the virtualized container management system, creates a container execution unit 14 according to the received preprocessed container operation request, abstracts a container task (i.e., a container operation request), and operates as an independent individual, thereby improving the overall operation performance of the container.
The container engine 13 runs closely related to the preprocessing of container operation requests. The container engine 13 takes the preprocessed container operation request as input, and dynamically creates a corresponding container execution unit 14 according to different input parameters. The container engine 13 analyzes the received preprocessed container operation request, inputs the analyzed request into a message queue, sequentially schedules the requests in the message queue to create container execution units, and threads the created container execution units; in addition, the container engine 13 is also used to monitor the state of the threaded container execution unit 14.
In one embodiment, the container engine 13 may include a parser, message queue, scheduler, generator, monitoring task, and the like. The parser is used for analyzing the input parameters, verifying the validity of the input parameters, packaging the input parameters into a message unit, and pushing the message unit into a message queue. The scheduler obtains the message queue messages, performs message unit allocation and scheduling according to the running state of the existing container execution unit 14, and creates the container execution unit 14. The generator threads the container execution unit 14, joining it as a thread into the container process space and running it. The monitoring task monitors the state of the existing process space thread (container execution unit 14), and comprises the following steps: thread memory occupancy rate, thread creation and exit, zombie thread cleaning and the like.
In step S3040, the container execution unit performs a corresponding container operation on the container storage tier stack, where a current container storage tier in the container storage tier stack is created based on a previous container storage tier stack, and a stack bottom layer of the container storage tier stack is a mirror image base layer.
The container task (i.e. the container execution unit 14) is a basic work execution unit of the virtualized container management system, and the work content includes: creating container store tiers, stacking container store tiers, merging container store tiers, removing container store tiers, caching container store tiers, spawning container store tier branches, switching container store tiers across branches, merging container store tiers across branches, comparing inter-branch container store tiers, deleting container store tier branches, and the like. The container execution unit 14 performs a corresponding container operation on a corresponding container storage level in the container storage level stack by the driving of the container driver 16.
Further, because there is a dependency relationship between container storage tiers in the container storage tier stack, the container operation request includes an operation request to the current container storage tier or a multi-dimensional operation between container storage tier components. For example: cross-branch difference comparison in container storage layer, cross-branch merging and deleting operation, etc. The operation objects are positioned at the branches of different time sequences, the operation among the objects relates to the actions of data synchronization, data comparison, data combination and the like, and the operation is equivalent to multi-dimensional operation based on time and space.
Further, since the current container storage tier in the container storage tier stack is created based on the previous container storage tier stack, the current container storage tier in the container storage tier stack only contains differentiated data, such as change data, change actions, and the like, from the previous container storage tier. The storage space of the virtual container is greatly reduced, and switching, merging, comparing, marking and state rollback among a plurality of containers can be realized. Accordingly, stacking the container storage layers comprises: performing differentiation comparison on data of a current container storage layer and data of a previous container storage layer, determining the data of the current container storage layer, and stacking the data of the current container storage layer on the previous container storage layer, wherein the differentiation comparison comprises at least one of the following steps: and performing differentiation comparison, creation time comparison and operation action comparison on secondary system data. Eventually forming a stack of data between containers.
In the virtualized container management method provided in this embodiment, a container client sends a container operation request to a container service, then the container service preprocesses the container operation request, schedules the container operation request, and distributes the preprocessed container operation request to a container engine, the container engine creates a container execution unit according to the received preprocessed container operation request, and finally the container execution unit executes a corresponding container operation on a container storage layer stack, where a current container storage layer in the container storage layer stack is created based on a previous container storage layer stack, and a stack bottom layer of the container storage layer stack is a mirror image base layer, so that container management is changed from one-dimensional management to multidimensional management, that is, from a single time axis dimension to a time and space dimension, data fusion of container storage layers with different space dimensions is achieved, the degree of freedom of operation and the degree of freedom of deployment of the virtual container are expanded.
Fig. 4 is a block diagram of a container task system of a virtualized container management method according to an embodiment. As shown in fig. 4, a container execution unit (job) as a container task executes various container operations on a container storage layer stack stored in a container store (graph) by being driven by a container driver (driver) according to the schedule of a container engine. The container operations include creating a container storage tier (create tier), stacking a container storage tier (stack tier), merging a container storage tier (merge tier), removing a container storage tier (delete tier), spawning a container storage tier branch (create branch), switching a container storage tier (switch branch), merging a container storage tier (merge branch), comparing inter-branch container storage tiers (compare branch), and deleting a container storage tier branch (delete branch).
Embodiments of the present application also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform a virtualized container management method, the method comprising: the container client sends a container operation request to the container service; the container service preprocesses the container operation request, schedules the container operation request and distributes the preprocessed container operation request to a container engine; the container engine establishes a container execution unit according to the received preprocessed container operation request; the container execution unit executes corresponding container operation on the container storage layer stack, a current container storage layer in the container storage layer stack is established based on a previous container storage layer stack, and the stack bottom layer of the container storage layer stack is a mirror image base layer.
The above are merely exemplary embodiments of the present application, and are not intended to limit the scope of the present application.
In general, the various embodiments of the application may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.
Embodiments of the application may be implemented by a data processor of a mobile device executing computer program instructions, for example in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages.
Any logic flow block diagrams in the figures of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored on a memory. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, Read-Only Memory (ROM), Random-Access Memory (RAM), optical storage devices and systems (Digital versatile disks (DVD) or Compact Disks (CD)), etc., the computer-readable medium can comprise a non-transitory storage medium, the data processor can be of any type suitable to the local technical environment, such as, but not limited to, general purpose computers, special purpose computers, microprocessors, Digital Signal Processors (DSPs), Application Specific Integrated circuits (SAICs), Programmable logic devices (FGPAs), and processors based on a multi-core processor architecture.
Claims (10)
1. A virtualized container management method, comprising:
the container client sends a container operation request to the container service;
the container service preprocesses the container operation request, schedules the container operation request, and distributes the preprocessed container operation request to a container engine;
the container engine establishes a container execution unit according to the received preprocessed container operation request;
the container execution unit executes corresponding container operation on the container storage layer stack, a current container storage layer in the container storage layer stack is established based on a previous container storage layer stack, and a stack bottom layer of the container storage layer stack is a mirror image base layer.
2. The method of claim 1, wherein the container service preprocesses the container operation request, comprising:
the container service determines the dependency relationship of the container storage layer corresponding to the container operation request and other container storage layers in the container storage layer stack.
3. The method of claim 2, wherein the container service preprocesses the container operation request and comprises at least one of:
the method comprises the steps of obtaining mirror image information, obtaining container storage layer information, establishing a mirror image and container mapping relation, establishing a container and container storage layer mapping relation, establishing a container storage layer and container operation command mapping relation, combining container operation commands related to the same container and the same storage layer, and establishing a container storage layer data cache.
4. The method according to any one of claims 1 to 3, wherein the container engine creates a container execution unit according to the received preprocessed container operation request, and the method comprises the following steps:
the container engine analyzes the received preprocessed container operation request, inputs the analyzed request into a message queue, sequentially schedules the requests in the message queue to create a container execution unit, and threads the created container execution unit;
the container engine is also configured to monitor a state of the threaded container execution unit.
5. The method of any one of claims 1 to 3, wherein the container operation request comprises an operation request to a current container storage tier or a multi-dimensional operation between container storage tiers.
6. A method according to any of claims 1 to 3, wherein the container operation request comprises at least one of the following requests:
creating a container storage tier request, stacking container storage tiers requests, merging container storage tier requests, removing container storage tier requests, caching container storage tier requests, deriving container storage tier branch requests, switching container storage tier requests across branches, merging container storage tier requests across branches, comparing inter-branch container storage tier requests, deleting container storage tier branch requests;
accordingly, the container operation includes at least one of:
creating a container store tier, stacking container store tiers, merging container store tiers, removing container store tiers, caching container store tiers, deriving container store tier branches, switching container store tiers across branches, merging container store tiers across branches, comparing inter-branch container store tiers, and deleting container store tier branches.
7. The method of claim 6, wherein a current container storage tier in the stack of container storage tiers contains only differencing data from a previous container storage tier.
8. The method of claim 7, wherein stacking the container storage layer comprises:
performing differentiation comparison on data of a current container storage layer and data of a previous container storage layer, determining the data of the current container storage layer, and stacking the data of the current container storage layer on the previous container storage layer, wherein the differentiation comparison comprises at least one of the following steps: and performing differentiation comparison, creation time comparison and operation action comparison on secondary system data.
9. A virtualized container management system, comprising: the system comprises a container client, a container service, a container engine, a container execution unit, a container storage and a container driver;
the container client is configured to send a container operation request to the container service;
the container service is configured to preprocess the container operation request, schedule the container operation request, and distribute the preprocessed container operation request to the container engine;
the container engine is configured to create the container execution unit according to the received preprocessed container operation request;
the container execution unit is configured to execute corresponding container operations on a container storage layer stack, a current container storage layer in the container storage layer stack is created based on a previous container storage layer stack, and a stack bottom layer of the container storage layer stack is a mirror image base layer;
the container storage is configured to store each container storage stack layer in the stack of container storage layers with a mirror image base layer as a bottom layer of the stack;
the container driver is configured to perform a corresponding container operation on the container storage layer stack according to the driving of the container execution unit.
10. A computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements a virtualized container management method according to any of claims 1-8.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010294730.2A CN113535321A (en) | 2020-04-15 | 2020-04-15 | Virtualized container management method, system and storage medium |
| PCT/CN2021/086548 WO2021208844A1 (en) | 2020-04-15 | 2021-04-12 | Virtualized container management method and system, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010294730.2A CN113535321A (en) | 2020-04-15 | 2020-04-15 | Virtualized container management method, system and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113535321A true CN113535321A (en) | 2021-10-22 |
Family
ID=78083945
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010294730.2A Pending CN113535321A (en) | 2020-04-15 | 2020-04-15 | Virtualized container management method, system and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113535321A (en) |
| WO (1) | WO2021208844A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115098220A (en) * | 2022-06-17 | 2022-09-23 | 西安电子科技大学 | Large-scale network node simulation method based on container thread management technology |
| WO2023160327A1 (en) * | 2022-02-23 | 2023-08-31 | International Business Machines Corporation | Container image management |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114936066A (en) * | 2022-04-15 | 2022-08-23 | 支付宝(杭州)信息技术有限公司 | Mirror image stacking method, mirror image stacking device, mirror image stacking apparatus, mirror image stacking medium, and program product |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103095805B (en) * | 2012-12-20 | 2018-03-30 | 江苏辰云信息科技有限公司 | A kind of cloud storage system that data are carried out with intelligent multi-zone supervision |
| CN107038203A (en) * | 2016-12-30 | 2017-08-11 | 北京工业大学 | The Bedding storage mechanism of Internet of Things perception data " vector of tracing to the source " |
| US9983891B1 (en) * | 2017-03-21 | 2018-05-29 | Veritas Technologies Llc | Systems and methods for distributing configuration templates with application containers |
| CN109951551B (en) * | 2019-03-21 | 2021-03-19 | 联想(北京)有限公司 | Container mirror image management system and method |
-
2020
- 2020-04-15 CN CN202010294730.2A patent/CN113535321A/en active Pending
-
2021
- 2021-04-12 WO PCT/CN2021/086548 patent/WO2021208844A1/en active Application Filing
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023160327A1 (en) * | 2022-02-23 | 2023-08-31 | International Business Machines Corporation | Container image management |
| US11960870B2 (en) | 2022-02-23 | 2024-04-16 | International Business Machines Corporation | Container image management |
| CN115098220A (en) * | 2022-06-17 | 2022-09-23 | 西安电子科技大学 | Large-scale network node simulation method based on container thread management technology |
| CN115098220B (en) * | 2022-06-17 | 2024-04-16 | 西安电子科技大学 | Large-scale network node simulation method based on container thread management technology |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021208844A1 (en) | 2021-10-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112418438B (en) | Container-based machine learning procedural training task execution method and system | |
| US8862933B2 (en) | Apparatus, systems and methods for deployment and management of distributed computing systems and applications | |
| WO2021208844A1 (en) | Virtualized container management method and system, and storage medium | |
| US10990288B2 (en) | Systems and/or methods for leveraging in-memory storage in connection with the shuffle phase of MapReduce | |
| US20180217872A1 (en) | Decoupling partitioning for scalability | |
| US9594637B2 (en) | Deploying parallel data integration applications to distributed computing environments | |
| CN111641515B (en) | VNF life cycle management method and device | |
| US20160085738A1 (en) | Cloud-Based Parallel Computation Using Actor Modules | |
| KR101656360B1 (en) | Cloud System for supporting auto-scaled Hadoop Distributed Parallel Processing System | |
| US20230393879A1 (en) | Coordinated Container Scheduling For Improved Resource Allocation In Virtual Computing Environment | |
| CN104780146A (en) | Resource manage method and device | |
| US11487555B2 (en) | Running PBS jobs in kubernetes | |
| CN112905297A (en) | Container cluster resource scheduling method and device | |
| KR101765725B1 (en) | System and Method for connecting dynamic device on mass broadcasting Big Data Parallel Distributed Processing | |
| US20210390405A1 (en) | Microservice-based training systems in heterogeneous graphic processor unit (gpu) cluster and operating method thereof | |
| KR102376477B1 (en) | Electronic system with data exchange mechanism and method of operation thereof | |
| JP5030647B2 (en) | Method for loading a program in a computer system including a plurality of processing nodes, a computer readable medium containing the program, and a parallel computer system | |
| KR101640231B1 (en) | Cloud Driving Method for supporting auto-scaled Hadoop Distributed Parallel Processing System | |
| US10530892B2 (en) | Processing request for multi-versioned service | |
| US7313786B2 (en) | Grid-enabled ANT compatible with both stand-alone and grid-based computing systems | |
| US11656944B1 (en) | Code function checkpoint and restore | |
| CN112631994A (en) | Data migration method and system | |
| KR102045997B1 (en) | Method for scheduling task in big data analysis platform based on distributed file system, program and computer readable storage medium therefor | |
| CN113472557A (en) | Virtual network element processing method and device and electronic equipment | |
| CN113326098B (en) | Cloud management platform supporting KVM virtualization and container virtualization |
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 |