CN117032905A - Method and system for associating container cluster with block storage and virtual machine - Google Patents
Method and system for associating container cluster with block storage and virtual machine Download PDFInfo
- Publication number
- CN117032905A CN117032905A CN202311294657.9A CN202311294657A CN117032905A CN 117032905 A CN117032905 A CN 117032905A CN 202311294657 A CN202311294657 A CN 202311294657A CN 117032905 A CN117032905 A CN 117032905A
- Authority
- CN
- China
- Prior art keywords
- volume
- block
- association
- controlling
- instruction
- 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.)
- Granted
Links
- 238000003860 storage Methods 0.000 title claims abstract description 147
- 238000000034 method Methods 0.000 title claims abstract description 95
- 230000002085 persistent effect Effects 0.000 claims abstract description 110
- 230000004044 response Effects 0.000 claims abstract description 84
- 230000002688 persistence Effects 0.000 claims abstract description 41
- 230000008569 process Effects 0.000 claims abstract description 31
- 238000013507 mapping Methods 0.000 claims abstract description 22
- 239000003818 cinder Substances 0.000 claims description 65
- 241000380131 Ammophila arenaria Species 0.000 claims description 7
- 230000014759 maintenance of location Effects 0.000 claims 2
- 230000005540 biological transmission Effects 0.000 abstract description 7
- 238000004891 communication Methods 0.000 description 9
- 238000012423 maintenance Methods 0.000 description 7
- 230000003993 interaction Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000007726 management method Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000010354 integration 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
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/4555—Para-virtualisation, i.e. guest operating system has to be modified
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0604—Improving or facilitating administration, e.g. storage management
- G06F3/0607—Improving or facilitating administration, e.g. storage management by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0662—Virtualisation aspects
- G06F3/0665—Virtualisation aspects at area level, e.g. provisioning of virtual or logical volumes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45583—Memory management, e.g. access or allocation
-
- 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)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method, a system and a virtual machine for associating a container cluster with block storage, and relates to the technical field of service deployment, wherein the method comprises the steps of firstly controlling the container cluster to create a resource object with a persistent volume declaration object; then controlling the persistent volume declaration object to send an association instruction to the block storage, and receiving a response result corresponding to the association instruction in real time; then, after the control block stores the volume which is created according to the association instruction, generating a response result by utilizing the attribute parameters of the volume, and sending the response result to the persistence volume declaration object; controlling the persistent volume declaration object to acquire the attribute parameters of the volume according to the received response result, and mapping the volume into the block equipment by utilizing the attribute parameters; and finally, after the block equipment is mounted to the resource object, the association between the resource object and the block storage is controlled. According to the method, the block equipment is directly mounted in the resource object of the container cluster in the association process, so that the efficiency of storage access and data transmission is improved.
Description
Technical Field
The present invention relates to the field of service deployment technologies, and in particular, to a method, a system, and a virtual machine for associating a container cluster with a block storage.
Background
Container clusters are directed to containerized deployments, which need to be associated with block storage during use. Taking the use of openstack block storage service by kubernetes cluster as an example, the process of associating the two is mainly implemented by a third party plug-in, for example: cinder CSI Plugin. However, configuration Cinder CSI Plugin requires complex steps and setup, and relies on the OpenStack environment, while such plug-ins also suffer from latency problems, lower performance, and higher deployment and maintenance costs.
Disclosure of Invention
In view of the above, the present invention aims to provide a method, a system and a virtual machine for associating a container cluster with a block storage, in which a block device is directly mounted to a resource object of the container cluster in an association process, thereby improving efficiency of storage access and data transmission; according to the method, an OpenStack environment is not required to be deployed when the Kubernetes cluster is associated with the Cinder block storage service, and only the Cinder block storage related components are required to be deployed, so that the configuration flow is simplified, the performance and response time in the interaction process of the Kubernetes cluster and the Cinder block storage are improved, and the problems in the prior art are solved.
In a first aspect, embodiments of the present invention provide a method for associating a container cluster with a block store, where the method is applied to a virtual machine in which the container cluster and the block store have been deployed; wherein the resource object of the container cluster is connected with the persistent volume declaration object; the persistent volume declaration object is connected with the block storage; the persistent volume declaration object is also connected with a block device in the virtual machine;
the method comprises the following steps:
controlling the container cluster to create a resource object with a persistent volume declaration object;
controlling the persistent volume statement object to send an association instruction to the block storage, and receiving a response result corresponding to the association instruction in real time;
after the control block stores the volume which is created according to the association instruction, generating a response result by utilizing the attribute parameters of the volume, and sending the response result to the persistence volume declaration object;
controlling the persistent volume declaration object to acquire the attribute parameters of the volume according to the received response result, and mapping the volume into the block equipment by utilizing the attribute parameters;
after the block device is mounted to the resource object, the association between the resource object and the block storage is controlled.
In one embodiment, the step of controlling the container cluster to create a resource object with a persistent volume declaration object includes:
Acquiring an initialized Kubernetes container cluster and a Cinder block storage from a virtual machine;
acquiring a PV (photovoltaic) persistent volume corresponding to the Cinder block storage, and creating a PVC persistent volume declaration object by using the PV persistent volume;
the Kubernetes container cluster is controlled to create a Pod resource object and associate the Pod resource object with a PVC persistence volume declaration object.
In one embodiment, the step of controlling the persistent volume declaration object to send the association instruction to the block store and receiving the response result corresponding to the association instruction in real time includes:
establishing a long link between the PVC persistent volume declaration object and the block storage Cinder;
using the long link to control the PVC persistence volume declaration object to send an association instruction to the Cinder block storage; the associated instruction at least comprises a request instruction for creating a volume;
and controlling the PVC persistence declaration object to monitor the response result sent by the Cinder block storage in real time.
In one embodiment, the step of generating a response result by using the attribute parameters of the volume after the control block stores the volume is created according to the association instruction and transmitting the response result to the persistent volume declaration object includes:
after receiving the association instruction, the block storage Cinder establishes a volume according to a request instruction in the association instruction, and acquires attribute parameters of the volume;
Determining a response result corresponding to the association instruction by utilizing the attribute parameters of the volume; wherein, the response result at least comprises a unique ID value corresponding to the volume;
and sending the response result to the PVC persistence statement object.
In one embodiment, after the step of sending the response result to the PVC persistence declaration object, the method further includes:
the long link between the PVC persistence volume declaration object and the block store Cinder is closed.
In one embodiment, the step of controlling the persistent volume declaration object to obtain the attribute parameters of the volume according to the received response result and mapping the volume into the block device using the attribute parameters includes:
controlling the PVC persistent volume statement object to analyze the response result to obtain the attribute data and the corresponding ID value of the volume;
determining a mapping instruction between the PVC persistence volume declaration object and the block equipment according to the attribute data of the volume and the corresponding ID value;
and mapping the volume corresponding to the PVC persistent volume declaration object into the block equipment by using the mapping instruction.
In one embodiment, after mounting the block device to the resource object, the step of controlling the association of the resource object with the block storage completion includes:
acquiring a starting path corresponding to the block equipment and a terminating path corresponding to the Pod resource object;
Determining a mounting instruction according to the attribute data of the initial path, the termination path and the block equipment;
and after the block equipment is mounted to the resource object by using the mounting instruction, controlling the resource object to be associated with the block storage.
In one embodiment, a process for controlling the association of a resource object with a block store completion includes:
acquiring a Kubernetes container cluster and storing a corresponding palm associated instruction by a Cinder block;
the resource object is controlled to be associated with the block storage by using a helm association instruction.
In a second aspect, embodiments of the present invention provide a system for associating a container cluster with a block store, where the system is applied to a virtual machine in which the container cluster and the block store have been deployed; wherein the resource object of the container cluster is connected with the persistent volume declaration object; the persistent volume declaration object is connected with the block storage; the persistent volume declaration object is also connected with a block device in the virtual machine;
the system comprises:
a first association module for controlling the container cluster to create a resource object with a persistent volume declaration object;
the second association module is used for controlling the persistent volume statement object to send association instructions to the block storage and receiving response results corresponding to the association instructions in real time;
The third association module is used for controlling the control block to generate a response result by utilizing the attribute parameters of the volume after the volume is created according to the association instruction, and sending the response result to the persistent volume declaration object;
a fourth association module, configured to control the persistent volume declaration object to obtain an attribute parameter of the volume according to the received response result, and map the volume into the block device by using the attribute parameter;
and the fifth association module is used for controlling the association between the resource object and the block storage after the block equipment is mounted on the resource object.
In a third aspect, an embodiment of the present invention further provides a virtual machine, where the virtual machine includes: container clusters and block storage; the resource object of the container cluster is connected with the persistent volume declaration object; the persistent volume declaration object is connected with the block storage; the persistent volume declaration object is also connected with a block device in the virtual machine;
the virtual machine adopts the steps of the association method of the container cluster and the block storage mentioned in the first aspect in the process of associating the container cluster and the block storage.
In a fourth aspect, embodiments of the present invention also provide an electronic device, including a processor and a memory, the memory storing computer-executable instructions executable by the processor, the processor executing the computer-executable instructions to implement the steps of the method for associating container clusters with block storage provided in the first aspect.
In a fifth aspect, embodiments of the present invention also provide a storage medium storing computer-executable instructions that, when invoked and executed by a processor, cause the processor to implement the steps of the method for associating container clusters with block stores provided in the first aspect.
The embodiment of the invention provides a method, a system and a virtual machine for associating a container cluster with a block storage, wherein the method is applied to the virtual machine with the deployed container cluster and the deployed block storage; wherein the resource object of the container cluster is connected with the persistent volume declaration object; the persistent volume declaration object is connected with the block storage; the persistent volume declaration object is also connected with a block device in the virtual machine. In the process of associating a container cluster of a virtual machine with a block store, firstly controlling the container cluster to create a resource object with a persistent volume declaration object; then controlling the persistent volume declaration object to send an association instruction to the block storage, and receiving a response result corresponding to the association instruction in real time; then, after the control block stores the volume which is created according to the association instruction, generating a response result by utilizing the attribute parameters of the volume, and sending the response result to the persistence volume declaration object; controlling the persistent volume declaration object to acquire the attribute parameters of the volume according to the received response result, and mapping the volume into the block equipment by utilizing the attribute parameters; and finally, after the block equipment is mounted to the resource object, the association between the resource object and the block storage is controlled. According to the method, the block equipment is directly mounted in the resource object of the container cluster in the association process, so that the efficiency of storage access and data transmission is improved; the method has the advantages that an OpenStack environment is not required to be deployed when the Kubernetes cluster is associated with the Cinder block storage service, only the Cinder block storage related components are required to be deployed, so that the configuration flow is simplified, the performance and response time in the interaction process of the Kubernetes cluster and the Cinder block storage are improved, and the problems of higher delay, lower performance and higher deployment and maintenance cost in the prior art are solved.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
In order to make the above objects, features and advantages of the present invention more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are needed in the description of the embodiments or the prior art will be briefly described, and it is obvious that the drawings in the description below are some embodiments of the present invention, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of a method for associating a container cluster with a block store according to an embodiment of the present invention;
fig. 2 is a flowchart of step S101 in a method for associating a container cluster with a block storage according to an embodiment of the present invention;
FIG. 3 is a flowchart of step S102 in a method for associating a container cluster with a block store according to an embodiment of the present invention;
fig. 4 is a flowchart of step S103 in a method for associating a container cluster with a block store according to an embodiment of the present invention;
FIG. 5 is a flowchart of step S104 in a method for associating a container cluster with a block store according to an embodiment of the present invention;
FIG. 6 is a flowchart of step S105 in a method for associating a container cluster with a block store according to an embodiment of the present invention;
FIG. 7 is a flowchart of a method for associating a container cluster with a block store to control the association of a resource object with the block store according to an embodiment of the present invention;
FIG. 8 is a schematic diagram of a system for associating a container cluster with a block store according to an embodiment of the present invention;
FIG. 9 is a flowchart of another association method of container clusters and chunk store provided by an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a virtual machine according to an embodiment of the present invention;
fig. 11 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Icon:
910-a first association module; 920-a second association module; 930-a third association module; 940-fourth association module; 950-a fifth association module;
1010—a cluster of containers; 1020-block storage; 1030-resource object; 1040-persist volume declaration object; 1050-block device;
a 101-processor; 102-memory; 103-bus; 104-communication interface.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the present invention will be clearly and completely described in conjunction with the embodiments, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Container clusters are directed to containerized deployments, which need to be associated with block storage during use. Taking the use of openstack block storage service by kubernetes cluster as an example, the process of associating the two is mainly implemented by a third party plug-in, for example: cinderCSIPlugin. In particular, cinderCSIPlugin is a solution for using the openstack cinder block storage service in Kubernetes clusters. It integrates Cinder storage into Kubernetes by implementing the CSI (ContainerStorageInterface) specification of Kubernetes so that Kubernetes users can conveniently manage and use Cinder volumes as persistent storage. By using the CinderCSIPlugin, kubernetes users can directly utilize the block storage services provided by openstack cinder and integrate with other Kubernetes functions such as dynamic volume allocation, pod scheduling, and lifecycle management. In this way, a user can easily manage and use the OpenStack block store in the Kubernetes cluster, providing a reliable persistent storage solution for applications.
In the above process, the PVC initiates a request to the opentackcinder to create a volume through the createvalume interface. The full name of PV is persistence volume, namely: persistent volumes, which are an abstraction of the underlying shared storage, are created and configured by administrators. The PVC is known as PersistenVolumeClaim, namely: persistent volume declarations, PVC is a declaration stored by users, PVC and Pod are comparison types, pod is a consumption node, PVC consumes PV resources, pod can request CPU memory, and PVC can request specific storage space and access modes. For a truly stored user, the storage implementation details of the bottom layer do not need to be concerned, and only the PVC needs to be directly used.
After the Cinder creates the volume, the control rpubrish interface mounts the volume to the target host, that is, after the virtual machine in which the Kubernetes is located is mounted to the virtual machine, the volume becomes a block device on the virtual machine. Then the node side mounts the volume to a globalmount catalog through a nodestagevolume; and finally, the global volume is mounted to the pod by a nodepulish interface.
The existing scheme has the following problems in the association process:
configuration and complexity aspects: configuring a CinderCSIPlugin may require some complex steps and settings, particularly involving communication and authentication with the openstack cinderapi. This requires a certain knowledge and experience of the administrator and may require additional configuration effort, increasing the complexity of deployment and management.
Depending on the OpenStack environment: cinderCSIPlugin is designed for integration with the OpenStack storage service and therefore depends on an OpenStack running environment. If there is no OpenStack environment available, or if the OpenStack cinderapi cannot be accessed in other environments, then CinderCSIPlugin cannot be used.
Performance and latency issues: the use of CinderCSIPlugin for data storage involves communication with openstack cinder through Kubernetes and CSI drivers, possibly introducing some performance overhead and additional network delay. This may have some impact on certain applications that have extremely high performance requirements.
Deployment and maintenance work problems: deployment and maintenance of a CinderCSIPlugin may require some additional work, including installation, configuration, and updating. This requires a certain technical knowledge and expertise of the administrator to ensure proper operation and continued availability of the plug-in.
In summary, it is known that the configuration of the CinderCSIPlugin requires complex steps and settings, and depends on the OpenStack environment, and such plug-ins have delay problems, and are low in performance and high in deployment and maintenance costs. Based on the method, the system and the virtual machine for associating the container cluster with the block storage are provided, and the method has the advantages that the block equipment is directly mounted in the resource object of the container cluster in the association process, so that the efficiency of storage access and data transmission is improved; according to the method, an OpenStack environment is not required to be deployed when the Kubernetes cluster is associated with the Cinder block storage service, and only the Cinder block storage related components are required to be deployed, so that the configuration flow is simplified, the performance and response time in the interaction process of the Kubernetes cluster and the Cinder block storage are improved, and the problems in the prior art are solved.
For the convenience of understanding the present embodiment, first, a method for associating a container cluster with a block storage disclosed in the present embodiment is described in detail, where the method is applied to a virtual machine where the container cluster and the block storage are deployed; wherein the resource object of the container cluster is connected with the persistent volume declaration object; the persistent volume declaration object is connected with the block storage; the persistent volume declaration object is also connected with a block device in the virtual machine.
On the basis, as shown in fig. 1, the method comprises the following steps:
in step S101, the control container cluster creates a resource object with a persistent volume declaration object.
The persistent volume declaration related in the persistent volume declaration object is PVC (Persistent Volume Claim), and PVC is a declaration stored by a user, so that the user really stores the persistent volume declaration object without concern about storage implementation details of the bottom layer, and only needs to directly use the PVC. The persistent volume declares the persistent volume in the object as PV (Persistent Volume), an abstraction of the underlying shared storage. The resource object is a consumption node and can request the memory of the host CPU corresponding to the virtual machine; while the persistent volume declaration object may request a particular storage space and access pattern.
Step S102, controlling the persistent volume statement object to send an association instruction to the block storage, and receiving a response result corresponding to the association instruction in real time.
And after the container cluster and the block storage are deployed in the virtual machine, the container cluster sends an association instruction to the block storage by using the persistent volume declaration object, and receives a response result of the instruction in real time after the association instruction is sent.
In step S103, the control block generates a response result using the attribute parameters of the volume after creating the complete volume according to the association instruction, and sends the response result to the persistent volume declaration object.
For block storage, after receiving an association instruction sent by a persistent volume declaration object, a volume creation process is performed according to the association instruction. After the block storage completes the creation of the volume, the attribute data of the volume is utilized to generate a response result of the association instruction, and the response result is recalled into the persistent volume declaration object.
Step S104, controlling the persistent volume declaration object to acquire the attribute parameters of the volume according to the received response result, and mapping the volume into the block device by utilizing the attribute parameters.
After the persistent volume declaration object receives the response result from the block device, the attribute parameters of the volume can be obtained from the response result. The attribute parameters at this time can remain corresponding to the volume, so the volume can be mapped into the block device using the attribute parameters.
Step S105, after the block device is mounted to the resource object, the association between the resource object and the block storage is controlled.
The block device is disposed in the virtual machine and does not belong to the container cluster, so the block device can be mounted into the resource object using the attribute parameters of the volume. At this point, an association is achieved between the resource object and the block store, specifically, the block store associates the generated volume with the resource object of the container cluster by persisting the volume declaration object and the block device. In an actual scenario, for a host machine of a virtual machine, the method is also applicable to a physical host machine related to the host machine, which is not described herein.
The association method of the container clusters with the block store is described below with particular reference to Kubernetes container clusters and Cinder block store. In one embodiment, the step S101 of controlling the container cluster to create a resource object with a persistent volume declaration object, as shown in fig. 2, includes:
step S201, an initialized Kubernetes container cluster and a Cinder block storage are obtained from a virtual machine;
step S202, acquiring a PV persistence volume corresponding to a Cinder block storage, and creating a PVC persistence volume declaration object by using the PV persistence volume;
In step S203, the Kubernetes container cluster is controlled to create a Pod resource object, and associate the Pod resource object with the PVC persistence volume declaration object.
The above process ultimately enables the creation of Pod resource objects with PVC persistence volume declarations in Kubernetes container clusters.
In one embodiment, the step S102 of controlling the persistent volume declaration object to send the association instruction to the block store and receive the response result corresponding to the association instruction in real time, as shown in fig. 3, includes:
step S301, establishing a long link between a PVC persistent volume declaration object and a block storage Cinder;
step S302, a long link is used for controlling a PVC persistent volume statement object to send an association instruction to a Cinder block storage; the associated instruction at least comprises a request instruction for creating a volume;
step S303, the PVC persistence declaration object is controlled to monitor the response result sent by the Cinder block storage in real time.
The PVC persistence volume declaration object sends an association instruction to the Cinder block store through the associated transport interface. The associated instruction comprises a relevant request instruction for creating the volume, and the Cinder block storage can complete the creation process of the volume according to the associated instruction. For PVC persistence volume declaration objects, long links need to be established with the block store Cinder and then associated instructions need to be sent to the Cinder block store. And simultaneously, monitoring the response result of the associated instruction sent by the Cinder block storage in real time.
In one embodiment, the step S103 of generating a response result by using the attribute parameters of the volume after the volume is created according to the association instruction and transmitting the response result to the persistent volume declaration object is stored by the control block, as shown in fig. 4, and includes:
step S401, after receiving the association instruction, the block storage Cinder establishes a volume according to a request instruction in the association instruction, and acquires attribute parameters of the volume;
step S402, determining a response result corresponding to the association instruction by utilizing the attribute parameters of the volume; wherein, the response result at least comprises a unique ID value corresponding to the volume;
step S403, the response result is sent to the PVC persistence statement object.
Specifically, after the block storage Cinder receives the association instruction, the volume is built by using a request instruction in the association instruction. After the establishment of the coil is completed, corresponding attribute parameters can be obtained, and a response result of the association instruction is determined according to the attribute parameters, wherein the response result comprises an ID value capable of uniquely characterizing the coil. And then the response result is sent to the PVC persistent declaration object, and the PVC persistent declaration object can directly acquire the response result of the association instruction through the monitoring process under normal conditions.
After the step of sending the response result to the PVC persistence volume declaration object, the long link is no longer needed, at which point the long link between the PVC persistence volume declaration object and the block store Cinder may be closed.
In one embodiment, the step S104 of controlling the persistent volume declaration object to obtain the attribute parameters of the volume according to the received response result and mapping the volume to the block device by using the attribute parameters, as shown in fig. 5, includes:
step S501, the PVC persistent volume declaration object is controlled to analyze the response result to obtain the attribute data and the corresponding ID value of the volume;
step S502, determining a mapping instruction between a PVC persistence volume declaration object and block equipment according to the attribute data of the volume and the corresponding ID value;
step S503, mapping the volume corresponding to the PVC persistence volume statement object into the block device by using the mapping instruction.
The PVC persistence volume declaration object obtains the attribute data and corresponding ID value of the volume, i.e., maps the volume to a piece of block equipment of the virtual machine. Specifically, the response result is analyzed after being acquired by the PVC persistence volume declaration object, so as to obtain the attribute data of the volume and the corresponding ID value; and then, mapping the volume from the PVC persistence volume declaration object to the block equipment by using the mapping instruction generated by the attribute data of the volume and the corresponding ID value.
In one embodiment, after the block device is mounted to the resource object, step S105 in associating the resource object with the block storage completion is controlled, as shown in fig. 6, including:
Step S601, acquiring a starting path corresponding to block equipment and a terminating path corresponding to a Pod resource object;
step S602, determining a mounting instruction according to the attribute data of the initial path, the termination path and the block equipment;
step S603, after the block device is mounted to the resource object by using the mounting instruction, the association between the resource object and the block storage is controlled.
At this time, the block device contains the relevant information of the volume, so that the association between the container cluster and the block storage can be realized by associating the block device with the resource object. In a specific implementation process, the volume can be formatted on kubernetes nodes and mounted in a global temporary directory; the volume may also be mounted from a global temporary directory to a designated directory. In the specific implementation process, a mounting instruction of the volume is determined by using a starting path corresponding to the block device, a terminating path corresponding to the Pod resource object and attribute data of the block device, and then the mounting instruction is used for mounting the block device to the resource object, and then the resource object is controlled to be associated with the block storage.
In one embodiment, the process of controlling the association of resource objects with block store completions, as shown in FIG. 7, includes:
Step S701, a Kubernetes container cluster and a corresponding palm association instruction stored by a Cinder block are obtained;
in step S702, the associating of the resource object with the block storage is completed under the control of the helm associating instruction.
A specific association process may be deployed using a helm, which is a package manager of Kubernetes, similar to apt, yum, pip, that can quickly find, download, and install software packages. In the process of controlling the association of the resource object and the block storage by using the helm association instruction, the association can be completed quickly by executing a simple command, so that the configuration and deployment process between the Kubernetes cluster and the Cinder block storage service is simplified. Compared with the existing implementation mode, the method does not need to deploy an openstack cluster, and only needs to deploy a Cinder component. Because the pod is directly mounted on the block device of the host, the storage access and the data transmission are optimized, and the performance and the response time of the Kubernetes cluster to the Cinder block storage service are improved.
In a specific implementation process, referring to another association method of container clusters and block storage as shown in fig. 8, when Kubernetes creates Pod with PVC, PVC initiates a request to openstack container to create a volume through a CreateVolume interface, and after creation is completed, the ID of the volume is returned. The PVC then gets the initialization information for the volume, which is mapped to a block device (/ dev/rbd 0) of the host. Finally, the block device (/ dev/rbd 0) is directly mounted to the Pod, so that the Pod can store, communicate and use in the Cinder block.
According to the method for associating the container cluster with the block storage, which is mentioned in the embodiment, the block equipment is directly mounted in the resource object of the container cluster in the association process, so that the efficiency of storage access and data transmission is improved; the method has the advantages that an OpenStack environment is not required to be deployed when the Kubernetes cluster is associated with the Cinder block storage service, only the Cinder block storage related components are required to be deployed, so that the configuration flow is simplified, the performance and response time in the interaction process of the Kubernetes cluster and the Cinder block storage are improved, and the problems of higher delay, lower performance and higher deployment and maintenance cost in the prior art are solved.
Corresponding to the association method of the container cluster and the block storage provided by the foregoing embodiment, the embodiment of the present invention provides an association system of the container cluster and the block storage, where the system is applied to a virtual machine where the container cluster and the block storage are deployed; wherein the resource object of the container cluster is connected with the persistent volume declaration object; the persistent volume declaration object is connected with the block storage; the persistent volume declaration object is also connected with a block device in the virtual machine;
on this basis, as shown in fig. 9, the system includes:
A first association module 910 for controlling the container cluster to create a resource object with a persistent volume declaration object;
the second association module 920 is configured to control the persistent volume declaration object to send an association instruction to the block storage, and receive a response result corresponding to the association instruction in real time;
a third association module 930, configured to control the control block to generate a response result using the attribute parameters of the volume after creating the volume according to the association instruction, and send the response result to the persistent volume declaration object;
a fourth association module 940, configured to control the persistent volume declaration object to obtain an attribute parameter of the volume according to the received response result, and map the volume into the block device using the attribute parameter;
and a fifth association module 950, configured to control association between the resource object and the block storage after the block device is mounted to the resource object.
In one embodiment, the first association module 910 is further configured to: acquiring an initialized Kubernetes container cluster and a Cinder block storage from a virtual machine; acquiring a PV (photovoltaic) persistent volume corresponding to the Cinder block storage, and creating a PVC persistent volume declaration object by using the PV persistent volume; the Kubernetes container cluster is controlled to create a Pod resource object and associate the Pod resource object with a PVC persistence volume declaration object.
In one embodiment, the second association module 920 is further configured to: establishing a long link between the PVC persistent volume declaration object and the block storage Cinder; using the long link to control the PVC persistence volume declaration object to send an association instruction to the Cinder block storage; the associated instruction at least comprises a request instruction for creating a volume; and controlling the PVC persistence declaration object to monitor the response result sent by the Cinder block storage in real time.
In one embodiment, the third association module 930 is further configured to: after receiving the association instruction, the block storage Cinder establishes a volume according to a request instruction in the association instruction, and acquires attribute parameters of the volume; determining a response result corresponding to the association instruction by utilizing the attribute parameters of the volume; wherein, the response result at least comprises a unique ID value corresponding to the volume; and sending the response result to the PVC persistence statement object.
In one embodiment, the association system of container clusters and chunk stores further comprises: a fifth association module; the fifth association is provided between the third association module 930 and the fourth association module 940, which is configured to: the long link between the PVC persistence volume declaration object and the block store Cinder is closed.
In one embodiment, the fourth association module 940 is further configured to: controlling the PVC persistent volume statement object to analyze the response result to obtain the attribute data and the corresponding ID value of the volume; determining a mapping instruction between the PVC persistence volume declaration object and the block equipment according to the attribute data of the volume and the corresponding ID value; and mapping the volume corresponding to the PVC persistent volume declaration object into the block equipment by using the mapping instruction.
In one embodiment, the fifth association module 950 is further configured to: acquiring a starting path corresponding to the block equipment and a terminating path corresponding to the Pod resource object; determining a mounting instruction according to the attribute data of the initial path, the termination path and the block equipment; and after the block equipment is mounted to the resource object by using the mounting instruction, controlling the resource object to be associated with the block storage.
In one embodiment, the fifth association module 950 is further configured, in a process of controlling the association of the resource object with the block store to complete, to: acquiring a Kubernetes container cluster and storing a corresponding palm associated instruction by a Cinder block; the resource object is controlled to be associated with the block storage by using a helm association instruction.
According to the association system of the container cluster and the block storage, which is provided by the embodiment of the invention, the block equipment is directly mounted in the resource object of the container cluster in the association process, so that the efficiency of storage access and data transmission is improved; the method has the advantages that an OpenStack environment is not required to be deployed when the Kubernetes cluster is associated with the Cinder block storage service, only the Cinder block storage related components are required to be deployed, so that the configuration flow is simplified, the performance and response time in the interaction process of the Kubernetes cluster and the Cinder block storage are improved, and the problems of higher delay, lower performance and higher deployment and maintenance cost in the prior art are solved.
The association system for container cluster and block storage provided by the embodiment of the invention has the same implementation principle and technical effects as those of the foregoing embodiment of the association method for container cluster and block storage, and for brevity, reference may be made to corresponding contents in the foregoing embodiment of the method where the embodiment of the apparatus is not mentioned.
The present embodiment also provides a virtual machine, as shown in fig. 10, including: container clusters 1010 and block stores 1020; the resource object 1030 of the container cluster 1010 is connected with the persistent volume declaration object 1040; the persistent volume declaration object 1040 interfaces with the chunk store 1020; the persistent volume declaration object 1040 is also connected to a block device 1050 in the virtual machine;
the virtual machine adopts the steps of the association method of the container cluster and the block storage mentioned in the above embodiment in the process of associating the container cluster 1010 and the block storage 1020.
The embodiment also provides an electronic device, the structural schematic diagram of which is shown in fig. 11, the device includes a processor 101 and a memory 102; the memory 102 is configured to store one or more computer instructions that are executed by the processor to implement the container cluster and block storage association method described above.
The server shown in fig. 11 further comprises a bus 103 and a communication interface 104, the processor 101, the communication interface 104 and the memory 102 being connected by the bus 103.
The memory 102 may include a high-speed random access memory (RAM, random Access Memory), and may further include a non-volatile memory (non-volatile memory), such as at least one magnetic disk memory. Bus 103 may be an ISA bus, a PCI bus, an EISA bus, or the like. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one bi-directional arrow is shown in FIG. 11, but not only one bus or type of bus.
The communication interface 104 is configured to connect with at least one user terminal and other network units through a network interface, and send the encapsulated IPv4 message or the IPv4 message to the user terminal through the network interface.
The processor 101 may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in the processor 101 or instructions in the form of software. The processor 101 may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU for short), a network processor (Network Processor, NP for short), etc.; but also digital signal processors (Digital Signal Processor, DSP for short), application specific integrated circuits (Application Specific Integrated Circuit, ASIC for short), field-programmable gate arrays (Field-Programmable Gate Array, FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The various methods, steps and logic blocks of the disclosure in the embodiments of the disclosure may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present disclosure may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in the memory 102, and the processor 101 reads information in the memory 102, and in combination with its hardware, performs the steps of the method of the previous embodiment.
The embodiment of the present application also provides a storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the association method of container clusters and block storage of the previous embodiment.
In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. The above-described apparatus embodiments are merely illustrative, for example, the division of the units is merely a logical function division, and there may be other manners of division in actual implementation, and for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some communication interface, indirect coupling or communication connection of devices or units, electrical, mechanical, or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer readable storage medium executable by a processor. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Finally, it should be noted that: the above examples are only specific embodiments of the present invention, and are not intended to limit the scope of the present invention, but it should be understood by those skilled in the art that the present invention is not limited thereto, and that the present invention is described in detail with reference to the foregoing examples: any person skilled in the art may modify or easily conceive of the technical solution described in the foregoing embodiments, or perform equivalent substitution of some of the technical features, while remaining within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention, and are intended to be included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A method for associating a container cluster with a block store, wherein the method is applied to a virtual machine in which the container cluster and the block store are deployed; wherein the resource object of the container cluster is connected with a persistent volume declaration object; the persistent volume declaration object is connected with the block store; the persistent volume declaration object is also connected with a block device in the virtual machine;
The method comprises the following steps:
controlling the container cluster to create a resource object with the persistent volume declaration object;
controlling the persistent volume declaration object to send an association instruction to the block storage, and receiving a response result corresponding to the association instruction in real time;
after the block storage is controlled to create the complete volume according to the association instruction, generating the response result by utilizing the attribute parameters of the volume, and sending the response result to the persistent volume declaration object;
controlling the persistent volume declaration object to acquire the attribute parameters of the volume according to the received response result, and mapping the volume into the block equipment by utilizing the attribute parameters;
and after the block equipment is mounted to the resource object, controlling the resource object to be associated with the block storage.
2. The method of claim 1, wherein the step of controlling the container cluster to create a resource object with the persistent volume declaration object comprises:
acquiring an initialized Kubernetes container cluster and a Cinder block storage from the virtual machine;
acquiring a PV (photovoltaic) persistent volume corresponding to the Cinder block storage, and creating a PVC persistent volume declaration object by using the PV persistent volume;
Controlling the Kubernetes container cluster to create a Pod resource object, and associating the Pod resource object with the PVC persistence volume declaration object.
3. The method for associating a container cluster with a block store according to claim 2, wherein the step of controlling the persistent volume declaration object to send an association instruction to the block store and receiving a response result corresponding to the association instruction in real time comprises:
establishing a long link between the PVC persistent volume declaration object and the block storage Cinder;
controlling the PVC persistent volume declaration object to send the association instruction to the Cinder block storage by using the long link; wherein the association instructions at least comprise a request instruction for creating the volume;
and controlling the PVC persistence statement object to monitor the response result sent by the Cinder block storage in real time.
4. The method of claim 3, wherein the step of controlling the block store to generate the response result using the attribute parameters of the volume after creating a complete volume according to the association instruction and transmitting the response result to the persistent volume declaration object comprises:
After the block storage Cinder receives the association instruction, the volume is built according to the request instruction in the association instruction, and attribute parameters of the volume are obtained;
determining the response result corresponding to the association instruction by utilizing the attribute parameters of the volume; wherein the response result at least comprises a unique ID value corresponding to the volume;
and sending the response result to the PVC persistence statement object.
5. The method of associating a container cluster with a chunk store of claim 4, wherein after the step of sending the response result into the PVC persistence claim object, the method further comprises:
closing the long link between the PVC persistence volume declaration object and the block store Cinder.
6. The method of claim 5, wherein the controlling the persistent volume declaration object to obtain the volume's attribute parameters based on the received response results and mapping the volume into the block device using the attribute parameters comprises:
controlling the PVC persistence volume statement object to analyze the response result to obtain attribute data and a corresponding ID value of the volume;
Determining a mapping instruction between the PVC persistence volume declaration object and the block device according to the attribute data of the volume and the corresponding ID value;
and mapping the volume corresponding to the PVC persistence volume statement object into the block equipment by utilizing the mapping instruction.
7. The method of associating a container cluster with a chunk store of claim 6, wherein the step of controlling the resource object to complete association with the chunk store after mounting the chunk device to the resource object comprises:
acquiring a starting path corresponding to the block device and a terminating path corresponding to the Pod resource object;
determining a mounting instruction according to the initial path, the termination path and attribute data of the block equipment;
and after the block equipment is mounted to the resource object by using the mounting instruction, controlling the resource object to be associated with the block storage.
8. The method of claim 7, wherein controlling the association of the resource object with the chunk store comprises:
acquiring the Kubernetes container cluster and storing a corresponding helm associated instruction by a Cinder block;
And controlling the resource object to be associated with the block storage by utilizing the helm association instruction.
9. An association system of container clusters and block storages, wherein the system is applied to virtual machines where the container clusters and the block storages are deployed; wherein the resource object of the container cluster is connected with a persistent volume declaration object; the persistent volume declaration object is connected with the block store; the persistent volume declaration object is also connected with a block device in the virtual machine;
the system comprises:
a first association module for controlling the container cluster to create a resource object with the persistent volume declaration object;
the second association module is used for controlling the persistent volume statement object to send association instructions to the block storage and receiving response results corresponding to the association instructions in real time;
the third association module is used for controlling the block storage to generate the response result by utilizing the attribute parameters of the volume after the volume is created according to the association instruction, and sending the response result to the persistent volume declaration object;
a fourth association module, configured to control the persistent volume declaration object to obtain an attribute parameter of the volume according to the received response result, and map the volume to the block device by using the attribute parameter;
And the fifth association module is used for controlling the association between the resource object and the block storage after the block equipment is mounted to the resource object.
10. A virtual machine, the virtual machine comprising: container clusters and block storage; the resource object of the container cluster is connected with the persistent volume declaration object; the persistent volume declaration object is connected with the block store; the persistent volume declaration object is also connected with a block device in the virtual machine;
the virtual machine adopts the steps of the association method of the container cluster and the block storage according to any one of claims 1 to 8 in the process of associating the container cluster and the block storage.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311294657.9A CN117032905B (en) | 2023-10-09 | 2023-10-09 | Method and system for associating container cluster with block storage and virtual machine |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311294657.9A CN117032905B (en) | 2023-10-09 | 2023-10-09 | Method and system for associating container cluster with block storage and virtual machine |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117032905A true CN117032905A (en) | 2023-11-10 |
| CN117032905B CN117032905B (en) | 2024-01-23 |
Family
ID=88632276
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311294657.9A Active CN117032905B (en) | 2023-10-09 | 2023-10-09 | Method and system for associating container cluster with block storage and virtual machine |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117032905B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111209011A (en) * | 2019-12-31 | 2020-05-29 | 烽火通信科技股份有限公司 | Cross-platform container cloud automatic deployment system |
| CN111708659A (en) * | 2020-06-10 | 2020-09-25 | 中国—东盟信息港股份有限公司 | Method for constructing cloud native disaster tolerance architecture based on kubernets |
| CN114020457A (en) * | 2021-10-29 | 2022-02-08 | 济南浪潮数据技术有限公司 | OpenStack deployment method and device and electronic equipment |
| DE102020120822A1 (en) * | 2020-08-06 | 2022-02-10 | Endress+Hauser Conducta Gmbh+Co. Kg | stopcock |
| CN114116205A (en) * | 2021-11-10 | 2022-03-01 | 新华三大数据技术有限公司 | Resource management method and device based on kubernets, storage medium and electronic equipment |
| CN116450287A (en) * | 2023-03-20 | 2023-07-18 | 天翼云科技有限公司 | Method, device, equipment and readable medium for managing storage capacity of service container |
-
2023
- 2023-10-09 CN CN202311294657.9A patent/CN117032905B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111209011A (en) * | 2019-12-31 | 2020-05-29 | 烽火通信科技股份有限公司 | Cross-platform container cloud automatic deployment system |
| CN111708659A (en) * | 2020-06-10 | 2020-09-25 | 中国—东盟信息港股份有限公司 | Method for constructing cloud native disaster tolerance architecture based on kubernets |
| DE102020120822A1 (en) * | 2020-08-06 | 2022-02-10 | Endress+Hauser Conducta Gmbh+Co. Kg | stopcock |
| CN114020457A (en) * | 2021-10-29 | 2022-02-08 | 济南浪潮数据技术有限公司 | OpenStack deployment method and device and electronic equipment |
| CN114116205A (en) * | 2021-11-10 | 2022-03-01 | 新华三大数据技术有限公司 | Resource management method and device based on kubernets, storage medium and electronic equipment |
| CN116450287A (en) * | 2023-03-20 | 2023-07-18 | 天翼云科技有限公司 | Method, device, equipment and readable medium for managing storage capacity of service container |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117032905B (en) | 2024-01-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109561171B (en) | Configuration method and device of virtual private cloud service | |
| US20180210752A1 (en) | Accelerator virtualization method and apparatus, and centralized resource manager | |
| US20240045824A1 (en) | Remote Mapping Method, Apparatus and Device for Computing Resources, and Storage Medium | |
| US20220004410A1 (en) | Method For Deploying Virtual Machine And Container, And Related Apparatus | |
| CN108924274B (en) | Domain name system DNS processing method and device, storage medium and electronic equipment | |
| US8417848B2 (en) | Method and apparatus for implementing multiple service processing functions | |
| CN113141405B (en) | Service access method, middleware system, electronic device, and storage medium | |
| CN106657180B (en) | Information transmission method and device for cloud service, terminal equipment and system | |
| CN112350918B (en) | Service traffic scheduling method, device, equipment and storage medium | |
| CN114489512B (en) | Method and device for limiting container capacity, electronic equipment and storage medium | |
| KR102486236B1 (en) | Apparatus and method for network function virtualization in wireless communication system | |
| CN111124299A (en) | Data storage management method, device, equipment, system and storage medium | |
| US11575949B2 (en) | Providing files of variable sizes based on device and network conditions | |
| CN115913937B (en) | Container multi-network card network configuration method, device, equipment and storage medium | |
| CN111698730B (en) | Flow control method, operating system, terminal equipment and distributed system | |
| CN109582592B (en) | Resource management method and device | |
| CN113037812A (en) | Data packet scheduling method and device, electronic equipment, medium and intelligent network card | |
| CN117032905B (en) | Method and system for associating container cluster with block storage and virtual machine | |
| EP3857826B1 (en) | Flexible unnumbered destination tunnels for virtual networks | |
| CN110795209A (en) | Control method and device | |
| CN113495776A (en) | VNF instantiation method and device | |
| CN113342456A (en) | Connection method, device, equipment and storage medium | |
| CN116389599A (en) | Gateway service request processing method and device and cloud native gateway system management method and device | |
| CN113886153B (en) | Network card pressure testing method and device based on container | |
| CN115987990A (en) | Multi-cluster load balancing method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |