CN111367615B - Method, device, equipment and storage medium for facilitating container instance scheduling - Google Patents
Method, device, equipment and storage medium for facilitating container instance scheduling Download PDFInfo
- Publication number
- CN111367615B CN111367615B CN201811603115.4A CN201811603115A CN111367615B CN 111367615 B CN111367615 B CN 111367615B CN 201811603115 A CN201811603115 A CN 201811603115A CN 111367615 B CN111367615 B CN 111367615B
- Authority
- CN
- China
- Prior art keywords
- container
- container instance
- directory
- host
- mount
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 29
- 238000010586 diagram Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
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
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/4555—Para-virtualisation, i.e. guest operating system has to be modified
-
- 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/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
- G06F9/5038—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (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 discloses a method, a device, equipment and a storage medium for facilitating container instance scheduling, wherein the method comprises the following steps: when the mount volume of the container is created, the mount host directory with the unique identification is bound to the container directory on the host machine operated by each container instance, so that the mount host directory of the container instance and the mount host directories of other container instances do not collide when any container instance is dispatched to other host machines. The application solves the technical problems that the prior art does not have the flexibility of automatic drifting of the container or has larger invasiveness to the container application, thereby realizing the efficient and flexible scheduling of the container examples.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for facilitating scheduling of container instances.
Background
Container (Container): the virtualization technology is mainly characterized by comprising standardized packaging of software and depending environments, and applications are isolated from each other, but share an operating system kernel and can run on a plurality of mainstream operating systems.
Examples of containers: multiple running container instances of the same application.
Dock: one implementation of container technology is also an open-source container implementation tool which is currently the mainstream. Dock is an open-source application container engine that allows developers to package their applications and rely on packages into a portable container and then release them to any popular Linux machine, and also allows virtualization.
Container scheduling system: refers to a system capable of automatically creating containers and managing containers according to the status of computing resources (CPU, memory, etc.).
Kubernetes: one implementation of the container scheduling system is also an open-source container scheduling system which is mainstream at present, and is called K8S for short.
And (3) mounting a coil: the directories within the container need to be mapped to host file system directories, technically called mount volumes.
As shown in FIG. 1, when a host (node two) of a container instance encounters a failure, such as an anomaly in the host network or a host crash, the container dispatch system will migrate the container instance on the failed host (node two) to another host (node one). Because the mount host directories of the multiple container instances are consistent and are all/opt/usr/app/log, the file systems of the containers can collide, and the normal operation of the application system is affected.
In the prior art, the method for avoiding the conflict generated by the file system generally adopts the following two schemes:
(1) Method of increasing the state of a container: the container examples are numbered, and the mounted volumes are distinguished according to the numbers.
(2) Constraint container application limit mount volume: the container mount volume is restricted to output data externally by other means such as an interface means.
However, both of these approaches suffer from the disadvantage: the scheme (1) can solve the problem of conflict of the mounted volumes, but the containers can only be scheduled according to the sequence of the mounted volumes, and the flexible characteristic of automatic drifting of the containers is sacrificed. When the scheme (2) is adopted, because the logs and business exchange data of many container application instances are output in a file mode, the implementation mode has great invasiveness to the application.
Disclosure of Invention
The present application aims to solve at least one of the technical problems in the related art to some extent. To this end, it is an object of the present application to provide a method, apparatus, device and storage medium that facilitate scheduling of container instances.
The technical scheme adopted by the application is as follows:
in a first aspect, the present application provides a method of facilitating scheduling of container instances, the method comprising: when the mount volume of the container is created, the mount host directory with the unique identification is bound to the container directory on the host machine operated by each container instance, so that the mount host directory of the container instance and the mount host directories of other container instances do not collide when any container instance is dispatched to other host machines.
The step of binding the mount host directory with the unique identifier to the container directory on the host running on each container instance when the mount volume of the container is created specifically includes: intercepting a request to create the container upon receiving the request; setting a root directory with unique identification for each container instance; when creating the mount volume, the mount host directory for each container instance is set to the root directory plus a subdirectory, which is the container directory.
Wherein the step of setting a root directory with a unique identifier for each container instance specifically includes: when each container instance is created, inputting a time stamp for creating each container instance, an IP address of a host machine on which each container instance is mounted, a container ID and a random number into a preset algorithm, and obtaining the unique identification of each container instance; and setting a primary subdirectory under the original root directory of each container instance, wherein the primary subdirectory is named as the unique identifier, so that each container instance has the root directory with the unique identifier.
The step of binding the mount host directory with the unique identifier to the container directory on the host running on each container instance when creating the mount volume of the container further includes: and writing the mount host directory with the unique identification into an environment variable.
In a second aspect, the present application provides an apparatus for facilitating scheduling of container instances, the apparatus comprising a catalog setup module for binding, on a host on which each container instance is running, a mount host catalog having a unique identifier to the container catalog when creating a mount volume for the container, for causing the mount host catalog of the container instance to not collide with mount host catalogs of other container instances when scheduling the container instance to other hosts.
Wherein, this catalogue sets up the module and includes: a container creation request interception unit for intercepting a request for creating the container when the request is received; a container instance root directory setting unit configured to set a root directory having a unique identification for each container instance; and a mount host directory setting unit configured to set, when the mount volume is created, the mount host directory of each container instance to add a subdirectory to the root directory, the subdirectory being the container directory.
The container instance root directory setting unit comprises a unique identification generation subunit and a container instance root directory generation subunit, wherein the unique identification generation subunit is used for inputting a time stamp for creating each container instance, an IP address of a host machine on which each container instance is mounted, a container ID and a random number into a preset algorithm when each container instance is created, so as to obtain the unique identification of each container instance; the container instance root directory generation subunit is configured to set a primary subdirectory under the original root directory of each container instance, where the primary subdirectory is named as the unique identifier, so that each container instance has a root directory with the unique identifier.
Wherein the apparatus further comprises: and the environment variable writing module is used for writing the mount host directory with the unique identification into the environment variable.
In a third aspect, the present application provides an apparatus for facilitating scheduling of container instances, the apparatus comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a method as described above.
In a fourth aspect, the present application also provides a computer-readable storage medium storing computer-executable instructions for causing a computer to perform a method as described above.
The beneficial effects of the application are as follows:
when the mount volume of the container is created, the mount host machine catalog with the unique identifier is bound to the container catalog on the host machine operated by each container instance, so that when one container instance is dispatched to other host machines, the mount host machine catalog of the container instance does not conflict with the mount host machine catalog of other container instances, and the technical problems that the container automatic drifting flexibility or the invasiveness to the container application is not possessed in the prior art are solved, and the efficient and flexible dispatching of the container instance is realized.
In addition, the application also realizes the writing of the catalog of the mounting host machine with the unique identification into the environment variable. If the log file or other business file output in the mounted volume needs to be accessed, the real file path can be obtained from the environment variable.
Drawings
FIG. 1 is a schematic diagram of a prior art container instance scheduling method;
FIG. 2 is a flow diagram of one embodiment of a method of facilitating container instance scheduling in accordance with the present application;
FIG. 3 is a schematic diagram of the specific flow of step S12 in FIG. 2;
FIG. 4 is a schematic diagram of an example scheduling method for containers of the present application;
fig. 5 is a schematic diagram of an embodiment of an apparatus for facilitating container instance scheduling in accordance with the present application.
Detailed Description
It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other.
Embodiment one:
referring to fig. 2, fig. 2 is a flow chart illustrating an embodiment of a method for facilitating scheduling of container instances according to the present application. The method of fig. 2 includes:
step S11: when the mount volume of the container is created, the mount host directory with the unique identification is bound to the container directory on the host machine operated by each container instance, so that the mount host directory of the container instance and the mount host directories of other container instances do not collide when any container instance is dispatched to other host machines.
In step S11, the container has a plurality of (including two) container instances.
Referring to fig. 3, fig. 3 is a schematic flowchart of step S11 in fig. 2, and fig. 3 specifically includes the following steps:
step S111: intercepting a request to create the container upon receiving the request;
step S112: setting a root directory with unique identification for each container instance;
wherein, step S112 includes the following steps:
(1) When each container instance is created, inputting a time stamp for creating each container instance, an IP address of a host machine on which each container instance is mounted, a container ID and a random number into a preset algorithm, and obtaining the unique identification of each container instance;
for example, a unique identifier of a container instance is obtained, the unique identifier is generated by a preset algorithm, and input data of the preset algorithm is: the unique identification of the container instance can be obtained from the output data of the preset algorithm, wherein the time stamp is generated when the container instance is created, the IP address of the host on which the container instance is mounted, the ID of the container and one or more random numbers.
(2) And setting a primary subdirectory under the original root directory of each container instance, wherein the primary subdirectory is named as the unique identifier, so that each container instance has the root directory with the unique identifier.
For example, the original root directory of the container instance is/opt/usr/, and the new root directory of the container instance is/opt/usr/unique identifier.
Step S113: when creating the mount volume, the mount host directory for each container instance is set to the root directory plus a subdirectory, which is the container directory.
For example, the container directory is/app/log, then the mount host directory for each container instance is/opt/usr/unique identification/app/log. Thus, the mount host directory for different container instances will not be duplicated.
Thus, as shown in fig. 4, when the container instance B on the node two needs to be migrated to the node one, the mount host directory of the container instance B is inconsistent with the mount host directory of the container instance a, so that the file system of the mount volume of the container does not collide, and the scheduling of the container instance a is successfully performed. The implementation method of the embodiment can be realized by arranging a proxy scheduling process between the scheduling management system K8S and the Docker, wherein the proxy scheduling process is respectively communicated with the scheduling management system K8S and the Docker through a communication protocol.
In addition, the method of the present embodiment may further include the steps of: and writing the mount host directory with the unique identification into an environment variable. If the log file or other business file output in the mounted volume needs to be accessed, the real file path can be obtained from the environment variable.
Embodiment two:
referring to fig. 5, fig. 5 is a schematic structural diagram of an apparatus for facilitating container instance scheduling according to an embodiment of the present application. The apparatus of fig. 5 includes a catalog setting module 51 and an environment variable writing module 52, where the catalog setting module 51 is configured to bind, on a host machine on which each container instance operates, a mount host machine catalog with a unique identifier to the container catalog when creating a mount volume of the container, so that the mount host machine catalog of the container instance does not collide with mount host machine catalogs of other container instances when scheduling the container instance to other host machines. The environment variable writing module 52 is configured to write the mount host directory with the unique identifier to an environment variable. In other embodiments, the environment variable writing module 52 may be omitted.
The catalog setting module 51 includes a container creation request interception unit 511, a container instance root catalog setting unit 512, and an mount host catalog setting unit 513. The container creation request interception unit 511 is configured to intercept a request for creating the container when the request is received; a container instance root directory setting unit 512 for setting a root directory having a unique identification for each container instance; the mount host directory setting unit 513 is configured to set the mount host directory of each container instance to the root directory plus a subdirectory that is the container directory when the mount volume is created.
The container instance root directory setting unit 512 includes a unique identifier generating subunit 5121 and a container instance root directory generating subunit 5122, where the unique identifier generating subunit 5121 is configured to, when creating each container instance, input a timestamp of creating the each container instance, an IP address of a host on which the each container instance is mounted, a container ID, and a random number into a preset algorithm, and obtain the unique identifier of the each container instance; the container instance root directory generating subunit 5122 is configured to set a primary sub-directory under the original root directory of each container instance, where the primary sub-directory is named as the unique identifier, so that each container instance has a root directory with the unique identifier.
The working method of the device of this embodiment is the same as that of the first embodiment, and will not be described here.
Embodiment III:
the present application also provides an apparatus for facilitating scheduling of container instances, the apparatus comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method as described in embodiment one.
Embodiment four:
the present application also provides a computer-readable storage medium storing computer-executable instructions for causing a computer to perform the method of embodiment one.
In summary, when the method, the device, the equipment and the storage medium for facilitating the scheduling of the container instances are used for creating the mount volume of the container, the mount host directory with the unique identifier is bound to the container directory on the host machine operated by each container instance, so that when one container instance is scheduled to other host machines, the mount host directory of the container instance and the mount host directory of other container instances do not collide, thereby realizing successful scheduling of the container instances. In addition, the application also realizes the writing of the catalog of the mounting host machine with the unique identification into the environment variable. If the log file or other business file output in the mounted volume needs to be accessed, the real file path can be obtained from the environment variable.
While the preferred embodiment of the present application has been described in detail, the present application is not limited to the embodiments, and those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the present application, and the equivalent modifications or substitutions are included in the scope of the present application as defined in the appended claims.
Claims (4)
1. A method for facilitating scheduling of container instances, comprising:
when a mount volume of a container is created, binding a mount host machine catalog with a unique identifier to a container catalog on a host machine operated by each container instance, and writing the mount host machine catalog with the unique identifier into an environment variable so that the mount host machine catalog of the container instance does not conflict with mount host machine catalogs of other container instances when any container instance is scheduled to other host machines;
the step of binding the mount host directory with the unique identifier to the container directory on the host running on each container instance when creating the mount volume of the container specifically includes:
intercepting a request to create the container upon receiving the request;
when each container instance is created, inputting a time stamp for creating each container instance, an IP address of a host machine mounted on each container instance, a container ID and a random number into a preset algorithm, and obtaining the unique identification of each container instance; setting a primary sub-directory under the original root directory of each container instance, wherein the primary sub-directory is named as the unique identifier, so that each container instance has the root directory with the unique identifier;
when the mount volume is created, the mount host directory of each container instance is set to be the root directory plus a subdirectory, the subdirectory being the container directory.
2. The device is characterized by comprising a catalog setting module and an environment variable writing module, wherein the catalog setting module is used for binding a host computer catalog with unique identification to a container catalog on a host computer operated by each container instance when a mounted volume of the container is created, so that the mounted host computer catalog of the container instance and the mounted host computer catalog of other container instances do not collide when the container instance is dispatched to other host computers; the environment variable writing module is used for writing the catalog of the mounting host machine with the unique identifier into the environment variable;
the catalog setting module comprises:
a container creation request interception unit for intercepting a request for creating the container when the request is received;
a container instance root directory setting unit, configured to set a root directory with a unique identifier for each container instance; and
a mount host directory setting unit configured to set, when the mount volume is created, the mount host directory of each container instance to add a subdirectory to the root directory, the subdirectory being the container directory;
the container instance root directory setting unit includes a unique identification generation subunit and a container instance root directory generation subunit,
the unique identifier generating subunit is configured to input, when each container instance is created, a timestamp of creating the each container instance, an IP address of a host machine on which the each container instance is mounted, a container ID, and a random number into a preset algorithm, so as to obtain the unique identifier of the each container instance;
the container instance root directory generation subunit is configured to set a primary sub-directory under the original root directory of each container instance, where the primary sub-directory is named as the unique identifier, so that each container instance has a root directory with the unique identifier.
3. An apparatus for facilitating scheduling of container instances, comprising:
at least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor; wherein,,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of claim 1.
4. A computer-readable storage medium storing computer-executable instructions for causing a computer to perform the method of claim 1.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811603115.4A CN111367615B (en) | 2018-12-26 | 2018-12-26 | Method, device, equipment and storage medium for facilitating container instance scheduling |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811603115.4A CN111367615B (en) | 2018-12-26 | 2018-12-26 | Method, device, equipment and storage medium for facilitating container instance scheduling |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111367615A CN111367615A (en) | 2020-07-03 |
| CN111367615B true CN111367615B (en) | 2023-08-18 |
Family
ID=71206076
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811603115.4A Active CN111367615B (en) | 2018-12-26 | 2018-12-26 | Method, device, equipment and storage medium for facilitating container instance scheduling |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111367615B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112398929B (en) * | 2020-11-04 | 2023-12-05 | 北京金和网络股份有限公司 | Number issuing method based on container and number issuing device |
| CN112506755B (en) * | 2020-12-18 | 2023-11-03 | 北京顺达同行科技有限公司 | Log acquisition method, device, computer equipment and storage medium |
| CN112905537B (en) * | 2021-02-20 | 2022-09-02 | 北京百度网讯科技有限公司 | File processing method and device, electronic equipment and storage medium |
| CN113190325A (en) * | 2021-04-09 | 2021-07-30 | 大唐微电子技术有限公司 | Container creation method and device |
| CN113342461B (en) * | 2021-05-31 | 2023-04-07 | 北京市商汤科技开发有限公司 | Equipment mounting method and device, computer equipment and readable storage medium |
| CN114327687B (en) * | 2022-03-09 | 2022-05-20 | 恒生电子股份有限公司 | Method, device and equipment for constructing sub-application in micro front-end mode and storage medium |
| CN116107515B (en) * | 2023-04-03 | 2023-08-18 | 阿里巴巴（中国）有限公司 | Storage volume mounting and accessing method, equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105893010A (en) * | 2015-11-17 | 2016-08-24 | 乐视云计算有限公司 | Host scheduling method and system used for container deployment |
| CN106383852A (en) * | 2016-08-30 | 2017-02-08 | 中国民生银行股份有限公司 | Docker container-based log acquisition method and apparatus |
| CN107728947A (en) * | 2017-10-13 | 2018-02-23 | 郑州云海信息技术有限公司 | A kind of cold moving method of container and system |
| CN108762882A (en) * | 2018-04-02 | 2018-11-06 | 杭州朗和科技有限公司 | A kind of moving method, moving apparatus, medium and the computing device of Docker containers |
| CN108845917A (en) * | 2018-04-09 | 2018-11-20 | 东峡大通（北京）管理咨询有限公司 | File journalization carry module, system and method in container |
-
2018
- 2018-12-26 CN CN201811603115.4A patent/CN111367615B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105893010A (en) * | 2015-11-17 | 2016-08-24 | 乐视云计算有限公司 | Host scheduling method and system used for container deployment |
| CN106383852A (en) * | 2016-08-30 | 2017-02-08 | 中国民生银行股份有限公司 | Docker container-based log acquisition method and apparatus |
| CN107728947A (en) * | 2017-10-13 | 2018-02-23 | 郑州云海信息技术有限公司 | A kind of cold moving method of container and system |
| CN108762882A (en) * | 2018-04-02 | 2018-11-06 | 杭州朗和科技有限公司 | A kind of moving method, moving apparatus, medium and the computing device of Docker containers |
| CN108845917A (en) * | 2018-04-09 | 2018-11-20 | 东峡大通（北京）管理咨询有限公司 | File journalization carry module, system and method in container |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111367615A (en) | 2020-07-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111367615B (en) | Method, device, equipment and storage medium for facilitating container instance scheduling | |
| US10698772B2 (en) | Storage system with multiple write journals supporting synchronous replication failure recovery | |
| US10649955B2 (en) | Providing unique inodes across multiple file system namespaces | |
| EP3432132B1 (en) | Data storage method and device | |
| US11494130B2 (en) | Operation data accessing device and accessing method thereof | |
| CN109739668A (en) | A kind of method of data transmission between virtual machines, system and equipment | |
| CN111782318A (en) | Sharing access system and method for remotely mounting local disk to cloud desktop virtual machine | |
| US9537932B2 (en) | Emulating test distributed application on server | |
| US20200379653A1 (en) | Reclaiming free space in a storage system | |
| US20210165767A1 (en) | Barriers for Dependent Operations among Sharded Data Stores | |
| CN109753244A (en) | A kind of application method of Redis cluster | |
| EP4124953A2 (en) | Computing cluster bring-up on any one of a plurality of different public cloud infrastructures | |
| CN105739930A (en) | Storage framework as well as initialization method, data storage method and data storage and management apparatus therefor | |
| US10990286B1 (en) | Parallel upgrade of nodes in a storage system | |
| CN113438295A (en) | Container group address allocation method, device, equipment and storage medium | |
| WO2022057439A1 (en) | Communication device for bare metal server and elastic block storage, intelligent network card, and system | |
| CN104199716A (en) | Virtual machine thermal migration method, physical host and system | |
| JP6418419B2 (en) | Method and apparatus for hard disk to execute application code | |
| WO2021217870A1 (en) | Cluster installation method, device, and apparatus using excel file, and storage medium | |
| CN114003342A (en) | Distributed storage method and device, electronic equipment and storage medium | |
| US11042665B2 (en) | Data connectors in large scale processing clusters | |
| US20210240399A1 (en) | Storage system with continuous data verification for synchronous replication of logical storage volumes | |
| US10642788B1 (en) | Sand timer algorithm for tracking in-flight data storage requests for data replication | |
| US10768834B2 (en) | Methods for managing group objects with different service level objectives for an application and devices thereof | |
| CN105045629A (en) | Diskless workstation equipment startup method and system |
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 | ||
| CB02 | Change of applicant information |
Address after: 518000 w601, Shenzhen Hong Kong industry university research base, 015 Gaoxin South 7th Road, high tech Zone community, Yuehai street, Nanshan District, Shenzhen City, Guangdong Province Applicant after: ASPIRE TECHNOLOGIES (SHENZHEN) LTD. Address before: 518000 south wing, 6th floor, west block, Shenzhen Hong Kong industry university research base building, South District, high tech Industrial Park, Nanshan District, Shenzhen City, Guangdong Province Applicant before: ASPIRE TECHNOLOGIES (SHENZHEN) LTD. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |