CN111880738A - Method for automatically creating and mounting LVM (logical volume manager) volume in K8s environment - Google Patents
Method for automatically creating and mounting LVM (logical volume manager) volume in K8s environment Download PDFInfo
- Publication number
- CN111880738A CN111880738A CN202010742438.2A CN202010742438A CN111880738A CN 111880738 A CN111880738 A CN 111880738A CN 202010742438 A CN202010742438 A CN 202010742438A CN 111880738 A CN111880738 A CN 111880738A
- Authority
- CN
- China
- Prior art keywords
- lvm
- volume
- environment
- size
- mounting
- 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
- 238000000034 method Methods 0.000 title claims abstract description 47
- 238000012217 deletion Methods 0.000 claims description 3
- 230000037430 deletion Effects 0.000 claims description 3
- 238000004519 manufacturing process Methods 0.000 claims description 3
- 238000006243 chemical reaction Methods 0.000 abstract description 2
- 238000007726 management method Methods 0.000 description 5
- 238000005192 partition Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- 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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
-
- 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/0629—Configuration or reconfiguration of storage systems
-
- 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/0638—Organizing or formatting or addressing of data
- G06F3/0644—Management of space entities, e.g. partitions, extents, pools
Abstract
The invention particularly relates to a method for automatically creating and mounting an LVM (logical volume manager) volume in a K8s environment. The method for automatically creating and mounting the LVM volume in the K8s environment is based on a Kubernets environment, firstly, a mirror image for automatically creating and mounting the LVM volume is manufactured, then, the mirror image manufactured by running a Configmap pipe and a Job management single copy Pod is defined, and container authority, environment variables, required mounting and node selection are configured; and finally, running the previously created yaml file including the Configmap and the Delploymet by using a Kubernets client, realizing the automatic creation and mounting of the LVM volume by the running of the target node, repeatedly running and supporting the subsequent expansion of the LVM volume, and providing the node service to use the local storage. According to the method for automatically creating and mounting the LVM volume in the K8s environment, the conversion from a target disk to the LVM volume is completed by reading the relevant configuration through Kubernetes Job, and the LVM volume is mounted on a target directory for service use.
Description
Technical Field
The invention relates to the technical field of cloud computing, in particular to a method for automatically creating and mounting an LVM (logical volume manager) volume in a K8s environment.
Background
Kubernetes, K8s for short, is an abbreviation used to replace the 8 characters "ubernet" with 8. As an open source for managing containerized applications on multiple hosts in a cloud platform, the goal of kubernets is to make it simple and efficient to deploy containerized applications (powerfull). Kubernets provides a mechanism for resource application deployment, planning, updating, and maintenance.
The kubernets cluster workload may use multiple storage methods, and most disk plug-ins use remote storage in order to make persistent data and compute nodes independent of each other, but remote storage generally cannot provide excellent read-write performance for local storage. LVM (logical volume management) represents a local disk that is directly bound to a compute node, but is used on the premise that the process of creating and mounting a directory needs to be done manually. The current mainstream way to realize the local directory is LVM, which is used as a mechanism for managing the disk partitions in the Linux environment, and a user can conveniently adjust the size of each partition without stopping the machine.
In order to improve the usability of creating and mounting the directory, the invention provides a method for automatically creating and mounting the LVM volume in a K8s environment.
Disclosure of Invention
The invention provides a simple and efficient method for automatically creating and mounting an LVM (logical volume manager) volume in a K8s environment, so as to make up for the defects of the prior art.
The invention is realized by the following technical scheme:
a method for automatically creating and mounting an LVM volume in a K8s environment is characterized in that: based on a Kubernetes environment, the method comprises the following steps:
firstly, a mirror image for executing automatic creation and mounting of an LVM (logical volume manager) volume is manufactured, a LVM2 package is installed on the basis of a primary basic mirror image, and a relevant Linux command required by the automatic creation and mounting of the LVM volume can be executed;
secondly, defining five basic operations of the Configmap management Shell script implementation, including reading a disk to create a PV (physical volume), creating a VG (volume group) and adding the PV into the volume group, reading a size to create or extend an LV (logical volume), formatting the LV or extend the LV, and reading a target path to mount the LV;
thirdly, defining a mirror image for operating and manufacturing a single-copy Pod for Job management, configuring container authority, environment variables, required mounting and node selection;
and fourthly, running the previously created yacml file including the Configmap and the Delploymet by using a Kubernets client, realizing the automatic creation and mounting of the LVM volume by the running of the target node, repeatedly running and supporting the subsequent expansion of the LVM volume, and providing the node service to use the local storage.
In the first step, the related Linux commands include, but are not limited to, pvcreate, vgcreate, vgextend, lvcreate, lvextend, mkfs, resize2fs commands.
In the second step, the process of creating and mounting the LVM is automatically defined by the Configmap, including configuring the PV, configuring the VG, configuring the LV, formatting the LV, and configuring the mount.
The process of configuring the PV is as follows: circularly reading a disk parameter list, checking whether each disk exists or not by using the fdisk-l, if not, performing the operation continuously; then PVs checks whether the disk has already done PV, if not, creates PV by executing pvcreate command, otherwise, exits normally until all disks are processed.
The procedure for configuring VGs is as follows: firstly, the VGs checks whether VG already exists, and if the vgcreate command is not executed, VG is generated according to the created PV; otherwise, circularly reading the disk parameter list, checking whether the PV is in the VG, if the vgextend command is not executed, adding the PV into the VG, otherwise, normally exiting until all disks are processed.
The procedure for configuring the LV is as follows: first LVs checks if the LV already exists, if there is no read plan LV size execute the lvcreate command to create the LV, if the execution failure represents plan size exceeding VG actual size, use VG available size to create the LV, otherwise exit normally; otherwise, reading the size of the planned LV, executing the lvextend command to expand the LV, judging according to command output if the execution fails, if the match represents that the current LV size is equal to the planned size, if the Insufficient represents that the current planned size exceeds the actual size of VG, expanding the LV by using the available size of VG, and otherwise, representing that the current LV size exceeds the planned size, and normally exiting.
The process of formatting the LV is as follows: first df checks if the LV is already mounted, if not, executes mkfs. ext4 command formatting the LV; otherwise, judging the LV size and the mount directory size, and executing resize2fs to expand the LV if the former exceeds the latter.
The configuration mount process is as follows: firstly, grep checks whether LV exists in/etc/fstab, if no target directory is read and mount configuration is added to/etc/fstab, otherwise normal exit is carried out; mount-a is then executed, at which point the target directory has been successfully mounted.
In the third step, the environment variables comprise a disk list stored in a place, a planned LV size and a target mounting path; the required mount comprises/run,/etc/fstab,/dev, Configmap and a target path; configuration node selection ensures that the Pod operates at the target node.
When the service requirement of the node needs to expand the size of the local storage volume, the configuration of the environment variables in the third step is adjusted, such as the size of a disk list and the size of a planned LV, then Job deletion is executed through a Kubernetes client, and then the fourth step is executed, so that the expansion of the size of the local storage volume can be automatically completed.
The invention has the beneficial effects that: according to the method for automatically creating and mounting the LVM volume in the K8s environment, the conversion from a target disk to the LVM volume is completed by reading the relevant configuration through Kubernetes Job, and the LVM volume is mounted on a target directory for service use.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a schematic diagram of the method for automatically creating and mounting the LVM volume in the K8s environment.
Detailed Description
In order to make those skilled in the art better understand the technical solution of the present invention, the technical solution in the embodiment of the present invention will be clearly and completely described below with reference to the embodiment of the present invention. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The method for automatically creating and mounting the LVM volume in the K8s environment is based on a Kubernets environment and comprises the following steps:
firstly, a mirror image for executing automatic creation and mounting of an LVM (logical volume manager) volume is manufactured, a LVM2 package is installed on the basis of a primary basic mirror image, and a relevant Linux command required by the automatic creation and mounting of the LVM volume can be executed;
step two, defining five basic operations of the Configmap management Shell script implementation, including reading a disk to create a PV, creating a VG and adding the PV into the PV, reading a size to create or expand the LV, reading a format LV or an expansion LV, and reading a target path to mount the LV;
thirdly, defining a mirror image for operating and manufacturing a single-copy Pod for Job management, configuring container authority, environment variables, required mounting and node selection;
and fourthly, running the previously created yacml file including the Configmap and the Delploymet by using a Kubernets client, realizing the automatic creation and mounting of the LVM volume by the running of the target node, repeatedly running and supporting the subsequent expansion of the LVM volume, and providing the node service to use the local storage.
In the first step, the related Linux commands include, but are not limited to, pvcreate, vgcreate, vgextend, lvcreate, lvextend, mkfs, resize2fs commands.
In the second step, the process of creating and mounting the LVM is automatically defined by the Configmap, including configuring the PV, configuring the VG, configuring the LV, formatting the LV, and configuring the mount.
The process of configuring the PV is as follows: circularly reading a disk parameter list, checking whether each disk exists or not by using the fdisk-l, if not, performing the operation continuously; then PVs checks whether the disk has already done PV, if not, creates PV by executing pvcreate command, otherwise, exits normally until all disks are processed.
The procedure for configuring VGs is as follows: firstly, the VGs checks whether VG already exists, and if the vgcreate command is not executed, VG is generated according to the created PV; otherwise, circularly reading the disk parameter list, checking whether the PV is in the VG, if the vgextend command is not executed, adding the PV into the VG, otherwise, normally exiting until all disks are processed.
The procedure for configuring the LV is as follows: first LVs checks if the LV already exists, if there is no read plan LV size execute the lvcreate command to create the LV, if the execution failure represents plan size exceeding VG actual size, use VG available size to create the LV, otherwise exit normally; otherwise, reading the size of the planned LV, executing the lvextend command to expand the LV, judging according to command output if the execution fails, if the match represents that the current LV size is equal to the planned size, if the Insufficient represents that the current planned size exceeds the actual size of VG, expanding the LV by using the available size of VG, and otherwise, representing that the current LV size exceeds the planned size, and normally exiting.
The process of formatting the LV is as follows: first df checks if the LV is already mounted, if not, executes mkfs. ext4 command formatting the LV; otherwise, judging the LV size and the mount directory size, and executing resize2fs to expand the LV if the former exceeds the latter.
The configuration mount process is as follows: firstly, grep checks whether LV exists in/etc/fstab, if no target directory is read and mount configuration is added to/etc/fstab, otherwise normal exit is carried out; mount-a is then executed, at which point the target directory has been successfully mounted.
In the third step, the environment variables comprise a disk list stored in a place, a planned LV size and a target mounting path; the required mount comprises/run,/etc/fstab,/dev, Configmap and a target path; configuration node selection ensures that the Pod operates at the target node.
When the service requirement of the node needs to expand the size of the local storage volume, the configuration of the environment variables in the third step is adjusted, such as the size of a disk list and the size of a planned LV, then Job deletion is executed through a Kubernetes client, and then the fourth step is executed, so that the expansion of the size of the local storage volume can be automatically completed. When the Pod status is complete, the configuration mounted target directory available size has already been adjusted.
In the fourth step, a Kubernetes client is used for operating Configmap and Job, when the Pod state is complete, the nodes are checked, and at the moment, the local disk is automatically converted into an LVM (logical volume manager) volume and is mounted to a target directory, so that the service of node operation can be provided;
compared with the prior art, the method for automatically creating and mounting the LVM volume in the K8s environment has the following characteristics:
firstly, the processing process of automatically creating and mounting the LVM volume can be flexibly customized by means of the Shell script;
secondly, the steps required by the tasks can be automatically completed at one time by using the Job object in the Kubernetes cluster, any manual operation process is not required, the configuration controllability is guaranteed, the manual operation error is avoided, and the usability and manageability of the node for creating and mounting the LVM volume are greatly improved.
The above-described embodiment is only one specific embodiment of the present invention, and general changes and substitutions by those skilled in the art within the technical scope of the present invention are included in the protection scope of the present invention.
Claims (10)
1. A method for automatically creating and mounting an LVM volume in a K8s environment is characterized in that: based on a Kubernetes environment, the method comprises the following steps:
firstly, a mirror image for executing automatic creation and mounting of an LVM (logical volume manager) volume is manufactured, a LVM2 package is installed on the basis of a primary basic mirror image, and a relevant Linux command required by the automatic creation and mounting of the LVM volume can be executed;
step two, defining five basic operations of the Configmap management Shell script implementation, including reading a disk to create a PV, creating a VG and adding the PV into the PV, reading a size to create or expand the LV, reading a format LV or an expansion LV, and reading a target path to mount the LV;
thirdly, defining a mirror image for operating and manufacturing a single-copy Pod for Job management, configuring container authority, environment variables, required mounting and node selection;
and fourthly, running the previously created yacml file including the Configmap and the Delploymet by using a Kubernets client, realizing the automatic creation and mounting of the LVM volume by the running of the target node, repeatedly running and supporting the subsequent expansion of the LVM volume, and providing the node service to use the local storage.
2. The K8s environment automated LVM volume creation and mounting method of claim 1, wherein: in the first step, the related Linux commands include, but are not limited to, pvcreate, vgcreate, vgextend, lvcreate, lvextend, mkfs, resize2fs commands.
3. The K8s environment automated LVM volume creation and mounting method of claim 2, wherein: in the second step, the process of creating and mounting the LVM is automatically defined by the Configmap, including configuring the PV, configuring the VG, configuring the LV, formatting the LV, and configuring the mount.
4. The method for automated LVM volume creation and mount of the K8s environment of claim 3, wherein: the procedure for configuring the PV is as follows: circularly reading a disk parameter list, checking whether each disk exists or not by using the fdisk-l, if not, performing the operation continuously; then PVs checks whether the disk has already done PV, if not, creates PV by executing pvcreate command, otherwise, exits normally until all disks are processed.
5. The method for automated LVM volume creation and mount of the K8s environment of claim 3, wherein: the procedure for configuring VGs is as follows: firstly, the VGs checks whether VG already exists, and if the vgcreate command is not executed, VG is generated according to the created PV; otherwise, circularly reading the disk parameter list, checking whether the PV is in the VG, if the vgextend command is not executed, adding the PV into the VG, otherwise, normally exiting until all disks are processed.
6. The method for automated LVM volume creation and mount of the K8s environment of claim 3, wherein: the procedure for configuring the LV is as follows: first LVs checks if the LV already exists, if there is no read plan LV size execute the lvcreate command to create the LV, if the execution failure represents plan size exceeding VG actual size, use VG available size to create the LV, otherwise exit normally; otherwise, reading the size of the planned LV, executing the lvextend command to expand the LV, judging according to command output if the execution fails, if the match represents that the current LV size is equal to the planned size, if the Insufficient represents that the current planned size exceeds the actual size of VG, expanding the LV by using the available size of VG, and otherwise, representing that the current LV size exceeds the planned size, and normally exiting.
7. The method for automated LVM volume creation and mount of the K8s environment of claim 3, wherein: the process of formatting the LV is as follows: first df checks if the LV is already mounted, if not, executes mkfs. ext4 command formatting the LV; otherwise, judging the LV size and the mount directory size, and executing resize2fs to expand the LV if the former exceeds the latter.
8. The method for automated LVM volume creation and mount of the K8s environment of claim 3, wherein: the configuration mount process is as follows: firstly, grep checks whether LV exists in/etc/fstab, if no target directory is read and mount configuration is added to/etc/fstab, otherwise normal exit is carried out; mount-a is then executed, at which point the target directory has been successfully mounted.
9. The K8s environment automated LVM volume creation and mounting method of claim 1, wherein: in the third step, the environment variables comprise a disk list stored in a place, a planned LV size and a target mounting path; the required mount comprises/run,/etc/fstab,/dev, Configmap and a target path; configuration node selection ensures that the Pod operates at the target node.
10. The K8s environment automation creating and mounting LVM volume method according to claim 1 or 9, wherein: when the service requirement of the node needs to expand the size of the local storage volume, the configuration of the environment variables in the third step is adjusted, then Job deletion is executed through a Kubernets client, and then the fourth step is executed, so that the expansion of the size of the local storage volume can be automatically completed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010742438.2A CN111880738A (en) | 2020-07-29 | 2020-07-29 | Method for automatically creating and mounting LVM (logical volume manager) volume in K8s environment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010742438.2A CN111880738A (en) | 2020-07-29 | 2020-07-29 | Method for automatically creating and mounting LVM (logical volume manager) volume in K8s environment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111880738A true CN111880738A (en) | 2020-11-03 |
Family
ID=73201076
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010742438.2A Pending CN111880738A (en) | 2020-07-29 | 2020-07-29 | Method for automatically creating and mounting LVM (logical volume manager) volume in K8s environment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111880738A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112463616A (en) * | 2020-12-02 | 2021-03-09 | 中国建设银行股份有限公司 | Chaos testing method and device for Kubernetes container platform |
| CN113391952A (en) * | 2021-06-07 | 2021-09-14 | 北京同创永益科技发展有限公司 | Automatic backup method based on LVM snapshot in cloud native environment |
| CN113741961A (en) * | 2021-11-08 | 2021-12-03 | 梯度云科技(北京)有限公司 | Method and device for submitting big data calculation operation based on Kubernetes container arrangement software |
| CN114816272A (en) * | 2022-06-23 | 2022-07-29 | 江苏博云科技股份有限公司 | Magnetic disk management system under Kubernetes environment |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104283959A (en) * | 2014-10-14 | 2015-01-14 | 国云科技股份有限公司 | Performance-grading-based storage mechanism suitable for cloud platform |
| CN107193504A (en) * | 2017-06-02 | 2017-09-22 | 郑州云海信息技术有限公司 | A kind of method and system of automation distribution and establishment application memory based on Kubernetes |
| CN107707688A (en) * | 2017-10-19 | 2018-02-16 | 杭州数梦工场科技有限公司 | A kind of method and device of kubernetes clusters parsing host host name |
| CN110012088A (en) * | 2019-03-29 | 2019-07-12 | 山东浪潮云信息技术有限公司 | A kind of Redis principal and subordinate's cluster automatically dispose scheme based on Kubernets |
| CN110297641A (en) * | 2019-06-25 | 2019-10-01 | 四川长虹电器股份有限公司 | Layout dispositions method is applied based on kubernetes |
| CN110941393A (en) * | 2019-10-31 | 2020-03-31 | 北京浪潮数据技术有限公司 | Logical volume management-based LV supply method, device, equipment and medium |
| CN111162941A (en) * | 2019-12-26 | 2020-05-15 | 浪潮云信息技术有限公司 | Method for automatically managing virtual IP (Internet protocol) in Kubernetes environment |
-
2020
- 2020-07-29 CN CN202010742438.2A patent/CN111880738A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104283959A (en) * | 2014-10-14 | 2015-01-14 | 国云科技股份有限公司 | Performance-grading-based storage mechanism suitable for cloud platform |
| CN107193504A (en) * | 2017-06-02 | 2017-09-22 | 郑州云海信息技术有限公司 | A kind of method and system of automation distribution and establishment application memory based on Kubernetes |
| CN107707688A (en) * | 2017-10-19 | 2018-02-16 | 杭州数梦工场科技有限公司 | A kind of method and device of kubernetes clusters parsing host host name |
| CN110012088A (en) * | 2019-03-29 | 2019-07-12 | 山东浪潮云信息技术有限公司 | A kind of Redis principal and subordinate's cluster automatically dispose scheme based on Kubernets |
| CN110297641A (en) * | 2019-06-25 | 2019-10-01 | 四川长虹电器股份有限公司 | Layout dispositions method is applied based on kubernetes |
| CN110941393A (en) * | 2019-10-31 | 2020-03-31 | 北京浪潮数据技术有限公司 | Logical volume management-based LV supply method, device, equipment and medium |
| CN111162941A (en) * | 2019-12-26 | 2020-05-15 | 浪潮云信息技术有限公司 | Method for automatically managing virtual IP (Internet protocol) in Kubernetes environment |
Non-Patent Citations (1)
| Title |
|---|
| 李红岩，乔洁，王莉: "《Linux下逻辑卷管理的原理与实现》", 《科技风》, no. 203, pages 37 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112463616A (en) * | 2020-12-02 | 2021-03-09 | 中国建设银行股份有限公司 | Chaos testing method and device for Kubernetes container platform |
| CN113391952A (en) * | 2021-06-07 | 2021-09-14 | 北京同创永益科技发展有限公司 | Automatic backup method based on LVM snapshot in cloud native environment |
| CN113391952B (en) * | 2021-06-07 | 2022-03-11 | 北京同创永益科技发展有限公司 | Automatic backup method based on LVM snapshot in cloud native environment |
| CN113741961A (en) * | 2021-11-08 | 2021-12-03 | 梯度云科技(北京)有限公司 | Method and device for submitting big data calculation operation based on Kubernetes container arrangement software |
| CN114816272A (en) * | 2022-06-23 | 2022-07-29 | 江苏博云科技股份有限公司 | Magnetic disk management system under Kubernetes environment |
| CN114816272B (en) * | 2022-06-23 | 2022-09-06 | 江苏博云科技股份有限公司 | Magnetic disk management system under Kubernetes environment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111880738A (en) | Method for automatically creating and mounting LVM (logical volume manager) volume in K8s environment | |
| CN111522628B (en) | Kubernetes cluster building deployment method, framework and storage medium based on OpenStack | |
| US8291403B2 (en) | Install-unit upgrade using dynamic configuration data manipulation and merging | |
| US20190082004A1 (en) | Systems and methods for instantiating services on top of services | |
| CN107566165B (en) | Method and system for discovering and deploying available resources of power cloud data center | |
| US20100325624A1 (en) | Method and System for Application Portability | |
| CN107632937B (en) | Method and device for testing virtual machine cluster and readable storage medium | |
| CN102402446A (en) | Method and device for installing application software | |
| CN106648771B (en) | Openstack cloud platform custom deployment system and deployment method | |
| CN111930465A (en) | Kubernetes-based dreams master-slave cluster deployment method and device | |
| CN116860746A (en) | Processing system for lightweight big data | |
| CN114510464A (en) | Management method and management system of high-availability database | |
| CN110795105A (en) | Automatic compiling and deploying method and system for power distribution automation master station system | |
| CN111930466A (en) | Kubernetes-based data synchronization environment deployment method and device | |
| CN113296796A (en) | Project release method, device, system, storage medium and electronic equipment | |
| CN115617459A (en) | Method, device and equipment for resource scheduling | |
| CN115357198A (en) | Mounting method and device of storage volume, storage medium and electronic equipment | |
| CN107515760B (en) | OpenStack multi-node automatic installation method and system | |
| EP3764174A1 (en) | System and method for module enginnering with sequence libraries | |
| CN112685051A (en) | Method, device, platform and storage medium for automatically executing shell script | |
| CN111858234A (en) | Task execution method, device, equipment and medium | |
| CN110377397B (en) | Stock application rapid deployment and expansion method based on virtual machine replication | |
| CN113590415B (en) | Port management system, method, equipment and medium of deep learning training platform | |
| CN202662000U (en) | Node virtualization deployment device of render farm | |
| US11477090B1 (en) | Detecting deployment problems of containerized applications in a multiple-cluster environment |
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 |