CN112579008B - Storage deployment method, device and equipment of container orchestration engine and storage medium - Google Patents
Storage deployment method, device and equipment of container orchestration engine and storage medium Download PDFInfo
- Publication number
- CN112579008B CN112579008B CN202011572978.7A CN202011572978A CN112579008B CN 112579008 B CN112579008 B CN 112579008B CN 202011572978 A CN202011572978 A CN 202011572978A CN 112579008 B CN112579008 B CN 112579008B
- Authority
- CN
- China
- Prior art keywords
- storage
- storage system
- container
- physical
- physical server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 238000004590 computer program Methods 0.000 claims description 12
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 230000001360 synchronised effect Effects 0.000 description 9
- 230000008569 process Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 6
- 230000005291 magnetic effect Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 230000003068 static effect Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 230000005294 ferromagnetic effect Effects 0.000 description 1
- 230000037406 food intake Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000026676 system process Effects 0.000 description 1
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/0614—Improving the reliability of storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F16/275—Synchronous replication
-
- 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
-
- 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
-
- 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/0671—In-line storage system
- G06F3/0673—Single storage device
- G06F3/0674—Disk device
- G06F3/0676—Magnetic disk device
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Databases & Information Systems (AREA)
- Computing Systems (AREA)
- Data Mining & Analysis (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a storage deployment method, a storage deployment device, storage deployment equipment and storage media of a container orchestration engine. The method comprises the following steps: installing and running a container orchestration engine in a physical server; configuring and operating a storage system based on a physical server; creating a storage volume in a storage system; a mounting relationship of the data volume and the container group in the container orchestration engine is established. According to the method, the storage system is configured in the physical server, and the mounting relation between the storage volumes in the storage system and the container group in the container arrangement engine is established, so that the containers in the container group can read and write data on the storage volumes in the storage system based on the mounting relation, and further the use of storage resources in the physical server by the container arrangement engine is realized. In addition, the application also provides a storage deployment device, equipment and a storage medium of the container arrangement engine, and the beneficial effects are the same as the above.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a storage deployment method, apparatus, device, and storage medium for a container orchestration engine.
Background
The container orchestration engine is used for managing the containerized applications on a plurality of hosts in the cloud platform, and the goal of the container orchestration engine is to enable the deployment of the containerized applications to be simple and efficient, and the container orchestration engine provides a mechanism for deploying, planning, updating and maintaining containers.
The containers are resource groups which are divided based on the resources of the operating system and are mutually isolated, and conflicting resource use requirements can be balanced among the containers.
The container orchestration engine and the container are used as an emerging technology, the development and business operation modes are greatly changed, the container is flexible, the stateful container needs to use shared storage, when the container orchestration engine and the container are directly deployed on the physical server, the physical server can only provide computing and network resources for the container orchestration engine, the local storage of the physical server can not provide flexibility and high availability for the stateful application, and resources such as disk positions, storage and the like of the physical server are wasted.
It is seen that the provision of a storage deployment method for a container orchestration engine to enable the use of storage resources in a physical server by the container orchestration engine is a problem that needs to be solved by those skilled in the art.
Disclosure of Invention
The application aims to provide a storage deployment method, a storage deployment device, storage deployment equipment and a storage medium of a container orchestration engine, so that the container orchestration engine can use storage resources in a physical server.
In order to solve the technical problems, the application provides a storage deployment method of a container orchestration engine, comprising the following steps:
installing and running a container orchestration engine in a physical server;
configuring and operating a storage system based on a physical server;
Creating a storage volume in a storage system;
A mounting relationship of the data volume and the container group in the container orchestration engine is established.
Preferably, the configuration and operation of the storage system based on the physical server comprises:
deploying a storage system in a physical service;
mounting a physical disk in a physical server to a storage system;
and running a storage system on which the physical disk is mounted.
Preferably, mounting a physical disk in a physical server to a storage system includes:
the physical disk is mounted to the storage system by transparently transferring the physical address of the physical disk in the physical server to the storage system.
Preferably, the number of physical servers is greater than 1;
accordingly, deploying a storage system in a physical service, comprising:
Installing a storage system in each physical server;
and establishing a distributed data synchronization relationship of the storage system among the physical servers.
Preferably, establishing the mounting relationship of the data volume to the group of containers in the container orchestration engine comprises:
The mounting relationship of the data volume and the group of containers in the container orchestration engine is established based on the storage class corresponding to the container orchestration engine.
Preferably, the container orchestration engine comprises a Kubernetes engine, and the container group comprises a pod container group.
Preferably, the configuration and operation of the storage system based on the physical server comprises:
The storage system is run based on the physical server configuration and through DaemonSet.
In addition, the application also provides a storage deployment device of the container programming engine, which comprises:
A container engine operation module for installing and operating a container orchestration engine in a physical server;
The storage system operation module is used for configuring and operating the storage system based on the physical server;
a storage volume creation module for creating a storage volume in a storage system;
And the container group mounting module is used for establishing the mounting relation between the data volume and the container group in the container arrangement engine.
In addition, the application also provides a storage deployment device of the container programming engine, which comprises:
a memory for storing a computer program;
a processor for implementing the steps of the storage deployment method of the container orchestration engine described above when executing the computer program.
Furthermore, the present application provides a computer readable storage medium having a computer program stored thereon, which when executed by a processor implements the steps of a storage deployment method of a container orchestration engine as described above.
The storage deployment method of the container arrangement engine provided by the application comprises the steps of firstly installing and operating the container arrangement engine in a physical server, configuring and operating a storage system based on the physical server, further creating a storage volume in the storage system, and establishing a mounting relation between a data volume and a container group in the container arrangement engine. According to the method, the storage system is configured in the physical server, and the mounting relation between the storage volumes in the storage system and the container group in the container arrangement engine is established, so that the containers in the container group can read and write data on the storage volumes in the storage system based on the mounting relation, and further the use of storage resources in the physical server by the container arrangement engine is realized. In addition, the application also provides a storage deployment device, equipment and a storage medium of the container arrangement engine, and the beneficial effects are the same as the above.
Drawings
For a clearer description of embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described, it being apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to the drawings without inventive effort for those skilled in the art.
FIG. 1 is a flow chart of a storage deployment method of a container orchestration engine according to embodiments of the present application;
FIG. 2 is a flow chart of a storage deployment method of a particular container orchestration engine according to embodiments of the present application;
FIG. 3 is a schematic storage deployment diagram of a container orchestration engine under a specific application scenario according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a storage deployment apparatus of a container orchestration engine according to an embodiment of the present application;
fig. 5 is a schematic diagram of a hardware composition structure of a storage deployment device of a container orchestration engine according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. Based on the embodiments of the present application, all other embodiments obtained by a person of ordinary skill in the art without making any inventive effort are within the scope of the present application.
The container orchestration engine and the container are used as an emerging technology, the development and business operation modes are greatly changed, the container is flexible, the stateful container needs to use shared storage, when the container orchestration engine and the container are directly deployed on the physical server, the physical server can only provide computing and network resources for the container orchestration engine, the local storage of the physical server can not provide flexibility and high availability for the stateful application, and resources such as disk positions, storage and the like of the physical server are wasted.
Therefore, the core of the application is to provide a storage deployment method of a container orchestration engine, so as to realize the use of storage resources in a physical server by the container orchestration engine.
In order to better understand the aspects of the present application, the present application will be described in further detail with reference to the accompanying drawings and detailed description.
As shown in fig. 1, an embodiment of the present application discloses a storage deployment method of a container orchestration engine, including:
Step S10: the container orchestration engine is installed and run in a physical server.
It should be noted that, the execution body of the embodiment may be a physical server configuration device having a communication control relationship with respect to a physical server, where the physical server is a server device formed by physical hardware, and the hardware configuration of the physical server includes a processor, a hard disk, a memory, a system bus, and the like, which is similar to a general-purpose computer architecture, but since a highly reliable service needs to be provided, requirements in terms of processing capability, stability, reliability, security, scalability, manageability, and the like are higher than those of a computer.
This step begins with installing and running a container orchestration engine in the physical server, where the container orchestration engine is an abstraction layer provided between the resource pools and the application containers running on those resource pools, the main problem solved is how to combine discrete resources into a pool and deploy various applications onto this pool, ranging from simple three-tier network architecture to large-scale data ingestion and processing, and all processing operations in between. The purpose of this step of installing and running the container orchestration engine in the physical server is to further establish in a subsequent step the call relationship of the container orchestration engine to the storage resources in the physical server.
Step S11: the storage system is configured and operated based on the physical server.
It should be noted that, this step is based on the configuration of the physical server and running the storage system, so as to further implement management of physical storage resources in the physical server through the storage system, and further provide, based on the storage system, the storage resources integrated by the storage system to the container arrangement engine.
The order of execution between step S11 and step S10 is not fixed, and may be executed simultaneously, and is not particularly limited here, as the case may be.
Step S12: a storage volume is created in a storage system.
After the storage system is configured and operated based on the physical server, the storage volume is further created in the storage system, wherein the storage volume is equivalent to the storage resource managed by the storage system which is further divided to generate a result, and the purpose of creating the storage volume in the storage system is to further establish the mounting relationship between the storage volume and the container group in the container arrangement engine in the subsequent step, so that the effect that the storage volume in the storage system can be accessed through the container group in the container arrangement engine is achieved, and the use of the storage resource in the physical server by the container arrangement engine is achieved.
Step S13: a mounting relationship of the data volume and the container group in the container orchestration engine is established.
After the storage volume is created in the storage system, the mounting relationship between the data volume and the container group in the container arrangement engine is further defined, wherein the mounting relationship is the data access relationship of the container group to the data volume, and the containers in the container group can access the data volume based on the mounting relationship and read and write data on the data volume. Wherein, the container group consists of one or more containers with the same functions, which are distributed on the same node and share the same naming space. Based on the mounting relation between the storage volumes and the container groups in the container arrangement engine, the effect that the storage volumes in the storage system can be accessed through the container groups in the container arrangement engine can be achieved, and therefore the use of storage resources in the physical server by the container arrangement engine is further achieved.
The storage deployment method of the container arrangement engine provided by the application comprises the steps of firstly installing and operating the container arrangement engine in a physical server, configuring and operating a storage system based on the physical server, further creating a storage volume in the storage system, and establishing a mounting relation between a data volume and a container group in the container arrangement engine. According to the method, the storage system is configured in the physical server, and the mounting relation between the storage volumes in the storage system and the container group in the container arrangement engine is established, so that the containers in the container group can read and write data on the storage volumes in the storage system based on the mounting relation, and further the use of storage resources in the physical server by the container arrangement engine is realized.
Based on the above embodiment, as a preferred implementation manner, establishing a mounting relationship between the data volume and the container group in the container arrangement engine includes:
The mounting relationship of the data volume and the group of containers in the container orchestration engine is established based on the storage class corresponding to the container orchestration engine.
In the present embodiment, the mounting relationship between the data volume and the container group in the container arrangement engine is established between the data volume and the container arrangement engine based on the storage class corresponding to the container arrangement engine. The cluster manager of the container arrangement engine can meet the storage requirements of users with different service quality levels, backup strategies and any strategy requirements by providing different storage classes. Dynamic storage volume provisioning is implemented using storage classes (StorageClass) that allow storage volumes to be created on demand, and this embodiment can further ensure the reliability of the process of establishing the mounting relationship of data volumes to groups of containers in the container orchestration engine.
As shown in fig. 2, an embodiment of the present application discloses a storage deployment method of a container orchestration engine, including:
step S20: the container orchestration engine is installed and run in a physical server.
Step S21: a storage system is deployed in a physical service.
Step S22: and mounting the physical disk in the physical server to a storage system.
Step S23: and running a storage system on which the physical disk is mounted.
Step S24: a storage volume is created in a storage system.
Step S25: a mounting relationship of the data volume and the container group in the container orchestration engine is established.
In this embodiment, when the storage system is configured and operated based on the physical server, the storage system is first installed and deployed in the physical server, and then the physical disk in the physical server is mounted to the storage system, so as to ensure that the storage system can format the physical storage resources in the physical server, thereby realizing management of the physical storage resources, and further operating the storage system on which the physical disk is mounted on the basis of the formatting, and further completing the purpose of configuring and operating the storage system in the physical server. The present embodiment further ensures the reliability of the storage system process based on the physical server configuration and operation.
In addition, when the types of the physical disks in the physical server are more than one, in the process of mounting the physical disks in the physical server to the storage system, the physical disks of the corresponding types can be mounted to the storage system according to the actual storage performance requirements of the containers in the container arrangement engine and the capacity ratio among the physical disks of different types. Different types of physical disks referred to herein include, but are not limited to, SSD (Solid state drive, solid state STATE DISK), SATA (serial disk, SERIAL ATA), and SAS (SERIAL ATTACHED SCSI, serial attached Small computer System interface) disks.
Based on the foregoing embodiment, as a preferred implementation manner, the mounting the physical disk in the physical server to the storage system includes:
the physical disk is mounted to the storage system by transparently transferring the physical address of the physical disk in the physical server to the storage system.
In the embodiment, in the process of mounting the physical disk in the physical server to the storage system, a manner of transmitting the physical address of the physical disk in the physical server to the storage system is adopted, so that the storage system learns the access path of the physical disk, and the storage system can initiate access to the physical disk relatively accurately according to the physical address. In addition, transparent transmission (pass-through) in this embodiment refers to transmission of the content from the source address to the destination address without any change to the content of the service data, regardless of the content of the service being transmitted in the communication. The present embodiment further ensures the reliability of the process of mounting the physical disk in the physical server to the storage system.
In addition, on the basis of the above embodiment, as a preferred embodiment, the number of physical servers is greater than 1;
accordingly, deploying a storage system in a physical service, comprising:
Installing a storage system in each physical server;
and establishing a distributed data synchronization relationship of the storage system among the physical servers.
It should be noted that, the key point of this embodiment is that the number of physical servers is greater than 1, that is, the plurality of physical servers in this embodiment each install and run the container arrangement engine, and when the storage system is deployed in the physical service, the storage system is installed in each physical server, and a distributed data synchronization relationship of the storage systems between the physical servers is established, so as to achieve the purpose of building a distributed storage system between the physical servers from the storage systems in each physical server. The present embodiment further ensures the reliability of storage deployment of the container orchestration engine in the physical server when the number of physical servers is greater than 1.
Based on the series of examples described above, as a preferred implementation, the container orchestration engine comprises a Kubernetes engine and the container group comprises a pod container group.
It should be noted that Kubernetes is abbreviated as K8s, and is an open-source container orchestration engine. The goal of Kubernetes for managing containerized applications on multiple hosts in a cloud platform is to make deploying containerized applications simple and efficient, and the Kubernetes engine provides a mechanism for application deployment, planning, updating, and maintenance. The pod container group is a resource organization mode in the Kubernetes engine, is the smallest resource organization mode in the Kubernetes engine, and is generally composed of one or more containers with the same function, and the containers are distributed on the same node and share the same naming space. This embodiment further ensures the use of storage resources in the physical server by the Kubernetes engine.
Further, as a preferred embodiment, the configuration and operation of the storage system based on the physical server includes:
The storage system is run based on the physical server configuration and through DaemonSet.
DaemonSet is a controller in the Kubernetes engine that can ensure that each or a portion of the physical server nodes in the physical server cluster run a pod copy, create a pod container set when a new physical server node joins the physical server cluster, and recycle the pod container set when a physical server node leaves the cluster. If DaemonSet is deleted, all the pod container groups it created are also deleted, the pod container groups in DaemonSet cover the entire physical server cluster. The present embodiment further ensures the reliability of storage deployment to the container orchestration engine in the physical server.
To enhance understanding of the foregoing embodiments of the present application, the present application further provides a scenario embodiment in a specific application scenario, and a storage deployment diagram of a container arrangement engine in a specific application scenario is shown in fig. 3.
The storage deployment process of the container orchestration engine comprises:
1. configuring a hardware server
And providing the storage resources of the physical server for the container, thereby realizing the distributed storage under the container. In the first step, it is necessary to configure a disk for a physical server, and allocate SSD, SATA, SAS disks according to a reasonable performance and capacity ratio.
2. Installing an operating system and installing K8S
Installing an operating system, and installing K8S on the operating system. In the container environment, the service runs in K8S to obtain high availability and resilience.
3. The distributed storage service is run DaemonSet way and the disk is passed through to the distributed storage service pod.
Distributed storage is run on each physical server DaemonSet way, and k8S provides high availability maintenance for this class of pod and maintains their state. The distributed storage service, after each physical server comes up, passes the disk of the physical server through to the distributed storage service in the container.
4. Distributed storage services on each physical node server form a distributed storage cluster, and storage is provided outside.
5. The distributed storage clusters are configured in K8S, and the K8S can use dynamic use storage in a storage class or persistent volume mode.
Referring to fig. 4, an embodiment of the present application discloses a storage deployment apparatus of a container orchestration engine, including:
a container engine running module 10 for installing and running a container orchestration engine in a physical server;
A storage system operation module 11 for configuring and operating a storage system based on a physical server;
a storage volume creation module 12 for creating a storage volume in the storage system;
the container group mounting module 13 is configured to establish a mounting relationship between the data volume and the container group in the container arrangement engine.
In one embodiment, the storage system operation module 11 includes:
the storage system deployment module is used for deploying the storage system in the physical service;
the physical disk mounting module is used for mounting the physical disk in the physical server to the storage system;
and the operation module is used for operating the storage system on which the physical disk is mounted.
In one embodiment, a physical disk mounting module includes:
and the transparent mounting module is used for mounting the physical disk to the storage system in a manner of transparent transmitting the physical address of the physical disk in the physical server to the storage system.
In one embodiment, the number of physical servers is greater than 1;
Correspondingly, the storage system deployment module comprises:
the system installation module is used for installing a storage system in each physical server;
And the synchronization relation establishing module is used for establishing the distributed data synchronization relation of the storage system among the physical servers.
In one embodiment, the container group mounting module 13 includes:
And the storage class mounting module is used for establishing a mounting relation between the data volume and the container group in the container arrangement engine based on the storage class corresponding to the container arrangement engine.
In one embodiment, the container orchestration engine comprises a Kubernetes engine and the container group comprises a pod container group.
In one embodiment, the storage system operation module 11 includes:
and a system operation sub-module for operating the storage system based on the physical server configuration and through DaemonSet.
The storage deployment device of the container arrangement engine firstly installs and operates the container arrangement engine in a physical server, configures and operates a storage system based on the physical server, further creates a storage volume in the storage system, and establishes a mounting relation between a data volume and a container group in the container arrangement engine. The device configures the storage system in the physical server and establishes the mounting relation between the storage volume in the storage system and the container group in the container arrangement engine, so that the containers in the container group can read and write data on the storage volume in the storage system based on the mounting relation, and further, the use of storage resources in the physical server by the container arrangement engine is realized.
Based on the hardware implementation of the program module, and in order to implement the storage deployment method of the container orchestration engine according to the embodiment of the present application, the embodiment of the present application further provides a storage deployment device of the container orchestration engine, where a virtual machine is operated and a virtual machine disk corresponding to the virtual machine is established with a communication connection, and fig. 5 is a schematic diagram of a hardware composition structure of the storage deployment device of the container orchestration engine according to the embodiment of the present application, and as shown in fig. 5, the storage deployment device of the container orchestration engine includes:
A communication interface 1 capable of information interaction with other devices such as network devices and the like;
And the processor 2 is connected with the communication interface 1 to realize information interaction with other devices and is used for executing the storage deployment method of the container arrangement engine provided by one or more technical schemes when running the computer program. And the computer program is stored on the memory 3.
Of course, in practice, the various components in the storage deployment device of the container orchestration engine are coupled together by bus system 4. It will be appreciated that the bus system 4 is used to enable connected communications between these components. The bus system 4 comprises, in addition to a data bus, a power bus, a control bus and a status signal bus. But for clarity of illustration the various buses are labeled as bus system 4 in fig. 5.
The memory 3 in the embodiment of the present application is used to store various types of data to support the operation of the storage deployment device of the container orchestration engine. Examples of such data include: any computer program for operating on a storage deployment device of a container orchestration engine.
It will be appreciated that the memory 3 may be either volatile memory or nonvolatile memory, and may include both volatile and nonvolatile memory. The non-volatile Memory may be, among other things, a Read Only Memory (ROM), a programmable Read Only Memory (PROM, programmable Read-Only Memory), erasable programmable Read-Only Memory (EPROM, erasable Programmable Read-Only Memory), electrically erasable programmable Read-Only Memory (EEPROM, ELECTRICALLY ERASABLE PROGRAMMABLE READ-Only Memory), Magnetic random access Memory (FRAM, ferromagnetic random access Memory), flash Memory (Flash Memory), magnetic surface Memory, optical disk, or compact disk-Only (CD-ROM, compact Disc Read-Only Memory); The magnetic surface memory may be a disk memory or a tape memory. The volatile memory may be random access memory (RAM, random Access Memory) which acts as external cache memory. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM, static Random Access Memory), synchronous static random access memory (SSRAM, synchronous Static Random Access Memory), dynamic random access memory (DRAM, dynamic Random Access Memory), synchronous dynamic random access memory (SDRAM, synchronous Dynamic Random Access Memory), and, Double data rate synchronous dynamic random access memory (DDRSDRAM, double Data Rate Synchronous Dynamic Random Access Memory), enhanced synchronous dynamic random access memory (ESDRAM, enhanced Synchronous Dynamic Random Access Memory), synchronous link dynamic random access memory (SLDRAM, syncLink Dynamic Random Access Memory), direct memory bus random access memory (DRRAM, direct Rambus Random Access Memory). the memory 2 described in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.
The storage deployment method of the container orchestration engine disclosed in the above embodiments of the present application may be applied to the processor 2 or implemented by the processor 2. The processor 2 may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the storage deployment method of the container orchestration engine described above may be performed by instructions in the form of integrated logic circuits or software of hardware in the processor 2. The processor 2 described above may be a general purpose processor, DSP, or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. Processor 2 may implement or execute the storage deployment methods, steps and logic blocks of the disclosed container orchestration engines in embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the storage deployment method of the container programming engine disclosed by the embodiment of the application can be directly embodied as the execution completion of the hardware decoding processor or the combined execution completion of the hardware and software modules in the decoding processor. The software modules may be located in a storage medium located in the memory 3 and the processor 2 reads the program in the memory 3 and in combination with its hardware performs the steps of the storage deployment method of the container orchestration engine described above.
The corresponding flow in the storage deployment method of each container orchestration engine according to the embodiments of the present application is implemented when the processor 2 executes the program, and is not described herein for brevity.
In an exemplary embodiment, the present application also provides a storage medium, i.e. a computer storage medium, in particular a computer readable storage medium, for example comprising a memory 3 storing a computer program executable by the processor 2 for performing the steps of the storage deployment method of the aforementioned container orchestration engine. The computer readable storage medium may be FRAM, ROM, PROM, EPROM, EEPROM, flash Memory, magnetic surface Memory, optical disk, or CD-ROM.
In several embodiments provided by the present application, it should be understood that the disclosed apparatus, terminal, and storage deployment method of the container orchestration engine may be implemented in other ways. The above described device embodiments are only illustrative, e.g. the division of the units is only one logical function division, and there may be other divisions in practice, such as: multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. In addition, the various components shown or discussed may be coupled or directly coupled or communicatively coupled to each other via some interface, whether indirectly coupled or communicatively coupled to devices or units, whether electrically, mechanically, or otherwise.
The units described as separate units may or may not be physically separate, and units displayed 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 each embodiment of the present application may be integrated in one processing unit, or each unit may be separately used as one unit, or two or more units may be integrated in one unit; the integrated units may be implemented in hardware or in hardware plus software functional units.
Those of ordinary skill in the art will appreciate that: all or part of the steps of implementing the storage deployment method embodiment of the container orchestration engine described above may be performed by hardware associated with program instructions, where the program described above may be stored on a computer-readable storage medium, which when executed, performs the steps of the storage deployment method embodiment comprising the container orchestration engine described above; and the aforementioned storage medium includes: a removable storage device, ROM, RAM, magnetic or optical disk, or other medium capable of storing program code.
Or the above-described integrated units of the application may be stored in a computer-readable storage medium if implemented in the form of software functional modules and sold or used as separate products. Based on such understanding, the technical solution of the embodiments of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium, comprising several instructions for causing a storage deployment device (which may be a personal computer, a server, or a network device, etc.) of a container orchestration engine to perform all or part of the storage deployment method of the container orchestration engine according to the embodiments of the present application. And the aforementioned storage medium includes: a removable storage device, ROM, RAM, magnetic or optical disk, or other medium capable of storing program code.
The storage deployment equipment of the container arrangement engine firstly installs and operates the container arrangement engine in a physical server, configures and operates a storage system based on the physical server, further creates a storage volume in the storage system, and establishes a mounting relation between a data volume and a container group in the container arrangement engine. The device configures the storage system in the physical server, and establishes the mounting relation between the storage volume in the storage system and the container group in the container arrangement engine, so that the containers in the container group can read and write data on the storage volume in the storage system based on the mounting relation, and further, the use of storage resources in the physical server by the container arrangement engine is realized.
In addition, the embodiment of the application also discloses a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program realizes the steps of the storage deployment method of the container arrangement engine when being executed by a processor.
The application provides a computer readable storage medium, which is characterized in that firstly, a container arrangement engine is installed and operated in a physical server, a storage system is configured and operated based on the physical server, then a storage volume is created in the storage system, and the mounting relation between a data volume and a container group in the container arrangement engine is established. The computer readable storage medium is characterized in that a storage system is configured in a physical server, and a mounting relation between a storage volume in the storage system and a container group in a container arrangement engine is established, so that a container in the container group can read and write data on the storage volume in the storage system based on the mounting relation, and further, the use of storage resources in the physical server by the container arrangement engine is realized.
The storage deployment method, the device, the equipment and the storage medium of the container programming engine provided by the application are described in detail. In the description, each embodiment is described in a progressive manner, and each embodiment is mainly described by the differences from other embodiments, so that the same similar parts among the embodiments are mutually referred. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section. It should be noted that it will be apparent to those skilled in the art that various modifications and adaptations of the application can be made without departing from the principles of the application and these modifications and adaptations are intended to be within the scope of the application as defined in the following claims.
It should also be noted that in this specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
Claims (7)
1. A storage deployment method of a container orchestration engine, comprising:
installing and running a container orchestration engine in a physical server;
configuring and operating a storage system based on the physical server;
Creating a storage volume in the storage system;
establishing a mounting relationship between the storage volume and a container group in the container arrangement engine;
Wherein the configuring and operating a storage system based on the physical server includes:
Deploying the storage system in the physical service;
Mounting a physical disk in the physical server to the storage system;
operating the storage system on which the physical disk is mounted;
The number of the physical servers is greater than 1;
Accordingly, the deploying the storage system in the physical service includes:
Installing the storage system in each of the physical servers;
establishing a distributed data synchronization relationship of the storage system among the physical servers;
the mounting the physical disk in the physical server to the storage system includes:
And mounting the physical disk to the storage system in a manner of transmitting the physical address of the physical disk in the physical server to the storage system.
2. The storage deployment method of the container orchestration engine according to claim 1, wherein the establishing a mount relationship of the storage volumes to groups of containers in the container orchestration engine comprises:
The mounting relationship of the storage volumes to the set of containers in the container orchestration engine is established based on a storage class corresponding to the container orchestration engine.
3. The storage deployment method of a container orchestration engine according to claim 1 or 2, wherein the container orchestration engine comprises a Kubernetes engine, and the group of containers comprises a group of pod containers.
4. A storage deployment method of a container orchestration engine according to claim 3, wherein the configuring and running a storage system based on the physical server comprises:
the storage system is operated based on the physical server configuration and through DaemonSet.
5. A storage deployment apparatus of a container orchestration engine, comprising:
A container engine operation module for installing and operating a container orchestration engine in a physical server;
The storage system operation module is used for configuring and operating the storage system based on the physical server;
a storage volume creation module for creating a storage volume in the storage system;
The container group mounting module is used for establishing a mounting relation between the storage volume and a container group in the container arrangement engine;
The storage system operation module is specifically configured to deploy the storage system in the physical service; mounting a physical disk in the physical server to the storage system; operating the storage system on which the physical disk is mounted;
The number of the physical servers is greater than 1;
correspondingly, the storage system operation module is specifically configured to install the storage system in each physical server; establishing a distributed data synchronization relationship of the storage system among the physical servers;
The storage system operation module is specifically configured to mount the physical disk to the storage system by transmitting a physical address of the physical disk in the physical server to the storage system.
6. A storage deployment device of a container orchestration engine, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the storage deployment method of the container orchestration engine according to any one of claims 1 to 4 when executing the computer program.
7. A computer readable storage medium, characterized in that it has stored thereon a computer program which, when executed by a processor, implements the steps of the storage deployment method of the container orchestration engine according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011572978.7A CN112579008B (en) | 2020-12-24 | 2020-12-24 | Storage deployment method, device and equipment of container orchestration engine and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011572978.7A CN112579008B (en) | 2020-12-24 | 2020-12-24 | Storage deployment method, device and equipment of container orchestration engine and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112579008A CN112579008A (en) | 2021-03-30 |
| CN112579008B true CN112579008B (en) | 2024-07-09 |
Family
ID=75139964
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011572978.7A Active CN112579008B (en) | 2020-12-24 | 2020-12-24 | Storage deployment method, device and equipment of container orchestration engine and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112579008B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113672350B (en) * | 2021-08-20 | 2023-12-29 | 深信服科技股份有限公司 | Application processing method and device and related equipment |
| CN114115730B (en) * | 2021-11-02 | 2023-06-13 | 北京银盾泰安网络科技有限公司 | Application container storage engine platform |
| CN114116381B (en) * | 2021-11-12 | 2024-09-17 | 苏州浪潮智能科技有限公司 | Container-based storage system and container processing method |
| CN114281263B (en) * | 2021-12-27 | 2024-03-29 | 深圳市名竹科技有限公司 | Storage resource processing method, system and equipment of container cluster management system |
Family Cites Families (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7747835B1 (en) * | 2005-06-10 | 2010-06-29 | American Megatrends, Inc. | Method, system, and apparatus for expanding storage capacity in a data storage system |
| US8943203B1 (en) * | 2009-07-10 | 2015-01-27 | Netapp, Inc. | System and method for storage and deployment of virtual machines in a virtual server environment |
| US10649679B2 (en) * | 2016-11-23 | 2020-05-12 | Nutanix, Inc. | Containerized application extensions in distributed storage systems |
| US20180205616A1 (en) * | 2017-01-18 | 2018-07-19 | International Business Machines Corporation | Intelligent orchestration and flexible scale using containers for application deployment and elastic service |
| US10884816B2 (en) * | 2017-03-28 | 2021-01-05 | International Business Machines Corporation | Managing system resources in containers and virtual machines in a coexisting environment |
| US10601917B2 (en) * | 2017-06-27 | 2020-03-24 | Red Hat, Inc. | Containerized high-performance network storage |
| US10908999B2 (en) * | 2018-07-30 | 2021-02-02 | EMC IP Holding Company LLC | Network block device based continuous replication for Kubernetes container management systems |
| CN111104368B (en) * | 2019-12-16 | 2023-08-22 | 浪潮云信息技术股份公司 | Method and system for realizing storage capacity expansion of container |
| CN111258720A (en) * | 2020-01-19 | 2020-06-09 | 苏州浪潮智能科技有限公司 | Service arranging method, system, equipment and medium based on cloud management platform |
| CN111625317A (en) * | 2020-05-15 | 2020-09-04 | 苏州浪潮智能科技有限公司 | Container cloud construction method and related device of business system |
| CN111966305B (en) * | 2020-10-22 | 2021-02-09 | 腾讯科技（深圳）有限公司 | Persistent volume allocation method and device, computer equipment and storage medium |
-
2020
- 2020-12-24 CN CN202011572978.7A patent/CN112579008B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN112579008A (en) | 2021-03-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112579008B (en) | Storage deployment method, device and equipment of container orchestration engine and storage medium | |
| US20240283840A1 (en) | Client-directed placement of remotely-configured service instances | |
| US7725559B2 (en) | Virtual data center that allocates and manages system resources across multiple nodes | |
| US11146620B2 (en) | Systems and methods for instantiating services on top of services | |
| US7694298B2 (en) | Method and apparatus for providing virtual server blades | |
| US7257584B2 (en) | Server file management | |
| US11675499B2 (en) | Synchronous discovery logs in a fabric storage system | |
| US11520919B2 (en) | Sharing of data among containers running on virtualized operating systems | |
| US20090210875A1 (en) | Method and System for Implementing a Virtual Storage Pool in a Virtual Environment | |
| US8495323B1 (en) | Method and system of providing exclusive and secure access to virtual storage objects in a virtual machine cluster | |
| US20070061441A1 (en) | Para-virtualized computer system with I/0 server partitions that map physical host hardware for access by guest partitions | |
| US20070067366A1 (en) | Scalable partition memory mapping system | |
| US8825819B2 (en) | Mounting specified storage resources from storage area network in machine provisioning platform | |
| US10133646B1 (en) | Fault tolerance in a distributed file system | |
| US10594800B2 (en) | Platform runtime abstraction | |
| US9928056B1 (en) | Operating system update management | |
| CN111338854A (en) | Kubernetes cluster-based method and system for quickly recovering data | |
| CN102521063A (en) | Shared storage method suitable for migration and fault tolerance of virtual machine | |
| CN113504954A (en) | Method, system and medium for calling CSI LVM plug-in, dynamic persistent volume provisioning | |
| US10776173B1 (en) | Local placement of resource instances in a distributed system | |
| CN105068836A (en) | SAS (serial attached SCSI) network based remotely-shareable start-up system | |
| US9141368B2 (en) | Managing boot loaders for virtual hard disks | |
| CN111488322B (en) | File system service method and device and server equipment | |
| WO2022128296A1 (en) | Transferring an operating image into a multi-tenant environment | |
| CN107944010A (en) | The method and apparatus of reading and writing of files in a kind of distributed file system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |