CN114356501A - Persistent memory access method and device for container in cloud platform virtual machine - Google Patents
Persistent memory access method and device for container in cloud platform virtual machine Download PDFInfo
- Publication number
- CN114356501A CN114356501A CN202111651614.2A CN202111651614A CN114356501A CN 114356501 A CN114356501 A CN 114356501A CN 202111651614 A CN202111651614 A CN 202111651614A CN 114356501 A CN114356501 A CN 114356501A
- Authority
- CN
- China
- Prior art keywords
- persistent memory
- virtual machine
- container
- namespace
- 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
- 230000002085 persistent effect Effects 0.000 title claims abstract description 178
- 238000000034 method Methods 0.000 title claims abstract description 55
- 238000013507 mapping Methods 0.000 claims abstract description 17
- 230000008569 process Effects 0.000 claims description 11
- 238000004590 computer program Methods 0.000 claims description 6
- 238000012217 deletion Methods 0.000 claims description 6
- 230000037430 deletion Effects 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a persistent memory access method and a persistent memory access device for a container in a cloud platform virtual machine, wherein the access method comprises the following steps: creating a first persistent memory name space on storage equipment under a host machine node according to storage use request information of a container in the virtual machine, mapping the first persistent memory name space to the inside of the virtual machine, finding the storage equipment according to successful scanning, and correspondingly creating a second persistent memory name space inside the virtual machine; and creating and mounting a file system on the second persistent memory name space, wherein the container in the virtual machine accesses the first persistent memory name space through the file system. The method and the device have the advantages that the naming space on the virtual machine is created in a mode that the naming space on the persistent memory device is mapped to the virtual machine, and the file system is created and mounted on the naming space on the virtual machine.
Description
Technical Field
The invention relates to the technical field of cloud computing, in particular to a persistent memory access method and device for a container in a cloud platform virtual machine.
Background
With the rapid development of cloud computing technology, related container technology such as kubernets (k8s, containerization application) is widely used. In order to use storage resources in an environment such as kubernets, cloud computing manufacturers generally adopt a scheme of automated management of storage resources, for example, according to container storage use requirements, a cloud platform automatically performs operations such as creation, mounting, deletion, or capacity expansion of container volumes, so as to avoid manual operations such as creation, deletion, and the like of container volumes, and further reduce operation and maintenance workload. The use of persistent memory in data centers is increasingly common, however, due to the particularity of the use mode in the persistent memory, the conventional automated storage resource management scheme only supports the conventional disk and storage array, and cannot be used for performing automated access to the persistent memory, and a solution is urgently needed.
Disclosure of Invention
In order to solve the problem that a container cannot automatically access a persistent memory in the prior art, one or more embodiments of the present invention can provide a persistent memory access method and apparatus for a container in a cloud platform virtual machine, so as to achieve the technical purposes of automatically accessing a persistent memory by a container, and the like.
To achieve the technical object, the present invention provides a persistent memory access method for a container in a cloud platform virtual machine, where the persistent memory access method includes, but is not limited to, one or more of the following steps.
Creating a first persistent memory name space on storage equipment under a host machine node according to storage use request information of a container in a virtual machine; the storage device is a persistent memory device.
And mapping the first persistent memory name space to the inside of the virtual machine so that the virtual machine scans and discovers the storage device.
And correspondingly creating a second persistent memory name space inside the virtual machine according to the storage device found by successful scanning.
And creating and mounting a file system on the second persistent memory namespace, wherein the container in the virtual machine accesses the first persistent memory namespace through the file system.
In order to achieve the technical object, the present invention can also provide a persistent memory access device for a container in a cloud platform virtual machine. The device includes, but is not limited to, a first space creating unit, a namespace mapping unit, a second space creating unit, and a file system forming unit, which are described in detail below.
The system comprises a first space creating unit, a first persistent memory naming space creating unit and a second space creating unit, wherein the first space creating unit is used for creating a first persistent memory naming space on storage equipment under a host machine node according to storage use request information of a container in a virtual machine; the storage device is a persistent memory device.
And the namespace mapping unit is used for mapping the first persistent memory namespace to the interior of the virtual machine so as to enable the virtual machine to scan and discover the storage equipment.
And the second space creating unit is used for finding the storage equipment according to successful scanning and correspondingly creating a second persistent memory name space inside the virtual machine.
And the file system forming unit is used for creating and mounting a file system on the second persistent memory namespace, and the container in the virtual machine accesses the first persistent memory namespace through the file system.
To achieve the above technical object, the present invention can also provide a computer device, which includes a storage and a processor, wherein the storage stores computer readable instructions, and the computer readable instructions, when executed by the processor, cause the processor to execute the steps of the persistent memory access method for a container in a cloud platform virtual machine according to any embodiment of the present invention.
To achieve the above technical objects, the present invention may also provide a storage medium storing computer-readable instructions, which when executed by one or more processors, cause the one or more processors to perform the steps of the persistent memory access method for a container in a cloud platform virtual machine according to any one of the embodiments of the present invention.
To achieve the above technical object, the present invention can also provide a computer program product, wherein when instructions of the computer program product are executed by a processor, the steps of the persistent memory access method for a container in a cloud platform virtual machine according to any embodiment of the present invention are performed.
The invention has the beneficial effects that:
the method and the device have the advantages that the naming space on the virtual machine is created in a mode that the naming space on the persistent memory device is mapped to the virtual machine, and the file system is created and mounted on the naming space on the virtual machine. According to the invention, the works of creating, mounting, unloading, deleting and the like of the Itanium memory naming space can be automatically realized according to the storage use requirements of the container, the workload of manually creating persistent memory resources is greatly reduced, the working efficiency of the container in the cloud platform virtual machine is greatly improved, the method can be better suitable for the scene that the container and the container arrangement system are deployed in the virtual machine, and the technical support is provided for improving the performance of the container in the cloud platform virtual machine.
Drawings
Fig. 1 is a flowchart illustrating a persistent memory access method for a container in a cloud platform virtual machine according to one or more embodiments of the present invention.
FIG. 2 is a diagram illustrating logic for implementing persistent memory device access and management in one or more embodiments of the invention.
FIG. 3 is a flow diagram illustrating a method for persistent memory access with a container that may be used for storage resource release in one or more embodiments of the invention.
Fig. 4 is a schematic diagram illustrating a composition of a persistent memory access device for a container in a cloud platform virtual machine according to one or more embodiments of the present invention.
FIG. 5 is a schematic diagram showing the internal structural components of a computer device in one or more embodiments of the invention.
Detailed Description
The following explains and explains a persistent memory access method and apparatus for a container in a cloud platform virtual machine in detail with reference to the drawings of the specification.
As shown in fig. 1, which may be combined with fig. 2 and 3, one or more embodiments of the present invention may provide a persistent memory access method for a container in a cloud platform virtual machine. The persistent memory access method for a container in a virtual machine includes, but is not limited to, one or more of the following steps, which are described in detail below.
The invention aims at the scenes of containers, container arrangement systems and the like deployed in the cloud platform virtual machine to realize the access and management of the containers to the persistent memory. The container orchestration system according to the present invention is a software system for container scheduling and cluster management, which may include but is not limited to open source kubernets, and can provide a basic mechanism for container application extensibility, thereby performing life cycle management of containers. The invention deploys the container arrangement system (such as kubernets) in the virtual machine nodes, submits the request for creating the container to the container arrangement system, wherein the request for creating the container can comprise the names of the used storage plug-ins, the space size of the storage resources, the position topology information of the running virtual machine nodes and the like, and then the implementation process of accessing the storage resources can be implemented according to the following steps.
The persistent memory device of the present embodiment may specifically be an AEP (Apache Pass, aoteng) persistent memory device, and the persistent memory device is initialized in a Host (Host) system to complete creation of a persistent memory area (region). More specifically, the embodiments of the present invention can create a persistent memory region in a non-volatile persistent (AppDirect) mode using a persistent memory management command (ipmctl, a management utility tool), but are not limited thereto.
The embodiment of the invention can install the control module of the container storage plug-in on the master node (master) of the container arrangement system, and the control module can register the storage plug-in driver with the container arrangement system and is used for responding to the storage use request of the container. The container arrangement system is used for calling a container storage plug-in control module to create an AEP namespace interface according to the storage use request, and the container storage plug-in control module can be used for sending a request to the virtual machine management platform, so that a proper Host node is selected according to the virtual machine node position topology information.
Optionally, in this embodiment of the present invention, according to the storage use request information of the container in the virtual machine, a first persistent memory namespace is created on a storage device under the host node, and the process may include: the method includes the steps of reading storage space size information contained in storage use request information, determining the size of a storage space applied by a container, and determining first persistent memory name space size information based on the storage space size information.
A persistent memory namespace (namespace) on a persistent memory device is a way to partition a storage area, which can be understood to be similar to a sector of a conventional disk. In a host node (system), a mode of a first persistent memory namespace (namespace) is a devdax (devicedirect access) mode, and is identified as a character device in the host system. The embodiment of the invention can create namespace with a devdax mode on the AEP persistent memory of the Host system, and the device name displayed under the current system is/dev/dax0.x, wherein x behind 0 is used for representing namespace number, and the ranking can be started from 0.
Optionally, mapping the first persistent memory namespace to the inside of the virtual machine in the embodiment of the present invention includes: and adding character equipment information to the process of the virtual machine, wherein the character equipment information is information of character equipment associated with the first persistent memory name space. Specifically, in the embodiment of the present invention, the character device information/dev/dax0.x corresponding to the namespace created above is added to the virtual machine process, so that the character device information/dev/dax0.x is recognized as a persistent memory device inside the virtual machine. In the embodiment of the present invention, a virtual machine management platform interface may be called by a container storage plug-in control module, and a/dev/dax0.x character device corresponding to the created AEP namespace is added to a running virtual machine, where the virtual machine of the embodiment may be, for example, a qemu (virtual operating system simulator) virtual machine, and certainly is not limited thereto.
When adding equipment to qemu, the embodiment of the invention uses the following qemu instruction:
object_addmemory-backend-file,id＝mem_x,share＝on,mem-path＝/dev/dax0.x,size＝xxxG
wherein, the size parameter in the instruction represents the space size of AEP namespace, and mem _ x is used for representing the index number corresponding to namespace; the following qemu instruction is then executed, completing the addition of/dev/dax0. x devices.
device_add nvdimm,id＝nvdimm_x,memdev＝mem_x
As shown in fig. 2, in the embodiment of the present invention, a first persistent memory namespace 1 is created on a persistent memory device for use by a current container; the first persistent memory namespace 2 is illustrated as the namespace for use by other containers. And mapping the first persistent memory name space 1 into the virtual machine to establish the contact between the virtual machine and the persistent memory device, and further providing storage service for the container application through the first persistent memory name space 1.
The first persistent memory namespace may be a plurality of first persistent memory namespaces, and may provide storage services for different container applications respectively. The second persistent memory namespace corresponds to the first persistent memory namespace 1 in FIG. 2, although not limited thereto.
Optionally, in this embodiment, creating the second persistent memory namespace correspondingly inside the virtual machine includes: and creating a second persistent memory name space associated with block device information in the virtual machine, wherein the block device information corresponds to the character device information.
In the virtual machine, the mode of the second persistent memory namespace (namespace) is an fsdax (filesystem direct access) mode, and the second persistent memory namespace (namespace) is identified as a block device in the virtual machine system.
The embodiment of the invention can install the working module of the container storage plug-in on the workload node of the container arrangement system, the working module can be used for creating the added AEP equipment into a namespace with an fsdax mode in the virtual machine, the namespace of the mode can support the creation of a file system on the AEP equipment, the AEP equipment is mounted in an dax (direct access) mode, then a mounting point is added into the namespace of the container, and the container under the current virtual machine node is scheduled to run through the container arrangement system after the mounting of the file system is finished. The embodiment of the invention can realize the persistent memory namespace formatting interface through the working module, thereby re-identifying the hot-added/dev/dax0.x equipment as the persistent memory in the virtual machine and creating the namespace with the fsdax mode on the persistent memory; a file system is then created on the fsdax namespace, as further described below.
It is understood that the access of the container to the persistent memory device in the embodiment may specifically include writing of data and/or reading of data.
Optionally, the creating and mounting the file system on the second persistent memory namespace in this embodiment includes: and identifying the second persistent memory name space as a block device, creating a file system on the block device, and mounting the file system.
The method for accessing the persistent memory of the container can be realized by using the container storage plug-in, and the invention provides a method for realizing the container storage plug-in based on the AEP persistent memory. The AEP persistent memory is a novel storage medium, has the characteristics of low delay, high bandwidth and holding write-in of data compared with the traditional Disk and SSD (Solid State Disk), and also has the characteristic of power-off non-volatility compared with the common memory.
Aiming at the scene that the container and the container arrangement system are deployed in the virtual machine, the invention provides a method for realizing the container storage plug-in for the container to use the AEP persistent memory, the use of the AEP persistent memory is automatically managed in a container storage plug-in mode, and the container storage plug-in can be realized through a control module and a working module. The method includes automatically creating namespaces in devdax mode on a host AEP device according to container storage requirements and hot-adding namespaces to virtual machine processes. The method comprises the steps of re-discovering the persistent memory device inside the virtual machine, creating a namespace of an fsdax mode on the persistent memory device inside the virtual machine, and then creating a file system on the fsdax namespace and providing the file system for a container to use.
As shown in fig. 3, the persistent memory access method for a container in a cloud platform virtual machine according to the embodiment of the present invention may further include, but is not limited to, step 500 and step 600, which are described in detail below.
When the file system is prepared to be unloaded, the embodiment of the invention can call the persistent memory namespace unloading interface of the working module of the container storage plug-in through the container arrangement system, and unload the file system used by the previous container; the embodiment of the invention also calls an interface of the container storage plug-in control module for removing AEP namespace through the container arrangement system, and the control module initiates a request for removing the AEP namespace on the virtual machine to the virtual machine management platform so as to complete the removal of the/dev/dax0.x equipment on the virtual machine; although not limited thereto.
It should be understood that, when a container is deleted, the storage resource used by the container is deleted simultaneously by the container arrangement system of the present invention, that is, the case where the use of the persistent memory resource by the container of the present invention is finished includes the case where the container is deleted, but is not limited thereto. When the container is deleted, the storage resource is not used any more, the invention calls the persistent memory name space unloading interface through the container arrangement system to remove the file system mounting point from the name space of the container, and then unloads the file system.
In the embodiment of the invention, the following qemu instruction can be used for removing the/dev/dax0.x equipment corresponding to the AEP namespace from the virtual machine:
device_del nvdimm_x
wherein, nvdimm _ x in the command is used for representing an index number corresponding to namespace; the following qemu instruction is then executed:
object_del mem_x
For the condition that the container application is deleted by the container arrangement system, the AEP namespace in the virtual machine where the container is located is automatically unloaded through the container storage plug-in, and the AEP namespace is deleted in the host system, so that the work of creating, mounting, unloading, deleting and the like of the AEP namespace is automatically realized according to the container storage requirement, namely the problem of calling the persistent memory is faced.
As shown in fig. 4, based on the same technical concept, one or more embodiments of the present invention can also provide a persistent memory access apparatus for a container in a cloud platform virtual machine. The persistent memory access device includes, but is not limited to, a first space creating unit, a namespace mapping unit, a second space creating unit, and a file system forming unit, which are described in detail below.
The first space creating unit is used for creating a first persistent memory name space on the storage device under the host machine node according to the storage use request information of the container in the virtual machine. The storage device of the present invention is a persistent memory device.
Optionally, the first space creating unit is configured to read storage space size information included in the storage use request information, and may be configured to determine first persistent memory namespace size information based on the storage space size information, so as to create the first persistent memory namespace on the storage device.
And the namespace mapping unit is used for mapping the first persistent memory namespace to the interior of the virtual machine so as to enable the virtual machine to scan and discover the storage equipment.
Optionally, the namespace mapping unit is configured to add character device information to the virtual machine process, where the character device information is information of a character device associated with the first persistent memory namespace.
And the second space creating unit is used for correspondingly creating a second persistent memory name space inside the virtual machine according to the storage device discovered by successful scanning.
Optionally, the second space creating unit is configured to create a second persistent memory namespace associated with block device information inside the virtual machine, where the block device information corresponds to the character device information.
And the file system forming unit is used for creating and mounting a file system on the second persistent memory name space, and the container in the virtual machine accesses the first persistent memory name space through the file system.
Optionally, the file system forming unit is configured to identify the second persistent memory namespace as a block device. The file system forming unit may be further configured to create a file system on the block device and mount the file system.
The persistent memory access device for the container in the cloud platform virtual machine in one or more embodiments of the present invention may further include a storage resource releasing module.
The storage resource releasing module can be used for unloading and deleting the file system according to the fact that the use of the persistent memory resources by the container is finished, and can be used for deleting the character device information and the second persistent memory name space. The storage resource releasing module is further configured to send a deletion notification of the persistent memory namespace to the host node based on completion of deletion of the second persistent memory namespace, so as to delete the first persistent memory namespace.
As shown in fig. 5, based on the same inventive technical concept, one or more embodiments of the present invention can also provide a computer device, where the computer device includes a storage and a processor, and the storage stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the processor executes the steps of the persistent memory access method for a container in a cloud platform virtual machine according to any embodiment of the present invention. It should be understood that the detailed execution process of the persistent memory access method for a container in a cloud platform virtual machine according to the present invention is described in detail in this specification, and is not described herein again.
As shown in fig. 5, based on the same technical concept, one or more embodiments of the present invention can further provide a storage medium storing computer-readable instructions, which when executed by one or more processors, cause the one or more processors to perform the steps of the persistent memory access method for a container in a cloud platform virtual machine according to any embodiment of the present invention. It should be understood that the detailed execution process of the persistent memory access method for a container in a cloud platform virtual machine according to the present invention is described in detail in this specification, and is not described herein again.
Based on the same inventive technical concept as the persistent memory access method for the container in the cloud platform virtual machine, one or more embodiments of the present invention can also provide a computer program product, and when instructions in the computer program product are executed by a processor, the steps of the persistent memory access method for the container in the cloud platform virtual machine in any embodiment of the present invention are performed. It can be understood that the detailed execution process of the persistent memory access method for the container in the cloud platform virtual machine according to the present invention is described in detail in this specification, and is not described herein again.
The logic and/or steps represented in the flowcharts or otherwise described herein, such as an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable storage medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable storage medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer cartridge (magnetic device), a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM-Only Memory, or flash Memory), an optical fiber device, and a portable Compact Disc Read-Only Memory (CDROM). Additionally, the computer-readable storage medium may even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic Gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic Gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
In the description herein, references to the description of the term "the present embodiment," "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present invention, "a plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents and simplifications made in the spirit of the present invention are intended to be included in the scope of the present invention.
Claims (10)
1. A persistent memory access method for a container in a cloud platform virtual machine is characterized by comprising the following steps:
creating a first persistent memory name space on storage equipment under a host machine node according to storage use request information of a container in a virtual machine; the storage device is a persistent memory device;
mapping the first persistent memory name space to the inside of a virtual machine so that the virtual machine scans and discovers the storage device;
according to the successful scanning, the storage equipment is found, and a second persistent memory name space is correspondingly established inside the virtual machine;
and creating and mounting a file system on the second persistent memory namespace, wherein the container in the virtual machine accesses the first persistent memory namespace through the file system.
2. The method according to claim 1, wherein the creating a first persistent memory namespace on a storage device under a host node according to storage usage request information of the container in the virtual machine comprises:
reading the storage space size information contained in the storage use request information;
determining first persistent memory namespace size information based on the storage space size information to create a first persistent memory namespace on the storage device.
3. The method of claim 1 or 2, wherein mapping the first persistent memory namespace to the virtual machine interior comprises:
and adding character equipment information to the process of the virtual machine, wherein the character equipment information is the information of the character equipment associated with the first persistent memory name space.
4. The method according to claim 3, wherein the correspondingly creating a second persistent memory namespace inside the virtual machine comprises:
creating a second persistent memory namespace associated with block device information inside the virtual machine, the block device information corresponding to the character device information.
5. The method of claim 4, wherein creating and mounting a file system on the second persistent memory namespace comprises:
identifying the second persistent memory namespace as a block device;
and creating a file system on the block device, and mounting the file system.
6. The method of claim 3, further comprising:
unloading and deleting the file system, and deleting the character device information and the second persistent memory name space according to the fact that the container has finished using the persistent memory resources;
sending a deletion notification of the persistent memory namespace to the host node based on the completion of the deletion of the second persistent memory namespace, so as to delete the first persistent memory namespace.
7. A persistent memory access device for a container in a cloud platform virtual machine, comprising:
the system comprises a first space creating unit, a first persistent memory naming space creating unit and a second space creating unit, wherein the first space creating unit is used for creating a first persistent memory naming space on storage equipment under a host machine node according to storage use request information of a container in a virtual machine; the storage device is a persistent memory device;
the namespace mapping unit is used for mapping the first persistent memory namespace to the interior of the virtual machine so as to enable the virtual machine to scan and discover the storage equipment;
a second space creating unit, configured to discover the storage device according to successful scanning, and correspondingly create a second persistent memory namespace inside the virtual machine;
and the file system forming unit is used for creating and mounting a file system on the second persistent memory namespace, and the container in the virtual machine accesses the first persistent memory namespace through the file system.
8. A computer device comprising a memory and a processor, the memory having stored therein computer-readable instructions which, when executed by the processor, cause the processor to perform the steps of the method for persistent memory access of a container in a cloud platform virtual machine according to any of claims 1 to 6.
9. A storage medium storing computer readable instructions, which when executed by one or more processors, cause the one or more processors to perform the steps of the method for persistent memory access for containers in cloud platform virtual machines according to any of claims 1 to 6.
10. A computer program product, characterized in that instructions in the computer program product, when executed by a processor, perform the steps of the method for persistent memory access for a container in a cloud platform virtual machine according to any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111651614.2A CN114356501A (en) | 2021-12-30 | 2021-12-30 | Persistent memory access method and device for container in cloud platform virtual machine |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111651614.2A CN114356501A (en) | 2021-12-30 | 2021-12-30 | Persistent memory access method and device for container in cloud platform virtual machine |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114356501A true CN114356501A (en) | 2022-04-15 |
Family
ID=81104118
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111651614.2A Pending CN114356501A (en) | 2021-12-30 | 2021-12-30 | Persistent memory access method and device for container in cloud platform virtual machine |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114356501A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108667904A (en) * | 2018-04-10 | 2018-10-16 | 浙江大学 | A kind of Docker containers long-distance inner volume management method and system |
| CN111858509A (en) * | 2020-07-06 | 2020-10-30 | 苏州浪潮智能科技有限公司 | Distributed computing method and device based on container |
| CN113687908A (en) * | 2021-07-23 | 2021-11-23 | 济南浪潮数据技术有限公司 | PMEM virtual machine creation method, device, equipment and readable storage medium |
| CN113687779A (en) * | 2021-07-29 | 2021-11-23 | 济南浪潮数据技术有限公司 | Data migration method and device, electronic equipment and readable storage medium |
| CN113806019A (en) * | 2021-09-15 | 2021-12-17 | 济南浪潮数据技术有限公司 | Method for binding and unbinding PMEM (Power management and communication) equipment in OpenStack cloud platform |
-
2021
- 2021-12-30 CN CN202111651614.2A patent/CN114356501A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108667904A (en) * | 2018-04-10 | 2018-10-16 | 浙江大学 | A kind of Docker containers long-distance inner volume management method and system |
| CN111858509A (en) * | 2020-07-06 | 2020-10-30 | 苏州浪潮智能科技有限公司 | Distributed computing method and device based on container |
| CN113687908A (en) * | 2021-07-23 | 2021-11-23 | 济南浪潮数据技术有限公司 | PMEM virtual machine creation method, device, equipment and readable storage medium |
| CN113687779A (en) * | 2021-07-29 | 2021-11-23 | 济南浪潮数据技术有限公司 | Data migration method and device, electronic equipment and readable storage medium |
| CN113806019A (en) * | 2021-09-15 | 2021-12-17 | 济南浪潮数据技术有限公司 | Method for binding and unbinding PMEM (Power management and communication) equipment in OpenStack cloud platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106648463B (en) | Nand Flash block management method and system | |
| CN111124286A (en) | Libcloud-based multi-cloud management implementation method | |
| EP3322155B1 (en) | Virtual disk processing method and apparatus | |
| US20120102289A1 (en) | Organization of a small object area and a large object area in a java heap | |
| WO2017050064A1 (en) | Memory management method and device for shared memory database | |
| CN112612623B (en) | Method and equipment for managing shared memory | |
| CN115686932B (en) | Backup set file recovery method and device and computer equipment | |
| CN113032099A (en) | Cloud computing node, file management method and device | |
| WO2024041376A1 (en) | Distributed graph data processing system, method, apparatus and device, and storage medium | |
| CN110955488A (en) | Virtualization method and system for persistent memory | |
| CN110753040B (en) | Request processing method and device | |
| CN115269450A (en) | Memory cooperative management system and method | |
| CN111352689B (en) | Method and device for realizing seamless migration of application containerized deployment | |
| CN108304144B (en) | Data writing-in and reading method and system, and data reading-writing system | |
| CN112559127B (en) | Virtual machine creation method, device, host and storage medium | |
| CN116760913B (en) | Method and system for issuing k8s cluster protocol conversion platform configuration | |
| CN111352899A (en) | Path aggregation method, access method, communication device and storage medium | |
| CN110471744B (en) | Password modification method, device, equipment and computer readable storage medium | |
| CN111399753B (en) | Method and device for writing pictures | |
| CN114356501A (en) | Persistent memory access method and device for container in cloud platform virtual machine | |
| CN115562590A (en) | Method, system, equipment and storage medium for using cloud hard disk by cloud host | |
| CN106775456B (en) | A kind of data processing method, apparatus and system | |
| CN107423096A (en) | A kind of method and device for realizing software installation | |
| CN117539409B (en) | Query acceleration method and device based on data cache, medium and electronic equipment | |
| EP3933582B1 (en) | Distributed storage method and device, electronic apparatus and computer-readable medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220415 |